How to Know If Your HVAC Dispatching Is Costing You $10K/Month
Dispatch is the one operational function that touches every other efficiency metric in your business. A dispatcher who sends the wrong tech to the wrong job doesn't just cause one inefficient call — they trigger a chain of downstream costs: longer cycle times, higher callback rates, lower average tickets, and lower revenue per truck per day. Yet in most HVAC businesses under $3M, dispatching is done by feel, managed reactively, and never measured.
This article gives you the five metrics that expose dispatch inefficiency, the 2025 benchmarks for each, and the four specific dispatch decisions that generate the most margin loss — all translatable into a dollar figure you can verify against your own numbers in about 20 minutes.
Why Dispatch Loss Is Invisible
Bad dispatching doesn't show up as a line item anywhere. There's no "dispatch inefficiency" category in QuickBooks. What shows up instead are the symptoms: a technician who runs 3 calls on a day the schedule showed 6, an afternoon of no-revenue drive time nobody noticed, a senior tech who spent Tuesday doing maintenance visits while a junior tech struggled through a complex diagnostic two zones over. Each of these has a dollar value. None of them get measured.
The core problem is that dispatching in most small HVAC operations is optimized for one variable: who's available right now. Availability is visible. The dispatcher can see it on the board. What they can't see — without a deliberate measurement system — is skill match, route efficiency, revenue yield per tech, and the downstream cost of each mismatch decision they make throughout the day.
"I finally sat down and tracked my lead tech's day in 15-minute increments for a week. He was billing about 4.5 hours out of a 9-hour day. The rest was drive time, waiting on customers, part runs, and admin. When I saw that number I almost couldn't believe it. I was paying a $32/hr tech to drive and wait half his shift." — HVAC owner, 5 trucks, $1.6M revenue
The 5 Dispatch Metrics That Expose the Leak
Find out which dispatch metric is your primary margin leak — in 8 minutes.
MarginPlug's Delivery pillar benchmarks your revenue yield per dispatched hour, drive time ratio, and first-call completion rate against operators at your revenue level, then identifies the specific dispatch decision pattern driving your loss.
Run the free diagnostic Free during beta · No credit card · 8 minutesWhat Poor Dispatch Actually Costs: A 4-Truck Example
Let's put a number on it. A 4-truck operation running 220 days per year with an average dispatch utilization rate of 62% instead of the 74% top-quartile benchmark. That 12-point utilization gap on 4 techs dispatched 9 hours per day works out as follows:
At 50% gross margin, that $319,000 in unrealized revenue represents $160,000 in gross profit that doesn't require a single new customer, new truck, or marketing dollar to capture — just a more deliberate dispatch process. Even if you assume a 35% capture rate on recovered capacity (demand is the constraint, not just time), that's still $56,000 in annual gross profit from fixing a process problem that costs almost nothing to implement.
The 4 Dispatch Decisions That Generate the Most Loss
The dispatcher sees that Tech A finished a call in the north end of the market and Tech B is available in the south. A new call comes in from the center of the market — 12 miles from Tech A, 14 miles from Tech B. The dispatcher assigns it to Tech B because they just came back from a short call and seem "fresher." Neither assignment is optimized for geography. Over the course of a day, 6–8 of these decisions add up to 30–50 miles of excess driving per tech — an hour or more of unpaid windshield time that could have been a billed call.
Geographic routing means sequencing calls so that each tech's day forms a logical geographic cluster, not a scattered pattern across the whole service area. It requires looking 2–3 calls ahead on the schedule, not just the next assignment. In dense markets, geographic dispatch consistently produces 15–20% better utilization than availability-only dispatch, with no change in tech count or marketing spend.
A senior technician completing a routine maintenance visit generates the same revenue as a junior tech completing the same visit — but costs significantly more in fully-loaded labor and represents capacity that could have been producing a $600–$1,200 complex diagnostic or replacement call instead. Every hour a senior tech spends on a call a junior tech could handle is an hour of senior capacity consumed at junior revenue yield.
This happens because dispatchers default to the most experienced available tech when calls come in — it feels safer. The customer gets a great tech, the call goes smoothly, and nobody complains. The cost is invisible: the senior tech ran 4 maintenance visits instead of 2 diagnostics and a repair, and the revenue gap between those two days is $800–$1,400 on a single technician's schedule.
In most small HVAC operations, the morning fills up — customers call the night before, agreements get scheduled, the day looks good at 8am. By 1pm, two techs have finished their morning calls and the afternoon schedule has gaps. The dispatcher starts making calls to fill in, but by then the urgent customers from 10am have already called someone else. The techs drift into unproductive time — supply runs, shop time, the second call of the day getting stretched because there's no pressure to move.
The fix is proactive same-day scheduling, not reactive. Every operation with a service agreement base has the capability to schedule agreement visits on short notice — they're customers who already said yes and are expecting a call. Agreement visits can fill afternoon gaps profitably and efficiently without any marketing spend.
Dispatching is managed in real time, under pressure, with incomplete information. Every decision feels reasonable in the moment because it's based on what's visible right now — who's available, where they are, what the customer needs. The problem is that individual dispatch decisions that feel reasonable in isolation can produce systematic patterns over time that significantly erode efficiency. Without reviewing dispatch decisions after the fact, these patterns never get identified or corrected.
The dispatcher who sends senior techs to maintenance calls 40% of the time doesn't know they're doing it at that rate — they're making individual decisions, not tracking patterns. A weekly dispatch review that takes 20 minutes and looks at three numbers — drive time ratio, skill match rate, and daily utilization by tech — will surface these patterns within two to three weeks and give the dispatcher specific behavior to change rather than general feedback to "route better."
Your 20-Minute Dispatch Audit
You don't need new software to run a basic dispatch audit. Pull the last 30 days of completed jobs from your service platform. For each tech, calculate: total hours on the clock versus total billable hours recorded. The gap is non-billable time — drive time, waiting, admin, and idle. Divide non-billable by total hours to get your non-billable ratio. Subtract from 100% to get your utilization rate.
If your service platform records GPS mileage or job location, map three days of calls for your most and least efficient techs side by side. The geographic pattern difference is usually immediately visible — one tech's calls cluster, the other's scatter. That scatter is your drive time ratio problem made visual.
Compare your utilization rate to the benchmarks in the table below. Every point below 72% is capacity being consumed by non-billable time. At your average revenue yield per hour, calculate the annual cost of that gap. That's your dispatch efficiency number — the amount you're leaving on the table from the current process, measurable in 20 minutes, fixable without a dollar of capital investment.
| Utilization rate | Revenue yield / dispatched hr | Annual cost vs. 74% benchmark | Assessment |
|---|---|---|---|
| 74–80% | $185–$260/hr | At or above benchmark | Focus on skill match and call mix optimization |
| 66–73% | $140–$185/hr | $45K–$120K/yr lost | Route clustering and fill list will recover most of this |
| 58–65% | $100–$140/hr | $130K–$240K/yr lost | Geographic routing and skill match both broken |
| Under 58% | Under $100/hr | $250K+/yr lost | Dispatch is the primary margin constraint in the business |
Know your dispatch efficiency number — and what closing the gap to benchmark is worth annually.
MarginPlug's Delivery pillar calculates your revenue yield per dispatched hour, benchmarks your utilization rate, and identifies which of the four dispatch failure modes is your primary driver. Free during beta.
Run the free diagnostic Free during beta · No credit card · Results in minutes