Monitoring
See how caseload is distributed right now, correct the picture where it is wrong, and get told when a region drifts.
Monitoring is where operations teams spend most of their time. It answers three questions:
- What does my caseload distribution look like right now? — the Caseload Dashboard.
- Is that picture actually right, and can I fix it where it is not? — the Data Editor.
- How do I hear about drift without watching a screen? — Alerts.
Why distribution drifts
Nobody sets out to build an unbalanced caseload. It happens because the inputs move and the boundaries do not:
- Clients are admitted and discharged in different places at different rates.
- Staff join, leave, and change availability.
- Referral patterns shift with demographics and with what other providers in the area are doing.
- Territory boundaries were drawn at a point in time and have not been revisited.
The result compounds quietly. One region absorbs a few more clients each month until, a year later, it is carrying half again what its neighbours carry — and that shows up as overtime, missed visits, and turnover long before anyone attributes it to geography.
What imbalance costs
- Travel. Territories that no longer match where clients actually are mean more driving and less time delivering service.
- Overtime. An overloaded region is an expensive region.
- Turnover. Sustained overload is one of the most reliable predictors of staff leaving, and replacing a worker costs far more than rebalancing a boundary.
- Service quality. Missed and cancelled visits concentrate where capacity is thinnest.
A working rhythm
Daily — glance at the dashboard. Check the freshness indicator and whether any alerts have fired.
Weekly — look at trends rather than levels. A region that has moved steadily in one direction for a month matters more than one that spiked yesterday.
Monthly — open the map. Ask whether the region structure still matches how you actually operate, and whether it is time to model a change in Preview or run a Balance job.
Quarterly — produce a report. It gives you a dated record of where things stood and makes the effect of what you changed visible.
Before you trust the dashboard
Check the data freshness indicator, and if anything looks surprising, check the sync history. See Sync and Data Freshness.