Scheduling: Overview
Objective. Open the Scheduling home, set the team and period, read the headline schedule state, and route into planner, optimization and publication as distinct steps.
The home screen is the front door to a team's schedule: it answers, at a glance, where this period stands before you dive into building, optimising or publishing. The value of reading it correctly is not over-trusting a healthy headline.
See it in the demo
What this screen answers
A Sales or CSM person opens the overview to answer: for this team and period, what state is the schedule in and where do I start? It frames the three distinct steps of Scheduling - plan a draft, optimise it, publish it - and points to the areas (planner, coverage, optimization, publication, audit) where each job is done. Use it to orient a demo or an account review before going deeper.
The task
Set the scope to the team or site and the planning period you care about (for example the week W42 used across these modules). Read the headline: how the period is covered, whether violations are outstanding, and whether a version is published. Then move into the planner to inspect the draft, into optimization to reshape it, and into publication to make it live - treating each as a separate step rather than one button.
How to read it
The headline coverage here is planned coverage against a forecast, not what actually happened on the floor - actual activity against the plan is measured in Real-Time Adherence, not here. A healthy-looking headline only says the current draft matches the forecast it was built on. Do not read a green overview as 'the week is handled': confirm which forecast version the draft uses and whether it is actually published before you rely on it.
Honest limits
The overview summarises; it does not by itself prove the forecast is current, the labour rules are configured to the customer's policy, or the schedule is published and acknowledged. Those are confirmed on the configuration, optimization and publication screens. Confirm supported rules, integrations and publication controls with product; the demo runs on seeded data.
Interpretation check
The overview headline is planned coverage against a forecast - not actual delivery, and not proof the week is published. Confirm forecast version and publication state before trusting it.
In the field
A contact-centre or RCM operation (e.g. OVO-style) opening the week before go-live: the overview frames whether to trust the headline or step into the planner to check the peak intervals first.
Practical task
On the demo, scope the overview to a team and period and write a two-line reading: what state the schedule is in, and the two things you would confirm (forecast version, publication state) before trusting the headline.
Self-check
A healthy overview headline is shown. Does that mean the week is handled?
No. It means the current draft matches the forecast it was built on. Confirm the forecast version is live and that a schedule is actually published before relying on it.
Where is 'what actually happened on the floor' measured, if not here?
In Real-Time Adherence. The overview shows planned coverage; adherence compares actual activity and output against the published plan.
What are the three distinct steps the overview frames?
Plan a draft against the requirement, optimise it against rules and cost, then publish it as the single live version. Keeping them distinct is the core teaching point.
Verified vs demo. Screen is live in the demo at /#/home; exact controls, labels and figures are SME-validation-pending.