Build the schedule in 30 minutes. Recover 4 to 9 hours a week.
A 14-minute playbook for independent owners. The overlap audit, the demand curve build, and the daypart schedule structure that takes labor cost down without taking shifts away from anyone who wants them.
Owners running this routine recover 4 to 9 hours per week per location.
Read This First
Most independent owners schedule by memory. Last week's schedule, copy-paste, adjust for time-off requests, post. The result is a schedule that fits last week's demand curve, not next week's. Off by 4 to 9 hours per week per location, every week, all year.
The fix isn't a fancier scheduling tool. It's a rebuild of the inputs. An 8-week demand curve. A daypart-aware structure. An overlap audit. After that, the schedule writes itself in 30 minutes.
One schedule cycle to install. Permanent recovery.
Marty saves us hours every week. The platform is intuitive, the team is fast, and whenever something comes up they have it fixed before I can worry about it. Excited to see where it goes next.
Timothy Tow
Owner, Bin 35 Bistro
What you will have by the end of this page
01An hours-per-week recovery number specific to your operation.
02The 8-Week Demand Curve template you can build in 90 minutes.
03The Overlap Audit checklist for shift handoffs.
04A Daypart Schedule Build worksheet you can use Sunday night.
05The post-cycle review that catches the next set of inefficiencies before they harden.
Quick Win, 60 Seconds
The Schedule Waste Calculator
Five inputs. Two buckets of recoverable waste.
$
min
Your estimated annual loss:
$50,450
Shift overlap waste
Both staff clocked in during the handoff window
$12,012
Forecast mismatchbiggest
8% over-staffing on dayparts that don't need it
$38,438
Your routing
Forecast mismatch is where you lose the most. Start with Chapter 3 (8-Week Demand Curve) and Chapter 5 (Daypart Schedule Build). Both fix the upstream signal.
Bring your questions to a free working session. No system access needed for the call.
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. Fourteen minutes. One system.
Each chapter ends with something you've actually done.
CHAPTER 01
Inventory the schedule you have today
Pull last week's published schedule and circle every shift that exists for a reason you can't immediately articulate. "Because that's what we always do" doesn't count. Most schedules carry 3 to 6 of those phantom shifts. They were added during a busy season two years ago and never got removed.
The inventory exercise takes 20 minutes and surfaces the easy wins. Shifts that exist for inertia, not for demand. Cuts to those shifts are the lowest-friction labor recovery in the building.
Filled example, phantom shift inventory
Sunday brunch barback 9am to 12pm. Set up after 2023 brunch surge, brunch covers down 30% since.
Tuesday opener prep cook 8am to 10am. Covered by Wed deliveries now, 4 hrs/wk wasted.
Friday host 4pm to 6pm. Overlaps with weekend host who clocks in at 5pm, 1 hr overlap.
Late-night dishwasher Mon to Wed. Kitchen closes earlier on weeknights, last 90 min often idle.
Your turn
Print last week's schedule. For each shift, write the demand reason. Anything you can't articulate is a phantom shift. Most owners find 3 to 6.
Takeaway
The first hours back are the ones you stopped justifying years ago.
CHAPTER 02
The Overlap Audit
Shift handoffs are where minutes pile up. The closer clocks out at 11:15. The opener clocks in at 10:45. Thirty overlapping minutes at $22 loaded wage is $11. Multiply by 35 transitions per week and you're at $385 a week, or $20K a year per location.
Audit every transition once. The fix is rarely "cut the overlap to zero," because you need some handoff time. The fix is moving from 18 minutes of overlap to 8 minutes through handoff checklists and scheduled prep.
Overlap audit, before / after
Handoff
Before
After
Saved/wk
Open → Mid kitchen
22m × 6
10m × 6
1.2 hr
Mid → Close server
18m × 7
8m × 7
1.2 hr
Day → Night bar
25m × 5
10m × 5
1.3 hr
Your turn
Time five shift transitions this week. Note the actual overlap. If anything is over 12 minutes, identify the handoff task that's eating the time. Fix the task, the overlap shrinks naturally.
Takeaway
Eight minutes of structured handoff beats 18 minutes of unstructured overlap.
CHAPTER 03
Build the 8-Week Demand Curve
Pull POS sales by hour for the last 8 weeks. Not 4 weeks (too noisy), not 13 weeks (too smoothed). Eight weeks gives you the current demand pattern with enough signal to staff to. Everything downstream depends on this curve being right.
Look at the curve by day of week and hour. You'll find dayparts where you're 30% overstaffed and dayparts where you're under. Both are problems. Overstaffing is the obvious cost. Understaffing kills service and capped revenue.
Filled example, Tuesday demand curve
Hour
Avg sales
Cur staff
$/labor hr
11a-12p
$240
5
$48
12p-1p
$910
5
$182
1p-2p
$540
5
$108
2p-3p
$180
5
$36
Your turn
Pull 8 weeks of hourly POS data. Drop into a sheet, average by day-of-week and hour. Calculate sales-per-labor-hour at each cell. Anything under $80/hr in a tipped-FOH role is a staffing question.
Takeaway
The curve is the schedule. Staff the curve, not the habit.
CHAPTER 04
Stagger to match the curve
The default schedule has everyone start at 11 and everyone leave at 10. The demand curve almost never looks like that. The fix is staggered shifts: 10:30 / 11:00 / 11:30 for the lunch ramp, with paired late-cuts when the dinner pace softens.
Staggering looks small on paper but compounds. A 30-minute cut-back across four servers four nights a week is 8 hours. Over 52 weeks that's 416 hours, or roughly $9K at a typical loaded wage.
Most owners see 6 to 9 hours back per week per location once the stagger is dialed in.
Staggered shift example, Tuesday FOH
Role
Default
Staggered
Server 1
11:00-9:00
10:30-2:30 + 5:00-9:00
Server 2
11:00-9:00
11:00-3:00 + 5:30-9:30
Server 3
11:00-9:00
11:30-3:30 + 6:00-10:00
Your turn
Take your busiest weekday. Apply the stagger to FOH only. Hold BOH constant. Compare the labor cost vs. the existing schedule. Most owners see meaningful hours back on the very first staggered day.
Takeaway
The default schedule fights the demand curve. The staggered schedule rides it.
CHAPTER 05
The 30-Minute Build Routine
With the demand curve and the staggered template in place, the actual schedule build collapses to 30 minutes. You're not making creative decisions every Sunday. You're applying the template to next week's known constraints (time-off, sales forecast, event bookings).
The order matters. Build by daypart. Build kitchen first (less flexibility), then bar, then floor, then host/support. Each pass is 5 to 8 minutes if you have the inputs ready.
30-minute build sequence
Min 0-3: pull next week's forecast, time-off requests, event bookings.
Min 3-10: kitchen build (BOH first, least flexible).
Min 10-16: bar build.
Min 16-23: floor build with stagger applied.
Min 23-27: host / support / runners.
Min 27-30: final pass, post.
Your turn
Time yourself this Sunday. If you can't get the build under 60 minutes with the template, the template needs more pre-decision. Rework the template, not the build.
Takeaway
If the build takes longer than 30 minutes, the template is doing too little.
CHAPTER 06
The Post-Cycle Review
Every 4 weeks, run a 15-minute review. Pull the actual labor % vs. the target by daypart. Identify the two dayparts that drifted most. Adjust the template for the next cycle. That's it. The point is incremental refinement, not constant overhaul.
Most owners try to optimize everything every week. That's why they never optimize anything. The 4-week cadence gives the changes time to settle and produce signal.
Post-cycle review template
Pull actual labor % by daypart for the last 4 weeks.
Compare to target. Highlight the two largest variances.
For each: adjust the template (add/remove a stagger, retime a handoff, change a daypart line).
Document the change in a single line in the schedule template's changelog.
Re-run for next 4 weeks. Repeat.
Your turn
Put a recurring 15-minute block on the calendar every 4 weeks. The cadence is the system. The review without the cadence becomes "when I get to it," which means never.
Takeaway
Tune two dayparts every four weeks. Compounds faster than rebuilding everything.
Print this cheat sheet
The Cheat Sheet
One page. Print it. Pin it.
Everything in this playbook, condensed.
Phantom Shift Inventory
Print the schedule. Articulate the demand reason for every shift. Anything without a reason = phantom. Most owners find 3-6.
Overlap Audit
Time five shift transitions. Anything over 12 min = handoff task eating time. Target 8 min of structured handoff.
8-Week Demand Curve
POS hourly sales, last 8 weeks. Avg by day-of-week × hour. Compute $/labor-hr per cell. Under $80/hr (FOH) = staffing question.
Staggered Shifts
Replace 11:00 starts with 10:30 / 11:00 / 11:30. Pair late-cuts when pace softens. 6-9 hours back per day per location.
30-Min Build
BOH (5-7 min) → Bar (5-7 min) → Floor with stagger (7 min) → Host/support (4 min) → final pass (3 min). Template carries the decisions.
4-Week Post-Cycle
Top 2 daypart variances. Adjust template, not schedule. Document one-line change. Compound, don't rebuild.
What this playbook can't do
You now have the system. Marty runs it for you.
A playbook can't:
Pull and refresh the 8-week demand curve every Sunday for you
Surface phantom shifts the moment they appear in your weekly build
Watch real overlap minutes per transition and flag drift
Run the post-cycle review automatically every 4 weeks
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.