HVAC Dispatch Routing: A Busy Truck Isn't a Full Schedule

Dale Whitmore looks at five moving trucks and a crowded board. “We're slammed. We need more people before we can do more work.” Across four surrounding counties, a day spent on the road can look like every available hour is already earning.

Movement is not completed work.

Dale is our illustrative five-technician owner in Springfield, Missouri, not a client case study. During his ride-along with Marco, six calls were planned. Four billable calls were completed in nine hours. Forty minutes went into reaching the first stop. Twenty-five went into a supply-house visit.

That night, the subtraction went onto a legal pad. His established weekly example leaves about 117.5 billable hours and roughly 45 usable jobs, rather than the 65 he schedules against. Routing asks which part of that lost time can actually be changed.

Where did the drive time actually go?

Pull a few recent days from dispatch and the technicians' work records. Use departure, arrival and job-completion times where available. Ask the crew about gaps rather than treating every unexplained minute as waste.

Separate five categories: travel needed to reach customers, avoidable crossings of the territory, parts collection, waiting for access or instructions, and work performed on site. A supply-house visit may look like travel but need a stocking or parts-readiness fix. A late departure may begin with a job estimate that was too short.

The BLS description of HVAC technician work includes assignments at multiple locations and travel between sites. Travel belongs in the plan. That source does not establish a universal percentage you can recover through better routing.

Use your true weekly capacity calculation to keep those categories connected to the hours you can actually sell. Compare similar work types and days before deciding a route was inefficient.

Dale's forty-minute first leg is not automatically avoidable. The twenty-five minutes at the supply house may involve a different decision altogether. The pad becomes more useful when each subtraction has a cause, rather than one large label called windshield time.

How do you cluster the territory without breaking appointment promises?

Draw a simple map of the area you already serve. Group nearby addresses into practical zones using actual travel paths. A river crossing, highway bottleneck or rural road can matter more than the distance between two pins.

Then put constraints beside each job before rearranging anything:

• The arrival window already promised, and whether the customer has agreed to flexibility.
• The required technician, skills, equipment and crew size.
• Expected on-site time and a sensible allowance for uncertainty.
• Parts readiness and any unavoidable pickup.
• Travel from the previous job and onward to the next commitment.

Cluster compatible flexible work around fixed commitments. Do not move a promised morning visit into the afternoon because it makes a prettier route. Ask before changing an agreed window, and tell the customer what is changing.

For routine work that has not been booked, offer windows that help the route. A maintenance customer with flexibility may suit a zone day. A homeowner with a failed system may need a different decision. Geography is one constraint, not the only one.

Make the intake offer usable: “We have [available window] for that area; would it suit you?” The office should not invent a zone-day promise before checking technician availability.

Dale's board records when a customer was booked. He also needs it to show a plausible sequence. Six appointments written in order of arrival are not yet a route a technician can complete.

What changes when an urgent call lands across town?

Give dispatch a rule for breaking the geographic plan. Use your approved urgency and service-eligibility process, then identify the next feasible arrival from a technician who can do the work.

That is not always the truck nearest the pin. That technician may lack the required skill or part, be midway through work they cannot leave, or owe another customer a firm arrival window.

Before moving a job, write a short exception note:

• New request: location, work type and assessed priority.
• Feasible responder: technician or crew, current commitment and earliest realistic arrival.
• Tradeoff: extra travel, delayed visits or buffer consumed.
• Decision owner: who approves the change and contacts affected customers.
• Next update: when dispatch checks the revised plan again.

Sometimes the right choice adds miles. Record the reason so the end-of-day review does not call a justified response a routing failure. Sometimes the honest answer is a later appointment than the caller wanted. Do not promise immediate dispatch because a map shows an apparently nearby truck.

Dale's ride-along included eighteen minutes in a driveway while the office untangled a double booking. Geographic clustering alone would not have fixed that. Clear authority and an updated board matter when the plan changes after the first truck leaves.

What does fifteen minutes saved really add up to?

Put the unit beside the number. “Fifteen minutes per technician” is incomplete until you say whether it is per day or per week.

Here is a planning illustration, not a measured improvement in Dale's shop. Assume five technicians each have five working days where a genuine fifteen-minute travel saving is available.

The last row is not six hours. The time period changes the answer by a factor of five.

Count the actual technician-days where a saving is possible. Do not multiply by twenty-five automatically when some people spend the week at one installation or are unavailable. Check that the route change did not simply move the travel into another part of the day.

Recovered minutes are not automatically extra jobs. They may be scattered across people, appear too late for a usable appointment, or provide needed room for an overrun. Leave your scheduling buffer intact. A new job also needs the right technician, enough continuous time and a customer who can accept the window.

Dale's roughly 45-job example does not become a larger promise because the arithmetic produces 6.25. He has a possible time saving to test. He still needs to see where that time lands on the board.

How do you avoid spending the same technician hours twice?

Use one person-hour ledger for service and install, even if you display two boards. A technician assigned to an installation is unavailable for service during those same hours.

Take a separate daily example. Five people scheduled for eight hours provide 40 gross person-hours. Suppose two of them share a four-hour installation, with thirty minutes of round-trip travel per person.

That commitment uses 2 × (4 + 0.5) = nine person-hours. Forty minus nine leaves 31 gross person-hours unallocated, before other travel, meetings, breaks, documentation and existing work. It does not leave 31 billable hours.

Do not record the installation as four hours in one board, leave both people available for eight hours in the service board, and then add the apparent openings together. Count the travel once in the same ledger, using the same unit.

Service and install capacity requires this distinction. Crew hours describe how long the job occupies a crew; person-hours describe how much of your total labor it consumes.

Maintenance uses those same hours. Use the maintenance agreement capacity model to place the visits you have promised, then cluster flexible appointments within real remaining capacity. A route is not improved if it leaves an agreement obligation with nowhere to go.

Dale draws from the same technician pool for service and install. A shorter route cannot solve a board that has assigned a person's afternoon twice. The legal pad and both work types need to use the same hours.

What belongs in the daily dispatch check?

Start with one manageable part of the territory. Build the next day from committed windows, technician suitability, realistic job durations, travel and protected buffer. A simple route card can hold the details:

• Person or crew: assigned people, workday and any fixed absence.
• Job sequence: location, purpose, duration estimate and promised window.
• Readiness: required skills, equipment, parts and access confirmed.
• Travel and buffer: planned legs and the time still uncommitted.
• Changes: approved exception, customer update and next review owner.

Check it before departure, when a material change occurs and at the end of the day. Compare planned and actual travel, completed work, arrival-window performance, overtime and callbacks. Note long jobs, weather and urgent exceptions so the comparison stays fair.

Do not reward a short drive that produces rushed work or a missed promise. You want more usable time with the service experience intact. Use the capacity planning checklist to connect the route to the rest of the week, and revisit when to run ads only after you know which openings are real.

Picture Dale taking the legal pad out again. The forty-minute first leg, supply-house stop and driveway delay no longer sit in one unexplained subtraction. Each has a question beside it: necessary travel, a readiness problem, or a dispatch conflict?

He has not added a truck or promised another job. He has made tomorrow's route something the crew and office can examine together. The next capacity decision can start with that day, instead of how busy five moving trucks look.