Build a full weekly restaurant staff schedule in under 10 minutes. Edit staff names, roles, and hourly wages, fill in shift hours for each day, watch total labor cost and labor-as-% of revenue update live against industry benchmarks, and download a 7-sheet Excel workbook with two-week scheduling, 4-week labor-vs-sales tracking, time-off log, KPI dashboard, and action plan.
| Staff Member | Role | $/Hr | Mon | Tue | Wed | Thu | Fri | Sat | Sun | Hrs | Cost | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DAILY TOTALS | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | $0 | |||
Your Weekly Schedule Summary
Labor Cost by Day
The template is built around the same workflow a seasoned floor manager uses on a Sunday morning before posting next week’s schedule — just faster, free, and with the labor math already wired up. Plan to spend 10-15 minutes the first time and 5 minutes per re-edit after that. The defaults are sensible enough that you can hand the screen to a brand-new manager and they’ll know what to do.
A restaurant schedule is the single most-leveraged operational document in the building. It controls labor cost (the second-largest line item on the P&L after food), it controls service quality (understaffed Saturday nights kill repeat business), and it controls staff retention (badly written schedules drive the best people out the door first). Get the schedule right and everything downstream — labor %, ticket times, guest experience, retention — tends to fall into line. Get it wrong and no amount of training, menu engineering, or marketing fixes the problem.
The structure below is the standard format used by full-service casual dining operations. The percentages and shift patterns come from operations data across thousands of independent restaurants. They’re not laws — QSR runs leaner, fine dining runs heavier, food trucks run differently still — but they’re the right starting point to pressure-test your own schedule against.
| Schedule Element | Industry Standard | Why It Matters |
|---|---|---|
| Labor cost as % of revenue | 25-35% | Single most-watched schedule metric. Under 25% usually means understaffed; over 35% means margin is bleeding. |
| When to post the schedule | By Thursday for the following Mon-Sun | Less than 3 days notice triggers Fair Workweek penalties in some cities and burns out staff everywhere. |
| Front-of-house ratio | 1 server per 16-20 covers | Casual dining standard. Fine dining drops to 1:10. Counter service can run 1:30+. |
| Back-of-house ratio | 1 line cook per 40-60 covers | Varies sharply by menu complexity. Build a 2-deep bench at every station so a no-show doesn’t kill service. |
| Hours per $1,000 revenue | < 18 hrs | Productivity proxy. Most QSRs run 10-14; FSR sits at 14-18; fine dining can climb to 22+. |
| Overtime threshold | < 5% of total hours | Chronic OT means the schedule is wrong, not that staff is working hard. Add headcount before paying 1.5x. |
| Shift swap window | No swaps within 24 hrs | Protects the schedule from last-minute chaos. Swaps must be initiated by staff, not managers. |
| Forecasted covers per shift | Updated weekly | Schedule against forecasted covers, not headcount-from-last-week. Pull POS data Friday morning. |
Two structural rules worth knowing before you start scheduling. First, schedule against forecasted sales, not against “who’s available”. A schedule built from staff availability with no sales overlay is the #1 reason labor % drifts above 35%. Pull last week’s POS, project the upcoming week (adjust for events, weather, holidays), and only then start placing staff on shifts. Second, protect your peak shifts. Friday and Saturday dinner generate 35-45% of weekly revenue in most concepts — understaffing them costs you tips, retention, and reviews. Overstaffing slow shifts is recoverable; understaffing peaks is not.
Schedule quality is measured by four numbers, in roughly this order of importance: labor cost as % of revenue, hours per $1,000 of revenue, overtime as % of hours, and shift-fill rate (the % of shifts that actually run with full staffing as posted). Hit those four and the schedule is working. Miss any one consistently and the schedule is your bottleneck.
Labor cost as % of revenue (25-35%). The full-service casual dining average in 2026 is 30-32%. Counter-service and QSR typically run 22-28% because the service model needs fewer hands. Fine dining and high-touch concepts can hit 34-40% because of tipped FOH, sommeliers, and stronger BOH brigades. The single biggest lever isn’t wages — it’s matching the schedule to forecasted covers. A line cook standing on a slow Tuesday burns the same labor dollars as one slammed on Saturday night, but only the second one earns them back. Pull POS data weekly and build the schedule against it, not against last week’s headcount.
Hours per $1,000 of revenue (< 18 hrs). This is the productivity proxy that lets you compare schedules across different revenue levels. A $20k week with 380 hours scheduled = 19 hours per $1,000 = slightly heavy. A $20k week with 320 hours = 16 hours per $1,000 = well-run. Counter-service and high-volume QSR run 10-14. Casual dining 14-18. Fine dining 18-24. If yours is well above the benchmark for your concept, you’re either understaffing in skill (lots of inexperienced hands taking longer) or overstaffing in volume (extra bodies covering the same workload).
Overtime as % of hours (< 5%). Most operators treat OT as a cost line. The smart ones treat it as a signal. Chronic overtime almost always means the schedule is under-staffed by one headcount and the existing staff is absorbing the gap at 1.5x pay. If a single staff member is regularly running OT, hire to fill the gap — the cost is identical, the burnout risk drops, and you build bench strength. Track OT weekly with the Restaurant Labor Cost Calculator if you don’t already have it in your POS.
Shift-fill rate (> 95%). The percentage of posted shifts that actually run with the staff that was scheduled. Anything under 90% means call-outs, no-shows, and last-minute swaps are eating you alive. Veteran operators fix this with three rules: post the schedule by Thursday for the following Monday-Sunday, no swaps inside 24 hours of shift start, and require shift trades to be staff-to-staff (not manager-to-staff). A high fill rate is the single biggest predictor of consistent service quality.
Fair Workweek compliance (location-dependent). A growing list of cities (Seattle, New York, San Francisco, Chicago, Philadelphia, Los Angeles, Emeryville, Berkeley, San Jose, Oregon statewide) now require advance notice of schedules — typically 7-14 days — with predictability pay penalties for last-minute changes. If you’re operating in any of those markets, check your local ordinance before posting; the penalties for non-compliance can hit $100-$500 per shift per affected employee. Even outside Fair Workweek jurisdictions, 7-day advance notice is the de facto standard staff expect.
A schedule that lives in a PDF folder doesn’t change behavior. The operators who actually hit labor targets translate the schedule into three operating cadences: a weekly forecast, a nightly cover check, and a Monday morning variance review. Each one is short, repeatable, and connects directly to a decision someone has to make.
The weekly forecast (Friday morning, 20 minutes). Pull last week’s POS sales by day and daypart. Pull the events calendar for the upcoming week (local games, weather, holidays, school schedules). Project each day’s covers ±10% and build the next week’s schedule against that forecast, not against “who’s available.” Post by Thursday for Mon-Sun and you’re inside Fair Workweek thresholds in almost every market.
The nightly cover check (5 minutes, every shift). Before service, the on-duty manager checks the forecast against early indicators — the reservations book, the patio weather, the call volume. If covers will likely run 15%+ above or below forecast, the manager has the authority to send a staff member home early or call in an extra hand. The schedule isn’t sacred; the labor target is.
The Monday morning variance review (15 minutes). Pull last week’s POS revenue and last week’s actual labor (from the time clock, not from the posted schedule). Compare to your budget. Three numbers matter: total labor cost vs budget, labor % vs target (25-35%), and overtime as % of hours. If any are red, the manager who owns the schedule has a fix in motion before Tuesday’s draft. This single cadence is the difference between schedules that work and schedules that don’t.
Once the schedule cadence is locked, two operational tools take it from “plan on paper” to “plan that gets executed.” First, your menu and pricing — if labor % trends above target despite a tight schedule, the fix may be on the revenue side, not the labor side. A modest price increase across high-velocity items can pull labor % into the green band without cutting hours. Run the math through the Restaurant Profit Margin Calculator and the Food Cost Calculator before you cut a shift. Second, your customer-facing digital menu — faster ordering means fewer FOH hours per cover, which directly improves the hours-per-$1,000 metric. Menubly gives you a beautiful, mobile-friendly digital menu with QR code ordering for $9.99/month — in about 30 minutes, no developer needed. Restaurants that route table orders through QR code menus instead of server-taken orders typically cut server hours per cover by 15-25%, which is more labor leverage than most schedules can find anywhere else.
Start by pulling last week's POS sales by day and daypart, then forecast the upcoming week (adjust for events, weather, holidays, school schedules). Build a roster of staff with role, hourly wage, and availability, then place shifts against the forecast — heavier coverage on Friday/Saturday dinner, lighter on Sunday afternoon and Monday. Aim for labor cost between 25-35% of revenue. Post the schedule by Thursday for the following Monday-Sunday, confirm every shift via text, and adopt a 24-hour rule against last-minute swaps. Re-run the schedule weekly with updated POS data, not by copying last week's draft.
The 25-35% rule means total labor cost (wages + payroll taxes + benefits) should land between 25% and 35% of total revenue. Counter-service and QSR run lower (22-28%) because the service model needs fewer hands. Full-service casual dining sits at 28-34%. Fine dining and high-touch concepts can hit 34-40% because of tipped FOH, sommeliers, and stronger BOH brigades. The percentage in this template tracks wages only — to get total loaded labor, add 12-15% for payroll taxes and workers' comp. Use the Restaurant Labor Cost Calculator for the loaded number.
Full-time restaurant staff typically work 30-40 hours per week; part-time staff 15-25 hours. The aggregate target is hours per $1,000 of revenue: under 18 hours is well-run for full-service, 14-18 is the casual dining sweet spot, and 10-14 is typical for high-volume QSR. Fine dining and high-touch concepts can climb to 18-24 because of the service ratio. If your total weekly hours run above the benchmark for your concept, you're either understaffing in skill (inexperienced hands taking longer) or overstaffing in volume — the fix is matching the schedule to forecasted covers.
A scheduling template (this page) is a downloadable framework you edit each week — typically in Excel or printed — and post for the team. A scheduling tool (like Menubly's interactive Restaurant Staff Scheduler) is a live web app where staff can see assignments, swap shifts, request time off, and the manager can publish updates instantly. Templates are best for small teams that don't need real-time updates and prefer paper or PDF schedules; tools are better once you have 10+ staff or operate in a Fair Workweek city. Most operators use both — the template for planning, the tool for publishing.
Post the schedule by Thursday for the following Monday-Sunday at the absolute latest — most veteran operators post on Tuesday or Wednesday. Less than 3 days of notice burns out staff, kills shift-fill rate, and triggers Fair Workweek penalties in major US cities. If you operate in Seattle, New York, San Francisco, Chicago, Philadelphia, Los Angeles, Emeryville, Berkeley, San Jose, or anywhere in Oregon, local ordinances require 7-14 days of advance notice with predictability-pay penalties of $100-$500 per shift per affected employee for last-minute changes.
Pull last week's POS sales by day and daypart (lunch / dinner / late night). Project the upcoming week by adjusting for known events: local games, school schedules, holidays, weather, marketing pushes. Translate projected sales into projected covers (revenue ÷ average ticket). Apply your staffing ratios: 1 server per 16-20 covers for casual dining, 1 line cook per 40-60 covers, 1 host per 60+ covers. Build the schedule against that forecast, not against availability. Re-run the forecast every Friday morning before drafting the next week.
Fair Workweek (also called Predictable Scheduling) laws require employers to post staff schedules 7-14 days in advance and pay predictability-pay penalties for last-minute changes. As of 2026, ordinances are active in Seattle, New York City, San Francisco, Chicago, Philadelphia, Los Angeles, Emeryville, Berkeley, San Jose, and statewide in Oregon. Penalties typically range from $100-$500 per shift per affected employee. Even outside Fair Workweek jurisdictions, 7-day advance notice is the de facto standard staff expect — and the fastest way to lose your best people is by chronically posting the schedule late.
Three rules work for most independent restaurants. First, require time-off requests at least 14 days in advance — log them in writing (the time-off tracker sheet in the Excel download has the format). Second, post the schedule by Thursday for the following Monday-Sunday so staff can plan around it. Third, enforce a hard 24-hour rule against shift swaps: swaps must be initiated by staff (not manager-to-staff), and any swap requested within 24 hours of a shift start is declined. The combination keeps the schedule predictable and pushes accountability onto the team where it belongs.
The schedule itself shows wages only — what you owe each staff member for hours worked. Total loaded labor cost is wages plus 12-15% for payroll taxes (FICA, Medicare, state unemployment, federal unemployment, workers' compensation) plus any benefits and employee meals. A line cook making $18/hour actually costs about $21-$22/hour fully loaded. When you compare labor % against the 25-35% target, use the loaded number, not the wage-only number from this template. The KPI Dashboard sheet in the Excel download has the conversion.
Menubly is a free online menu builder for restaurants, cafes, food trucks, bakeries, bars, and service businesses. You can create an interactive digital menu, share it with a link or QR code, and accept online orders with built-in payments — all from one platform. Sign up at menubly.com to get started.
