Delivery KPIs that actually matter for a Nigerian fleet
Open most fleet management dashboards and you will find twenty numbers competing for attention. Distance covered, idle time, fuel estimates, speed averages, a dozen chart types. Almost none of it changes what a dispatcher does the next morning.
After watching a few hundred businesses actually run their day-to-day operations, five numbers keep showing up as the ones that change decisions. Everything else is either a distraction or feeds into one of these.
1. On-time delivery rate
This is the percentage of deliveries completed within the window you promised the customer, whether that window is "same day", "within two hours", or a specific time slot. It is calculated simply: completed on-time deliveries divided by total deliveries attempted, for a given period.
The mistake most businesses make is tracking this at the fleet level only. Break it down by rider and by route zone. A fleet-wide 88% on-time rate can hide one rider at 60% dragging the average down, or one delivery zone with genuinely difficult road access that needs a longer promised window rather than a faster rider.
2. First-attempt success rate
How many deliveries succeed on the first try, without a redo, a reschedule, or a customer complaint that the rider never showed. A failed first attempt costs roughly double, between the wasted trip, the second attempt, and the customer's patience.
Most failed first attempts trace back to two causes: an address that was never verified before dispatch, or a rider who arrived outside the window the customer expected. Both are fixable with a five-minute confirmation call or message before the rider leaves, not after.
3. Active shift utilisation
Of the hours a rider is clocked in, what percentage is spent actually moving toward a delivery, versus idle, waiting, or on unrelated stops? This number exposes a problem that is invisible from the outside: a rider can complete their assigned deliveries and still spend forty percent of a shift doing very little.
A rider covering four deliveries in an eight-hour shift is not automatically underused. If those four deliveries were spread across Lagos in heavy traffic, that might be a full day's work. Utilisation only means something alongside distance and delivery count for the same shift.
4. Cost per delivery
Fuel, rider pay for the shift, and any vehicle maintenance allocated to that period, divided by completed deliveries. Most businesses know their total monthly delivery cost. Far fewer know the cost per individual delivery, which is the number that actually tells you whether a new customer contract, a new route, or a new hire makes financial sense.
This is also the number that catches fuel-related issues early. A sustained rise in cost per delivery, with distance and delivery count holding steady, points to a fuel problem worth investigating before it becomes a pattern.
5. Time-to-flag resolution
When a route deviation, extended stop, or other flagged event happens, how long does it take from the flag being raised to someone on the team actually reviewing it? A flag that sits unreviewed for three days is not much better than no flag detection at all.
This is less about the rider and more about your own process. If flags pile up faster than your team reviews them, either the detection is too sensitive and needs tuning, or the review step needs to be assigned to someone specific rather than left as everyone's job.
Where this data already lives
If you are running deliveries through a dispatch system with GPS tracking, most of this is already being captured. The Traxx dashboard calculates on-time rate, shift utilisation, and flag activity automatically from the same trip data used for the live map, so the numbers above do not require a separate spreadsheet to maintain.