Mon – Sat: 9:00 AM – 7:00 PM IST
Logistics

What is route planning?

Deciding which vehicle takes which drops in which order — and the constraints that make the obvious answer wrong.

In short

Route planning determines how orders are assigned to vehicles and in what sequence they are delivered, within constraints: vehicle capacity, delivery windows, driver hours, access restrictions and service times. The objective is usually lowest cost or distance subject to meeting every window.

Why It Matters

Why this matters in practice

Routing by hand or by habit produces routes that look sensible and are usually ten to twenty per cent longer than they need to be, because a person cannot evaluate the combinatorics. The constraints are what make it hard: a plan that ignores delivery windows or access restrictions is optimal on paper and fails on the road.

Reduces distance and vehicle count against manual planning
Enforces delivery windows and driver-hour limits
Produces realistic ETAs for customer notification
Plan versus actual comparison exposes bad assumptions
How It Works

How it works in practice

1

Capture the constraints

Vehicle capacity and type, delivery windows, access restrictions, driver hours and shift patterns.

2

Set realistic service times

Time at each drop, which varies by customer and is the figure most often wrong in a plan that fails.

3

Optimise

Orders assigned to vehicles and sequenced, respecting every hard constraint and minimising the chosen objective.

4

Release and track

The plan goes to drivers; actual progress is tracked against it so exceptions surface during the day, not after.

5

Compare plan against actual

Where actual consistently exceeds planned time, the underlying assumption is wrong and should be corrected.

Worked example

A worked example: the constraint that was not in the model

A business implements route optimisation and sees planned route times fall by 18 percent. Actual times barely move, and drivers report that the plans do not work.

The model was missing constraints that drivers held in their heads. Three customers accept deliveries only before eleven. One industrial estate has a height restriction excluding the larger vehicles. Two city-centre stops require a particular unloading bay that is occupied at lunchtime. Service time at a hospital is forty minutes, not the ten assumed for everything.

Optimisation is only as good as the constraints it knows about, and the constraints that matter most are usually undocumented because experienced drivers simply work around them. Capturing them is unglamorous interview work rather than a software task. Once service times were measured per customer type and access constraints recorded, the planned savings became real — smaller than the original 18 percent, and actually achievable.

Key terms

The vocabulary, briefly

Term What it means
Stop A single delivery or collection point on a route.
Time window The period during which a customer will accept delivery.
Vehicle constraint Capacity, weight, dimensions or access restrictions limiting what a vehicle can do.
Drop density Stops per unit area, which is the main determinant of route efficiency.
Dynamic routing Re-planning during the day as conditions change.
What Goes Wrong

Common mistakes worth avoiding

Service times assumed uniform

A supermarket delivery and a city-centre shop take very different times. One average makes every route wrong.

Ignoring access restrictions

Vehicle size limits, timed access and unloading constraints invalidate otherwise optimal routes.

Never comparing plan with actual

Without feedback, the same wrong assumptions are planned against indefinitely.

Optimising distance only

Distance is a proxy. Cost includes time, driver hours and vehicle type, which can rank routes differently.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Planned vs actual route time Model accuracy. A persistent gap means constraints are missing.
Drops per hour The core productivity measure, driven mostly by drop density and service time.
Time window compliance Deliveries made within the agreed window, which is what customers judge.
Vehicle fill rate Capacity utilisation by weight and by volume, which can differ substantially.
FAQ

Questions we are asked about this

Static routing builds fixed routes run repeatedly, suiting stable delivery patterns. Dynamic routing re-optimises each day against actual orders, suiting variable demand.
Not to plan, but to compare plan against actual — which is where the improvement comes from. Without feedback the assumptions never get corrected.
Accurate geocoded addresses, realistic service time per stop, vehicle capacities and restrictions, customer time windows, and driver hours. Service time is the most commonly wrong input — using one average for every stop will produce plans that work for some customers and fail consistently at others. Measure it by customer type before trusting any optimisation output.
No, and systems presented that way tend to be rejected. Optimisation handles the combinatorial arithmetic no human can do well — sequencing thirty stops against windows and capacities — while planners hold context the model does not: a customer having a difficult week, a road closed since yesterday, a driver unfamiliar with an area. The productive arrangement is optimisation proposing and planners adjusting, with adjustments captured as constraints when they recur.
It varies enormously with starting point and drop density, and anyone quoting a general figure is guessing. Operations with dense urban routes and good data have more to gain from sequencing; sparse rural routes are constrained by distance regardless of sequence. The honest approach is to measure your current planned-versus-actual performance first, because that baseline tells you how much slack exists before any system is bought.
Valuable where conditions genuinely change — same-day orders, cancellations, traffic disruption, failed deliveries — and it requires live vehicle tracking and reliable driver communication to be worth anything. It also requires drivers to accept mid-route changes, which is as much a management question as a technical one. Static daily planning done well beats dynamic planning done badly by a wide margin.
Related

Where to read next

What is proof of delivery?

Read more

Freight cost management

Read more

3PL billing models

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.