Promo-intake rule
↓ produced
The week-13 planned peak
Clients declare peaks two weeks out on one page. The holiday promo arrived as a plan input instead of a Thursday emergency, and 249 OT hours were chosen, not absorbed.
Implementation Engagement · The First Quarter
Overtime spend down 22% in thirteen weeks
The quarter-results exhibit is the engagement's scoreboard: one trend line, thirteen weeks, and a deliberate up-week at the end. Overtime hours fell from a 320-hour weekly average to a planned floor, and the one week they rose, they rose on purpose: chosen on Monday, staffed by volunteers, for a promo declared two weeks out.
The headline
Four numbers the GM and the finance lead both signed off on
-22%
Overtime spend versus the prior quarter. The engagement's anchor number, and it is exact: 3,245 hours against 4,160.
3,245
OT hours this quarter vs 4,160 the quarter before. Every week itemized in the trend below.
~$30K
Saved in the quarter: ~$107K vs ~$137K at the illustrative fully-loaded OT rate of $33/hour.
5 days
Schedule visibility for staff, every week of the quarter. Before: next day, sometimes same day.
The trend
Thirteen weeks of overtime hours, one planned peak
Weekly OT hours
Week 13: planned peak (chosen Monday)
Prior-quarter average: 320 hrs/week
Prior avg 320
305
292
280
268
258
248
240
232
226
220
215
212
249
Week 1: First planned schedule; reactive OT already down.
Week 2: Standards tuned after Friday review.
Week 3: First full promo declared via the intake rule.
Week 5: Temp pool used instead of a Friday scramble.
Week 11: Lowest reactive OT of the year.
Week 13: Planned peak. See the callout below.
Week 13 · The planned peak
A client holiday promo landed in week 13, declared two weeks out through the promo-intake rule. The capacity plan showed the gap on Monday, overtime was chosen that morning at the crews the supervisors picked, and the crews volunteered in advance. 249 OT hours, every one of them scheduled before the week began. No Thursday panic, no floor walk, no surprise on the finance lead's report.
Overtime did not disappear. It became a decision. Twelve weeks stepped down as the forecast, the standards, and the Monday cadence took hold. The thirteenth week stepped up, on purpose, and still finished 22% under the prior-quarter average. That is the difference between overtime as a shock absorber and overtime as a tool.
The mix shift
Less overtime, and a different kind of overtime
Planned share of OT
Before~15%
Quarter end~70%
The share of OT hours chosen on Monday instead of begged for on Friday. The rest is true surprise, and it is shrinking.
Weekly forecast error
Before~27%
Quarter end~11%
Trailing 8-week baseline by client and activity, plus the promo-intake rule. When one existed at all, the old forecast missed by a quarter.
Friday scrambles
Weekly → 2 in 13 weeks
Both promo-driven, both caught by Wednesday. The supervisors' floor walk asking who can stay tonight went from a ritual to an exception.
Ship SLAs
Held every week
The overtime cut cost nothing on the service side. Illustrative, and the point of the exercise: capacity planned, not capacity gambled.
The mechanism
How each number moved: every result traces to one part of the model
Measured labor standards
↓ produced
Schedules that match the work
Units per labor hour measured for six core activities over two weeks of observation. The GM's instinct, written down and tested, is why required hours can be trusted.
Monday cadence
↓ produced
Planned share ~15% → ~70%
Thirty minutes on Monday: forecast to required hours to gap to a decision. OT gets chosen at chosen crews, or a flex action fires instead. Schedules publish 5 days ahead.
A forecast the GM can read
↓ produced
Forecast error ~27% → ~11%
Trailing baseline, seasonality factors, promo intake. Explainable on one page, tuned in the Friday review, and explicitly not a black box.
After the quarter
What continues without Diazovate in the room
The cadence is the machine
Monday planning, 30 minutes: plan published, schedules out 5 days ahead. Friday review, 20 minutes: forecast vs actual, standards drift, next week's risks. The GM runs both. They ran the last six weeks of the quarter without help.
Standards get re-measured quarterly
Labor standards drift as products, packouts, and crews change. A quarterly re-measure of the six core activities is on the calendar, with the same two-week observation method used in the build.
The graduation stance
The model is a structured workbook plus one small forecast-refresh script, and the client owns both. Nothing else was stable enough to deserve automation yet. If the workbook ever stops being enough, the model migrates into workforce software as-is: same standards, same forecast, same Monday meeting.