How to route service technicians across multiple trucks

Routing one truck is easy: go to the nearest next stop. Routing six trucks is a different problem, because every stop you give one tech is a stop you've taken from another, and the customer windows don't care about your geography. This is the method small service companies use to route multiple trucks well without hiring a dispatcher to do it, and what to automate when it stops fitting in an evening.

What good routing actually optimizes

It's tempting to measure routing by miles. Miles matter, but they're third on the list. In order:

  1. Every time window is kept. A missed 8–10 window costs more than ten extra miles: a callback, a bad review, a free service call to make it right.
  2. Every job has a qualified tech. The shortest route to a job the tech can't finish is a wasted trip. (If you haven't done this yet, read how to schedule field technicians by skill and certification first; matching comes before routing.)
  3. Total drive time is low. Now minimize windshield time, with fuel and overtime as the costs.

Hold that order and most routing decisions make themselves.

Step 1: Fix the anchors

Before you route anything, place the jobs that can't move:

  • Emergencies go in the earliest slot of the nearest qualified tech. Burst pipe, no heat in January, gas smell, sewage backup: first stop of the day, no exceptions.
  • Hard appointments. Inspector meetings, builder schedules on new construction, commercial sites with access hours, customers who took the morning off work.
  • Full-day jobs. An install or a tear-off takes the whole truck. Put it on the route and that truck is done; don't try to tuck a service call around it.

Anchors typically eat 30–40% of the day's capacity. Everything else is routed around them.

Step 2: Cluster the rest by area, not by tech

Take the remaining jobs and group them geographically: north side, downtown, the two suburbs you serve, whatever your map looks like. Ignore who's doing them for now. The goal is clusters of stops a single truck could work without crossing town.

Then assign clusters to trucks, with two constraints:

  • A cluster goes to a tech whose anchors are already in or near it. If Marcus has an 8 a.m. emergency in Las Colinas, the Las Colinas cluster is his.
  • Every job in the cluster must be one the tech is qualified for. If one isn't, pull that job out and treat it as a single assignment to the right tech, even if it costs miles. Qualification beats geography.

This is the step dispatchers get wrong by habit. The instinct is to start with the tech ("what does Dante have tomorrow?") and fill his day. Starting with the map produces tighter routes every time.

Step 3: Sequence each truck around its windows

Now you have each truck's list of stops. Order them:

  1. Lay the time-windowed stops on a timeline first: the 8–10, the 12–2, the "after 3."
  2. Fill the gaps between them with the flexible stops, nearest-next from wherever the truck will be.
  3. Add realistic durations. Diagnostics run 45–90 minutes; installs run hours; "quick" maintenance is rarely under 30. Use your own history, not optimism.
  4. Add drive time between stops at the time of day the truck will actually be driving. A 20-minute hop at 10 a.m. is 35 minutes at 4:30.

If the timeline runs past the tech's shift, you've found an overbooked truck. Don't shave the durations to make it fit; that's how windows get missed. Move a flexible job instead (next step).

Step 4: Leave room for tomorrow's emergency

The emergency you haven't taken yet will arrive at 8:15 tomorrow. If every truck is booked to the minute, it goes to whoever's nearest, and that tech's whole day slides. Two ways to plan for it:

  • A float slot. Leave one 60–90 minute gap on one senior tech's route, mid-morning. If no emergency comes, pull a flexible job forward into it.
  • A designated bumper. Mark the job on each truck that moves first if an emergency lands. The customer is usually a recurring-maintenance account that won't mind a reschedule.

Shops that do this absorb emergencies with one phone call. Shops that don't make four.

Step 5: Hand each tech their day in a form they'll follow

A route only works if the tech drives it in order. Paper lists get reshuffled. Group texts get lost. What works is one link per tech, with the stops in order, the time windows visible, the job notes attached, and a navigation button for each stop so the next address is one tap away. If the day changes, the link should change, not a new text thread.

When to automate

At two or three trucks, this whole process is 20–30 minutes a night, and doing it by hand is fine; you'll know the map better than any software. The break point is usually around five trucks and thirty jobs. Clustering and sequencing by hand stops improving, the night-before hour turns into two, and the person doing it is the owner, at 9 p.m., after a full day in the field.

That's where routing software earns its keep, with one caveat: generic route optimizers (the kind built for deliveries) will give you the shortest path and ignore everything in steps 1 and 2. For service work you need a tool that matches first and routes second. Nightfold does both from a CSV export: anchors emergencies into the earliest slot, keeps certified work with certified techs, sequences each truck around its customer windows, and tells you in plain English which jobs didn't fit and why. Every tech gets a link to their day with Google or Apple Maps navigation built in.

Start with the method, though. A dispatcher who understands anchors, clusters and windows will get more out of any tool, and will catch it the one time it's wrong.

Route tomorrow tonight.

14-day free trial for every service category. No credit card. Works with the CSV export from Jobber, Housecall Pro, ServiceTitan or any CRM.