Route Planning: More Visits Without a Longer Day
A route planning guide: visit sequencing, geographic clustering, time windows, traffic realities and measuring field efficiency.
The cost of a day in the field is fixed; the only variable is how much of that day is spent driving. The cheapest way to increase visits is not working harder but fixing the sequence.
Three realities that break plans
- Visits are not equal in length. A fifteen-minute delivery and a two-hour installation cannot share one plan; duration estimates must follow the visit type.
- Customers have time windows. A customer who says “afternoons only” breaks the geographically optimal order. A window is a stronger constraint than distance.
- Traffic varies by hour. A 20-minute drive at 08:00 is 50 minutes at 17:30. A plan built on fixed distances does not hold by the end of the day.
Sequencing logic
Before reaching for complex algorithms, three simple rules deliver serious gains for most teams:
- Cluster geographically: build the day by area. A plan that crosses the city twice costs you a visit.
- Start at the far end: take the most distant point early and collect the nearer ones on the way back. The reverse means entering evening traffic with a long drive ahead.
- Place the windows first: fixed-time visits are the skeleton of the plan; flexible ones fill the gaps.
- Leave buffers: without 15–20% slack between visits, the first delay shifts the whole day.
Keeping the plan alive during the day
Even the best plan breaks by 10:00: a visit overruns, a customer cancels, an emergency comes in. What matters is not that the plan holds but that everyone knows when it changes.
- Engineers should mark “on the way / on site / completed” so the office can see status without calling.
- When a visit is cancelled, a nearby pending job should be offered in its place.
- When a delay occurs, the next customer should be told automatically — “we are running late” produces far fewer complaints than silent lateness.
- Emergency jobs should go to the nearest team, not the next in rotation.
Visit count should not be the target
This is the trap in route optimisation: a team doing 8 visits a day instead of 6 has gone backwards if the first-visit fix rate has fallen. Every unresolved visit generates a second one and raises the total cost. The target should be jobs completed, not visits made.
What to measure
- Share of time on the road: travel as a percentage of the working day. The clearest indicator of improvement.
- Average distance per visit.
- Plan adherence: how many planned visits happened and how many slipped?
- Window adherence: the share of visits arriving within the promised window.
- First-visit fix rate: if route optimisation lowers this, it is not an optimisation.
Frequently asked questions
Do I need a dedicated tool for route planning?
Not in a small team — geographic clustering and window-first ordering can be applied by hand. Automatic planning earns its place as daily visit counts and team size grow.
Is location tracking necessary for routing?
Not for planning; it helps with in-day updates and confirming visits happened. The purpose is keeping the plan alive rather than continuous monitoring — and that distinction must be stated clearly to the team.
Should we give customers a time or a window?
A window is more realistic and keepable. But a narrow window plus a notification when the engineer sets off produces a much better experience than a wide window.
Next step: to see visit planning and live field status, request a demo.