Shift Scheduling: Calculating Optimal Headcount for Each Service Period

Picture a 180-seat Anatolian lokanta in Konya: Friday night opens with nine servers and by 20:30 half the tables haven't ordered. The problem isn't lazy staff — it's that your headcount is built on last year's gut, not on workload. This piece walks through binding the schedule to actual demand data.

The Workload Formula

The core equation: tickets per hour × average service minutes ÷ 60 = required servers. In the Konya case, Saturday 13:00-15:00 averages 42 tickets/hour at 18 minutes service. 42 × 18 ÷ 60 = 12.6, rounded to 14 — matching the gut feel. Tuesday lunch is 14 × 16 = 3.7, so four servers in theory, six in practice (buffer for breaks and absentees).

Kitchen uses a separate coefficient: 1.2 plates/minute per hot line cook, 2.4 per cold line. A Friday throughput of 200 plates/hour requires 3 hot + 2 cold + 1 garde manger + 2 dish = 8 people. Drop to 5 for a pizzeria, climb to 9 for a charcoal kebab house — calibrate per cuisine.

Software Stack That Actually Works

The global market is dominated by 7shifts ($34.99/month starter, North America leader), Sling by Toast (free tier, POS-integrated), and Deputy (Australian, multilingual). Each pulls POS sales data and auto-suggests a draft schedule; manual tweak takes 15 minutes versus three hours on a blank spreadsheet.

For payroll integration in regulated markets (Turkey's SGK, EU social security, US Fair Workweek), check whether the vendor exports compatible CSVs. Hybrid setups — plan in 7shifts, push approved roster to Logo İK or ADP — are the norm above 50 seats.

Four-Week Calibration Plan

Finding your real coefficients takes one month of hourly POS exports. Pivot in Excel by day-hour-tickets-avg-service-time. Tag outliers (match day, wedding, blizzard) separately — they distort the mean.

• Weeks 1-2: baseline, log service time at current staffing
• Week 3: cut recommended headcount by 10% mid-week, measure complaints
• Week 4: compare guest feedback NPS and ticket times against baseline

FAQ

Is scheduling software overkill for small restaurants? Under 30 seats you can manage in Google Sheets; above 50 seats or with two daily shifts, software saves 4-5 hours weekly.

How do you handle seasonal swings? Maintain separate summer/winter baselines. Coastal Mediterranean towns typically run 2.4× summer multiplier, 0.6× winter — recalibrate yearly.

What's the right table-to-server ratio? Casual dining 4-5, fine dining 2-3, fast casual 8-10. High-check averages need fewer tables per server; fast turnover allows more.

Found this helpful? Share it.