Time and Activity: Capacity and leakage
Objective. Read where available capacity is lost across a team and explain why recovered capacity is not the same as recovered cash.
This screen aggregates where paid, available hours leak away - to idle, exceptions, unused availability - and frames it as a capacity opportunity. The entire task is reading that opportunity honestly: it is capacity, not cash.
See it in the demo
What this screen answers
Silent capacity loss is one of the three costs Time and Activity targets: available hours that drain away through exceptions nobody reviews. This screen answers 'across this team and period, how much available capacity is being lost, and to what?' - turning a vague sense of waste into a visible, sized opportunity.
The task
Scope to a team and period and read the leakage by its categories - what share of available time is lost and where. The task is to size the opportunity and point to its source, then hand it to a planning or Work Output conversation. Resist the urge to immediately convert hours into a money figure on this screen.
How to read it
The decisive guardrail, borrowed from Value Leakage: recovered capacity, billed value and collected cash must stay separate. This screen shows capacity opportunity - hours that could be redirected - not money saved or earned. Recovering an hour of capacity only becomes cash if that hour is redeployed to work that is billed and collected. The classic misread is multiplying leaked hours by a rate and presenting it as guaranteed savings.
Honest limits
A capacity figure is a ceiling on opportunity under stated assumptions, not a realised result. It depends on the available-hours denominator and the exception rules behind it, both of which are configurable. Confirm with product how leakage categories are defined, and keep the customer's financial realisation as a separate, owner-driven exercise rather than a number this screen can promise.
Interpretation check
Capacity leakage is an opportunity in hours, not cash. Recovered capacity only becomes money if redeployed to billed, collected work - keep capacity, billed value and collected cash strictly separate, exactly as Value Leakage does.
In the field
KnackGlobal (~6,000 seats): a few percent of leaked available time is a large capacity number, but the cost case is made only when freed capacity is shown redeploying to billed claim work - capacity visibility first, cash claim separately.
Practical task
On the demo capacity view, size one team's largest leakage category and write a one-line finding that states it as recoverable capacity (hours) and explicitly separates it from any cash claim.
Self-check
A customer multiplies leaked hours by an hourly rate and calls it savings. What do you correct?
That converts a capacity opportunity straight into cash. Recovered capacity is only money if the freed hours are redeployed to work that is billed and collected; the three must stay separate.
What does a leakage figure depend on that makes it configurable?
The available-hours denominator and the exception/idle rules behind it. Both are customer-specific, so confirm the definitions before quoting the size.
Where does the capacity opportunity go next?
Into a planning or Work Output conversation about redeploying freed hours - not into a savings claim made on this screen.
Verified vs demo. Screen is live in the demo at /#/capacity; exact controls and figures are SME-validation-pending.