How to Measure a Reduction in Restaurant Labor Overruns
A reduction in labor overruns is not the same as the same percentage reduction in total labor cost. Before evaluating a scheduling change or monitoring tool, define the overrun and the comparison period.
This is an educational worked example, not a customer case study or a claim about results delivered by Marty.
Define the baseline
Specify the location, period, labor categories and target. Record actual paid labor and explain whether the target reflects planned hours, sales volume or another method.
Compare like periods. If a location trades longer hours, raises wages or serves more guests, a simple before-and-after total can mislead. Keep the original baseline and document adjustments instead of changing the target after seeing the outcome.
Calculate the overrun first
In a hypothetical comparable period, Location A has a labor target of $20,000 and actual labor cost of $22,000. The overrun is $2,000.
In a later comparable period with the same target, actual labor cost is $21,500. The overrun is $1,500. The overrun fell by $500, or 25% of the original $2,000 overrun. Total labor cost fell by about 2.27%, calculated as $500 divided by $22,000.
Those hypothetical figures explain the denominator. They are not expected results or customer evidence. Neither percentage alone proves what caused the change.
Use the labor cost calculator for labor-to-sales ratios and a gap to your own target. The example here measures changes in that gap across periods.
Reuse the formulas
| Measure | Formula | Hypothetical example |
|---|---|---|
| Overrun | Actual cost − target cost, where actual exceeds target | $22,000 − $20,000 = $2,000 |
| Overrun decrease | Earlier overrun − later overrun | $2,000 − $1,500 = $500 |
| Overrun reduction % | Decrease / earlier overrun × 100 | $500 / $2,000 = 25% |
| Total labor cost decrease % | (Earlier actual − later actual) / earlier actual × 100 | $500 / $22,000 ≈ 2.27% |
Do not calculate an overrun-reduction percentage when the earlier overrun is zero. Report below-target cost as an underrun separately, and explain a target change before comparing periods.
Check whether the action happened
Retain the issue, manager response and actual time records. A delivered alert does not establish a staffing change. A staffing change does not establish savings if the same work moved to another shift or service suffered.
Use the payroll record to verify paid cost. Do not reduce recorded hours to make a target look better: compensable work must be paid under applicable wage rules. Department of Labor.
Test alternatives to the explanation
Ask whether sales increased, a holiday changed demand, wage rates moved, missing punches were corrected or coverage requirements changed. Document what you can and cannot isolate.
Existing tools can provide timely signals. 7shifts, for example, documents overtime alerts with specific prerequisites. Test what is already enabled before assuming you need a new system. 7shifts overtime alerts.
Report a narrow, supportable result
State the period, locations, definition and verified change. Keep annualized estimates apart from observed results. If you cannot isolate the effect of the tool, say the improvement occurred during the period rather than claiming the tool caused all of it.
The how Marty works explainer puts the later result check into the wider operating routine; it is not evidence for the hypothetical reduction above.
Put the findings to work
Carry the original target and cost definition into the next verification period. Marty is a managed profit-control layer using Find → Assign → Follow up → Verify. Its paid Cash Recovery Plan establishes the baseline; optional Managed Profit Control monitors agreed controls, alerts managers, follows up, escalates missed actions and verifies results.