Enough headcount, poor coverage
Objective. Equip Sales and CSM to run the coverage play: the customer has the right total headcount on paper yet still has shortage windows, missed intervals and skill gaps. Show how Capacity Planning, Scheduling and Real-Time Adherence separate an aggregate balance from real interval-and-skill coverage, and keep the FTE-balance misread out of the story.
A leader can prove the FTE count matches the plan and still watch certain intervals, skills or sites go uncovered. This play exposes why: an overall balance hides gaps by interval and by skill. Capacity Planning shows requirement versus available capacity with assumptions and skills; Scheduling turns the requirement into a feasible schedule and reveals the shortage windows and rule violations; Real-Time Adherence confirms whether the published schedule is actually being worked. The value is coverage where and when it is needed, not just on average. The boundary: a headline FTE balance is never proof that every skill and interval is covered.
See it in the demo
The problem and who feels it
The customer has done the maths: total FTE roughly equals total requirement, so on paper they are staffed. Yet specific windows are short - the Monday morning peak, the late shift, the one skilled queue - and work backs up there while other intervals sit quiet. Who feels it: a WFM or resource manager defending a plan that 'balances' but still misses; an operations leader fielding complaints about specific queues or times; a finance partner who hears 'we need more people' when the real issue is distribution, not total.
The root misread is treating an aggregate as a guarantee. An overall FTE balance can be perfectly healthy while a skill or an interval is chronically under-covered, because averages hide distribution.
The business impact
Poor coverage with adequate headcount is expensive twice over. Service failures in the gaps - breached SLAs, long waits, aged work - concentrated in the uncovered intervals and skills, even though the yearly or monthly plan looks fine. Wasted spend on the wrong answer - leaders hire to a total they already have, or pay overtime to cover a window that better scheduling would have covered, because the diagnosis stopped at the aggregate. And eroded trust in the plan: when a 'balanced' plan keeps failing in the same places, the planning function loses credibility and people revert to gut-feel staffing.
The decision this play protects is the most common staffing mistake: buying capacity to fix what is actually a coverage and scheduling problem.
Which applications address it and how they chain
The play chains the Workforce Management applications from plan to execution.
- Capacity Planning (https://capacityplanner.demo.timechamp.io/) - compares required capacity against available capacity by skill and interval, with the assumptions, shrinkage and service goals made explicit. This is where you show that the healthy headline balance hides a skill or interval gap.
- Scheduling (https://schedules.demo.timechamp.io/) - turns the requirement into a feasible schedule and surfaces the actual shortage windows, coverage by interval and rule violations. It makes the gap concrete and testable: draft, optimise, publish.
- Real-Time Adherence (https://rta.demo.timechamp.io/) - confirms whether the published schedule is being worked in the covered windows, so you can tell a coverage-design gap from an adherence gap.
The chain: the requirement by skill and interval (Capacity Planning) - a feasible schedule and its shortage windows (Scheduling) - whether the schedule is actually worked (Real-Time Adherence). Each stands alone, but together they move from 'we have the people' to 'the right people are in the right interval and are actually there'.
The value story and how it is measured
The value is coverage where and when it is needed: the ability to see which interval and which skill is short, fix it by redistributing or reshaping shifts before adding cost, and confirm the fix holds in execution.
Measure against the customer's baseline: coverage by interval and rule exceptions from Scheduling (not just a total FTE number); unresolved skill gaps and forecast accuracy/bias by the agreed method from Capacity Planning; and schedule adherence from Real-Time Adherence to confirm the covered windows are actually worked. The headline you are replacing - total FTE versus total requirement - is explicitly demoted from a conclusion to a starting input.
The honest boundary - what this does not solve
This play diagnoses and improves coverage; it does not manufacture people or override constraints. Be explicit.
- The FTE-balance misread is the headline limit: never let an overall balance be read as proof that every skill and interval is covered - it is precisely the error the play corrects, and it cuts both ways (a balance can hide a gap, and a gap does not always mean a shortage of total people).
- Validity depends on inputs: Scheduling coverage is only trustworthy on the current forecast version, rules, skills and time zone. A draft on an old forecast can look valid while failing the current coverage requirement.
- Some gaps are real shortages: if after optimisation a skill or interval still cannot be covered, the honest answer is a capacity or hiring decision in Capacity Planning, not a scheduling trick. Separate 'we can schedule our way out of this' from 'we genuinely need more of this skill'.
- Coverage is not output: being staffed in an interval does not guarantee the work gets done to standard - that is a Work Output question, not a coverage one.
Interpretation check
An overall FTE balance is not proof that every skill and interval is covered. The play's whole point is to break that misread - coverage must be read by interval and by skill, on the current forecast version, and confirmed in execution before anyone concludes the plan is sound or that more people are needed.
In the field
OVO contact-centre: the plan 'balances' at the day level yet the morning peak and one skilled queue keep failing SLA. The play shows the gap by interval and skill in Capacity Planning, tests whether Scheduling can cover it within the rules, and confirms adherence in the covered windows - distinguishing a scheduling fix from a genuine skill shortage, so the customer stops buying headcount to solve a distribution problem.
Practical task
In the demo, build the coverage story for one customer: in Capacity Planning show a healthy total FTE balance that hides a skill or interval gap; in Scheduling surface the shortage windows and whether optimisation closes them within the rules; in Real-Time Adherence confirm the covered windows are worked. Write the exact sentence you would use to retire the 'total balance means covered' misread, and name the one case where you would honestly recommend hiring instead of rescheduling.
Self-check
A customer says 'our total FTE matches the requirement, so coverage is fine'. What do you show them?
That an aggregate balance hides distribution. In Capacity Planning, show the requirement by skill and interval; in Scheduling, show the actual shortage windows and coverage by interval. A healthy total can sit on top of a chronically short interval or skill.
How do you tell a coverage-design gap from an adherence gap?
Scheduling shows whether the schedule covers the interval on paper; Real-Time Adherence shows whether the published schedule is actually being worked. A gap in the schedule is a design problem; a covered schedule that is not worked is an adherence problem - different fixes.
When is the honest answer 'you do need more people' rather than better scheduling?
When, after optimisation on the current forecast, a specific skill or interval still cannot be covered within the rules. Then it is a capacity or hiring decision in Capacity Planning, not a scheduling trick - and saying so protects credibility.
Why can a published schedule 'look valid' yet fail coverage?
Because it may be built on a stale forecast version, or wrong rules, skills or time zone. Validity against an old requirement is not validity against the current one - always check the forecast version behind the schedule.
The customer is fully covered in every interval but still missing SLA. Is this still a coverage play?
No. Coverage is necessary, not sufficient - being staffed does not guarantee the work is done to standard. That is a Work Output / output-attainment question, and the conversation should move there.
Verified vs demo. The requirement-by-skill-and-interval view, the shortage windows, optimisation and the adherence confirmation are demo-shown on seeded data. The customer's real volumes, handling standards, shrinkage, skills, service goals, forecast accuracy and schedule rules must be validated with product and the customer before the coverage numbers can be trusted.