Build the rota once. Publish it when it is real.
Shifts, availability, time off and who did what on the floor — on the same login as the bookings and the till. A week is built against the covers you have already taken, not against a blank grid.
- Draft the week privately
- Leave that blocks a shift
- On every plan
What it does
Build the rota, publish it once, and know who did what on the floor.
- Draft, then publish
- A week in draft is invisible to staff, because a rota people plan their lives around must not change under them between Tuesday and Thursday. Publishing is one deliberate action, and it is where the notifications batch — not one per cell you edited.
- Availability that is enforced, not noted
- People set the hours they can work, with exceptions for a one-off. A blocking conflict stops the shift being placed rather than warning about it after the week has gone out.
- Time off that actually blocks
- Approving leave writes the availability exceptions the conflict check reads. A request that shows as approved and still gets scheduled over is precisely the failure this is built to make impossible.
- Templates for the weeks that repeat
- Save a week you run often and apply it to another. A day that already has shifts on it is skipped rather than doubled up.
- A screen for the person, not just the manager
- Staff see their own schedule, request time off and set their availability, without reaching anything else in the venue.
- Who did what
- Refunds, voids, comps and discounts carry the member of staff who made them. “Who comped table nine?” becomes a question with an answer on Monday morning.
- A PIN at the shared device
- One tablet on the pass and several people using it. A short PIN attaches the action to the person without logging anybody out mid-service.
- Clocking in on the same tablet
- The same PIN clocks somebody in and out, so the till you already have becomes the clock — or a spare tablet by the staff door does. The screen hands itself back after each punch, because a terminal still showing the last person is one where the next person clocks in as them.
- Hours that become a timesheet on their own
- The week builds itself from the punches, with the hours per person and a queue of the days that need a human — a missed clock-out, two clock-ins in a row. Nothing is invented to fill a gap: an incomplete day is flagged rather than guessed at, because these minutes end up on a payslip.
How it runs
In order
- Mon 10:00
You build the week
Against the covers already in the diary rather than a guess. Conflicts surface as you place a shift, not at publish.
- Mon 10:40
You publish it
One action turns a draft into a commitment, and everybody rostered hears about it once.
- Wed 18:20
Something changes
A time-off request lands. Approving it writes the exception that stops next Saturday being scheduled over it.
- Fri 16:58
The shift starts
Two taps at the tablet by the door — a name and a PIN — and the hours are being counted. The board says who else is already on, which is the question that produces a double clock-in.
- Fri 19:02
On the floor
A refund is taken at the till under a PIN, stamped with who took it, and it is on the activity log before service ends.
What changes
Tonight, versus tonight with it on
- The rota is a spreadsheet screenshotted into a group chat.
- A published week each person can see — and only once it is final.
- Approved leave gets scheduled over, because two systems disagree.
- Approving the leave is what blocks the shift. One record, one answer.
- “Who comped that?” has no answer by Monday.
- Every refund, void and comp carries the person who made it.
- Next week is staffed without knowing how busy Saturday is.
- Built beside the diary, on the same login as the bookings.
- Hours live in a paper book by the door and get typed up on Sunday.
- Clocked at the tablet, on the timesheet as they happen.
Where it sits
One system, five pillars
Team & shifts is part of team & shifts.
Build the rota, publish it once, and know who did what on the floor. It runs on the same menu, the same tables and the same bill as everything else here — nothing to integrate, nothing to reconcile.
Fill the diary — and give a forgotten table a chance to be sold again.
Bookings & events
Take the order at the table, the counter or the kerb, and get it to the kitchen.
QR ordering · Digital menus · Live orders · Kitchen display · Guest payments · Dish recommendations · Sage AI waiter
Know what sold, what almost sold, and what caused the difference.
Dish reviews · Revenue & attribution · Analytics · AI insights · Guest intelligence · Automated messaging · Experiments · Discounts & promotions · Campaigns
Cost the menu on what you are actually paying for the food.
Stock & purchase orders
Compare what you ordered, what arrived, and what you were billed for.
Supplier control