Scheduling: Shift designer
Objective. Inspect or define shift templates (start, length, breaks) and see how a pattern maps to the coverage curve and rule limits - without mistaking a good template for a covered week.
The shift designer answers: do our shift patterns fit demand and our rules? The key read is that a well-shaped template is a building block, not coverage - the week is only covered when enough of the right shifts are scheduled against the live forecast.
See it in the demo
What this screen answers
A Sales or CSM person opens the shift designer to answer: are the shift shapes (start times, lengths, break placement) right for this demand pattern and within our rules? Good templates are what let the planner and optimizer build coverage that matches the demand curve rather than a flat block of bodies.
The task
Inspect or define shift templates for the team: start times staggered to the demand curve, lengths and break windows within rule limits. See how a given pattern would map onto the coverage curve - where a staggered start helps the peak, where a fixed block leaves a trough overstaffed.
How to read it
A well-shaped shift template improves the building blocks of a schedule; it does not by itself cover a given week. Coverage still depends on how many of each shift are scheduled against the current forecast. The misread to avoid: concluding 'our shift patterns are good, so coverage is handled.' The rules shown here are the template defaults; the customer's actual labour rules must be confirmed.
Honest limits
The designer governs the shapes available, not whether a specific period is covered or compliant - that is settled in the planner, coverage and optimization on the live forecast. Confirm with product which shift-rule constraints (max length, rest, break law) are enforced for a customer; the demo uses seeded defaults.
Interpretation check
A good shift pattern is a building block, not coverage - the week is only covered when enough of the right shifts are scheduled against the live forecast.
In the field
A back office moving from one fixed 9-to-5 block to staggered starts: the designer shapes the templates, but interval coverage is only proven once they are scheduled against the live forecast.
Practical task
On the demo designer, inspect one shift template and write how its start/length would help or hurt a named peak interval, noting that coverage is still settled in the planner.
Self-check
Our shift templates fit the demand curve well. Is the week covered?
No. Templates are building blocks. Coverage depends on how many of each are scheduled against the current forecast, read in the planner and coverage views.
What does a staggered start time buy you over a fixed block?
It lets staffing follow the demand curve, covering peaks without overstaffing troughs - better interval coverage for the same hours.
The rules shown in the designer - can you treat them as the customer's labour law?
No. They are template defaults in the demo. The customer's actual labour rules must be confirmed with product and configured.
Verified vs demo. Screen is live in the demo at /#/designer; exact controls, labels and figures are SME-validation-pending.