Sales per labor hour, or SPLH, is the number that shows whether a restaurant's labor is producing revenue or just producing paychecks. It is calculated shift by shift, day by day, and it catches overstaffing and understaffing long before a monthly P&L ever would.
What is sales per labor hour?
Sales per labor hour is total net sales divided by total labor hours worked, and it measures how much revenue each hour on the clock generates.
The formula is simple: SPLH = Total Net Sales / Total Labor Hours Worked. If a dinner shift brings in $4,200 in sales and the team worked a combined 95 labor hours, the SPLH for that shift is $44.21. On its own, that number does not mean much. Once it is tracked over time and compared to a target, it becomes one of the clearest signals in the entire operation.
SPLH is tracked separately by shift, since lunch, dinner, and late night each carry different staffing needs and different targets. A single blended daily number hides where the real problems are.
Why does SPLH matter more than labor cost percentage?
Labor cost percentage reports what already happened, while SPLH can be checked mid-shift and adjusted before the money is spent.
Labor cost percentage is Total Labor divided by Revenue. It is a lagging indicator: by the time it shows up on the P&L, the schedule is done and the hours are already paid. SPLH is a leading indicator. If SPLH drops on a Tuesday dinner, that tells a manager immediately that the shift is either overstaffed or undersold, and a decision can be made in real time, whether that is cutting a server early, pushing upselling, or noting the pattern for next week's schedule.
SPLH also holds up better when revenue swings. A week where revenue drops will spike labor cost percentage even if staffing was handled correctly, simply because the denominator shrank. SPLH does not have that distortion, because both sides of the equation reflect what actually happened on the floor.
Two restaurants can illustrate the gap. Both do $2M a year in revenue. Both pay their teams $15 an hour on average. One runs an SPLH of $42, the other runs $55. Same wage rate, same annual revenue, but the restaurant running $55 spends roughly $169,000 less on labor over the year, because every hour on the clock is producing more.
What should the SPLH target be?
The right SPLH target depends on the service model, and the starting point is a range tied to concept and price point.
| Service Model | Target SPLH Range |
|---|---|
| Fine dining | $30-$45 |
| Full-service casual | $35-$50 |
| Fast-casual | $45-$65 |
| QSR / Counter-service | $55-$80 |
These ranges are a starting point, not a ceiling to chase blindly. The practical approach is to calculate the current average SPLH first, then set a 30-day target that sits 10 to 15% above that baseline. That keeps the goal realistic and specific to the concept, rather than borrowed from a restaurant with a different price point and service style.
Results are not typical and will vary with your business, your market, your team and how much of the work you actually do. Client figures on this site come from recorded interviews and are dated. Nothing here is a guarantee of revenue, profit or growth.
How is current SPLH calculated and tracked day to day?
SPLH is calculated daily using POS net sales and time clock or scheduling software hours, logged on a simple tracker that takes about two minutes a day.
The process starts with pulling net sales and labor hours for each day of the last two weeks, then filling in a daily tracker with columns for net sales, labor hours, SPLH, target, and variance. That baseline average becomes the reference point for the 30-day target described above. Posting the tracker where managers can see it, and tracking daily rather than weekly, is what makes the number useful.
Weekly averages hide the real picture. A strong Saturday can mask a terrible Tuesday, and a restaurant that only checks SPLH once a week will miss the specific shifts that are bleeding labor dollars.
What causes SPLH to miss target, and how is that diagnosed?
A missed SPLH target comes from either a sales issue or a staffing issue, and the fix is different for each.
A sales issue means revenue came in lower than expected, whether from a slow day, weather, competition, or no local events. The fix is better forecasting and adjusting the future schedule for that pattern. A staffing issue means too many hours were on the floor for actual demand: over-scheduling, staff running past their scheduled end time, or calling in extra people unnecessarily. The fix there is schedule discipline and mid-shift cuts when volume does not match the plan.
There is also a mistake worth avoiding on the other side: pushing SPLH too high by understaffing. If service quality drops, ticket times spike, or the team starts burning out, SPLH has been pushed past the point of balance. Higher is not automatically better.
Who should be responsible for managing SPLH, the owner or the manager?
The location manager owns SPLH day to day, while the owner's role is to set the target and review results, not build the schedule.
One case from the Founders Board illustrates the shift. A bistro doing $2.1M a year had labor stuck at 36%, with the owner working 70 hours a week, covering shifts and micromanaging cut decisions. He had never calculated his SPLH and was managing labor by feel and last year's schedule template. Once he ran the numbers, his baseline turned out to be $65.
Tracking SPLH by shift revealed he was overstaffed by roughly 40 hours a week between 2 and 5 PM Monday through Thursday, while being understaffed during the 7 to 9 PM weekend peak, which was killing ticket times and costing sales. He reallocated those wasted afternoon hours to the weekend evening rush.
The bigger change was who built the schedule. The owner stopped doing it himself. His manager built the schedule using SPLH targets and sales projections, reported daily SPLH, and reviewed it weekly with the owner. Within 45 days, labor dropped from 36% to 29%, with an estimated annual profit impact of roughly $147,000. The owner's hours dropped to 40 a week, because the manager was running the system instead of him.
“The M1 is responsible for the labor cost metric, not the owner. An M1 who cannot manage SPLH is not ready to be an M1.”
Restaurants working through this kind of KPI system in a structured way, with a manager accountable for the number and an owner reviewing it rather than building it, is exactly the pattern documented in how a restaurant learns to run without the owner. For a broader view of where labor and prime cost should sit as a whole, see restaurant prime cost benchmarks.
The Founders Board gives owners a licence to the full Scaling Engine OS™, including the SPLH tracking system and the delegation framework that puts a manager in charge of the number. Details on how that works are on the Founders Board page, and owners ready to explore membership can start an application.
