How to Staff Your Restaurant Based on Sales Data

Labor is your second-largest expense. Most restaurants overspend by 3-5% on labor because schedules are based on habit, not data. That is $30,000-$50,000 per year on a $1M operation.

By Aidan Pierce, Founder9 min readUpdated May 2026

The Problem With Gut-Based Scheduling

3-5%typical labor cost savings from data-driven scheduling

Most restaurant managers build schedules based on what worked last time, staff availability, and gut feel. The result is consistent overstaffing during slow periods and occasional understaffing during rushes. Both are expensive — overstaffing wastes labor dollars, understaffing loses revenue through slow service and long waits.

The fix is surprisingly simple: use your actual POS sales data to determine exactly how many staff you need for each hour of each day. Your POS already has this data — you just need to use it.

Calculate Revenue Per Labor Hour

Revenue per labor hour (RPLH) is the key metric for staffing optimization. Divide each hour's (or shift's) total revenue by the number of labor hours deployed. A full-service restaurant should target $35-50 RPLH, fast casual $50-75, and QSR $60-90.

Pull this data for every shift for the past 4 weeks. You will immediately see which shifts are overstaffed (low RPLH) and which are understaffed (high RPLH with declining service quality or ticket times).

Build Staffing Templates From Sales Patterns

Your POS data shows predictable hourly sales patterns. Monday looks different from Friday. Lunch looks different from dinner. Build a staffing template for each day of the week based on the average hourly sales pattern from the past 4-6 weeks.

Start with your highest-volume day and work backwards. If Friday dinner (5-9pm) averages $4,000 in revenue and your target RPLH is $45, you need roughly 88 labor hours across that window — about 22 staff-hours per hour, or a crew of 22. Scale other shifts proportionally based on their revenue.

Pro tip: Stagger start times by 30-minute increments. Instead of bringing the whole dinner crew in at 4pm, bring the first wave at 4pm and the second at 4:30pm. This eliminates the gap where you have a full crew but no customers.

Cross-Train for Flexibility

The biggest obstacle to data-driven scheduling is inflexibility. If your dishwasher can only wash dishes, you need a dishwasher for every shift regardless of volume. But if your dishwasher can also prep and run food, you can schedule one person to cover all three roles during slow periods.

Cross-training also reduces your vulnerability to call-outs. A team where 80% of members can cover at least two positions gives you scheduling flexibility that a single-role team cannot match.

Adjust for Seasonality and Events

Your baseline staffing template handles normal weeks. But sales swing by 20-40% for holidays, local events, weather changes, and seasonal shifts. Build adjustment factors for known variables: +20% staffing for Valentine's Day, -15% for the first week of January, +30% when there is a game at the nearby stadium.

Track these adjustments and their outcomes over time. After one full year, you will have a complete seasonal staffing model that accounts for every predictable swing.

Automate Staffing Decisions with Meridian

Meridian analyzes your POS sales data alongside weather, events, and seasonal patterns to recommend optimal staffing for every shift. You will see exactly how many staff you need, which positions to schedule, and what your labor cost percentage will be — before the schedule goes out.

When actual sales differ from the forecast, Meridian alerts you so you can make real-time adjustments: send someone home early on a slow night or call in backup when a rush hits earlier than expected.

Frequently Asked Questions

Target labor cost varies by concept: full-service 30-35% (including benefits and payroll taxes), fast casual 25-30%, QSR 20-28%. More important than the percentage alone is prime cost (food + labor), which should stay below 60-65% of revenue. A restaurant with 28% food cost can afford 35% labor; one with 35% food cost needs labor closer to 28%.
Divide expected shift revenue by your target revenue per labor hour (RPLH). For example: if Friday dinner is expected to generate $4,000 across 4 hours, and your target RPLH is $45, you need 4000/45 = 89 total labor hours, or about 22 people for the 4-hour shift. Adjust by role (2 hosts, 8 servers, 6 kitchen, etc.) based on your service model.
One extra person per shift at $15/hour for 6 hours, across 7 days a week, costs $546/week or $28,400/year. Most restaurants have 2-3 overstaffed shifts per week, meaning $15,000-$40,000 in annual excess labor cost. This is pure waste — it does not improve service or revenue, it just inflates your labor line.
Scheduling software (7shifts, HotSchedules, Homebase) handles the logistics of building and distributing schedules, managing availability, and tracking time. But most scheduling tools do not tell you how many people you need — they just make it easier to schedule whatever number you decide on. The real value comes from analytics that determine optimal staffing levels based on sales data.
Build a buffer of on-call staff who can come in with 30-60 minutes notice, typically people who live nearby or want extra hours. Use real-time POS data to spot rushes early — if revenue at 11:30am is already 20% above forecast, call in backup before the noon rush hits. Over time, AI forecasting reduces the frequency of unpredicted rushes by accounting for more variables.

Related Guides

Schedule with data, not guesswork.

Meridian analyzes your sales patterns to recommend optimal staffing for every shift — so you stop overspending on labor and start maximizing revenue per labor hour.

No credit card required · 45-second setup · Cancel anytime

Cookie Preferences

We use essential cookies for authentication. We also use analytics cookies to improve our service.