Case Study

# 42% Less Distance: Insights from Our Hyderabad Hub

Doormile Team
Sep 18, 2025
2 min read

Numbers settle arguments. At our Hyderabad hub, the goal was simple: reduce avoidable distance without missing customer commitments. The result was a 42% reduction in total distance travelled.

Hyderabad is not an easy city for delivery planning. Dense commercial areas, fast-growing suburbs, flyover work, narrow service lanes, apartment security checks, and sudden traffic build-up can all change the day.

## The baseline

Before MileTruth, the hub planned routes in the usual way. Zones were drawn from experience, dispatchers sequenced stops manually, and riders adjusted on the road when something changed.

That process worked, but it carried hidden costs. Two riders might cross the same area in the same hour. A vehicle might take a longer loop to avoid one late stop. A dispatcher might hold back an order because the best vehicle was not obvious in the moment.

- Zone-based allocation that missed nearby cross-zone drops
- Manual stop sequencing during busy dispatch windows
- ETAs checked after routing instead of before dispatch
- Traffic and delay handling that depended on phone calls from riders

### What changed

The main change was treating the day's orders as one connected plan instead of separate zone lists. The route plan considered distance, rider capacity, delivery windows, traffic, and vehicle availability together.

During peak traffic hours in Hyderabad, some vehicles were arriving 20 to 30 minutes later than planned. By adjusting routes based on live traffic and battery levels, we reduced missed delivery windows and improved on-time performance.

Planning the day's deliveries together removed repeated cross-town travel.

## The results

- 42% reduction in total distance travelled across the hub
- 37% fewer vehicles required for the same delivery volume
- No SLA misses during the measured deployment window
- Lower fuel use and fewer unnecessary kilometres per parcel

> The improvement did not come from asking riders to work harder. It came from giving the team a better route plan before the vehicles left.

> Hyderabad Hub Operations

### Why this applies beyond one hub

The Hyderabad result was not a one-city exception. Most hubs deal with the same issues: overlapping routes, conservative sequencing, traffic surprises, charging constraints, and last-minute order changes.

A 42% cut in distance changes the cost of running the operation. It also gives dispatchers more breathing room when the day gets messy.