Capacity Planning: Scheduling
Objective. Explain the handoff from capacity to scheduling and that a required capacity is not a published schedule - scheduling is a distinct downstream step.
This screen is the bridge from capacity planning to scheduling: it shows how the requirement feeds the scheduling step. A CSM uses it to explain where capacity ends and scheduling begins.
See it in the demo
What this screen answers
A Sales or CSM person opens this to answer 'how does the plan become actual shifts?' Capacity planning says how many skilled people are needed by interval; scheduling turns that into feasible shifts for named people under rules. This screen shows the handoff so the two steps are not conflated.
The task
Scope to the plan and period, then read how the capacity requirement passes to scheduling. The key move is to narrate the boundary: capacity produces a requirement; scheduling consumes it to build and publish shifts. Describe it as 'the requirement feeding the scheduling step', not invented controls.
How to read it
A capacity requirement is not a schedule. The misread is treating 'the plan says 40 FTE in this interval' as though shifts exist to cover it - they do not until scheduling builds and publishes them, respecting rules, skills and employee constraints. Read this screen as a handoff, not a result. A requirement can be met on paper while no feasible schedule yet covers it.
Honest limits
This screen does not build or publish schedules - that is the Scheduling application, with its own rules, optimization and publication steps. Confirm with product how the capacity requirement actually flows into the customer's scheduling tool or into Time Champ Scheduling, and whether versions stay in sync.
Interpretation check
A capacity requirement is not a published schedule - scheduling is a distinct downstream step that turns the requirement into feasible, rule-respecting shifts for named people.
In the field
An operation that plans capacity in Time Champ but schedules elsewhere: the CSM must set expectations that a balanced plan still needs a feasible, published schedule before coverage is real.
Practical task
On this screen, write two lines: how the requirement passes to scheduling, and the boundary statement that a met requirement is not yet a published schedule covering it.
Self-check
The plan shows the interval is covered. Are the shifts in place?
No. A requirement is not a schedule. Shifts exist only once Scheduling builds and publishes them under rules and constraints; the requirement can be met on paper with no feasible schedule yet.
Where does capacity end and scheduling begin?
Capacity produces the skilled-people-by-interval requirement; Scheduling consumes it to construct and publish actual shifts. This screen is the handoff between the two.
What must you confirm about the handoff for a customer?
How the requirement flows into their scheduling tool or Time Champ Scheduling, and whether plan and schedule versions stay in sync - confirm with product.
Verified vs demo. Screen is live in the demo at /#/scheduling; exact controls and figures are SME-validation-pending.