How to Write a Restaurant Employee Schedule That Actually Works
Last updated: April 24, 2026
A restaurant schedule that actually works starts with projected sales volume, not with employee availability. You build backwards from what you expect to do in revenue — using your POS data from the same day and week in previous years — then staff to that volume using defined coverage ratios. Everything else is adjustments. If you're building schedules the other way around, filling in shifts based on who's available and who asked for time off, you're scheduling blind, and your labor cost will prove it. For most full-service restaurants, labor cost should run 30–35% of revenue. Fast casual and QSR targets sit closer to 25–30%. Rezku's 2026 labor cost data puts median labor costs for full-service operators at 36.5% — and the profitable ones at 34.2%. That 2.3-point gap is worth roughly $2,300/month on a restaurant doing $100K/month in sales. Scheduling is where most of that difference is won or lost. The specific fix: pull the last four weeks of sales data for each shift you're scheduling. Calculate your average cover count and revenue by daypart.
Set coverage ratios for your concept (more on those below). Build the schedule to those numbers. Then do one pass for time-off requests, availability, and overtime risks. That's the order of operations. It sounds basic because it is — the problem is most operators don't actually do it in this sequence. This post covers the full process: why most schedules fail before they're even published, how to build a sales-based schedule step by step, coverage standards by concept type, what predictive scheduling laws mean for your operation, and how cross-training changes the entire math on labor.
How do you write a restaurant employee schedule that works?
Start with projected sales volume from your POS data (same day/week, prior periods), not with staff availability. Assign coverage based on defined ratios for your concept type. Check for overtime exposure, time-off conflicts, and opening/closing coverage last. Publish at least two weeks in advance. This sequence keeps labor cost predictable instead of reactive.
Why Most Restaurant Schedules Don't Work
The failure isn't usually the schedule itself — it's the process that produced it. Here's what goes wrong: The manager schedules from memory. They know roughly who they need on a Friday night, add a buffer because last week was short-staffed, and call it done. There's no connection to actual forecasted volume. Busy weeks get overstaffed; slow periods get hit with surprise labor spikes. The schedule is built around availability, not need. An employee asks to not work Mondays, another needs to leave by 9, a third is only available three days. The manager builds a puzzle from constraints and hopes it covers the floor. It usually does — but inefficiently, with labor dollars clumping in the wrong dayparts. Opening and closing labor gets ignored. Every shift has setup and breakdown time that doesn't generate revenue. Scheduling three people to open a slow Tuesday is a choice that looks invisible in the day-to-day but shows up clearly in weekly labor reports. There's no visibility into overtime until it happens. Someone picks up a shift last-minute, a different employee calls out and their hours get redistributed, and by Thursday you've got two people approaching 40 hours with three shifts left in the week.
How to Build a Schedule Based on Actual Volume
Go into your POS and pull cover counts and revenue for the same shifts over the past 4–6 weeks. Note the ranges, not just the averages — a Tuesday that averages 80 covers but swings from 55 to 115 needs a different staffing approach than one that consistently hits 80.
If a Sunday lunch averages $4,200 in sales and your labor target is 32%, you have $1,344 in labor budget for that shift. That's your constraint. Staffing decisions flow from that number, not from what you think the floor will feel like.
Full-service front-of-house: typically 3–4 tables per server for sit-down, 1 expo per 4–5 servers at peak, 1 host per 50–60 covers. Fast casual: 1 cashier per 30–35 covers in lunch rush. BOH: 1 line cook per 40–50 covers depending on menu complexity. These are starting ratios — adjust for your specific layout and execution speed.
Not everyone needs to clock in at 4:00 for a 5:30 open. If you expect 60% of your covers between 6:30 and 8:00, you need full staffing then — not 90 minutes earlier. Stagger BOH in 30-minute increments based on when the production work actually builds.
Flag anyone projected to hit 37+ hours by mid-week. That gives you time to trim a shift or redistribute hours before overtime kicks in. Most scheduling software does this automatically; if you're on a spreadsheet, add a weekly-hours column and sort by it.
This matters more than it sounds. It allows your staff to plan, reduces last-minute call-out frequency, and in a growing number of cities, it's legally required.
Coverage Standards by Concept Type
| Concept | Server Ratio | BOH Ratio | Labor Target |
|---|---|---|---|
| Fine Dining | 2–3 tables per server | 1 cook per 25–35 covers | 30–38% |
| Full-Service Casual | 3–5 tables per server | 1 cook per 40–50 covers | 28–35% |
| Fast Casual | N/A (counter service) | 1 team member per 20–30 covers | 25–30% |
| Bar/High-Volume Casual | 4–6 tables per server | 1 cook per 45–60 covers | 28–34% |
These are benchmarks, not rules. Your ticket times, menu complexity, table turn rate, and kitchen layout will push these numbers in either direction. The point is to have a number — any thoughtful number based on your own data — rather than staffing from instinct.
Predictive Scheduling Laws: What You Need to Know
Even where it's not legally required, giving employees advance notice on schedules reduces no-show rates, improves retention, and makes your operation more predictable to manage. The operators who treat scheduling as a service to their staff end up with more reliable staff. That's not idealism — it's just what the numbers show when you track call-out rates before and after implementing better scheduling practices.
Cross-Training: The Scheduling Multiplier
Cross-training is the single biggest lever most operators underuse on scheduling. If every line cook can only work one station, you need a full complement of specialists every shift. If your line can rotate — if your sauté cook can work grill, if your prep person can jump expo — you have flexibility that lets you staff leaner on slow nights and absorb call-outs without going into crisis mode.
Build cross-training into onboarding from day one, not as an afterthought. Document which employees are certified on which stations. Update that list quarterly. When you're scheduling, you can then see immediately whether you have station coverage without a full crew — which often means you can schedule one fewer person on a shoulder shift without risking service. For BOH, standard station-specific procedures — including equipment operation like fryers, flat tops, and char broilers — should be written down and trained consistently. Operators who document and train fryer management procedures, for example, see fewer oil-quality issues and fewer equipment problems from improper handling. The fryer maintenance guide is worth reviewing when you're building out station training materials, and establishing how your kitchen trains on oil management is part of the broader kitchen staff training on fryer oil procedures that reduces waste and equipment wear.
Scheduling Tools: What's Worth Using
The tools that matter at different scales: Under 20 employees: A shared Google Sheet with a labor cost formula column works fine. It's not elegant but it does the job if someone is actually doing the math before publishing it. 20–60 employees: 7shifts, HotSchedules (now Fourth), or When I Work. All three connect to major POS systems, flag overtime, and allow employee availability submission and shift-swapping. Pricing is roughly $2–5 per employee per month. 60+ employees or multi-unit: Restaurant365 or Harri for full integration with payroll and P&L reporting. At this scale, having labor data flow directly into your accounting matters more than it does when you're running one location. The tool matters less than the process. A manager using a spreadsheet with a clear volume-based methodology will outperform a manager using expensive software and scheduling from habit.
Real Kitchen Example
A fast casual concept in Chicago — two locations, each doing $1.1M/year — was running labor at 32% across both units. The owner knew it was high but attributed it to minimum wage increases. When he audited the schedules, he found: The same number of staff was being scheduled for every Monday regardless of volume — a carry-over from an older manager's practice that nobody had questioned. Mondays at Location 2 were running 40% lower volume than the schedule assumed. He dropped one front-of-house position and staggered the remaining team member's start time by 90 minutes. Result: $420/week in recovered labor at that unit alone. He also found three employees at Location 1 regularly hitting 42–44 hours per week from shift swaps that managers were approving without checking cumulative hours. That overtime cost alone was $280–340/week. After implementing a simple overtime threshold alert in 7shifts, weekly overtime exposure dropped to near zero within 60 days. Combined, those two changes — better volume-based scheduling and overtime visibility — moved his labor rate from 32% to 29.4%. On $2.2M combined annual revenue, that's roughly $57,000 in annualized labor savings.
People Also Ask
How far in advance should a restaurant schedule be posted?
Two weeks minimum. Beyond compliance with predictive scheduling laws in many jurisdictions, employees who receive schedules with adequate notice call out less, plan around their shifts more reliably, and are less likely to leave for a competitor who does give advance notice. One week is the floor; anything less creates operational chaos and staffing instability.
What is a good labor cost percentage for a restaurant?
Full-service restaurants typically target 30–35% labor cost as a percentage of revenue. Fast casual aims for 25–30%. The more critical benchmark is prime cost (labor plus food cost combined) — profitable operations keep this under 60–65% of total revenue. Labor cost alone doesn't tell the full picture if food cost is also running high.
Sources
- Rezku — Restaurant Labor Costs Explained: 2026 Benchmarks
- Toast POS — How to Lower Restaurant Labor Costs in 2026
- U.S. Department of Labor — State Predictive Scheduling Laws
- Restaurant Business Online — Labor Management
- Purimax — Fryer Maintenance Guide
- Purimax — How to Train Kitchen Staff on Fryer Oil Management
