Restaurant labor tracking: FOH/BOH hours + productivity KPIs
Restaurant labor tracking is how you connect FOH and BOH hours to sales and guest volume using consistent rules—so staffing becomes a measurable system, not a daily argument. When you do it well, you can plan hours from forecasts, spot drift early, and explain performance by daypart and channel.
The goal isn’t to chase a single “perfect labor %”. The goal is to understand how many hours your concept needs to deliver service at your quality standard—and to keep that model stable as demand changes.
Why labor results drift without a system
Labor “gets worse” for predictable reasons: roles are classified differently from one manager to another, overtime isn’t flagged early, training hours get mixed into productivity, and dayparts get averaged into a single daily number. That’s why restaurant labor tracking starts with definitions before KPIs.
Set your FOH/BOH foundation
Reliable restaurant labor tracking depends on a stable mapping that doesn’t change week to week. Lock down the rules once, then improve operations on top of them.
What to standardize (list 1):
- Role mapping: assign every job code to FOH, BOH, or a defined shared bucket (management/support) with one consistent policy
- Time types: separate worked hours from paid non-work time (training, meetings, sick, holiday) and flag overtime clearly
- Location consistency: apply the same mapping across units so comparisons are valid in multi-location reporting
Once this is stable, your numbers stop moving for “definition reasons” and start reflecting real operational changes.
Capture the minimum data you actually need
Hours alone don’t tell you whether staffing was right—only that people were on the clock. Combine labor with demand and context:
- Hours from time clock/payroll
- Sales from POS (use one definition, commonly net sales before tax)
- Volume from POS/reservations (covers, orders, transactions)
- Context tags like daypart and channel (dine-in, delivery, takeaway, catering)
This turns restaurant labor tracking into a management tool because you can explain why hours were high or productivity was low.
Measure hours first, cost second
The operational lever is hours because hours are what you schedule. Cost is essential, but it varies by wage rates and payroll burden—so it’s best layered on after hour logic is clean.
A simple rule keeps restaurant labor tracking consistent:
- Use worked hours for productivity KPIs
- Use paid hours and total labor cost for cost control
Use productivity KPIs that change decisions
Pick a set of restaurant metrics that helps you schedule better, control overtime, and diagnose issues fast. The best KPIs work at total level and still make sense when sliced by FOH/BOH, daypart, and channel.
Core KPI formulas (list 2):
- Sales per Labor Hour (SPLH) = net sales / worked hours (FOH, BOH, total)
- Labor Cost % = total labor cost / net sales (FOH, BOH, total)
- Covers per Labor Hour = covers / worked hours
- Minutes per cover = (worked hours × 60) / covers
- FOH/BOH hours mix = FOH hours / total hours and BOH hours / total hours
- Overtime rate = overtime hours / total hours
In practice, SPLH and minutes per cover tend to be the most actionable outputs of restaurant labor tracking because they link staffing directly to throughput.
Read the numbers with a simple example
Assume net sales are $10,000, covers are 400, FOH worked hours are 120, BOH worked hours are 80, total worked hours are 200.
Total SPLH is $10,000 / 200 = $50 per hour. FOH SPLH is $10,000 / 120 = $83.3 per FOH hour. BOH SPLH is $10,000 / 80 = $125 per BOH hour. Covers per labor hour is 400 / 200 = 2.0. Minutes per cover are (200×60) / 400 = 30.
The point is to learn stable ranges for your concept, then react quickly when you drift outside them.
Make dayparts and channels visible
Daily totals hide the staffing story. Restaurant labor tracking becomes far more accurate when you measure the same KPIs by daypart (lunch vs dinner) and by channel (dine-in vs delivery). You’ll immediately see patterns like BOH load rising with delivery while FOH covers stay flat, or lunch needing a staffing floor even when sales dip.
This is where you get schedule improvements that actually stick: shift start times, station coverage, prep timing, and cross-training.
Run a plan vs actual routine
The best use of restaurant labor tracking is converting forecasts into planned hours, then reviewing the variance with clear drivers. Keep it simple and repeat weekly.
Weekly routine (list 3):
- Forecast sales and volume by daypart/channel, set productivity targets, convert targets into planned FOH/BOH hours, schedule to plan, then review variances in hours, SPLH, and overtime with driver notes
When performance misses, the drivers are usually straightforward: sales shortfall, minimum staffing floors, call-outs, training time, prep inefficiency, or menu/process bottlenecks. The win is correcting the next schedule, not just explaining the last one.
Avoid the mistakes that break trust in the numbers
Most teams lose confidence when definitions drift. Mixing worked and paid hours inside the same KPI is the classic error. Floating roles that bounce between FOH and BOH without a rule create fake trends. Salary managers can also distort comparisons if their cost allocation changes; even if you report their cost separately, tracking hours keeps operational reality visible.
How Finoko supports restaurant labor tracking
Finoko for restaurants helps implement restaurant labor tracking as a repeatable management workflow instead of a spreadsheet exercise. You can standardize FOH/BOH mappings, separate worked vs paid logic, and keep one consistent definition of sales and volume across dashboards and budgets. From there, Finoko shows productivity and variances by location, daypart, and channel—with drill-downs that explain whether changes came from sales, hours, mix, or overtime.
Conclusion
If you want labor to feel controllable, start with clean definitions, focus on hours-based productivity, and review by daypart and channel. With a consistent routine, restaurant labor tracking becomes a practical operating system for better schedules, lower overtime, and clearer accountability.