Start by mapping peak hours and required coverage for each zone (kitchen, floor, bar, host). Build templates for different day types (weekday vs weekend). Collect availability weekly, schedule fixed roles first, then fill flex positions. Publish at least one week ahead.
It depends on your restaurant size and service style. A general rule: 1 server per 4-6 tables for full service, 1 per 8-10 for casual dining. Kitchen staff depends on menu complexity. Track covers per shift to dial in your specific numbers.
7shifts is built specifically for restaurants. Turnozo is simpler and cheaper for smaller restaurants that don't need restaurant-specific features like tip pooling. Homebase works if you need a free plan. The best choice depends on your team size and budget.
At minimum one week. Two weeks is better and increasingly expected by staff. Some states have predictive scheduling laws requiring 7-14 days advance notice. Earlier posting reduces no-shows and last-minute scrambles.
Full-service restaurants should target 30-35% of revenue. Quick-service and fast-casual typically run 25-30%. Fine dining runs higher at 35-40% due to higher service standards. If you're consistently above your target, look at scheduling inefficiencies first: overtime, overstaffing slow periods, and no-shows are the most common culprits.
Get practical ideas
Open a ready-made prompt to summarize the article and apply it to your team.
Every Sunday night, somewhere, a restaurant manager is hunched over a spreadsheet trying to piece together next week's schedule. They're juggling availability texts, time-off requests scrawled on napkins, and the nagging feeling they've forgotten someone's standing Thursday class.
Sound familiar? You're not alone.
Restaurant scheduling is genuinely one of the hardest scheduling problems out there. You're dealing with split shifts, multiple positions, wildly unpredictable rushes, a workforce that turns over at 75-80% annually, and labor costs that eat up a third of your revenue. All while trying to keep both customers and employees happy.
This guide breaks down how to do it well. not perfectly, because perfection doesn't exist in restaurants. but well enough that you stop dreading Sunday nights.
Why Restaurant Scheduling Is Uniquely Difficult
Before we get into solutions, let's acknowledge what makes this harder than scheduling in other industries.
Multiple positions with different skills. A retail store might have cashiers and floor staff. A restaurant has hosts, servers, bartenders, bussers, food runners, line cooks, prep cooks, dishwashers, and managers. Each role requires different training, and not everyone is interchangeable.
Unpredictable demand. A random Tuesday can be dead. A random Wednesday can be slammed because some food blogger posted about you. Weather, local events, holidays (event and catering scheduling is a whole different beast), even what's on TV. they all affect how many covers you'll do.
Labor costs are your biggest variable expense. According to the National Restaurant Association, salaries and wages represent a median of 36.5% of sales (see our full restaurant staffing statistics breakdown) for full-service restaurants. Get scheduling wrong and that number climbs fast.
Turnover is relentless. The restaurant industry averages 75-80% annual turnover. That means by the end of the year, three out of four people on your team today might be gone. You're constantly onboarding, retraining, and adjusting the schedule for new faces.
Legal minefields. Overtime rules, break requirements, predictive scheduling laws (in some cities), tip credit calculations. one scheduling mistake can mean a compliance violation.
None of this is news to you if you run a restaurant. But it's worth naming because the solution has to account for all of it.
Restaurant Staffing Ratios: A Quick Reference
These ratios are starting points. Adjust based on your service style, menu complexity, and layout.
Front of House
Role
Full-Service
Casual Dining
Fast-Casual
Servers
1 per 4-5 tables
1 per 6-7 tables
1 per 8-10 tables
Bartenders
1 per 30-40 seats at bar
1 per 40-50 seats
N/A or 1
Hosts
1 per 50 covers/hour
1 per 75 covers/hour
N/A
Bussers
1 per 2-3 servers
1 per 3-4 servers
N/A
Food runners
1 per 3-4 servers
1 per 4-5 servers
N/A
Back of House
Role
Small (30-50 covers)
Medium (50-100 covers)
Large (100-200 covers)
Line cooks
2-3
3-5
5-8
Prep cooks
1-2
2-3
3-4
Dishwashers
1
1-2
2-3
Expeditor
Chef doubles as expo
1
1-2
Example: a 60-seat full-service restaurant on a Friday night (100 covers)
3 line cooks + 1 prep + 1 dishwasher + 1 expo = 6 BOH
Total: 13 staff + 1 manager on duty
Use these numbers as your baseline, then adjust based on your actual cover-per-hour data.
Front of House vs. Back of House Scheduling
FOH and BOH are two different animals, and scheduling them requires different thinking.
Front of House (FOH)
Your FOH team. hosts, servers, bartenders, bussers. scales directly with customer volume. More covers = more staff needed.
Key considerations:
Server-to-table ratio. The general benchmark is 1 server per 4-5 tables during normal service. Fine dining drops to 1 per 3. Casual/fast-casual can stretch to 1 per 6-7.
Stagger start times. Not everyone needs to arrive at the same time. Your lunch servers don't need to be there at open. Stagger arrivals in 15-30 minute intervals to match the flow of guests.
Bartender coverage. During cocktail rush (typically 5-7pm), you may need extra bartender support even if the dining room isn't full yet.
Hosts matter more than you think. An understaffed host stand during peak hours creates a bottleneck that ripples through the entire operation.
Back of House (BOH)
Your BOH team. line cooks, prep cooks, dishwashers. needs to be in position before service starts. Their schedule revolves around prep, service, and breakdown.
Key considerations:
Prep time is non-negotiable. Cooks need 1-3 hours of prep before service, depending on your menu. Schedule them early enough that they're not rushing.
Station coverage. Each station (grill, sauté, garde manger, etc.) needs someone qualified. You can't just throw a body at the fry station if they don't know the menu.
Dishwashers are your linchpin. When the dish pit falls behind, the entire kitchen slows down. Schedule enough dish coverage, especially during the back half of service when plates start stacking up.
Close crew matters. Whoever closes needs to be both capable and trustworthy. Don't rotate this randomly. find people who are good at it and keep them there.
How to Schedule for Peak Hours
Peak hours are where scheduling earns its keep. Get this wrong and you're either paying for people standing around or watching your team drown.
Step 1: Know Your Peaks
If you're not already tracking covers by hour, start. Most POS systems can generate this data. You're looking for:
When does the lunch rush actually start and end? (It's rarely exactly 12-1pm.)
When does dinner pick up? When does it taper off?
Which days are consistently busier?
Are there secondary peaks? (Saturday brunch, Sunday family dinner, late-night bar crowd)
Two weeks of data gives you a pattern. A month gives you a reliable one.
Step 2: Build to the Rush, Then Scale Down
Start by staffing for your peak hour. That's your maximum. Then work backward:
1 hour before peak: 75-80% of peak staffing (team is arriving, prepping)
Peak hours: Full staffing
1 hour after peak: 60-70% (some staff cut, closers remain)
Low periods: Minimum crew
This prevents the classic mistake of scheduling the same headcount from open to close. Nobody needs 6 servers at 3pm on a Tuesday.
Step 3: Use Split Shifts (Carefully)
Split shifts. where an employee works the lunch rush, goes home, and comes back for dinner. are common in restaurants. They can save labor costs, but they burn employees out if overused.
Best practices for split shifts:
Offer them voluntarily first. Some employees prefer them (students, parents).
Keep the gap meaningful. at least 3-4 hours. A 90-minute break isn't worth the commute.
Don't schedule the same person for split shifts more than 2-3 days per week.
Check your local labor laws. Some jurisdictions have minimum gap requirements or extra pay mandates for split shifts.
Step 4: Build in a Flex Position
A flex position is someone scheduled during peak hours who can work wherever they're needed. Maybe they start as a food runner, shift to bussing during the rush, and help the bar during cocktail hour.
Not every employee can do this. it takes cross-training. But having even one flex person per shift gives you a buffer that prevents small problems from becoming big ones.
Controlling Labor Costs Without Cutting Corners
Labor is your biggest controllable cost. The goal isn't to minimize it. it's to optimize it. Understaffing saves money in the short term and costs you in turnover, bad reviews, and lost customers.
Track Your Labor Cost Percentage
Know your number. Labor cost percentage = total labor cost ÷ total revenue × 100. Then compare like with like: payroll-only and loaded labor cost are not the same measure. Our labor cost percentage by industry reference shows both definitions and the official payroll calculation.
The National Restaurant Association's 2024 operator data puts median salaries, wages, and benefits at 36.5% of sales for full-service respondents and 31.7% for limited-service respondents. Profitable full-service operators reported a 34.2% median; loss-making operators reported 42.9%. Those are management benchmarks, not universal targets.
If your percentage is moving the wrong way, inspect pricing, sales, overtime, coverage, and staffing mix before you start cutting shifts.
Avoid Accidental Overtime
Overtime is a margin killer, and in restaurants, it sneaks up on you. A server picks up an extra shift. A cook stays to help close. By Friday, they're at 45 hours and you owe time-and-a-half you didn't budget for.
Three ways to prevent this:
Set weekly hour caps per employee and don't approve shifts that push past them.
Review hours mid-week. By Wednesday, you should know who's trending toward overtime.
Use scheduling software that flags it. This is one area where technology genuinely pays for itself. A tool like Turnozo will warn you when a schedule change would push someone into overtime before you approve it.
Schedule to Sales, Not to Shifts
Stop thinking "I need 4 servers for dinner." Start thinking "I'm forecasting $4,000 in dinner revenue, which means I need X staff."
Work backward from your revenue forecast:
Projected revenue for the shift
Target labor cost percentage (say 30%)
Available labor budget = $4,000 × 0.30 = $1,200
Average hourly cost per employee (including taxes/benefits)
Maximum labor hours = $1,200 ÷ average hourly cost
This math takes 5 minutes and prevents overstaffing slow shifts and understaffing busy ones.
Dealing With No-Shows and Call-Outs
They happen. No policy or threat eliminates them entirely, especially in an industry with 75%+ turnover. The question is how you handle them.
Build a Call-Out Buffer
If you have 10 people scheduled, assume 1 might not show up. That doesn't mean scheduling 11 people. it means having a plan for when you're short-staffed.
On-call list: Ask 1-2 employees if they're available as backup. Not formally scheduled, just willing to come in if needed.
Cross-trained staff: If your host can jump on food running and your bartender can serve tables, you have more flexibility when someone calls out.
Simplified menu for short-staff days. Some restaurants have a "short menu" they can switch to on unusually understaffed shifts. Fewer dishes = less kitchen strain.
Create a Clear Call-Out Policy
Employees should know:
How early they need to call (2 hours before shift minimum)
Who they contact (direct manager, not the group chat)
Whether they need to find their own replacement (varies by restaurant. some require it, others don't)
What happens with repeated call-outs (progressive discipline)
Write it down. Share it during onboarding. Apply it consistently.
Posting the Schedule: Timing and Communication
When and how you share the schedule matters more than most managers realize.
Post at Least 1-2 Weeks in Advance
The industry standard is posting the schedule at least one week ahead. Two weeks is better. Here's why:
Employees can plan their lives around it (childcare, school, second jobs)
Fewer same-week changes and swap requests
Some cities legally require advance posting (predictive scheduling laws in NYC, Chicago, Seattle, San Francisco, and others)
It shows respect for your team's time
If you're posting the schedule on Saturday for a Monday start, you're going to have problems. Availability conflicts, no-shows, and frustrated employees who feel like afterthoughts.
Use One Source of Truth
The schedule lives in one place. Not a whiteboard, a text thread, AND a spreadsheet. One place.
Whether that's a shared Google Sheet, a scheduling app, or a printed sheet on the wall. pick one and make sure everyone knows where to look. Mixed signals create chaos.
Digital scheduling tools beat paper for one simple reason: everyone sees updates in real time. When a swap happens or a shift changes, the schedule updates and everyone gets notified. No "I didn't see the new schedule" excuses.
Allow (and Encourage) Shift Swaps
Employees are going to need to swap shifts. This is not a problem. it's a feature. The alternative is constant call-outs from people who can't make a shift but don't have a sanctioned way to find coverage.
Build a shift swap policy that's easy to follow. Digital scheduling tools make this painless. employees swap in the app, you approve or deny, and the schedule updates.
Common Restaurant Scheduling Mistakes
Years of restaurant industry data and feedback point to the same recurring mistakes:
1. Scheduling Based on Seniority Instead of Skill
Your best server gets the best shifts. Sounds fair, right? Except now your Friday night crew is all veterans and your Tuesday lunch is all new hires struggling to keep up.
Schedule by skill fit, not tenure. Mix experienced and newer staff on every shift so newer employees can learn and service quality stays consistent.
2. Ignoring Employee Preferences
Some managers treat the schedule as a decree from above. But employees who get shifts that work with their lives are dramatically less likely to call out or quit.
Collect preferences. Some people want morning shifts. Some want evenings. Some need every other weekend off. You won't accommodate everything, but acknowledging preferences goes a long way.
3. Never Reviewing Schedule Performance
How do you know if last week's schedule was good? Did you hit your labor target? Were there any periods of over- or understaffing? Did anyone go into overtime?
After each week, spend 10 minutes reviewing:
Actual labor cost vs. target
Any overtime hours
Any under- or overstaffed periods
Call-out and swap frequency
This quick review, done consistently, helps you improve your scheduling week over week.
4. Using Paper or Spreadsheets for a 30+ Person Team
Spreadsheets work for a team of 5-8. Grab our free restaurant schedule template if that's where you are. Beyond that, the complexity of managing availability, swaps, overtime, and communication across a larger team exceeds what a spreadsheet was designed to handle.
This isn't a technology pitch. it's a practical reality. At a certain team size, the time you spend building and managing a spreadsheet schedule costs more than a scheduling tool would.
Choosing Scheduling Tools for Your Restaurant
If you've outgrown the spreadsheet (or never used one to begin with), here's what to look for in restaurant scheduling software:
Must-haves:
Mobile app for both managers and employees
Shift swap and coverage requests
Overtime alerts
Time tracking / clock-in
Schedule templates (copy last week's schedule and modify)
Nice-to-haves:
POS integration for labor-to-revenue tracking
Availability management
Team messaging
Payroll export
Skip if you're a small team:
AI demand forecasting
Labor budgeting tools
Multi-location management
Custom report builders
For single-location restaurants with under 30 employees, simplicity matters more than features. You want something your team will actually use. which means it needs to be fast, intuitive, and accessible from a phone.
Turnozo fits this profile. Drag-and-drop scheduling, one-tap clock-in, shift swaps, and automatic timesheets. Essential is €9.99/month for up to 10 employees and one location (centro), with every feature included. Pro is €2.99/employee/month from employee 11 or the second location (centro), billed across the whole workforce.
A Week-by-Week Scheduling System
Here's a repeatable system that takes the guesswork out of weekly scheduling:
Monday: Review last week. Pull your labor cost numbers. Any overtime? Any problems? Note what to adjust.
Tuesday: Check availability. Review time-off requests and any standing availability changes for next week.
Wednesday: Build the schedule. Use last week as a template. Adjust for expected volume, events, and availability changes.
Thursday: Post the schedule. Share it through your scheduling tool or post it in the agreed-upon location. This gives your team 10+ days notice.
Friday-Sunday: Handle swaps and adjustments. As swap requests come in, approve or deny based on your policy. Make minor adjustments as needed.
This cycle takes about 30-45 minutes per week once you have it dialed in. That's a lot less than the frantic Sunday-night scramble.
Essential is €9.99/month for up to 10 employees and one location (centro), with every feature included. Pro is €2.99/employee/month from employee 11 or the second location (centro), billed across the whole workforce.
