How to Build a Schedule That Doesn't Blow Your Labor Percentage
Share
One overstaffed Tuesday can cost you $520 in labor you never needed. Schedule two extra bodies for a shift that turns out to be a normal Tuesday, not the private event you were bracing for, and you've paid for hours that produced nothing but idle time at the host stand. Do that once a week for a quarter and you've spent $6,760 covering for a schedule that was never built around actual demand.
The Schedule Is Where Labor Cost Gets Decided
By the time payroll runs, the labor percentage is already locked in. The only point where you can actually control that number is before the week starts, when you're deciding who works which shift. A schedule built around last week's habit instead of this week's forecast is a schedule built to miss. If you haven't locked your concept's target yet, start with "What Percentage Should Labor Cost Be? Benchmarks by Concept, Not the Industry Average", everything below assumes you already know your number.
Start With the Sales Forecast, Not the Roster
Most schedules get built backward, pull up last week's schedule, copy it, make small tweaks. That approach bakes in every overstaffing mistake from the previous week and compounds it. Build the schedule from a sales forecast instead: look at the same day last year, the same day last month, and anything unusual happening this week, a holiday, a local event, weather, and staff to that number, not to habit.
Labor Hours per Projected Sales Dollar
The fastest way to catch overstaffing before it happens is to know your labor hours per $1,000 in projected sales, by shift, for your specific concept.
| Concept | Target Labor % of Sales | Approx. Labor Hours per $1,000 in Sales |
|---|---|---|
| FSR | 30–35% | 16–19 hours |
| QSR | 25–30% | 13–16 hours |
| Bar-Forward | 22–28% | 11–14 hours |
| Catering | 18–24% | 9–12 hours |
If a $10,000 sales day for an FSR calls for roughly 160–190 labor hours and the schedule as built runs 210 hours, that's 20–50 hours of labor scheduled beyond target, at a blended $19/hour wage, that's $380 to $950 in labor cost baked into the schedule before a single guest walks in the door.
Build in Blocks, Not Whole Shifts
Peak-hour staffing and shoulder-hour staffing are different problems. Scheduling one server for a full 5pm–close shift when the real rush is 6:30–8:30 means you're paying for two and a half hours of standing around before the rush and an hour after it dies down. Staggered start and end times matched to the actual sales curve, not the convenience of a clean shift block, is where a lot of the excess hours in the table above actually live.
The Worked Number
Take an FSR with a 32% labor target on a projected $8,500 Saturday. Target payroll: $2,720. The manager schedules based on last month's busier Saturday instead of this week's actual forecast and books $3,240 in payroll, a $520 miss for one night. Run that same overstaffing pattern on both weekend nights for 13 weeks and it's $13,520 in labor spent on a forecast that was never checked against this week's actual numbers.
Review Against Actuals Every Week
A schedule is a forecast, and forecasts need to get checked against what actually happened. Compare scheduled hours to clocked hours and scheduled sales to actual sales every week, and adjust the next week's schedule based on the gap, not based on gut feel about whether it "felt busy."
- Build the schedule from a sales forecast, not last week's roster
- Know your target labor hours per $1,000 in sales, by concept
- Stagger shift starts and ends to match the actual sales curve, not clean shift blocks
- Compare scheduled vs. actual every week and adjust the next one
Once the schedule is built right, the next leak to watch is overtime creeping in mid-week, see "The Overtime Mistake That Costs a Restaurant Manager Thousands a Year" for how that happens even on a well-built schedule.
For the full labor cost picture this pillar covers, start with "The Restaurant Labor Cost Playbook".
Catching a schedule that's about to run over target means checking the number before the week ends, not after. The Daily KPI Tracker Pro tracks labor cost against your concept's target every day, so an overstaffed Tuesday gets caught on Tuesday. See the Daily KPI Tracker Pro.