Route planning is the operational lever most HVAC contractors underestimate. Every hour a technician spends behind the wheel rather than on a service call is an hour the business pays for in labor cost without booking any revenue against it, and the cumulative drag of weak routing across a year is the single biggest unforced productivity loss most field service operations absorb. A working routing function turns the same fleet of trucks and the same roster of technicians into measurably more daily revenue, which is why the contractors who treat routing as a real operational discipline rather than an afterthought consistently out-earn the ones who let dispatchers wing it from a paper schedule.
The sections below cover why routing drives profit, the working stages of the routing workflow, the curveball scenarios that test the routing operation, the best-practice habits that separate strong routing from weak, the dollar math of routing discipline, and the software that makes all of it run.
Why Routing Drives Profit
Field service technicians produce revenue when they are on a job, and they produce zero revenue when they are driving between jobs. The ratio between those two states is what determines the daily revenue per truck, and that ratio is almost entirely a function of how well the routing function runs. A technician who spends three hours of an eight-hour day driving has only five hours to bill, while the same technician with one hour of total drive time has seven hours to bill. The same person, the same skill, the same truck, and the difference is two billable hours a day from routing alone, which is why revenue per truck day is the operational metric that exposes routing weakness fastest.
The compounding effect runs through the rest of the operation too. Better routing means lower fuel costs, less vehicle wear, less overtime when technicians push to finish the day's schedule, and a tighter ETA window the office can promise customers. The same dispatch operation that manages the routing function manages the customer-experience promises that come with it, which is why routing improvements show up across multiple operational metrics rather than just one.
The Routing Workflow
A working HVAC routing operation runs through five sequential stages on every shift. The stages are not optional; weak operations skip one or two and absorb the cost in inefficiency. Job intake is where the dispatcher gathers the day's confirmed appointments, recurring maintenance visits, and incoming service calls into a single working list with addresses, time windows, and technician skill requirements attached to each job.
Geocoding converts the addresses into mappable points so the routing logic can actually calculate distances between them. Tools like Google Maps handle this for one-off dispatchers, but a working FSM platform geocodes addresses automatically when the customer record is created. Clustering groups the day's jobs by geographic proximity so each technician's day stays within a contiguous service area rather than bouncing across town. Strong clustering accounts for the technician's home base, the customer's time window, and the equipment loadout each job requires.
Sequencing orders the jobs within each cluster to minimize total drive time, accounting for traffic patterns, one-way streets, parking availability, and the time-window constraints customers booked into. Dispatch sends the sequenced route to the technician with the right job notes attached, often through the work order document the technician will reference on site, plus a communication channel open back to the office so the technician can flag delays and the dispatcher can rebalance the schedule mid-day if something changes.
Handling Routing Curveballs
The cleanest routing plan survives until the first curveball, which usually arrives by 9:30 in the morning. The strong routing operations have explicit playbooks for the three most common scenarios. Emergency calls come in during the day and force the dispatcher to find the technician closest to the emergency address with the right skill set and the right parts on the truck, then rebalance the rest of that technician's day around the inserted call. The dispatchers who handle emergency insertion well are working from a live routing view, often surfaced through the same communication discipline that keeps the technician informed in real time, rather than from a printed paper schedule.
Technician called off on the day of the schedule means the dispatcher has to reassign the entire day's jobs across the remaining technicians, ideally re-optimizing the new routes rather than just dropping the missing technician's jobs onto whoever has open slots. Traffic and weather events compress the day's productive hours and require the dispatcher to push the least-time-sensitive jobs forward and prioritize the customers with the tightest time windows. The dispatchers who run these scenarios well lean on the live ETA feed from the field rather than guessing at how long jobs are actually taking.
Best Practices for Routing
The habits that separate strong routing operations from weak ones are mostly small and consistent rather than dramatic. Capture the job-specific information at intake (equipment type, access notes, customer time window) so the routing logic has real constraints to work with, not just addresses. Use the technician's home as the route start and end point rather than the shop, because the morning drive from home to the first job and the evening drive from the last job to home are real time the office should be optimizing. Cluster geographically before sequencing within the cluster, because trying to optimize the whole day at once usually produces a worse result than optimizing two or three clusters separately.
Schedule similar work types together on the same technician when the skill mix allows it, because the technician running three air conditioner tune-ups in a row works faster than the same technician toggling between heat pump install, gas furnace service, and a refrigerant leak hunt. Run the post-shift retrospective on actual drive time versus planned drive time at least weekly, because the data feeds the routing model with the realism that lets it tighten the next week's schedule. Pair the routing discipline with the broader operational KPIs the business tracks so the routing function gets reviewed alongside first-time fix rate and revenue per truck day rather than in isolation.
The Math of Routing Discipline
The dollar value of better routing is concrete enough to estimate. A residential HVAC technician billing at $150 to $200 per hour for service work who recovers one additional billable hour per day from tighter routing adds $750 to $1,000 per week to the business, or $37,500 to $50,000 per year per technician. A five-truck operation that runs the same improvement across the team adds $187,500 to $250,000 per year in margin, which is the entire annual salary of a strong dispatcher and the FSM subscription combined, several times over.
The fuel and vehicle-wear math runs in the same direction. A technician driving fifteen fewer miles a day at $0.70 per mile in fuel and maintenance saves $10.50 a day, $2,625 a year per technician, and that money never shows up in the P&L as a line item because the savings come from costs the business avoided rather than revenue it booked. The reporting layer the business runs is where the savings get surfaced, which is why measurement matters as much as the routing decisions themselves. Strong routing also feeds the lead generation side because the technicians who finish on time produce the five-star reviews that drive the next month's organic leads.
Smart Service for HVAC
If you are running an HVAC business and want a software stack that handles scheduling, dispatch, customer history, mobile invoicing, recurring service contracts, and the route optimization that turns drive time into billable time, Smart Service integrates with QuickBooks Desktop and QuickBooks Online and the iFleet mobile app keeps techs in the field synced with the office. Try a free demo to see how it fits!
