Scheduling: Configuration
Objective. Review the labour rules, skills, shift templates, time zones and publication controls that govern a schedule - the CSM's first validation stop, because every coverage and violation reading is only as correct as this configuration.
Configuration answers: what rules, skills, time zones and publication controls govern this schedule? The key read is that this is the ground truth behind every coverage and violation reading - wrong configuration makes a clean schedule clean against the wrong policy.
See it in the demo
What this screen answers
A Sales or CSM person opens configuration to answer: what labour rules, skill requirements, shift templates, time zones and publication/ownership controls are actually in force for this team? It is the CSM's first validation stop before trusting anything the planner, coverage or optimization screens show.
The task
Review the configured labour rules (rest, overtime, breaks), skill requirements, time zones for multi-site teams, and the publication and change-ownership controls for the account scope. Confirm each matches the customer's real policy, not just the demo defaults.
How to read it
Configuration is the ground truth that makes every other reading meaningful. If rules or time zones are wrong, a clean-looking draft is clean against the wrong policy - zero violations only means zero against the rules configured, and coverage windows are misread if the time zone is wrong. The misread to avoid: trusting a green coverage or zero-violation view without first confirming the configuration behind it is the customer's actual policy.
Honest limits
The demo configuration is seeded; it demonstrates the model, not a customer's real rules, skills, integrations or time-zone handling. Supported labour rules, integrations and publication controls for a specific customer must be confirmed with product before any compliance or coverage claim.
Interpretation check
Every coverage and violation reading is only as correct as the configuration behind it - wrong rules, skills or time zone make a clean schedule clean against the wrong policy.
In the field
A multi-site RCM operation across time zones: the CSM validates rules and time zones in configuration first, so a 'zero violations, fully covered' draft is not clean against the wrong policy.
Practical task
On the demo configuration, review the rules, skills and time-zone settings and write the four items you would validate with a customer before trusting any schedule reading.
Self-check
A schedule shows zero rule violations. Is it compliant?
Only against the rules configured. If the labour rules are not the customer's real policy, zero violations is meaningless. Validate configuration before trusting it.
Why is the time zone a configuration priority for multi-site teams?
Because coverage is read by interval. A wrong time zone shifts the coverage windows and makes every peak/trough reading wrong for that site.
Why is configuration the CSM's first validation stop?
Because it is the ground truth behind coverage and violations. Validating the forecast version, rules, skills and time zone here is what makes every downstream reading trustworthy.
Verified vs demo. Screen is live in the demo at /#/config; exact controls, labels and figures are SME-validation-pending.