Scheduling - Concepts and Key Terms
Objective. Build the mental model behind Scheduling and define its key terms plainly, so a Sales or CSM person reasons correctly about what a schedule is, what Generate/Optimise does, and when a plan becomes a commitment.
Scheduling has one core idea: a schedule is a plan against a forecast. Everything else - the draft, coverage by interval, optimization, violations, publication, acknowledgment - follows from that. This module sets out the core concept, a plain-language glossary of the terms that matter, how they chain from requirement to published commitment, and the single concept people most often get wrong.
See it in the demo
The core concept - a schedule is a plan against a forecast
A schedule is not a record of what happened; it is a plan built against a forecast of demand. Capacity Planning says how many people, with which skills, are required by interval. Scheduling lays actual shifts against that requirement and shows where the plan covers demand and where it falls short.
Three consequences flow from this and shape every correct reading:
- Coverage shown is planned, not actual. It compares required (forecast) to scheduled (draft). Whether people showed up and the work got done is Real-Time Adherence and Work Output.
- Generate/Optimise produces a draft bound by the rules you set. The optimiser reshapes the draft against your rules, cost and constraints; it does not change the forecast underneath.
- A published schedule is a commitment still subject to real-world change. Publishing makes one version live; absences and demand swings still happen, which is why Intraday Management and RTA exist.
Key terms defined plainly
- Requirement / demand - the staffing needed by interval, from the forecast (usually Capacity Planning's output).
- Forecast version - the specific forecast a draft is bound to. The most important thing to confirm, because a stale version makes a clean draft wrong.
- Draft - a schedule that is being built or optimised. Not live, carries no commitment.
- Coverage by interval - required versus scheduled at each interval of the day, not just the daily total. The peak, not the average, is where service succeeds or fails.
- Shortage window - an interval where required demand exceeds scheduled staffing; a surplus/trough is the opposite (idle cost).
- Rule / violation - a configured labour rule (rest, overtime, break) and a breach of it. Zero violations means zero against the rules configured.
- Optimization - reshaping a draft against rules, cost and constraints to cut shortage and overtime; a step, not a fix for bad inputs.
- Scenario - a simulated comparison of drafts on stated assumptions; comparable only on the same forecast version and period.
- Publication - making one draft the single live schedule, with an audit trail and a notice period.
- Acknowledgment - employees confirming their published shifts.
- Open shift / VTO - an unassigned shift offered out, and voluntary time off; levers to balance coverage after publication.
- Schedule stability - how much a published schedule churns afterwards; heavy churn signals a weak forecast or an unowned change process.
How the concepts chain together
The terms form one spine, requirement to commitment:
Forecast / requirement (bound as a forecast version) -> the planner lays shifts into a draft -> coverage by interval shows shortage windows and surplus -> optimization reshapes the draft against rules to clear violations and cut overtime (optionally compared as scenarios) -> publication makes one version live with acknowledgment -> post-publication, requests, open shifts and VTO handle change, and schedule stability tells you whether the forecast and process were sound.
The chain runs on one rule: each step is bound to the forecast version and configuration beneath it. Change the forecast version and the whole coverage curve changes; change the rules and 'zero violations' means something different. That is why the CSM validates forecast version, rules, skills and time zone before trusting anything downstream.
The one concept people most often get wrong
The single most common error is reading planned coverage as actual delivery - treating a green coverage view, or a well-optimised draft, as proof the week is handled.
It is wrong because coverage is a plan against a forecast: it says the draft matches forecast demand, nothing more. It does not confirm the forecast was right, that the draft was published, that violations were cleared, that people will adhere, or that the work will get done. The closely related error is treating a draft as a commitment - a draft is not live until it is published, on the correct forecast and with violations cleared, and even then it is subject to real-world change.
The habit that prevents both: before trusting any schedule, say out loud which forecast version it is bound to and whether it is a draft or published. Those two facts decide what the numbers actually mean.
Interpretation check
A schedule is a plan against a forecast. Coverage is planned (required-vs-scheduled), a draft is not a commitment until published, and optimization reshapes a draft against the rules you set without changing the forecast beneath it. Hold those and the terms read correctly.
In the field
When a KnackGlobal-scale operation adds Scheduling onto a Capacity Planning requirement, the concepts decide the conversation: the plan-against-forecast framing keeps the team from reading a draft's coverage as an outcome, and the forecast-version habit keeps a stale-forecast draft off the floor.
Practical task
Write the Scheduling spine from memory in one line (forecast/requirement -> draft -> coverage/shortage -> optimization/rules -> publication/acknowledgment -> change/stability). Then take three terms from the glossary and, for each, write the one-sentence misread that follows if you ignore its definition.
Self-check
In one sentence, what is a schedule?
A plan built against a forecast of demand - laying actual shifts against the required staffing by interval - not a record of what happened.
What does coverage by interval compare, and why interval not day?
Required (from the forecast) versus scheduled (the draft) at each interval. By interval because demand is not flat - a full daily total can still miss the peak, which is where service breaks.
What is the difference between a draft and a published schedule?
A draft is being built or optimised and carries no commitment; a published schedule is the single live version employees act on, with an audit trail and acknowledgment - but still subject to real-world change.
What is a forecast version and why confirm it?
The specific forecast a draft is bound to. Confirm it because a stale version makes a clean-looking draft fail current demand - coverage is only correct relative to the forecast behind it.
What is the single most common conceptual error?
Reading planned coverage as actual delivery - treating a green coverage view or a good draft as proof the week is handled. Coverage is a plan; delivery is RTA and Work Output.
Verified vs demo. The planner, coverage and optimization screens are demo-shown on seeded data. The exact term labels in a customer's configured product, and the supported rules and integrations, are confirm-with-product.