Capacity Planning - Common Misinterpretations
Objective. Provide a high-value quick-reference catalogue of the metric misreads specific to Capacity Planning, grouped by theme, each with the wrong reading, why it is wrong, and the correct reading - drawn from the app's workflow interpretation checks and the grounding guardrails.
Capacity Planning produces numbers that look definitive but are projections and simulations layered on configurable assumptions. The predictable misreads cluster into five themes: projection versus result, simulation versus execution, the balance-versus-coverage trap, assumption-driven figures read as facts, and capacity versus cash. For each misread below: the wrong reading, why it is wrong, and the correct reading. Use this as a fast check before you present or defend any capacity figure.
See it in the demo
Theme 1 - Projection read as a result
Misread: 'The volume forecast says X cases, so we will handle X.'
Why it is wrong: the volume forecast is projected arriving demand with error bars, not handled or completed work and not actuals.
Correct reading: it is the raw demand input at the start of the chain; it becomes a requirement only after standards and shrinkage are applied, and it carries forecast uncertainty.
Misread: 'The model is 95 percent accurate, so the next forecast is reliable.'
Why it is wrong: that accuracy is backtested on history - it describes past fit, not a guarantee for the next period, and it cannot cover a regime change (new client, product, unmodelled event).
Correct reading: accuracy is retrospective evidence of trust, and bias (a consistent over/under lean) matters as much as error size because a biased forecast systematically mis-staffs. State plainly when past accuracy may not carry.
Theme 2 - Simulation read as execution
Misread: 'Approve scenario B - that's our plan, so staffing is handled.'
Why it is wrong: a scenario is a simulation under stated assumptions. Selecting it hires, schedules and executes nothing, and it is 'best' only if its assumptions hold.
Correct reading: a scenario quantifies sensitivity. Validate its assumptions, then confirm with product whether and how a scenario is promoted to an approved plan - and remember execution happens in Scheduling and in real hiring.
Misread: 'A what-if shows we'd be fine at higher volume, so we're covered.'
Why it is wrong: a what-if is a simulation of one assumption change, not a decision or an achieved outcome.
Correct reading: it shows how far the requirement moves per driver - the risk you are quantifying - not a commitment.
Misread: 'The capacity review is approved, so the plan is executed.'
Why it is wrong: approving a review is an owned decision on the requirement, not the act of hiring or scheduling to it.
Correct reading: approval governs the plan; execution and the achieved service result are proven downstream and later.
Theme 3 - The balance-versus-coverage trap
Misread: 'Our overall FTE nets out balanced for the quarter, so staffing is solved.'
Why it is wrong: this is the app's core interpretation check. A net FTE balance does not prove every skill and interval is covered - you can be balanced overall while short of a scarce skill at peak and long of another in the trough.
Correct reading: always read coverage by skill and interval (/#/balancing), not the headline total. The total can be perfectly balanced and the operation still miss service at peak.
Misread: 'Big volume of this work type, so we just need more people.'
Why it is wrong: volume total hides the work-type mix, and different work types need different skills.
Correct reading: the mix, not just the total, drives which skills and intervals are short - a large volume of one type may need a scarce skill nobody else can do.
Theme 4 - Assumption-driven figures read as facts
Misread: 'The required FTE is 142, that's the number.'
Why it is wrong: required FTE is a computed requirement that depends entirely on its standards, shrinkage and occupancy assumptions - change any one and the number moves.
Correct reading: the deliverable is the requirement plus its drivers; a number without its assumptions is the problem you are solving, not the answer.
Misread: 'Shrinkage is set, so the requirement is right.'
Why it is wrong: shrinkage is often a default placeholder, and it swings the requirement more than almost any other input.
Correct reading: confirm shrinkage (and handling standards, occupancy) is the customer's measured figure before trusting the output.
Misread: 'The service level is green in the plan, so we'll hit it.'
Why it is wrong: a service goal is an input the plan is sized to, not an achieved result; moving the target moves the required headcount.
Correct reading: the plan is sized to hit the goal under its assumptions - achievement is measured in operation, not asserted by the plan.
Theme 5 - Capacity versus cash, and sample versus census
Misread: 'The plan frees 8 FTE, so that's X in savings.'
Why it is wrong: a capacity requirement is expressed in people and time; converting released capacity straight into a cash figure conflates two different things and skips whether that capacity is actually redeployed or removed.
Correct reading: keep capacity value separate from cash. Released or avoided capacity is an opportunity; cash realisation depends on a decision the customer makes and verifies elsewhere. Never present a capacity figure as money saved.
Misread: 'The plan covers everything because the forecast covers everything.'
Why it is wrong: the forecast may rest on partial data coverage or a work-type breakdown that does not match the customer's real mix.
Correct reading: confirm the data coverage and freshness and the work-type mix against reality; a plan built on a partial or stale demand picture is confident about the wrong thing. A connected source is not validated, current data.
Interpretation check
Every Capacity Planning figure is one of: a projection with error bars, a simulation under assumptions, or a requirement computed from configurable inputs. None is an executed action, a guaranteed result, or a cash amount - and a net balance is not coverage.
In the field
KnackGlobal (RCM): a leader seeing a balanced quarterly headcount total could conclude claims staffing is solved, while the plan is short of a specialised payer/denial skill at month-end peak. Reading coverage by skill and interval - not the net total - is what prevents a confident but wrong staffing conclusion, and the freed-capacity figure stays separate from any cost-per-claim cash claim.
Practical task
Take three figures from a demo capacity plan (a required-FTE number, a scenario comparison, and a forecast-accuracy figure). For each, write the likely wrong reading, why it is wrong, and the correct reading, and tag it with its theme. Then find one place where a net FTE balance hides a skill/interval gap and write the one-line correction.
Self-check
A customer points at a balanced quarterly FTE total and says staffing is solved. Which theme is this and what is the correct reading?
The balance-versus-coverage trap (Theme 3). A net balance does not prove skill/interval coverage; read coverage by skill and interval, since you can be balanced overall yet short of a scarce skill at peak.
A stakeholder treats a 95 percent backtested accuracy as a promise the next forecast is right. Why is this wrong?
Accuracy is backtested on history - past fit, not a future guarantee - and bias matters as much as error size. A regime change (new client/product/event) can break it. It is projection-read-as-result (Theme 1).
Why is converting '8 FTE freed' into a cash saving a misread?
Capacity value and cash must stay separate. Released capacity is an opportunity; cash depends on a customer decision to redeploy or remove that is made and verified elsewhere. Presenting capacity as money saved conflates the two.
What is the correct reading of 'required FTE is 142'?
It is a requirement computed from standards, shrinkage and occupancy assumptions - change one and it moves. The deliverable is the number plus its drivers, not the number alone.
A green service level in the plan is read as 'we'll hit the target.' What is the misread?
A service goal is an input the plan is sized to, not an achieved result. The plan is sized to hit it under its assumptions; actual achievement is measured in operation, not asserted by the plan (Theme 4).
Verified vs demo. The misreads are drawn from the demo's seeded figures and the app's own interpretation checks; the specific numbers, forecasting method and accuracy metric are demo/SME-validation-pending and must be confirmed with product for a customer. The guardrails themselves (projection vs result, simulation vs execution, balance vs coverage, assumption-driven, capacity vs cash) hold regardless of the figures.