Labour Costs Eating Your Margin? Smart Scheduling Saves £2,000/Month

The Tuesday problem every restaurant owner knows#

It is Tuesday at 7pm and you have six front-of-house staff on the floor. There are 14 covers. Two servers are essentially chatting near the host stand. The kitchen has four on the line for a ticket time of under 12 minutes. You are paying £540 in wages for an evening service that will generate £1,400 in revenue. Your labour ratio for that session: 38.6%. Your target was 28%. The problem is not laziness — it is that last Tuesday was a private dining event and the manager copied the rota. Without a data-led view of expected covers by hour, this keeps happening every week on the slow sessions.

What a healthy restaurant labour cost looks like#

Industry benchmarks for full-service restaurants sit at 30-35% of revenue for total labour (kitchen and front-of-house combined). Fine dining can run higher — 38-42% — but justifies it through spend per cover. Fast casual targets 25-28%. If your total labour cost is consistently above 35% on a week-on-week basis, you are eroding profit at a rate that cannot be recovered through volume alone. A £60,000-revenue restaurant running 36% labour versus 30% labour is spending £3,600 more per month on wages for the same output. That is £43,200 per year. Most of it is recoverable with better scheduling, not headcount cuts.

Why manual scheduling always overshoots#

Manual scheduling is conservative by nature. Managers schedule based on worst-case scenarios — because being understaffed on a busy night is visible and painful. Being overstaffed on a quiet night is invisible and comfortable. The result: consistent overstaffing during shoulder periods, quiet lunches, and mid-week evenings. In a 12-week audit across 40 independent restaurants, the average team was overstaffed by 1.8 FTE-equivalent hours per shift during off-peak periods. At £12/hour that is £21.60 per shift, £151.20 per week, £7,862 per year — just from overstaffing by under 2 hours per session.

How AskBiz builds demand-led schedules#

AskBiz analyses your historical POS data — covers by hour, by day, by week, by season — and generates a predicted cover curve for each upcoming day. The scheduling module maps that curve to your minimum cover-to-staff ratios (e.g., 1 FOH server per 12 covers, 1 line cook per 30 covers per hour) and generates an optimal schedule. If Tuesday evenings average 22 covers, it schedules 3 FOH instead of 6. If a bank holiday Monday historically runs 120% of a normal Monday, it flags the need for extra staff two weeks in advance. Managers still approve and adjust — but the starting point is data, not last week's rota.

Integrating with payroll: Xero and Sage Payroll#

Once the rota is approved in AskBiz, actual hours are tracked via the built-in clock-in/clock-out function. At end of week, AskBiz generates a payroll export that goes directly into Xero Payroll, Sage Payroll, or BrightPay. No manual timesheet transcription, no payroll errors from misread handwriting, no missed overtime flags. This also catches ghost hours — staff who clock out early but are paid for the full shift. On a 20-person team, this saves 3-4 hours per week in payroll admin and catches £200-500/month in payroll errors.

Before and after: a UK restaurant group#

A two-site restaurant group in Bristol was running 37.4% average labour cost across both sites. One site was at 34%, the other at 41% — the higher site had a manager who always erred on the side of overstaffing. After 8 weeks of demand-led scheduling via AskBiz, the high-cost site dropped to 33.8%. Combined group saving: £2,340/month in wage cost. The manager still made manual adjustments — for the annual beer festival, for private bookings, for public holidays — but those were layered on top of a data-driven baseline. The guesswork reduced by 80%.

Three scheduling rules that immediately reduce waste#

Rule one: never schedule more than your previous four-week average plus 20% buffer for any given session. Rule two: track labour cost as a percentage of revenue on the day, not just at month-end. If Tuesday lunch is tracking 48% labour by noon, you can send someone home before they finish the shift. Rule three: split labour reporting by kitchen and FOH — they have very different benchmarks and very different levers to pull. AskBiz shows you all three metrics in a single dashboard so you can act in the moment, not after the fact.

• Most restaurants schedule staff based on gut feel and last week's rota.
• The result: 6 staff on a quiet Tuesday costing £540 in wages for £1,200 revenue — a 45% labour ratio.
• AskBiz uses your historical sales data to predict covers by hour and generate an optimal schedule.