Shift Scheduling Rules-of-Thumb and Quick Templates

Welcome — schedule smarter, not harder

Good schedules match real demand while keeping people fresh and payroll controlled. This guide gives compact, practical rules of thumb you can apply quickly: role-based coverage ratios, buffer and overtime triggers, cross‑training guidelines, recommended shift lengths and breaks, and four short templates you can copy and adapt for your restaurant.

How to use these rules

Treat every number below as a starting point. Use your POS and historical covers to set realistic forecasts, then adapt the heuristics to your menu complexity, service style, and local pace. After scheduling, track actual covers and labor minutes to refine your local norms.

Core heuristics (quick reference)

• Server coverage (dine-in): brunch 12–18 covers per server per shift; weekday lunch 18–25; dinner 12–18 (dinner often needs more hands for plates, drinks, upsells).
• Bartenders: 1 bartender per 60–120 covers depending on cocktail complexity and bar traffic; add 1 for busy cocktail events.
• Bussers/runners: 1 per 3–5 servers for table turn and clearing during peaks; 1 per 6–10 servers off-peak.
• Line cooks: estimate by stations, not just covers. As a rule: 1 cook per 40–60 covers for a simple menu; 1 per 25–40 covers for complex/ingredient-heavy menus. Always include an expo/finish cook during peaks.
• Prep and dishwashing: schedule 1 prep for every 2–3 line cooks (or more if prep backlog exists). Dishwashing: 1 full-time per busy dinner shift; 1 part-timer for lunch or low-volume nights.
• Float/cross-train: have at least 1 float who can cover host/server/buss duties per every 3–5 sections during busy weekend periods.
• Shift lengths: partial peak shifts 4–6 hours; full shifts 7–8 hours (include required breaks). Avoid scheduling multiple back‑to‑back long shifts for the same person in consecutive days when possible.
• Call-off buffer: add 10–20% extra headcount for peak periods (weekend dinner, brunch) and 5–10% for predictable weekday peaks; use on-call or flexible shifts rather than pushing overtime.
• Overtime trigger: flag any employee scheduled over 40 hours weekly or when scheduled hours exceed budgeted hours by more than 8–10%—rework shifts before publishing.

Simple conversion: covers → labor minutes → positions

When you have a covers forecast, use this method to convert to staffing needs:

1. Choose a target Labor Minutes per Cover (LMC) based on service style: fast-casual 8–12 LMC; full-service lunch 12–18; full-service dinner 15–25.
2. Multiply: Total labor minutes = Forecasted covers × LMC.
3. Convert to hours: Total labor hours = Total labor minutes ÷ 60.
4. Decide average scheduled shift length (paid time on clock, minus unpaid break). Example: typical server shift = 5.5 hours paid availability.
5. Positions needed = Total labor hours ÷ average scheduled shift length. Apply role splits (FOH vs BOH) according to your historical ratios (typical split 40–55% FOH / 45–60% BOH depending on service).
6. Apply buffer (10–20% at peak). Round up partial positions to ensure coverage for service flow.

Example: forecast 120 covers for dinner, choose LMC = 18 (full-service dinner). Total minutes = 120 × 18 = 2,160 → 36 hours. If average server shift is 6 hours, you need 6 server-shifts (36 ÷ 6 = 6). Apply a 15% buffer → schedule ~7 server shifts. Then split cooks: if BOH is ~55% of labor, BOH hours = 19.8 (55% of 36) → with 6-hour cook shifts that's ~3.3 → schedule 4 cooks (including expo) for the shift.

Templates — copy and adapt

Practical scheduling checklist

• Use recent POS covers by daypart to set the forecast for each shift.
• Choose a reasonable LMC for each daypart and compute total labor minutes.
• Allocate FOH/BOH split based on your business model, then convert to shifts using average shift length.
• Add the call-off buffer and review total labor against your labor budget; iterate.
• Flag and rework schedules that produce overtime or excessive idle hours.
• Publish schedules with clear start/finish times and break expectations. Keep shift start times consistent when possible to reduce confusion.
• After service, record actual covers and labor minutes to refine LMC and server productivity targets.

Common mistakes to avoid

• Scheduling only by headcount without converting to labor minutes — this hides true workload differences between menu types.
• Using national averages without adjusting for menu complexity, table turnover, or service style.
• Relying on single-person coverage plans for predictable peaks (no float or backup).
• Pushing too many long shifts without rest — harms morale and increases mistakes during peak.

Next steps and experimenting

Try these steps for one week: pick a typical daypart, forecast covers, compute LMC, produce a schedule using the templates above, track actuals, and adjust LMC and buffer next week. Over 4–6 weeks you'll converge on reliable local rules.

Want an interactive calculator or a shared template your team can use and save? Consider turning this guide into a small toolkit with a covers-to-staff calculator, editable templates per location, and a schedule submission form so shifts become a living dataset for continuous improvement.