How a Dispatch Board Works
A calendar tells you what was booked. A dispatch board tells you whether today is going to hold — and it has to do that in about three seconds, because that is all the attention a dispatcher has to spare at 10am.
A dispatch board is a grid: technicians across one axis, time along the other, jobs as blocks inside it. Its job is to answer three questions instantly — what is unassigned, what is at risk, and who is free.
If your board cannot answer all three at a glance, it is a calendar with colours.
This is the interface layer of stage five in how scheduling software works. Here we look at the board itself.
Anatomy of a board
The three questions, and how the board answers them
What is unassigned?
The queue on the left holds work that has come in but has no technician. It should never be a separate screen — if a dispatcher has to click away to see unassigned work, jobs sit there unnoticed.
Each card in the queue needs three things visible without opening it: the job type, any promised arrival window, and priority markers such as agreement status. The card for an agreement holder with no cooling should look different from a flexible maintenance visit, because they demand different urgency.
What is at risk?
This is what separates a board from a calendar, and most shops underuse it.
“At risk” means a job that is still scheduled but probably will not be met — because the technician assigned to it is currently running over on the job before. On the board above, Dee is 52 minutes past her expected finish, so her 2pm appointment is flagged before anyone has called to complain.
A good board derives this automatically by comparing elapsed time against expected duration and projecting forward. A weak one requires the dispatcher to work it out by mental arithmetic, which under pressure means it does not get worked out at all.
Who is available?
Gaps have to be visible as gaps. Sal’s empty afternoon block reads as capacity, not as blank space — with the duration stated, because “free” is only useful if you know for how long.
Availability is more than an empty slot, though. A technician is available for a job only if they hold the required certification and can physically reach the address in time. That is why skill tags belong in the column header: Sal’s commercial certification is why the rooftop unit went to him and not to Ray.
Reading the states
| State | What it means | Set by |
|---|---|---|
| Scheduled | Assigned, not yet started | Dispatcher |
| En route | Technician is driving | Technician, in the app |
| On site | Work in progress | Technician |
| Overrunning | Elapsed time exceeds expected duration | System, automatically |
| At risk | A later job is threatened by a current overrun | System, automatically |
| Complete | Work order closed | Technician |
Notice which states the system sets and which the technician sets. Two of the six are derived automatically — and they are the two that make the board useful. Both depend entirely on technicians updating the other four honestly.
“Overrunning” and “at risk” are calculated from the timestamps a technician creates when they tap en route, on site and complete.
If a technician marks four jobs complete at 5pm because they forgot all day, the board showed fiction for eight hours. It did not report an error — it reported confidently wrong information, which is worse.
What drag-and-drop actually does
Moving a job block looks like editing a calendar. Underneath, a well-built system does several things at once: it re-sequences that technician’s remaining route, recalculates whether promised arrival windows still hold, checks the certification requirement against the new technician, and flags anything that has become at risk as a result.
That last part matters. Reassigning a job to solve one problem frequently creates another two stops down the day, and a board worth using tells you before you drop it rather than after.
This is a good question to put to any vendor during a trial: drag a job from one technician to another mid-afternoon and show me everything that changes. The answer separates a live board from a visual calendar quickly.
Day, week and map views
Day view is the working screen. It is where dispatch actually happens and where a dispatcher spends the morning.
Week view is for planning, not dispatching. It is where maintenance visits get placed and where you notice that Thursday is empty while Tuesday is overloaded.
Map view is for one specific question: who is nearest to this address right now. It is invaluable for emergency insertion and misleading for anything else, because proximity is not the same as availability. The nearest technician may be nearest precisely because they are stuck on a long job.
Configuration mistakes that make a good board useless
Too many technicians on one screen. Past ten or twelve columns, nothing is readable and the dispatcher scrolls sideways all day. Split by team, zone or trade.
Colour coding by job type instead of by state. Job type is useful information, but state is the urgent information. If your colours tell you what kind of work it is rather than whether it is in trouble, the board has stopped answering question two.
No visible arrival windows. A dispatcher moving jobs without seeing which have promised windows will break promises without knowing it.
Skill tags left unconfigured. If certifications are not in the system, the board will happily let you assign a commercial refrigerant job to someone who cannot legally perform it.
Frequently asked questions
What is the difference between a dispatch board and a calendar?
How many technicians can one dispatcher handle?
What does “at risk” mean on a dispatch board?
Should I use map view for dispatching?
Why does my dispatch board show wrong information?
Do I need a dispatch board with four technicians?
What to do next
- Check whether your current board answers all three questions without clicking away from one screen. If unassigned work lives elsewhere, that is the first fix.
- Switch your colour coding to state rather than job type if it is not already.
- Confirm skill tags and certifications are configured for every technician. Most shops set this up once and never revisit it after someone qualifies.
- In any trial, drag a job between technicians mid-afternoon and ask the vendor to show you everything that recalculates.
- How HVAC scheduling software works — the nine stages behind the board
- Capacity planning for HVAC businesses — deciding what the board is allowed to hold
- Scheduling & Dispatch — routing, arrival windows and mobile apps
The board illustrated here is a composite showing features common to field service dispatch interfaces, not a screenshot of any specific product. Layout, colour conventions and available states vary between platforms — check how a given system handles derived states such as at-risk flagging before assuming it does.