Scheduling: Dashboards
Objective. Scope to an org or team and period and read the headline scheduling KPIs (coverage, rule exceptions, acknowledgment, timeliness, stability) - as planned scheduling health, not achieved service.
Dashboards answer: across teams and the period, how healthy is scheduling? The key read is that these summarise planned scheduling quality, not actual delivery, and a green roll-up can still hide a stale forecast or a single broken peak.
See it in the demo
What this screen answers
A Sales or CSM person opens dashboards to answer: at a glance across teams and the period, how healthy is our scheduling - coverage, rule exceptions, acknowledgment, publication timeliness and stability? It is the review surface for the grounding's candidate measures.
The task
Scope to the org or team and the period. Read the headline KPIs: coverage by interval, outstanding rule exceptions, acknowledgment rate, publication timeliness and schedule stability. Use them to decide where to drill down, not as a final verdict.
How to read it
These KPIs summarise planned scheduling health, not achieved service - coverage here is planned against the forecast, not what RTA recorded. A healthy dashboard on a stale forecast is still wrong, and a roll-up can hide a single broken peak interval inside an otherwise green day. The misread to avoid: reading a green dashboard as 'service was good' or as proof every interval and team is covered. Drill down from the roll-up to the interval.
Honest limits
Dashboards show planned scheduling quality; delivery is confirmed in RTA, intraday and output. Confirm with product which metrics, definitions and thresholds apply for a customer, and against which forecast version coverage is computed; the demo uses seeded data.
Interpretation check
Dashboard health is planned scheduling quality, not achieved service - a green roll-up can still hide a stale forecast or a single broken peak interval; drill down before concluding.
In the field
A leader reviewing scheduling across sites before a QBR: the dashboard frames coverage, violations and timeliness, while the CSM is clear these are planned measures, with delivery confirmed in RTA.
Practical task
On the demo dashboards, scope to a team and period and write a three-line read: one strength, one thing the roll-up might be hiding, and the forecast-version check you would make.
Self-check
The scheduling dashboard is all green. Does that mean service was good?
No. It shows planned scheduling health against the forecast, not delivery. Actual service is confirmed in RTA and output. And green can still hide a broken peak - drill down.
Why can a healthy coverage KPI still be wrong?
Because coverage is planned against a forecast. If the forecast version is stale, the KPI is confidently measuring the wrong demand.
What does a falling schedule-stability KPI suggest?
Excessive churn after publication, usually signalling a weak forecast or an unowned change process worth investigating.
Verified vs demo. Screen is live in the demo at /#/dashboards; exact controls, labels and figures are SME-validation-pending.