Stops per Hour

A parcel driver may visit many addresses in one shift while a repair technician may finish fewer visits because each job takes longer, so stops per hour helps plan capacity only when the work being compared is similar. Some teams use on-road hours, from departure to return excluding scheduled breaks, while others use all paid working hours, including loading and paperwork, and SmartRoutes describes the on-road version as a distinct measure.

A fictional delivery route completes 96 stops in eight defined working hours for a rate of 12 stops per hour, but if the eight hours excluded loading while another route included it, a direct comparison would be unfair. Define a stop as an actual attempted visit or a successfully completed service, because a failed delivery attempt might count for routing productivity but not successful deliveries, and report both where the distinction matters.

Route density changes the number, since closely spaced urban addresses generally permit more stops than distant rural destinations, and geography is a planning factor, not a verdict on driver effort. Stop complexity matters too, as a furniture delivery with stairs and installation is not equivalent to dropping a small parcel at a reception desk, so classify work types before setting targets.

Traffic, parking restrictions and access procedures can lengthen time, and a driver may be delayed by factors outside their control, so review route conditions instead of punishing every low reading. The metric can be calculated at route, driver, team or period level, and for a combined rate you divide total completed stops by total eligible hours, because averaging individual rates without weighting can distort the result.

A fictional team has one route with 20 stops in two hours and another with 10 stops in five hours, so the combined rate is 30 divided by seven, about 4.3 per hour, while a simple average of 10 and 2 would incorrectly show six. Include only the same time window in numerator and denominator, since counting morning deliveries but the entire workday in hours understates the rate and counting all deliveries against driving-only minutes overstates it.

A higher figure is not always better, because rushing can increase safety incidents, damage and failed first attempts, so monitor on-time performance, customer experience and vehicle risk alongside speed. Upper's driver productivity guidance says to compare stop counts with route timing, service time and similar route conditions, and it warns that a dense neighbourhood and a spread-out territory do not support a raw driver ranking.

A planned rate can support staffing: divide forecast eligible stops by a realistic rate to estimate route hours, then add loading, breaks and travel allowances as appropriate and keep a buffer for variability. A sudden drop can signal traffic, new service requirements or poorly sequenced routes, and it can also reflect missing scans, so validate the data before changing headcount or incentives.

Technology can record arrivals and completions, but GPS alone may not prove a job was done, so match telematics to dispatch and proof-of-service records and protect staff and customer data under applicable rules. For field service, a completed visit may require diagnosis, repair and customer sign-off, and a short visit that fails to solve the issue can create a repeat stop, so first-time fix rate adds needed context.

A business owner should publish the metric definition with every dashboard, stating whether breaks, travel to depot, loading and failed visits are included, and review trends over enough routes to smooth unusual days, since one rainy afternoon can shift a small sample sharply. Stops per hour is a tool for understanding route design and capacity, to be used to ask where time goes, not to presume that the fastest driver gives the best service.