In this post
# HVAC Dispatch vs Scheduling: What's the Difference?
Contractors evaluating software often describe the same symptom — "our scheduling is a mess" — while meaning two completely different problems. One has a planning problem. The other has an assignment problem. They need different fixes, and buying the wrong one is expensive.
The short version
| Scheduling | Dispatch | |
|---|---|---|
| Question | Who works where, and when? | Which technician takes this job, and how do they get there? |
| Horizon | Days to weeks ahead | Now, or within hours |
| Deals in | Capacity, windows, durations | Skills, location, current status |
| Output | A calendar | A decision |
| Done by | Office, often in advance | Dispatcher, continuously |
| Fails as | Overbooked Tuesday, empty Thursday | Wrong technician, long drive, callback |
Scheduling
Scheduling is planning. It asks what the week can hold and commits appointments into it.
The decisions are about capacity and time: how long this job type takes, how much of the day is actually bookable once travel and admin come out, which windows to promise, where the maintenance visits go, how much slack to leave for the emergency that is coming.
Scheduling failures are shape failures. Tuesday is booked to capacity and Thursday has three empty afternoons. Every job is booked at two hours regardless of type. There is no slack, so Wednesday's no-heat call displaces a customer who took a morning off work.
You notice a scheduling problem at the end of the week, in the aggregate.
Dispatch
Dispatch is operational. It takes the schedule as it exists and makes assignment decisions against what is actually happening.
The decisions are about matching: who holds the skill, who is free, who is nearest right now, whose day has room. When the schedule and reality diverge — and they always do — dispatch is what absorbs it.
Dispatch failures are individual job failures. A technician sent across the county past two colleagues. Someone without the right ticket producing a callback. A customer ringing the office three times because nobody can tell them where the technician is.
You notice a dispatch problem one job at a time, all day.
How they fail each other
Good schedule, bad dispatch. The calendar is sensible and full. Then the day starts, an emergency arrives, and assignments get made by whoever answers the radio. Technicians criss-cross a territory that was clustered when it was planned. The schedule was fine; nothing enforced it.
Bad schedule, good dispatch. A sharp dispatcher making the best available call all day — on a schedule that overbooked Tuesday and left Thursday half empty. They are absorbing a planning failure with constant manual effort, and they will burn out.
Both bad. The common case, and it is usually diagnosed as a people problem when it is a systems problem.
Which one do you actually have?
A rough test.
Symptoms of a scheduling problem
- Days are wildly uneven across the week
- Jobs routinely overrun and the day slides
- Emergencies always displace booked customers
- Nobody can say what capacity is left before booking
- Maintenance visits pile into the same two days
Symptoms of a dispatch problem
- Technicians pass each other going opposite directions
- Callbacks because the wrong person went
- The office cannot say where anyone is without ringing them
- Reassignments take a series of phone calls
- The nearest technician is regularly not the one sent
If you recognise the first list, a calendar with better discipline gets you a long way. If you recognise the second, you need a dispatch board and live technician status — a calendar cannot give you those.
Most growing contractors eventually recognise both.
They share one dataset
The reason these are usually sold together is that they run on the same information, and separating them creates a reconciliation problem.
Both need: job duration by type, technician skills, technician availability, customer address, appointment window, priority.
Scheduling uses those to decide what can be committed. Dispatch uses them to decide who goes. If the schedule lives in one tool and assignments happen in another, someone spends their day keeping the two in agreement — and that person is the system.
See both in one place → The demo has a scheduling calendar and a dispatch board over the same jobs. Move something on either and the other reflects it.
Where the words get used loosely
"Dispatch board" usually means the operational view — jobs grouped by status, movable between them. That is dispatch.
"Scheduling software" in marketing usually means both, because tools that do one and not the other do not sell well.
"Field service management" means both plus work orders, invoicing and inventory.
None of that matters much, as long as you are clear which of your own problems you are trying to fix before you sit through a sales demo.
Related
- HVAC Dispatch Software → — the complete guide
- HVAC Scheduling Software → — building the week
- How to Schedule HVAC Technicians Efficiently →
Not sure which of these is your bottleneck? That is a useful first conversation. Talk to BDEVY →
hvac scheduling hvac dispatch software hvac service management software