Data Editor
The interactive map and region table: see your service area geographically, reassign postal areas, and correct metric values.
The Data Editor at /home/<team>/monitoring/map is where you see your service area properly and where you fix the region structure when it does not match how you actually operate.
It appears in the sidebar only once the team has a data source connected.
What is on the page
The map. Canadian postal areas drawn as polygons and shaded by whichever metric you have selected. Darker means more.
The metric overlay control. Switches which metric is being coloured. Changing the overlay is the fastest way to spot a problem — a region can look fine by client count and badly off by hours.
The boundary toggle. Switches between drawing region boundaries (regions as single shapes) and postal code boundaries (each area outlined individually). Region view is for seeing overall shape; postal code view is for working out which specific areas to move.
The region data table. Every region and area with its metric values, in sortable form. This is where you read exact numbers rather than shading.
Distribution charts. How your metrics are spread across regions, so you can see imbalance as a distribution rather than as a map.
Reassigning areas
Select an area and assign it to a different region.
This is the core operation of the page, and it is what you do when the region structure the platform discovered does not match your operational reality — a territory your source system records one way that your teams actually work another way.
Work in postal code boundary mode when you are doing this, so you can see exactly which areas you are moving.
Editing metric values
Metric cells in the table are editable.
Use this to correct a value you know to be wrong, or to model the effect of a change before it happens in your source system.
Optimal Workforce reads from your scheduling or HIMS platform and never writes back to it. Anything you change here — an area's region, a metric value — stays inside Optimal Workforce.
For an API source, that also means your edits are working values only: the next daily sync replaces metric values with what the vendor reports. If a number is wrong at source, fix it at source.
Undo and redo
Every change is tracked, and you can step backwards and forwards through them with the toolbar controls or the usual keyboard shortcuts. Experiment freely — you can always get back.
Configurations
The map can be pointed at a saved configuration rather than live data, which is how you review a scenario you built in the Preview Sandbox or a set of regions that came out of an optimization run.
Uploading from here
If the team uses a CSV source, there is an upload action on this page so you can refresh the data while you are already looking at it.
How to use it well
Start in region boundary mode with your primary metric. Get the overall shape before you look at detail.
Then switch metrics. Balance by client count and balance by hours are different pictures, and the difference between them is usually the interesting part.
Look for shapes, not just colours. A region that wraps around another, or one that reaches across a natural barrier, costs travel time regardless of how even its numbers look.
Check the small areas. Areas with one or two clients are usually mistyped postal codes. See Understanding Your Data.
Fix the structure before you optimize. An optimization run takes your region definitions as its starting point. If those are wrong, the result will be a very carefully computed answer to the wrong question.
Next
- Model a bigger change without touching live data: Preview Sandbox
- Let the platform propose a structure: Running an Optimization
- Get told when a region drifts: Alerts