The Delivery Operations Scorecard: 12 Metrics Every Small Fleet Should Track

A busy fleet can look productive while still losing time through repeated travel, long stops, unclear job status and failed deliveries. The answer is not to track every possible number. It is to choose a small scorecard that helps managers understand what happened, why it happened and what should change next.

This guide explains twelve practical delivery metrics for Australian owner-drivers and small fleets, including how to calculate them, how to interpret them and how to avoid using them unfairly.

First: measure the operation, not just the driver

Delivery performance depends on route design, job data, customer availability, vehicle condition, traffic, loading processes and driver execution. A driver should not be blamed for delays created by an unrealistic plan or an incorrect address.

Use metrics to identify system problems and support better decisions. Review context before drawing conclusions, and compare similar work with similar work.

The 12 metrics worth tracking

1. Planned versus actual kilometres

Formula: actual kilometres minus planned kilometres.

This gap can reveal diversions, address problems, route changes, missed stops or planning assumptions that did not match road conditions. Review large differences individually before treating them as poor performance.

2. Kilometres per completed stop

Formula: total route kilometres ÷ completed stops.

This makes distance easier to compare across routes of different sizes. Use it within similar service areas; rural and dense metropolitan routes naturally behave differently.

3. Route completion rate

Formula: completed planned stops ÷ total planned stops × 100.

A low result may signal an overloaded route, insufficient job information, customer absence or operational disruption. Record a reason for every incomplete job so the percentage leads to action.

4. On-time arrival rate

Formula: stops completed within the promised window ÷ stops with a promised window × 100.

Only measure genuine commitments. If every job is given an arbitrary time window, the metric becomes noisy and drivers may be encouraged to rush.

5. First-attempt completion rate

Formula: jobs completed on the first visit ÷ jobs attempted × 100.

Repeat visits consume capacity and add customer frustration. Track why a first attempt failed: nobody available, wrong address, access issue, unsuitable vehicle, missing item or another cause.

6. Average service time per stop

Formula: total time spent servicing stops ÷ completed stops.

Break this down by job type or customer category. The result helps planners assign more realistic durations instead of giving every stop the same estimate.

7. Route duration variance

Formula: actual route duration minus planned route duration.

Consistent overruns may indicate that travel estimates, stop durations, loading time or return-to-depot activity are missing from the plan.

8. Productive time ratio

Formula: driving time plus service time ÷ total shift time × 100.

This highlights time lost to waiting, unclear instructions, loading delays or avoidable administration. It should not be used to remove legitimate breaks or safe working practices.

9. Jobs completed per paid hour

Formula: completed jobs ÷ paid hours.

Use this carefully and only across comparable routes. A complex field-service job should not be compared with a quick parcel drop. The metric is most useful for trend analysis within the same work type.

10. Fuel used per 100 kilometres

Formula: litres used ÷ kilometres travelled × 100.

Changes can reflect load, driving conditions, idling, tyre pressure, vehicle maintenance and route shape. Review a rolling trend rather than reacting to one day.

11. Customer-contact exception rate

Formula: jobs requiring avoidable support contact ÷ total jobs × 100.

Examples include drivers calling for missing access notes or customers asking for an update because job status is unclear. These contacts reveal where better information or visibility could remove friction.

12. Exception resolution time

Formula: average time from an exception being reported to a decision being communicated.

Fast, clear decisions help prevent one disrupted job from affecting the entire route. Record the exception type, owner, action and outcome.

A simple weekly delivery scorecard

Start with five measures rather than all twelve. A balanced weekly view might include:

• Route completion rate
• First-attempt completion rate
• Planned versus actual kilometres
• Average service time by job type
• Number of exceptions and their main causes

Add fuel, on-time performance or productivity measures once the underlying job data is reliable.

How to interpret the numbers

Look for trends, not isolated events

A storm, vehicle breakdown or unusual customer delay can distort one day. Compare several weeks and annotate unusual events so they are not mistaken for normal performance.

Segment similar routes

Compare metropolitan runs with metropolitan runs, rural work with rural work, and installations with installations. Fair grouping makes the scorecard more useful and reduces misleading conclusions.

Pair every result with a reason code

A completion rate tells you what happened. A reason code tells you what to fix. Use a short, consistent list such as customer unavailable, incorrect address, access problem, capacity issue, vehicle issue or schedule overrun.

Discuss metrics with drivers

Drivers often know why a route underperformed. A short weekly review can identify unsuitable stop sequences, difficult sites and recurring customer problems that are invisible in the raw numbers.

Example: turning metrics into action

Suppose a small fleet sees strong completion rates but a rising number of kilometres per stop. A closer review shows that urgent jobs are being inserted into whichever route has the nearest driver, causing repeated cross-zone travel.

The corrective action is not simply to tell drivers to travel less. The business could create clearer geographic zones, define when an urgent job may interrupt an active route and compare the cost of same-day insertion with scheduling the job for the next suitable run.

In another case, route duration may repeatedly exceed the plan while kilometres remain close to target. That points toward underestimated service time, loading delays or customer access—not poor routing.

Data-quality rules

• Use consistent definitions for started, arrived and completed.
• Record cancellations separately from failed delivery attempts.
• Do not compare routes with materially different job types without context.
• Correct known GPS or status errors before reporting.
• Keep reason codes short enough that drivers will use them.
• Protect employee and customer information and limit access appropriately.
• Use operational data fairly and consistently with workplace obligations.

How RouterMe can help

RouterMe gives delivery teams a clearer operational record by bringing routes, job allocation, driver activity and progress updates into one workflow. When planned and completed work is recorded consistently, managers can review route outcomes and identify where the process—not just the driver—needs improvement.

Start small and improve the scorecard

Choose a handful of metrics that answer real business questions. Review them weekly, investigate exceptions and change the scorecard when a number no longer supports a useful decision. The purpose is not to create more reporting—it is to create better routes, clearer work and more reliable service.

Want a clearer view of your active routes and completed work? Visit RouterMe.com to get started.