Restaurant Staff Management Software
One login, scoped to the role. Owners and managers work in the admin. Waiters sign in to a portal of their own — their tables, their orders, their shift.
Why it matters
Most hospitality software is written for the person who bought it. The floor gets the same screens with the parts they shouldn't see hidden, which means a waiter three minutes into a Friday is navigating an owner's tool — past settings, past suppliers, past last month's margins — to find the four things a shift actually needs.
A shared login makes it worse in the other direction. If everyone signs in as the venue, then everyone can see everything, nobody's numbers are their own, and no record of who did what survives the night. The usual fix is to give staff a tablet nobody signs out of and hope.
The answer here is two places to work rather than one place with things hidden. Owners and managers work in the admin, where the business lives — the menu, the stock, the money, the rota. The floor signs in to a portal of its own: their tables, their orders, their shift, their numbers. Nobody is navigating past anything, and nothing sensitive is one wrong tap away during service.
What a shift looks like from the inside
They claim their tables
A waiter takes the tables they are working, so every order that lands on one is credited to somebody. A shift rostered to a section starts with that section suggested, and a table nobody has claimed falls back to whoever is covering it.
Their floor, not the whole floor
Table status, the orders on them, and what is still outstanding — filtered to the section they are actually walking. The bar, the host and the kitchen are on the same shift without holding tables at all.
Ready reaches the right person
When the kitchen finishes a ticket, the waiter holding that table is told. Not a bell across the room and not a screen somebody has to remember to look at — the person who has to walk to the pass.
Handovers get written down
Shift notes against a table number: the couple on nine are waiting on a bottle, twelve are splitting the bill, the birthday cake is in the walk-in. The things that get shouted across a pass and then forgotten.
Takeovers have to say why
Claiming a table someone else was holding is legitimate — a section left uncovered, somebody going home ill — but it moves the credit for everything ordered afterwards. So it is the one claim that asks for a reason, it is logged, and the waiter who lost the table is told. Otherwise the first they know of it is a bill they cannot see.
Their own numbers, and only theirs
Covers, orders, what they sold. A waiter can see how their own shift went without anybody's reporting being opened up to the floor.
The rota, and the arguments it usually causes
Scheduling is where most of the friction between an owner and a floor actually lives, and almost none of it is about the software. It is about who asked for Saturday off, whether anybody wrote it down, and who agreed to cover the shift nobody remembers agreeing to.
Build a week, or repeat one
Shifts go on a calendar with a date, a start and an end. The ones that happen every week — Saturday brunch, Friday bar cover — are saved once and applied across a range of dates instead of being retyped.
Staff say when they can work
Each person sets the hours they are available, by day of the week. It is there when the rota is built, so "I can't do Mondays" is a fact on the screen rather than something remembered wrong a month later.
Days off get asked for and answered
A request goes in from the portal, the owner approves or declines it, and the person is told. No group chat, and no version where somebody thought it had been agreed.
Swaps need the colleague and the owner
One person asks, the colleague accepts, and it then waits for the owner to sign off — because two staff quietly rearranging a Saturday is how a section ends up with nobody on it. Everyone is notified at each step.
Shifts that don't hold tables
Bar, kitchen, host and manager cover are on the rota without being counted as floor coverage. The same person can serve on Friday and tend bar on Saturday without either shift lying about who is holding a section.
Changes reach the person
A shift assigned, moved or removed sends a notification. Turning up for a shift that was changed on Wednesday is the failure this exists to prevent.
Hiring, leaving, and working two places
Invite by email
Send an invite, they set a password, they are on the floor the same day. There is no separate training system to get through first — the portal is four screens, and one of them is a list of their tables.
The details you actually need on file
Employment basis, contracted hours, a phone number, an emergency contact. Kept per venue, kept out of everything guest-facing, and there when somebody needs it at eleven on a Saturday.
One person, several venues
Hospitality staff work in more than one place. One account can hold a position at each, and what they see changes with the venue they are in — without a second login or a second password to forget.
A profile guests can see, if they want one
A name guests can use, a photo, the languages they speak. It is off until the staff member turns it on themselves, and each field is optional — sharing a nickname and two languages without sharing a photograph is just leaving that field empty.
Common questions
How fast can a new hire start?
They accept an email invite, set a password, and can be working a shift within minutes. The portal is small on purpose — there is no course to sit through first.
Can waiters see our reporting?
No. The floor works in a separate portal, and the business reporting isn't in it. What a waiter can see is their own shift — their covers, their orders, their sales.
Can staff swap shifts without asking us?
No. A swap needs the colleague to accept it and then the owner to approve it. Both halves are recorded, and everyone involved is notified at each step.
Someone goes home ill mid-service. What happens to their tables?
Another waiter claims them. Because that moves the credit for everything ordered afterwards, a takeover asks for a reason, is logged, and the person who lost the tables is told.
Do we have to rebuild the rota every week?
No. Shifts that repeat are saved once and applied across a date range, and staff availability is on screen while you build so you aren't rostering somebody onto a day they already said they can't work.
Our staff work at two of our venues. Is that two accounts?
One. A single account can hold a position at each venue, and what they see follows the venue they're working in.
Do guests see anything about our staff?
Only if that staff member switches it on themselves, and only the fields they fill in — a name, a photo, the languages they speak. Nothing is shown by default, and employment details never are.