Build the rota once. Publish it when it is real.
Shifts, availability, time off, new-starter inductions, certificates 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
- Pro plan and above
What it does
Build the rota, publish it once, and know who did what on the floor.
- Draft, then publishA 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 notedPeople 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 blocksApproving 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 repeatSave 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 managerStaff see their own schedule, request time off and set their availability, without reaching anything else in the venue.
- Who did whatRefunds, 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 deviceOne 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 tabletThe 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 ownThe 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.
- A new starter, inducted on one screenYour staff pack becomes a checklist: the handbook, the forms, fire exits, the till. You tick what you showed them, they tick what they were given — on their own phone, or with their PIN on your tablet — and you both confirm at the end. Every tick carries who made it and when.
- Certificates that warn you firstFood hygiene, first aid, a personal licence: the dates off the certificate and a private scan of it. You and the holder hear a month before it runs out, and again if it does — not when someone asks to see it.
- Training and skills, per personWhat each person was trained on, when, and by whom, with a refresher date if it needs one — and who can run the cellar, the till or the cocktail list, marked learning, competent or able to train others.
- Next of kin you can find at eleven at nightEmergency contacts, date of birth and address on each person’s record. Staff keep their own up to date from their phone, and nothing changes until a manager approves it. On every plan.
How it runs · in order
From the first step to the last.
- Mon 10:00You build the weekAgainst the covers already in the diary rather than a guess. Conflicts surface as you place a shift, not at publish.
- Mon 10:40You publish itOne action turns a draft into a commitment, and everybody rostered hears about it once.
- Wed 18:20Something changesA time-off request lands. Approving it writes the exception that stops next Saturday being scheduled over it.
- Fri 16:58The shift startsOne six-digit PIN at the tablet by the door and the hours are being counted. A manager can see who else is already on, which is the question that produces a double clock-in.
- Fri 19:02On the floorA refund is taken at the till under a PIN, stamped with who took it, and it is on the activity log before service ends.
The floor, fully staffedFri 20:30
What changes
Tonight, versus tonight with it on.
- Now: The rota is a spreadsheet screenshotted into a group chat.
- With AtTable: A published week each person can see — and only once it is final.
- Now: Approved leave gets scheduled over, because two systems disagree.
- With AtTable: Approving the leave is what blocks the shift. One record, one answer.
- Now: “Who comped that?” has no answer by Monday.
- With AtTable: Every refund, void and comp carries the person who made it.
- Now: Next week is staffed without knowing how busy Saturday is.
- With AtTable: Built beside the diary, on the same login as the bookings.
- Now: Hours live in a paper book by the door and get typed up on Sunday.
- With AtTable: Clocked at the tablet, on the timesheet as they happen.
- Now: The new-starter pack is a form in a folder, and nobody checks a certificate’s date until it has passed.
- With AtTable: A checklist you both confirm, and a reminder a month before a certificate runs out.
Where it sits
Team & shifts is part of team & shifts.
It runs on the same menu, the same tables and the same bill as everything else — nothing to integrate, nothing to reconcile.
Ordering
Take the order at the table, the counter or the kerb, and get it to the kitchen.
Revenue & insights
See all twenty features Know what sold, what almost sold, and what caused the difference.
Start here
Put next week on it.
Add your people, set their availability and build one week. Rota, clock-in, timesheets, inductions and certificates come with Pro and above; next of kin is on every plan.
45 days to go live · 21 days free once you're live · No card required · No minimum term