What does it mean to schedule staff to match demand?
It means building every week's schedule from actual sales data by day and daypart instead of repeating last week's template.
Most restaurant schedules are built on memory. Tuesday has always been a light day, so it gets the same four people it got last month and the month before that. Saturday has always been busy, so it gets seven people, plus maybe an extra server if someone remembers to add one. The schedule is not built from the business. It is copied from habit.
Matching staff to demand reverses that order. The schedule starts with what the sales data says a shift will actually do in revenue, then works backward to how many labor hours that revenue can support, and only then assigns people to fill those hours. The business sets the staffing level. The calendar does not.
Why do most restaurant schedules waste labor spend?
The average restaurant wastes 8-12% of labor spend because people are scheduled by routine rather than by when customers actually show up.
That gap is not about anyone being overpaid. It is about staff being in the building at times when there is not enough revenue to justify them being there, and understaffed at the times when revenue is highest. On a $1.5M restaurant running a 30% labor cost, that 8-12% works out to $36,000 to $54,000 a year sitting inside a schedule that nobody has rebuilt from data.
Sales patterns are not static. They move with the season, the weather, local events, and the slow drift of a neighborhood's habits. A schedule built once and reused every week cannot track any of that. A schedule rebuilt from the last four weeks of sales can.
How do you calculate the maximum labor hours for a shift?
Divide the shift's expected sales by the target sales per labor hour to get the maximum number of labor hours that shift can support.
The metric that connects scheduling to profitability is Sales Per Labor Hour, or SPLH. The formula for staffing is simple: expected sales divided by target SPLH equals maximum labor hours.
Here is how it plays out on a real shift. Tuesday dinner at a given restaurant averages $3,400 over the last four weeks. The target SPLH is $45. Maximum labor hours for that shift is $3,400 divided by $45, which comes out to 75.6 hours. If the dinner shift runs six hours, that is approximately 12 to 13 people on the floor and in the kitchen, not whatever number has historically been scheduled.
Compare that to Tuesday lunch at the same restaurant, which averages $1,800. The same math produces a much smaller crew for lunch. Staffing lunch and dinner identically, which is what most schedules do, means one of those two shifts is wrong every single day.
Results are not typical and will vary with your business, your market, your team and how much of the work you actually do. Client figures on this site come from recorded interviews and are dated. Nothing here is a guarantee of revenue, profit or growth.
What is target SPLH and how is it set?
Target SPLH is the sales volume each labor hour needs to generate, and it varies by service model.
| Service model | Target SPLH range |
|---|---|
| Full-service | $35-$50 per labor hour |
| Fast-casual | $45-$65 per labor hour |
| QSR | $55-$80 per labor hour |
Once a target SPLH is set, every scheduling decision has a ceiling. A shift does not get more labor hours than its expected sales can support, no matter how the team has always done it. For a deeper breakdown of how to set and track this number, see sales per labor hour benchmarks.
What mistakes cause a schedule to drift from demand?
The three most common mistakes are scheduling to who is available instead of what the business needs, reusing the same schedule every week, and failing to scale labor for day-of-week swings in revenue.
- Scheduling to availability, not demand: building the roster around who is free instead of what the shift's sales require guarantees misalignment.
- Running the same schedule every week: copy-pasting last week's template is static scheduling by definition, and sales patterns do not stay still.
- Not adjusting for day-of-week variance: a Saturday that does several times the revenue of a Tuesday needs proportionally more labor, not the same template with one extra server added on.
“One of our Founders Board members runs a hand roll bar concept. He had been distributing 70 labor hours per day to his team, against a goal of 61.5 hours. That mismatch, 8.5 excess hours per day, was showing up as a failing score on his own internal report. Never start with people. Always start with metrics.”
The fix in that case was the same fix that applies anywhere: decide the metric first, then build the roster to fit it. Think of it the way a coach builds a roster, deciding how many games the team needs to win before deciding who plays, not the other way around.
How do you know if the new schedule is working?
Compare scheduled hours against actual hours worked, and actual sales against projected sales, at the end of every week.
After each week closes, three comparisons tell the whole story: scheduled hours versus actual hours worked, actual sales versus projected sales, and actual SPLH versus target SPLH. Each week's results sharpen the next week's forecast. This is a feedback loop, not a one-time fix. The schedule gets rebuilt from fresh data every week, not reused.
This is one piece of the operating system that Founders Board members get a licence to run their restaurants on, alongside the metrics that connect labor, sales, and profit. Owners who want a coach to walk through their own numbers can apply here.
What results have operators seen from running their restaurant on real numbers?
Operators who rebuild their operations around real metrics, scheduling included, report fewer hours spent inside the business and clearer financial control.
Pizza Pizzazz installed KPIs on every line of its P&L within 90 days, which is the same discipline that makes a sales-driven schedule possible. Read the full account in the Pizza Pizzazz case study.
