Skip to content
DayRoute

How many stops per hour should a delivery driver make? And how to measure it

Updated

Short answer

There is no universal number: stops per hour depends on how close the stops are, how long each one takes, the delivery windows, the vehicle and the building, so a dense downtown route and a rural one cannot be compared. Measure your own stops per hour and on-time rate by route type, and compare with your own previous period. A quick estimate for one route type is 60 divided by the average minutes per stop (driving to it plus time at the stop): 4 minutes of driving and 6 at the stop gives about 6 stops an hour. That is arithmetic, not a benchmark. In DayRoute, analytics show both for the team and for each driver.

How it works in DayRoute

Why there is no universal number, and what drives it

The same driver gets very different results on two routes, and two companies do not run the same kind of day. A figure without route type, stop type and period is not a benchmark, so this page gives none. These are the things that move it.

  • Stop density: minutes of driving between stops
  • Service time: a package left at a door versus a signature, a stairwell, a dock queue, a pickup
  • Delivery windows: a tight window creates waiting or a longer path, and waiting counts as route time
  • Vehicle and load: capacity, loading order, parking
  • Shift design: breaks, start time versus traffic, route length
  • Failed attempts: a visit with no delivery still takes the time
  • Plan quality: how stops are split between drivers and put in order
Stop densityFewer stops per hour when…: Long drives between stops, as on rural routesMore stops per hour when…: Stops a few minutes apart, as downtown
Service timeFewer stops per hour when…: Signatures, stairs, dock queues, pickupsMore stops per hour when…: Packages left at the door
Delivery windowsFewer stops per hour when…: Tight windows that force waiting or detoursMore stops per hour when…: Wide windows or none
Vehicle and loadFewer stops per hour when…: Hard parking, a load you have to dig throughMore stops per hour when…: Easy parking, a van loaded in stop order
Shift designFewer stops per hour when…: Starts into rush hour, very long routesMore stops per hour when…: Start times that avoid peak traffic
Failed attemptsFewer stops per hour when…: Many visits with no deliveryMore stops per hour when…: Few failed visits
Plan qualityFewer stops per hour when…: Stops split badly between driversMore stops per hour when…: Stops grouped and ordered well

How DayRoute counts stops per hour

DayRoute is route planning and delivery management software for local delivery teams, made by EzOps. Its analytics page shows stops per hour next to on-time rate, distance and customer rating for the whole team or one driver, and each tile is compared with the same number of days right before. The picture is the demo company, a fictional delivery company, so its numbers, such as 3.9 stops per hour, are generated demo data, not a result or a benchmark.

  • Stops per hour: delivery visits on routes divided by planned route hours (route end minus route start)
  • Delivered per measured hour: delivered orders divided by measured hours, only for routes the driver app reported on; measured hours run from the first to the last location point or stop event
  • The planned time split of each route shows where the hours go: driving, at stops, break and waiting
The Stops per hour tile of the Analytics page of the fictional demo company, with delivered per measured hour. Generated demo data, not a result or a benchmark

Measure it together with on-time

Stops per hour alone rewards rushing. Read it next to the on-time numbers, so a faster day is not one that moved the cost to the customer.

  • In the time window: delivered orders with a window whose arrival is inside the window, divided by delivered orders with a window, with no tolerance
  • Within 15 min of ETA, and the median minutes off the plan
  • If stops per hour rises while the in-window share falls, you did not get faster

A method that works

Compare like with like, and compare with yourself. Excel export by day, driver and order is there for payroll or a client review.

  • Pick a period of two weeks to a month and keep route types apart (dense, suburban, rural; residential, business) by using the Excel export by order and grouping by your own ZIP or label
  • Write down stops per hour, in-window share and failed share for each route type
  • Compare each with the same route type in your previous period, and each driver with their own planned work rather than with the best driver
  • Look at the time split before blaming a driver: long waiting is a window problem, long driving is a plan problem

Frequently asked questions

What is a good number of stops per hour?

There is no universal answer. Compare with your own previous period for the same route type, and read it with the on-time rate.

Is a higher number always better?

No. Read it with the in-window share and the failed share, or you reward rushing.

How does DayRoute measure stops per hour?

Delivery visits on routes divided by planned route hours. “Delivered per measured hour” uses the hours the driver app reported.

Can I compare drivers?

Analytics show each driver next to their planned work, measured hours and ratings. Compare drivers on like-for-like routes.

Can I get the data out?

Yes. Analytics export to Excel by day, by driver and by order.

More answers

Answers →

Track stops per hour for each driver

Measure stops per hour on your own routes on a 1-month free trial, no credit card.

Want a walkthrough with us? Book a demo