Capacity Planning: Reports
Objective. Generate a shareable capacity requirement with its assumptions for sign-off, and frame it as a dated snapshot rather than a committed number.
The reports screen answers: can I hand finance or operations the capacity requirement and the assumptions behind it, in a form they can review and sign off? The deliverable is a defensible requirement, not a bare number.
See it in the demo
What this screen answers
The customer question is: can I export and share the capacity plan - the requirement plus the drivers and assumptions behind it - so a named owner can approve it. Both roles use it to turn an on-screen plan into something that leaves the tool for sign-off.
The task
Choose the report scope and period, then generate the view that carries both the requirement and the assumptions that produced it (volume, standards, shrinkage, service goal). The point is to share the number with its drivers attached, never the number alone.
How to read it
A report is a snapshot of one plan at one set of assumptions, as of the moment it was run. Re-run it after any input changes - a revised forecast, a corrected shrinkage figure - and you get a different number. The figures are projections, not committed headcount. The classic misread is circulating a report figure as a fixed commitment. Always read and share it as 'the requirement under these stated assumptions, dated.'
Honest limits
Export formats and the exact fields included are SME-validation-pending. A report documents a plan; it does not execute hiring or scheduling, and signing it off is an internal commercial step, not a system action. Confirm the figures against the customer's own baseline before they are quoted externally.
Interpretation check
A report is a dated snapshot of projected requirement under stated assumptions; it is not a committed headcount number.
In the field
A requirement defended to finance - as in a KnackGlobal-style headcount ask - lands only when the report carries the drivers, so the reviewer can challenge an assumption instead of arguing about a lone number.
Practical task
Generate a scoped capacity report and write the one sentence you would put on top of it so finance reads it as a dated, assumption-based requirement, not a commitment.
Self-check
Finance treats a capacity report as a locked commitment. What do you clarify?
It is a snapshot of a projection under stated assumptions as of its run date. Change an input and it changes - so it is a defensible requirement to review, not a fixed promise.
What must travel with the requirement number in a report?
Its assumptions and drivers - volume, standards, shrinkage, service goal - so the reader can see and challenge what produced it.
Does generating a report change staffing?
No. It documents a plan. Hiring and scheduling happen elsewhere and are separate, owned steps.
Verified vs demo. Screen is live in the demo at /#/reports; exact controls and figures are SME-validation-pending.