Overtime without better delivery
Objective. Equip Sales and CSM to run the overtime play: the customer is paying sustained overtime yet delivery is not improving in proportion. Show how Time and Activity, Work Output, Scheduling and Value Leakage separate paid hours from delivered output, expose where the overtime is going, and track the recoverable waste - capacity kept separate from cash.
Overtime is the most visible symptom of an operation that manages by effort. This play follows the money: Time and Activity quantifies the overtime and how the hours are used; Work Output tests whether those extra hours produced proportionally more clean output; Scheduling shows whether the overtime is a coverage-design problem (wrong distribution) rather than a volume problem; Value Leakage attributes the recoverable waste and tracks it to a verified recovery. The value is turning uncontrolled overtime into a managed, output-justified lever. The boundary: a recoverable-capacity figure is an opportunity, not cash saved, and cutting overtime without fixing the cause just moves the backlog.
See it in the demo
The problem and who feels it
The overtime line keeps climbing but the delivery line does not move with it. The operation has normalised extra hours as the way to keep up, and no one can say whether the last block of overtime actually bought any output. Who feels it: a finance or operations leader staring at an overtime bill that will not come down; a team manager who leans on overtime because it is the only lever they trust; a workforce planner who suspects the overtime is covering a scheduling or distribution problem rather than real extra demand.
The trap is that overtime feels like a direct response to backlog, so it is rarely questioned. But hours bought are not the same as work delivered, and sustained overtime is often paying to paper over a coverage or output problem that cheaper fixes would solve.
The business impact
Uncontrolled overtime without matching delivery drains margin and masks the real problem. The costs: direct premium spend on hours that may not be producing proportional clean output; diminishing and sometimes negative returns as tired teams produce more rework, so the overtime quietly funds quality failures; a hidden structural problem - a coverage gap or a process friction - left unaddressed because overtime keeps the wheels turning just enough; and a planning blind spot where overtime is treated as free flex rather than a costed decision.
In a cost-sensitive or displacement setting, 'cost per clean unit including overtime' is exactly the figure a competitor will attack or a CFO will demand - and an operation that cannot show the return on its overtime is exposed on both.
Which applications address it and how they chain
The play chains four applications to follow overtime from spend to justification to recovery.
- Time and Activity (https://time-activity.demo.timechamp.io/) - quantifies the overtime, separates absent time from available hours and overtime, and shows how the extra hours are actually used. This sizes the spend honestly.
- Work Output (https://work-output.demo.timechamp.io/) - tests the return: did the overtime hours produce proportionally more clean output, or did output-per-paid-hour and cost-per-clean-unit worsen once overtime is included? This is where effort is held to delivery.
- Scheduling (https://schedules.demo.timechamp.io/) - shows whether the overtime is covering a distribution problem: overtime, VTO and open-shift views reveal if better coverage design would remove the need for premium hours.
- Value Leakage (https://leakage.demo.timechamp.io/) - attributes the recoverable waste, assigns an owner and tracks recovery from baseline to verified, keeping recovered capacity distinct from cash.
The chain: how much overtime and how used (T and A) - what it delivered (Work Output) - whether scheduling would remove it (Scheduling) - the tracked, owner-assigned recovery (Value Leakage).
The value story and how it is measured
The value is turning overtime from an uncontrolled habit into a managed, output-justified lever: knowing what each block of overtime delivers, whether a scheduling change would make it unnecessary, and tracking the waste you remove.
Measure against the customer's own baseline: clean output per paid hour including overtime and cost per clean unit from Work Output (the honest return figures); overtime volume and its distribution from Time and Activity and Scheduling; and, once acted on, verified recovery with evidence and time to verification from Value Leakage. Keep two things honest - include overtime hours in the denominator so the return is not flattered, and keep recovered capacity separate from cash recovered.
The honest boundary - what this does not solve
This play exposes and sizes unproductive overtime and points to the fix; it does not let a customer cut overtime safely by itself. Be explicit.
- Capacity is not cash: a recoverable-overtime figure is an opportunity. It becomes a saving only when the customer actually removes the hours or redeploys them, and only if delivery holds - Value Leakage keeps capacity and cash separate for this reason.
- Cutting without fixing the cause moves the backlog: if overtime is covering a real coverage gap or a process friction, removing it simply pushes the work elsewhere. Validate the cause (Scheduling coverage, or Work Understanding friction) before recommending a cut.
- Return figures depend on definitions: output-per-paid-hour and cost-per-clean-unit are only as good as the agreed completion definition, source coverage, standards and quality signal - confirm these with product and the customer.
- Some overtime is legitimate: genuine demand spikes justify overtime; the play distinguishes justified premium hours from waste, it does not condemn all overtime.
Interpretation check
Overtime hours bought are not delivery achieved. The play is honest only when overtime hours are kept in the denominator (so output-per-paid-hour and cost-per-clean-unit are not flattered), when the cause is validated before any cut, and when recoverable capacity is reported separately from cash saved.
In the field
KnackGlobal RCM: sustained overtime on claim teams is a prime target in a cost-per-clean-claim displacement case. The play shows whether the overtime bought proportional clean output, whether better scheduling would remove it, and tracks the recoverable waste to verified recovery - producing the cost-per-clean-unit-including-overtime figure that wins the CFO argument, with capacity kept separate from cash.
Practical task
Using the demo, build the overtime story for one team: size the overtime in Time and Activity, test its return in Work Output with overtime in the denominator, check in Scheduling whether coverage design would remove it, and show how Value Leakage would track the recovery. Write the two honesty rules you will state in the call (overtime in the denominator; capacity not cash) and the one cause you would validate before recommending any cut.
Self-check
A customer is proud that overtime kept them on SLA. How do you test whether that overtime was worth it?
In Work Output, compare clean output per paid hour and cost per clean unit with overtime hours included in the denominator. If the return did not scale with the extra hours - or quality/rework worsened - the overtime funded effort, not proportional delivery.
Why bring Scheduling into an overtime conversation?
Because sustained overtime often covers a distribution problem, not a volume problem. Scheduling's coverage, overtime and VTO views show whether redistributing shifts within the rules would remove the need for premium hours - a cheaper fix than paying overtime indefinitely.
The customer wants to cut overtime 20% next month. What do you insist on first?
Validate what the overtime is covering. If it is a real coverage gap or process friction, cutting it just moves the backlog. Fix the cause (Scheduling coverage or a Work Understanding friction) first, then remove the now-unnecessary hours.
Where is the capacity-versus-cash line in this play?
Value Leakage sizes recoverable overtime as capacity opportunity and tracks it to verified recovery, but it is not cash until the customer actually removes or redeploys the hours and delivery holds. Capacity and cash are reported separately on purpose.
Is the play claiming all overtime is waste?
No. Genuine demand spikes justify overtime. The play distinguishes justified premium hours (they bought proportional clean output) from waste (they did not), using the customer's own output and cost figures.
Verified vs demo. The overtime breakdown, the output-per-paid-hour and cost-per-clean-unit figures, the coverage-design view and the tracked recovery are demo-shown on seeded data. The customer's actual overtime rates, completion definitions, standards, quality signal and schedule rules must be confirmed with product and the customer; recoverable overtime is an opportunity, not a realised saving.