Why urban routes deserve their own planning rules

A trunk run between two depots is fairly predictable: motorway miles, a known average speed, a sensible arrival time. The urban leg is where schedules go to die. Twenty drops spread across three square miles can look like a tidy two-hour job on a map and take five hours in practice.

The reason is that urban delivery is governed by time, not distance. Average speeds in busy city centres often sit between 8 and 12 mph once you account for traffic lights, bus lanes, school-run peaks and the crawl around a retail park. Add a parking restriction, a refused delivery and a blocked loading bay, and the arithmetic collapses. Planning that treats mileage as the main constraint will always over-promise. Planning that treats minutes per drop as the main constraint stands a chance.

Build a realistic picture of each urban area

Routing software is only as good as the data underneath it. Before you can optimise anything, you need to know what the street actually looks like at 8am on a Tuesday.

• Access restrictions: weight limits, width restrictions, timed pedestrianised zones, low traffic neighbourhoods, school streets and bus gates all change where a vehicle can legally go and when.
• Kerbside reality: a loading bay that is free at 6am may be a taxi rank or a market stall by 10am. Note the permitted hours, the maximum stay and whether a permit is required.
• Red routes and bus lanes: stopping on a red route is rarely worth the penalty. Know where you can and cannot pause.
• Entrances, not postcodes: a postcode can put a driver at the wrong side of a shopping centre or a gated estate. Record the actual goods-in entrance, the barrier code and the lift location.

Your drivers already hold most of this knowledge. Capture it in a shared reference that planners, agency staff and new starters can all use, and review it quarterly. Urban restrictions change more often than most people expect.

Use routing software as a tool, not an oracle

Modern routing platforms can handle time-based restrictions, vehicle profiles, live traffic and historic congestion patterns. That is genuinely useful, but the output is a starting point rather than a finished plan.

The most common mistake is leaving default service times in place. A default of three minutes per drop is optimistic when the stop involves a fifth-floor flat, a signature and a returns collection. Measure your own service times by stop type — kerbside, reception desk, multi-drop building, bulky item — and feed those in.

Always include the last fifty metres. A driver parked two streets away and walking a trolley to a door has added several minutes to the stop, and software that only counts driving time will miss it. Treat local knowledge as a correction layer: if a planner's route consistently gets adjusted by experienced drivers, the model is wrong, not the drivers.

Delivery windows that work for everyone

Customers love a one-hour window. Operations teams often hate them, because narrow windows remove the flexibility that keeps a route efficient. There is a workable middle ground.

• Offer time bands rather than precise slots for residential drops, and reserve tight windows for business customers who genuinely need them.
• Incentivise off-peak delivery. Early morning, late evening and weekend slots can be cheaper or bundled with a benefit, which spreads demand without forcing it.
• Let route density influence availability. If a street already has six drops on Tuesday, that is the day to offer.
• Group by building and street. Consolidating multiple orders into one visit is the single biggest efficiency gain available in dense areas.

Communicate proactively when a delay is likely. A short text saying the driver is running twenty minutes behind saves far more goodwill than an apology after the fact.

Vehicles, loading and the kerbside squeeze

Match the vehicle to the zone, not to habit. Cargo bikes and small electric vans suit tight, restricted quarters and can use cycle infrastructure and some loading bays that larger vehicles cannot. A 7.5-tonne vehicle may be the right choice for a suburban retail park and the wrong one for a medieval city centre.

Load in reverse drop order so the last parcel out is nearest the doors. Use trolleys and sack barrows where surfaces allow, and plan team deliveries for heavy or awkward items so nobody is double-parking a van on a busy street. Where volumes justify it, a micro-consolidation hub on the edge of a restricted zone lets you switch to smaller vehicles for the final mile and cuts the time each van spends circling.

Measure, review and refine

Track the numbers that reflect urban reality: drops completed per hour, first-time delivery success, failed deliveries, minutes per stop by type, and the number of penalty charge notices per hundred drops. Fuel and mileage matter, but they rarely tell you where the schedule broke.

Debrief drivers weekly — not to audit them, but to find the three streets that reliably cost fifteen minutes each. Then re-plan for the season, because school terms, holiday periods and winter light all shift the pattern. Urban routing is never finished. Small, regular adjustments are what keep a schedule honest and a driver's day achievable.