Plan restaurant staff schedules around demand
Build shifts from forecast covers, station skills, and paid hours. Check a worked schedule and review cost alongside service quality.
A flat schedule carries quiet-hour cost into every service and can leave peak hours short. Split opening preparation, the peak, and closing work. Record which roles need a trained person, who can move between stations, and when breaks occur. A busy Friday is not a useful baseline for Tuesday lunch. Keep forecast covers, planned hours, actual covers, and worked hours together so the manager can tell a forecasting error from a scheduling error. A cheaper schedule that increases wait times or creates overtime is not an improvement.
Controls to put in writing
- Demand: use recent comparable services, bookings, and events; record the forecast and its assumptions.
- Skills: map each station to trained employees; assign relief for breaks and absence.
- Hours: include preparation, service, cleaning, and closing rather than hiding these outside the schedule.
- Review: compare covers per paid hour, overtime, ticket times, and guest complaints on the same services.
A worked example
At a loaded cost of €15 per paid hour, the restaurant tests staggered starts on quiet services. The cover forecast stays at 600 per week.
| Week 1 | 320 hours; €4,800 | Baseline: 600 covers, 1.88 covers per hour. |
|---|---|---|
| Week 2 | 340 hours; €5,100 | The manager finds 20 hours of early starts with little demand. |
| Week 3 | 320 hours; €4,800 | Staggered starts remove those 20 hours and save €300 against week 2. |
| Week 4 | 318 hours; €4,770 | Keep the plan only if station coverage, breaks, and ticket times hold. |
At 600 covers, 318 hours gives 1.89 covers per hour. The €330 saving against week 2 is measurable; it does not justify leaving a critical station uncovered.
A practical operating process
- 1Forecast each service. Use four comparable weeks and current bookings. Mark events and exceptional services separately.
- 2Build the station plan. Allocate preparation, peak, break relief, and closing hours. Check availability and agreed working conditions before publishing.
- 3Record the actual shift. The lead records attendance, worked hours, overtime, and service problems. Explain changes while the reason is fresh.
- 4Review after seven days. Compare planned and actual hours with demand and service. Keep, revise, or reverse the change after four weeks.
FAQ
- How early should I publish the schedule?
- Set a stable notice period that meets applicable requirements and gives staff time to plan. Make urgent changes explicit and confirm them with affected staff.
- Can one person cover two stations?
- Only where their training and the expected workload allow it. Write down which station they own during the peak and who covers breaks.
- What if actual covers exceed the forecast?
- Use an agreed call-in or station-transfer plan. Record the extra hours and update the next forecast instead of treating overtime as unexplained drift.
- Which measure shows whether a change worked?
- Use paid hours and cost alongside covers per hour, ticket times, and complaints. A reduction in hours alone does not show a better schedule.
Keep reading
- Labor cost management: the percentage that decides whether your kitchen pays for itself
What labor cost percentage actually measures, target ranges by concept, and how to control it without bleeding service quality.
- Payroll as a percentage of restaurant revenue: targets and controls
Calculate payroll percentage on a consistent revenue period, separate its drivers, and use a four-week example to check corrective action.
- Calculate the cost of restaurant staff turnover
Add recruitment, vacancy cover, training, and early mistakes to calculate replacement cost. Track departures and test a specific retention action.
Browse by category
Want to review your purchasing?
Submit the details and we will confirm which invoices are useful.
Review 3 invoices free