Ask most restaurant operators how they measure labor efficiency, and they will give you one number: labor cost as a percentage of revenue. It is the metric the industry has used for decades. It is also, when used alone, one of the most misleading numbers in the restaurant business.
Labor cost percentage tells you what share of your revenue went to labor. What it does not tell you is whether your scheduling was efficient, whether you had the right number of people on the floor for the business you actually did, or where the real opportunities to tighten labor are hiding. For that, you need a different metric — one that isolates labor efficiency from revenue fluctuation. That metric is Sales Per Labor Hour.
What Is Sales Per Labor Hour?
Sales Per Labor Hour — commonly abbreviated as SPLH — measures how much net revenue your restaurant generates for every hour of labor scheduled. The formula is simple: total net sales divided by total labor hours worked in the same period.
If your restaurant did $5,400 in net sales on a Wednesday and your team worked a combined 126 labor hours across all positions, your SPLH for that day is $42.86. That single number tells you more about scheduling efficiency than the labor cost percentage ever could, because it connects output (sales) directly to input (hours) without being distorted by wage rate differences, benefit costs, or tax allocations.
SPLH answers the fundamental scheduling question: for the business I actually did today, did I have the right number of people working?
Why SPLH Is Better Than Labor Cost Percentage
Labor cost percentage has a structural flaw that makes it unreliable as a scheduling metric: it moves when revenue moves, even if your labor decisions were correct.
Consider a full-service restaurant that schedules $11,000 in labor for a week. If sales come in at $38,000, labor cost percentage is 28.9 percent — well within the typical FSR target of 28 to 32 percent. If sales come in at $33,000 because of bad weather on the weekend, labor cost percentage jumps to 33.3 percent. The labor dollars are identical. The scheduling decisions were identical. But the percentage tells you that you have a labor problem in the second scenario — when what you actually have is a sales problem.
SPLH eliminates this distortion. In the first scenario, if total labor hours were 310, SPLH is $122.58 at the weekly level. In the second scenario, with the same 310 hours, SPLH drops to $106.45. Both numbers are useful because they tell you the actual productivity of each labor hour — but SPLH does not conflate a revenue miss with a scheduling error. It keeps the two problems separate, which means you can diagnose and fix each one independently.
This distinction matters enormously in practice. An operator who sees a 33 percent labor cost week might panic and cut hours the following week. But if SPLH was within target, cutting hours would be exactly the wrong response — it would reduce service capacity without addressing the actual issue, which was sales volume.
How to Calculate SPLH
The calculation itself is straightforward, but the details matter.
For the numerator, use net sales — gross sales minus comps, discounts, and employee meals. Do not use gross sales, because that overstates the revenue your labor actually generated. For the denominator, use total labor hours actually worked — not scheduled hours. If someone was sent home early, count only the hours they worked. Include all hourly and salaried positions. For salaried managers, convert their compensation to an implied hourly figure based on their standard schedule, or simply use their scheduled hours.
Calculate SPLH at the daily level and aggregate to weekly. Daily SPLH gives you the operational detail you need to evaluate individual shifts. Weekly SPLH smooths out day-to-day noise and gives you the trend line that matters for financial planning.
Using SPLH by Daypart
The real power of SPLH emerges when you break it down by daypart — lunch versus dinner, or breakfast versus lunch versus dinner if your concept runs all three. Aggregate daily SPLH can mask significant inefficiencies that only become visible at the daypart level.
Here is a common example. A restaurant shows a daily SPLH of $40, which is within the target range for a full-service concept. But when you break it apart, lunch SPLH is $28 and dinner SPLH is $52. The dinner shift is highly efficient. The lunch shift is overstaffed relative to the sales it generates — and its poor performance is being averaged away by the strength of dinner.
Without daypart-level SPLH, this operator would never identify the lunch scheduling problem. With it, the path forward is clear: reduce lunch labor hours, simplify the lunch menu to require fewer covers per position, or invest in marketing to drive lunch traffic to a level that justifies the current staffing model.
Using SPLH by Day of Week
Day-of-week analysis is equally revealing. Most restaurants have a fairly consistent weekly pattern — slow on Monday and Tuesday, building through the week, peaking on Friday and Saturday. But scheduling often does not reflect this pattern with enough precision.
Tracking SPLH by day of week over a 13-week rolling period reveals exactly where scheduling is too loose or too tight. If your Wednesday SPLH consistently runs $32 while your Saturday SPLH consistently runs $55, you are almost certainly overstaffed on Wednesdays. The numbers make the case clearly — and they provide the evidence a manager needs to have a productive conversation with the scheduling team instead of relying on instinct.
The 13-week rolling view is important because it filters out one-off anomalies. A single bad Wednesday might be explained by weather or a local event. Thirteen consecutive Wednesdays with low SPLH is a scheduling pattern that needs to change.
Using SPLH by Position
The most granular and often most actionable SPLH analysis is by position category: front-of-house versus back-of-house, or broken down further into servers, bartenders, hosts, line cooks, prep cooks, and dishwashers.
Position-level SPLH reveals where labor is being deployed efficiently and where it is not. A restaurant might find that its kitchen SPLH is strong — the line is running lean and producing well — but its front-of-house SPLH is weak because it is scheduling too many servers for the cover count. Or the reverse: a lean front-of-house team that is working efficiently, subsidizing a kitchen that is overstaffed during slow prep hours.
This level of detail is what transforms SPLH from a reporting metric into a management tool. It does not just tell you that labor is off target — it tells you exactly where, which means you can fix the specific problem rather than making across-the-board cuts that damage service quality.
SPLH Benchmarks by Restaurant Type
SPLH targets vary by concept because different restaurant types require fundamentally different labor models. A fine-dining restaurant with a one-to-four server-to-table ratio and a full kitchen brigade will naturally have a lower SPLH than a quick-service concept where three employees can serve 80 guests an hour.
Full-service restaurants should target daily SPLH in the range of $35 to $50. The lower end of that range is typical for higher-labor concepts like fine dining or concepts with extensive tableside preparation. The higher end reflects efficient casual dining operations. Quick-service restaurants, with smaller crews and higher throughput, should target $50 to $75 per labor hour. Fast casual concepts typically fall in the $40 to $60 range, reflecting their hybrid service model.
These benchmarks are starting points, not absolute rules. Your specific target should be calibrated to your market, your average check size, and your service model. A restaurant with a $65 average check in a high-traffic urban market will have a different SPLH target than a $28-check suburban concept. The key is to establish your baseline, set a target, and track it consistently over time.
Making Scheduling Decisions with SPLH
Once you have several weeks of SPLH data, the metric becomes a powerful scheduling tool. The process is straightforward: review the prior week’s SPLH by day and daypart, identify the days and shifts where SPLH fell below target, and adjust the next week’s schedule accordingly.
If Tuesday lunch SPLH has been running $26 against a $38 target for three consecutive weeks, you have more labor on that shift than the sales justify. The options are clear: reduce hours, cross-train an employee to cover multiple positions, or accept the lower SPLH if there is a strategic reason (training a new hire, for example). But the decision is now grounded in data, not guesswork.
On the flip side, if Friday dinner SPLH is consistently above $55, you may be understaffed — which creates its own problems: longer ticket times, declining guest experience, and burned-out employees who are more likely to make mistakes or quit. SPLH that is too high is a warning sign just as much as SPLH that is too low.
The goal is not to maximize SPLH. The goal is to hit the target that balances labor efficiency with guest experience — and to do it consistently, every day, every shift.
Tracking SPLH Over Time
The Restaurant Finance Toolkit includes a Labor Scheduling and Cost Model with a built-in 13-week SPLH tracker that calculates daily, weekly, daypart, and day-of-week SPLH automatically. It also tracks fully loaded labor cost alongside SPLH so you can see both the efficiency and the financial impact of your scheduling decisions in one view. The template includes 219 formulas built specifically for restaurant labor analysis.
Tracking SPLH is not complicated. It requires two inputs — sales and hours — and one simple division. But the discipline of tracking it consistently, by day and by daypart, over a rolling 13-week window, is what separates operators who control their labor model from those who are controlled by it.
The author is a former CFO for a multi-unit restaurant brand. RestaurantBottomLine.com is dedicated to helping independent operators protect their financial model.
Labor cost percentage tells you the score. SPLH tells you how to change it.
Get the Restaurant Finance Toolkit →
PROTECTING THE BOTTOM LINE 