1 · One rota, all roles
Kitchen + FOH on one screen. Role chips — KP, CDP, sous, head chef, server, host, runner — assigned to shifts.
Kitchen and front-of-house on one rota, role-aware templates, the swap inbox that handles the chef who texts at 4pm. A working guide for independent UK restaurants who'd rather plate dinner than rebuild a spreadsheet.
Restaurant staff scheduling is the practice of building shift rotas that match the kitchen brigade and front-of-house team to forecast covers, with role-aware templates, swap-request workflows and live labour-cost percentage as takings come in. Done well, it keeps payroll inside band without leaving the chef short on a Saturday.
Done badly, it's three WhatsApp groups, a Sunday-night spreadsheet, and a manager who finds out about the no-show 20 minutes before service.
Kitchen + FOH on one screen. Role chips — KP, CDP, sous, head chef, server, host, runner — assigned to shifts.
"Friday dinner" with the standard brigade saved once, dropped on every Friday. Edit the exceptions, not the whole thing.
Last Friday's covers + this Friday's bookings + the weather = your starting point. Not last Friday alone.
Staff post swaps, role-matched colleagues see them, manager approves with one tap. The chat thread disappears.
Today's labour cost calculated from today's rota and yesterday's takings. If it's drifting, you spot it at 3pm, not at month-end.
Allergen-trained, level 2 food handler, manual handling — all sit on the staff record. Schedule the trained, not the available.
Last week's rota included Tuesday off for half the kitchen because of a wedding. Copy without checking and you'll be short a CDP next Tuesday. Templates by service-day beat copy-paste-by-week every time.
WhatsApp's fine until two people swap into the same shift and nobody told the duty manager. Swap inbox with approval workflow stops the double-book at the source.
Labour cost is a Tuesday afternoon problem. By Friday, it's structural. By month-end, it's the difference between profit and loss. Live tracking is the only way to manage it.
Then your chef's rota doesn't see the swap requests from FOH and your FOH rota doesn't see when the kitchen calls in a third KP. One rota, role chips. The chef still owns the kitchen line — they just write it in the same place.
Role chips, service-day templates, swap inbox and labour-cost % live as takings come in. Compliance and payroll export sit alongside. From £49 per restaurant per month on Essentials. Most kitchens pick Professional (£99) for shift swaps, the full compliance suite and payroll reports. The till and printed kitchen tickets are on Complete (£149), and the kitchen display screen is on Complete Plus (£199). 30-day free trial.
The practice of building shift rotas that match the brigade and FOH team to forecast covers, with role-aware templates, swap workflows and live labour-cost %.
Most independents target 25–32% labour cost vs net sales. The number that matters is the trend against your own previous quarter, not an industry benchmark.
No. One rota with role chips covers both. Splitting tools doubles admin and breaks swap workflows.
Tronc is handled by your payroll provider on top of the rota's timesheet. Hospitality App exports the timesheet CSV ready for any UK payroll provider.
Our free kitchen and front-of-house rota template puts both halves of the building on the same week, so the labour figure includes everybody. Split shifts work properly, prep gets its own rows, and the rest check reads a lunch and a dinner shift as one working day.
Sign up free, build a Friday-dinner template, post a swap request, watch labour % update. If it doesn't earn its keep by Sunday, walk away.
Start free trial