Break compliance is one of those things that sounds simple until you are running a Tuesday lunch peak with 14 Team Members and four position rotations. Then it becomes a quiet labor risk.
The Leader toggles Break Manager on. The roster reorders by break-due-time. Each card shows the Team Member, their shift hours, a 30-minute break duration block, and a stopwatch icon showing time-since-last-break-window-opened. The Leader sees who is overdue at a glance, taps the card, and sends them.
Most workforce-management mobile UIs are responsive translations of the desktop view. Break Manager was designed mobile-first because that is where it lives: the Director's apron during lunch peak. The cards are sized for one-thumb operation; the contrast is built for fluorescent kitchen lighting.
Every position. The roster reorders by break-due-time across all positions in the layout, so the Leader sees who is next regardless of whether they're on FOH, BOH, Drive-Thru, or Dining Room.
No. The Leader taps the Team Member's card to confirm. Auto-sending breaks during peak is too risky; the Leader is in the best position to judge whether the Drive-Thru can absorb a 30-minute gap right now.
Yes, on the Mobile Dashboard. The request shows up as a chip on the Leader's Break Manager screen with the elapsed-time stopwatch. The Leader confirms or defers.
OneClick surfaces the warnings in real-time but does not block the Leader. The labor-law layer of truth lives in HotSchedules and the time clock; OneClick treats those as the source of record and only flags when a break is overdue against the displayed shift hours.