Module: Rota
Live ticker, over-budget guard, four views.
The formula, the UK hospitality benchmarks, the green / amber / red banding — and why a rota that shows the running £ and % as you drag is the difference between running the number and being run by it.
Labour cost divided by sales, times a hundred. Two figures, one ratio. What matters is the definitions.
Labour cost is the total wage bill for the period. Hours worked × hourly rate for every worker on shift, summed. If you want a fully-loaded figure (recommended), add employer NIC (13.8% on earnings above the secondary threshold) and pension contributions (3% minimum under auto-enrolment for eligible workers).
Sales is gross takings for the same period, excluding VAT. VAT is not yours — it's held for HMRC. Including it inflates the denominator and flatters the ratio by around 17%. Most operators run their labour % against net sales.
Period matters. Daily gives you spikes and troughs that mean little. Weekly is the sweet spot for operational decisions. Monthly matches the accountant's view but is too slow to change anything.
Rough ranges for a single-venue independent, gross labour to net sales. Add 2–4 percentage points if you're loading employer NIC and pension into the labour figure.
| Venue type | Healthy range | Notes |
|---|---|---|
| Wet-led pub | 22–28% | Lower because drinks are self-service in pattern |
| Food-led pub / gastropub | 28–34% | Kitchen brigade + FOH |
| Casual dining restaurant | 26–32% | Section-service model, table turns matter |
| Fine dining restaurant | 30–38% | Higher labour per cover; usually paired with higher GP% |
| Café / coffee shop | 25–32% | Small team; owner hours often uncounted |
| Cocktail bar | 24–30% | Skilled labour, higher spend per cover |
| Hotel F&B | 28–35% | Multi-department; breakfast + service |
These are benchmarks, not targets. A wet-led pub running at 30% has an obvious problem to solve; a fine-dining restaurant running at 32% might be perfectly healthy. Target-set within your own trading pattern, not against a table.
Once you've set your target, run the actual against it in three bands. This is the model Hospitality App uses on the Owner Today card:
On publish, the rota's over-budget guard should raise a confirmation dialog if you're publishing a week that will break the red band against expected takings. A deliberate speed bump on the single most expensive mistake in the business.
Most operators calculate labour % after the week is over, when the wages have been run and the takings tallied. By then, the mistakes are baked in. A rota with a live labour-cost ticker — running £ and % updating as you drag shifts onto the week — moves the conversation forward by seven days.
The number that matters isn't last week's actual; it's this week's forecast against target, while there's still time to change it. Add a shift to Saturday, watch the £ tick up by £128 and the % by 0.4pp. Remove Sunday evening's second bartender, watch it drop. Publish when the forecast is where you want it.
Live doesn't replace the post-hoc report — you still need Labour tab in Insights to see planned-vs-actual variance week over week. But live is what stops the report being bad news.
Three places:
All three read from the same source: hourly rates on the staff record, hours from the rota (planned) or clock (actual), takings from the till (auto-recorded) or manual daily takings entry.
Live ticker, over-budget guard, four views.
Owner Today, Flash P&L, Insights.
The daily number that decides the week.
Sign up free, set your labour target, drag shifts onto the week and watch the ticker. If it doesn't change how you build a rota, walk away.
Start free trial See pricing