Every mile your technician drives to the next job is a mile you are paying for without billing a customer. For an HVAC company running 8 technicians, inefficient routing can easily cost $150,000+ per year in avoidable drive time — and that number goes up fast during peak season when every available hour matters.
Dispatch optimization is the discipline of assigning and routing technicians so they complete the most work in the least windshield time. This guide covers how it works, what tools enable it, and how to calculate whether the investment makes sense for your operation.
TL;DR
- The average HVAC technician spends 18–22% of their day driving between jobs — optimization targets cutting this to 10–14%
- A single recovered daily job slot per tech, multiplied across a 6-person team, adds roughly $180,000+ in annual revenue capacity
- AI-assisted dispatch routes account for live traffic, technician location, and skill requirements simultaneously — something no human dispatcher can do at scale
- Emergency call insertion is where dispatch software pays for itself fastest: filling gaps without disrupting the rest of the board is a 5-second software task versus a 20-minute manual exercise
- For the full HVAC operations picture, see our HVAC software guide
What Dispatch Optimization Actually Means
"Dispatch optimization" is used loosely in software marketing. For practical purposes, it means three distinct things:
Geographic routing. Assigning each new job to the technician who can reach it fastest from their current location — not their home address, not the office, but wherever they are right now.
Job sequencing. Ordering a technician's jobs for the day to minimize total drive time across all stops, not just the first job of the morning.
Dynamic re-routing. Adjusting routes in real time as jobs are added, completed early, or delayed — without requiring a dispatcher to manually reconstruct every tech's day.
Most HVAC companies are doing the first one manually (with varying accuracy) and ignoring the second and third. Software handles all three simultaneously.
The Math on Drive Time
Before investing in optimization software, it is worth grounding the ROI claim in real numbers.
Baseline assumptions:
- 8 technicians, 8-hour days
- Average job duration: 1.5 hours (mix of maintenance and repairs)
- Current average drive time: 20% of the day = 96 minutes/tech/day
- Target drive time with optimization: 12% = 58 minutes/tech/day
Time recovered per tech per day: 38 minutes
Jobs recovered per tech per day: 38 minutes ÷ 90-minute average job = ~0.4 jobs
Revenue impact: 0.4 jobs × $160 average ticket × 8 techs × 220 working days = $112,640/year
That is a conservative estimate. If your average ticket is higher, if you run more technicians, or if your current routing is particularly inefficient, the number scales upward quickly.
The Four Layers of Modern Dispatch Optimization
Layer 1: Real-Time Technician Location
You cannot optimize routes without knowing where your technicians are. GPS tracking — either dedicated vehicle hardware or app-based location sharing — feeds the dispatch board with current positions. This replaces the "call the tech and ask where they are" workflow that consumes 30–50 minutes of dispatcher time per day on a busy operation.
GPS data also enables after-the-fact analysis: which routes ran long, which technicians consistently have excessive drive time, which service areas are underserved relative to call volume.
Layer 2: Skill-Aware Assignment
Not every job can go to every technician. Commercial rooftop units require different certifications and experience than residential split systems. Boiler service is not the same as refrigerant work.
Dispatch optimization software maintains a skills profile for each technician and filters assignment candidates automatically. The dispatcher sees only eligible technicians for each job type — eliminating the training overhead of managing this manually.
Layer 3: Traffic-Aware Travel Time
Driving 10 miles through a suburb at 10 AM takes 18 minutes. Driving the same route at 4:45 PM takes 42 minutes. Routing software that uses static distance rather than live traffic underestimates afternoon travel time by 40–60% in metro areas.
Real-time traffic integration ensures your board shows accurate arrival windows — which means fewer "tech is running late" calls and more accurate customer ETAs.
Layer 4: Emergency Job Insertion
This is where optimization software proves its value most clearly. When an emergency call comes in at 1:30 PM, the dispatcher needs to:
- Identify which technicians are currently available or finishing soon
- Determine which tech can reach the emergency address fastest
- Assess whether inserting the emergency job will delay other customers unacceptably
- Notify affected customers of any time changes
- Update the board
Manually, this process takes 15–25 minutes and usually results in one or two customer callbacks. Software-assisted, it takes 30–60 seconds.
See how AI handles the intake side of emergency calls in our post on HVAC emergency call handling.
Common Dispatch Mistakes That Cost HVAC Companies Money
Starting the day from home address. Most companies route the first job of the day based on proximity to the technician's home. This is fine. But if that tech's last job is at the far end of the service area, routing the first job of the next day from home again adds unnecessary early-morning drive time. Software tracks where each tech ends their day and builds the next morning's first assignment accordingly.
Ignoring job duration variance. A maintenance visit takes 45 minutes. An installation takes 4–6 hours. Scheduling software that treats all jobs as equal-length creates cascading delays when a long job is underestimated. Good platforms use historical job duration data to build realistic buffers.
Over-concentrating techs in the same zone. When multiple calls come in from the same neighborhood, it is tempting to cluster your whole crew there. Optimization software balances geographic coverage so the rest of your service area is not left dark.
Manual emergency re-routing. The dispatcher who manually reconstructs five technician schedules after an emergency insertion will make mistakes and lose time. Automate this.
Evaluating Dispatch Software
When demoing platforms, test these specific scenarios:
- Drop a new emergency job 30 miles from your nearest technician — how long does it take the system to surface a recommendation?
- Add a job to a fully-booked day — does the system suggest the least-disruptive insertion point or just block you?
- Simulate a tech calling out sick at 7 AM — how quickly can the board be redistributed?
The full HVAC software evaluation framework is in our HVAC software guide. For AI-specific dispatch capabilities, see the AI dispatch guide.
Frequently Asked Questions
Does dispatch optimization software require GPS hardware in every vehicle? Most modern platforms offer app-based location tracking that works on the technician's existing smartphone, eliminating the need for dedicated vehicle hardware. App-based tracking is accurate enough for routing purposes and costs nothing beyond the software subscription.
What happens when a technician's app is turned off or loses signal? The platform should fall back to the last known location and flag the technician as "location unknown" on the dispatch board. Dispatchers can manually override the position or contact the tech via the platform's messaging system.
How much setup time is required before dispatch optimization works well? Most platforms deliver meaningful routing improvement immediately — the algorithms work even without historical data. Skill profiles, service area boundaries, and job type configurations take 1–2 days to set up correctly. Full optimization, informed by historical job duration data, typically improves over the first 60–90 days of operation.
Next Steps
Dispatch optimization is one of the highest-ROI investments an HVAC company can make — the payback period is typically measured in weeks, not months. Start with a dispatch audit: track your current average daily drive time per technician for one week, then use that baseline to quantify improvement after implementing optimized routing.
See full platform options at /hvac or read the broader HVAC software guide.