
Guides
Local delivery KPIs for first-year owners: what to track and how to read it
The local delivery KPIs a first-year owner should track: on-time rate, first-attempt success, damage claims, route earnings, cost per stop, repeat rate and capacity, with a worked example for each.
A first-year courier can drown in numbers. This guide picks the measures that explain whether a local delivery operation delivers on time and makes money. Each has a plain definition, a worked example and a limit. The figures in the examples are illustrations, not industry benchmarks, so build your own baseline from your own routes.
The measures at a glance
- On-time delivery rate:Deliveries completed inside the promised window, divided by all deliveries.
- First-attempt success rate:Deliveries completed on the first stop, divided by all deliveries attempted.
- Damage or claims rate:Deliveries with a damage or loss claim, divided by all deliveries.
- Repeat rate:The proportion of business accounts that booked in both of two consecutive 30-day periods.
- Route capacity:The stops per hour a particular route can realistically complete.
- Bookings-to-capacity ratio:Bookings compared with the capacity of the routes planned to handle them.
- Return visit:Another driver attempt at a stop to complete a delivery.
- Reason code:A category recording why a further delivery attempt was needed.
- Route earnings:Route billing after direct costs are subtracted.
- Unit cost:Route cost divided by completed stops or miles driven.
Service measures: on time, first attempt and damage
On-time delivery rate is the first number a client notices. Define the promised window in the contract, such as "between 1 and 3 p.m.", and count a delivery as on time only if it lands inside it. For example, 188 on-time deliveries out of 200 is a 94 percent rate. Read it by account, because one late-prone client can hide behind a good average.
First-attempt success rate shows how often the driver finishes at the first stop. If 180 of 200 deliveries succeed on the first try, the rate is 90 percent and the other 20 become return visits. A falling rate usually points to intake problems, such as wrong addresses or no one to receive the parcel.
Damage or claims rate counts deliveries that end in a damage or loss claim. Two claims in 200 deliveries is 1 percent. Track it beside your cargo insurance deductible, because small claims paid out of pocket never reach the insurer yet still erode the margin. Customer satisfaction can be as simple as a one-line follow-up to each account or a count of complaints per month.
There is no regulator-set standard for these rates, and published figures vary by service type. Set a target per contract, write it down, and compare each month with the month before.
Route earnings and unit cost describe the contract
Route earnings show what remains from a route after direct costs come out of its billing. Count driver pay, fuel, tolls, and parking among those costs. Use published driver pay information from the Bureau of Labor Statistics when assessing the pay input, rather than treating company-wide revenue as proof that every route contributes.
Unit cost gives a second view: divide route cost by completed stops for cost per stop, or by miles driven for cost per mile. For example, a route bills $1,800 in a month with $1,350 of direct costs, so route earnings are $450. Across 180 stops, cost per stop is $7.50. If the contract pays $10 a stop, $2.50 a stop is left.
A contract priced below its cost per stop is being renewed at a loss. Long rural runs can skew an average, while holiday overtime and temporary drivers can complicate month-to-month comparisons. The break-even worked through shows how the same numbers set a floor price.
Route contribution worksheet
- Take route monthly billing
- Subtract driver pay
- Subtract fuel and tolls
- Subtract parking citations
- Subtract allocated vehicle lease
- Divide cost by stops, then miles
Repeat rate describes account continuity
Repeat rate indicates whether accounts continue booking, but it cannot explain why they do or do not return. Compare accounts active in the latest 30-day period with those that booked in the preceding 30-day period. A change signals altered account behavior, not its cause.
Interpret the number against each account's usual frequency. A daily shipper going quiet may warrant a different conversation from an account that usually sends parcels twice a month. Call three accounts that have lapsed before changing rates or service.
Return visits reveal recurring delivery friction
Count a return visit whenever a driver makes another stop to finish a delivery. Review the monthly total beside its reason codes: the tally shows how often another attempt happens, while the categories can suggest where an operating response may help.
Use five reason codes: nobody home, wrong address, no signature, refused, and damaged. If nobody home leads, examine scheduling; if wrong addresses dominate, check the information collected at intake. Compare the total with broader service quality checks, since the count alone can point to the wrong fix.
Return visit reason codes
- Nobody home
- Wrong address
- No signature
- Refused
- Damaged
Look at return visits monthly so that one difficult week does not become the assumed pattern. Weather disruption can lift the total without showing a process failure, so compare similar periods before changing a procedure.
Capacity turns bookings into a staffing signal
Route capacity estimates how many stops an individual route can complete in an hour. Compare bookings with planned capacity to see pressure on staffing, but judge profitability separately. A schedule that looks full does not, on its own, show whether the work earns enough.
The route type changes the estimate. In the example chart, a driver completes 14 stops an hour in a dense downtown core but seven on suburban routes with longer driveways. A single company-wide figure can misstate available capacity, so base route scheduling on what each route can realistically handle.
Stops per hour by route type
- 14dense downtown Portland
- 7suburban long driveways
- 60bookings example
- 40one route capacity
For a staffing estimate, divide daily bookings by the stops each driver can complete in a day. With 60 daily stops and capacity of 40 stops per driver per day, plan for two drivers rather than one and a half. Check the bookings-to-capacity ratio weekly, so staffing choices reflect current demand.
If bookings exceed 90 percent of capacity for two weeks running, there is little room for a sick day without service failures. Treat that pattern as a hiring signal, not a pricing recommendation. Capacity can help decide whether to add a driver or decline work, but cannot establish a contract price.
Assign each measure a reader and a response
A KPI earns its place when someone knows what to do with it and understands its limits. Check bookings against capacity weekly, then review service rates, repeat rate, return visits, and route economics monthly. Treat each reading as evidence for a decision, not as a complete explanation of the operation.
| Measure | Review rhythm and possible response | Limit to remember |
|---|---|---|
| On-time delivery rate | Monthly, by account; ask why late stops cluster | A good average can hide one late-prone client |
| First-attempt success rate | Monthly; fix intake and scheduling gaps | It does not say why an attempt failed |
| Damage or claims rate | Monthly; compare with cargo insurance terms | Small claims paid directly may go unrecorded |
| Bookings compared with route capacity | Weekly; consider adding a driver or declining work | A full route can still lose money |
| Repeat rate | Monthly; check whether accounts return | It does not explain why an account stopped booking |
| Return visits by reason code | Monthly; look for recurring delivery problems | A difficult weather week can distort the total |
| Route earnings after direct costs | Monthly; identify contracts for a rate discussion | Holiday overtime complicates comparisons |
| Cost per stop and cost per mile | Compare with contract pricing at renewal | Long rural routes can skew averages |
Give each measure a named reader. The dispatcher can monitor capacity, the account manager can follow repeat bookings, and the route supervisor can record return reasons. The owner should review route earnings because repricing or leaving a contract is an owner decision; align those roles with the operations workflow.
Escalation triggers and owners
Two weeks above capacity -> owner hiring decision
Any repeat-rate drop -> account manager same week
Route losing money two months -> owner repricing or exit
Set escalation points before a reading creates pressure. Send bookings above capacity for two weeks to the person responsible for hiring decisions. A lower repeat rate should reach the account manager that week. If a route loses money for two months in succession, the owner can consider repricing or exiting.
Where the numbers meet the rules
Some KPIs overlap with legal duties. A rising claims rate is the moment to review cargo and liability coverage. If your vehicles are rated 10,001 pounds or more, federal safety rules may apply; the FMCSA rules for local courier fleets explain the first-route questions. Driver pay per route also depends on whether drivers are employees or contractors.
Keep a record trail behind every KPI
A useful KPI can be rebuilt from supporting records instead of relying on memory or an estimate. Keep route files and financial records together by route and month. That makes it possible to check how a dashboard value was reached and compare periods consistently.
Supporting items include mileage logs, fuel receipts, toll statements, parking citations, driver settlements, proof-of-delivery records, claims files, and payroll records. Connect each item with the route and month it explains. A KPI that cannot be reconstructed from its records remains a guess.







