Catch labor overruns mid-shift, not on payroll Friday.
A 13-minute playbook for independent owners. The mid-shift cut trigger, the daypart targets, and the 11am Daily Labor Report that pulls labor cost back to target before the week is gone.
Owners running this routine recover $90K to $450K a year across 4 units.
Read This First
Your labor cost drifts above target on specific dayparts and specific days of the week, not uniformly across the week. You only see the weekly aggregate when payroll runs, which is 10 to 14 days after the dollars were spent. By then the recovery window is closed.
The fix is not a better post-mortem. It's a mid-shift signal that says cut now or you're carrying too many bodies for this volume before the shift is over.
This playbook gives you that signal. By daypart, by day, by station.
$600K a year across 4 units. Marty pays for itself the first month.
Cary Attar
Owner, Fieldings Culinary Group
What you will have by the end of this page
01An overrun number specific to your operation, in dollars per week and per year.
02Daypart-level targets that surface the lunch problem the weekly average hides.
03The Mid-Shift Cut decision tree your MOD can run on the floor.
Heads up: this playbook gives you the routine. It does not run the routine for you every morning. Marty does. Keep reading if you want the routine. Skip to the bottom if you want it run for you.
The Playbook
Six chapters. Thirteen minutes. One system.
Each chapter ends with something you've actually done.
CHAPTER 01
Set targets by daypart, not just overall
A 28% weekly target hides a 38% lunch and an 18% dinner. The weekly average is a lie of arithmetic. You can hit it on average and still be bleeding on every lunch.
Set sub-targets by daypart, day of week, and station. The targets are different for a Sunday brunch vs. a Tuesday dinner. They're different for a fine-dining concept vs. a fast-casual concept. The point isn't the universal target. The point is having a target small enough to act on.
Filled example, full-service owner
Daypart
Mon-Thu
Fri-Sat
Sun
Brunch
n/a
29%
26%
Lunch
32%
30%
28%
Dinner
26%
22%
24%
Late night
35%
30%
n/a
Your turn
Pull your last 8 weeks of POS sales by hour and your timekeeping data by hour. Compute labor % per daypart. Set a target per daypart that is 1-2 points tighter than your current actual. Those become this week's signals.
Takeaway
You can't manage a weekly average. You can manage a daypart.
CHAPTER 02
The Mid-Shift Cut Trigger
Three signals tell your MOD it's time to send someone home an hour early: real sales pace vs. forecast (under 80% by hour 2), reservation/cover gap vs. headcount, overstaffed station relative to cover count. Any one trips the conversation. Any two trip the action.
The hardest part isn't the trigger. It's the conversation script. Most managers won't cut because they don't know how to ask. Give them the words and they will use them.
Mid-shift cut decision tree
By hour 2, is sales pace below 80% of forecast? If yes → continue. If no → no action.
Is the cover-back gap (open tables vs. servers) more than 1:1? If yes → continue.
Is any station overstaffed for current cover count? If yes → cut from that station first.
Conversation script: "Hey [name], we're running soft. I want to send you home an hour early. Same shift next week, no penalty. Cool?"
Your turn
Print the decision tree. Walk one of your MODs through it during a slow shift. Have them run it once with you watching. Then they own it.
Takeaway
Give MODs the script and they'll make the cut. Without the script they won't.
CHAPTER 03
The Schedule vs. Actual Variance Loop
Compare published schedule to actual punch data every Monday. The drift between them is where most lost labor dollars hide. Someone scheduled for 5 hours punched in for 6.5. Someone scheduled to leave at 9 left at 10:15. None of it shows up on the schedule.
The variance loop is a 10-minute Monday review. Pull schedule, pull actuals, list anything off by more than 30 minutes. Investigate the top 5 deltas. Fix the workflow that caused them.
Filled example, variance review
Name
Sched
Actual
Δ
Why
Tara M.
5h
6h25
+1h25
Closed late, no MOD cut
Malik R.
8h
8h05
+5m
OK
Sasha K.
6h
7h10
+1h10
Picked up section, no replacement
Your turn
Set a Monday 10am block. Run this for last week. Anything over 30 minutes of drift gets tagged with a workflow cause. Same cause showing up twice = process gap.
Takeaway
The drift between scheduled and actual is the money you're not seeing.
CHAPTER 04
The Tip Pool Reconciliation
Mis-administered tip pools push labor cost up because the restaurant carries the difference. Whether you're on a card-payout system, an integrated POS pool, or a manual distribution, the same pattern shows up: pooled tips don't match pooled tippable hours, and the restaurant absorbs the gap.
The reconciliation is one weekly comparison: total tippable wages times tip percentage should equal total tip-out. If they don't match by more than $20, investigate.
Tip pool reconciliation, weekly
Pull total credit card tips for the week.
Pull total cash tips declared.
Pull total tippable hours by tipped role.
Compute expected pool distribution per the policy.
Compare actual distribution. Anything off by more than $20 gets investigated.
Your turn
Run last week's reconciliation. If you can't pull the data in 15 minutes, the bigger problem is the data flow. Fix that first.
Takeaway
Tip pool variance is restaurant cost the owner never sees on the line.
CHAPTER 05
The Daily 11am Labor Report
One report. Three numbers. Sent to every MOD by 11am: yesterday's labor %, this week's running labor %, today's projected labor based on the schedule and the forecast. That's the entire report.
The report does two things. It surfaces the trend before payroll runs. And it makes labor cost a daily conversation instead of a Friday surprise. Once it's a daily conversation, MODs start running the cut trigger on their own.
Filled example, May 5 11am report
Subject: Labor Report, Tuesday May 5, 11:00am
Yesterday (Mon May 4): 31.4% (target 28%, +3.4 pts)
This week running (Mon-Tue): 30.8%
Today projected (based on sched + forecast): 32.1%
Action: Today is over target by 4 pts at the projection. MOD review schedule by 2pm. Mid-shift cut likely on PM bar.
Owner
Your turn
Build the template tomorrow. Send it manually for one week. By week two, automate the data pulls. By week three, MODs are responding to it before you send.
Takeaway
Make labor a daily conversation, not a Friday surprise.
CHAPTER 06
Cross-Training to Eliminate Single-Slot Risk
Single-slot positions like one bartender, one expo, one host create call-out vulnerability. When the single-slot calls out, you cover with double-overtime or you operate short. Both cost. Cross-training eliminates the vulnerability without adding headcount.
The matrix is one page. Every employee on rows. Every station on columns. Cells filled with current capability (Y / partial / no). The plan is to eliminate every "no" on a key station within 6 shifts of cross-training.
Cross-training matrix
Name
Bar
Expo
Host
Server
Tara M.
Y
part
Y
Y
Malik R.
part
Y
part
Y
Sasha K.
no
Y
Y
part
Your turn
Build your matrix this week. Identify your most vulnerable single-slot position. Schedule two cross-training shifts in the next 14 days. Update the matrix when complete.
Takeaway
Eliminate the single-slot, eliminate the call-out overtime. Math, not heroics.
Print this cheat sheet
The Cheat Sheet
One page. Print it. Pin it.
Everything in this playbook, condensed.
Daypart Targets
Set a target per daypart × day-of-week. Brunch / Lunch / Dinner / Late, Mon-Thu / Fri-Sat / Sun. Tighter than your current actual by 1-2 pts.
Mid-Shift Cut Trigger
By hour 2: sales pace under 80% + cover gap over 1:1 + overstaffed station = cut. Use the script.
Variance Loop
Mondays, 10 min. Schedule vs. actual. Anything over 30 min drift = workflow cause logged. Same cause twice = process gap.
Tip Pool Recon
Weekly. Total tippable wages × tip% = expected pool. Variance over $20 = investigate.
Daily 11am Report
Yesterday's labor % / This week's running / Today's projection. To every MOD by 11am.
Cross-Training Matrix
One page, employees × stations. Eliminate every "no" on a key station within 6 shifts.
What this playbook can't do
You now have the system. Marty runs it for you.
A playbook can't:
Watch your sales pace by hour vs. forecast in real time
Fire the Mid-Shift Cut alert to your MOD before hour 3
Surface overtime risk by Wednesday so you can rebalance before the week is gone
Run the schedule vs. actual variance loop for you every Monday
Marty does all of it.
Marty is the analyst sitting next to your GM. We plug into your POS, run this routine every morning before you open, alert the moment a number breaks, and review the rest of your operation in the background. It starts with a 2–3 store Cash Recovery Plan pilot. If the Cash Recovery Plan doesn't surface anything worth fixing, we refund the plan fees in full. You keep the work.