Most regional courier operations run on a handful of numbers their ops lead knows by feel — roughly how many packages moved today, roughly how many drivers had problems, roughly how the day compared to last week. "Roughly" is fine when margins are comfortable. When re-delivery costs are compressing your per-stop economics and parcel contracts have thin margins, managing by instinct stops being sufficient.
This is the metric stack that gives regional ops leads the visibility to run tighter operations — not a management dashboard designed for executive presentations, but a working set of operational indicators that actually drive decisions at dispatch level.
Metric 1: First-Attempt Delivery Rate (FADR)
This is the foundational number. First-attempt delivery rate is the percentage of attempted stops where the delivery is successfully completed on the first attempt. Industry data for regional carriers in residential-heavy routes shows FADR typically ranging from 72% to 88%, with significant variation by zone type, season, and day of week.
Track FADR at minimum by route zone and by day-of-week — not just in aggregate. An 82% overall FADR can hide a residential residential zone running at 61% (severely degrading your re-delivery cost) while commercial routes run at 97%. The aggregate masks the problem that needs fixing.
Metric 2: Re-Delivery Cost Per Stop
Calculated as total re-delivery expenditure (driver labor, fuel, re-sort overhead, customer service contacts) divided by number of re-delivery stops in the period. This gives you a fully-loaded cost per re-attempt, which typically runs $8–$14 for regional carriers at moderate stop density.
This number is most useful as a denominator for evaluating interventions. If an operational change (time-window optimization, availability-signal sequencing, pre-delivery notification) reduces your FFAD rate by 5 percentage points and you're running 500 stops/day, that's 25 fewer re-deliveries daily. At $10/re-delivery, that's $250/day or roughly $65,000/year in recoverable cost. Size the intervention cost against that number.
Metric 3: Cost Per Stop (Fully Loaded)
Not to be confused with re-delivery cost. Cost per stop is your total operating cost for the route — driver labor, fuel, vehicle depreciation, dispatch overhead — divided by successfully completed stops. This is the metric that reflects how efficiently your fleet is delivering value.
The nuance: cost per stop can look good on a day where drivers are running high-density commercial routes and look terrible on a day with high residential FFAD, because failed attempts inflate your total cost without adding to completed stops in the denominator. Tracking it alongside FADR reveals that relationship explicitly.
Metric 4: Stops Per Hour
Stop rate — delivered stops divided by active hours on road — is the core efficiency measure for individual drivers and routes. Benchmark ranges vary significantly by route type: dense urban commercial routes may run 12–18 stops/hour; suburban residential routes with variable service time (waiting at doors, navigating access points) more typically run 5–9 stops/hour.
Tracking stops/hour per driver and per route zone surfaces two things: drivers who need coaching on service time efficiency, and route zones where the sequence design is adding unnecessary dead time between stops. Both are actionable at the ops level. Service time variance at individual stops is worth tracking separately — high variance stops (apartment complexes, multi-unit buildings, commercial receiving desks) are the most predictable drag on route throughput.
Metric 5: Time-Window Compliance Rate
For stops with committed delivery windows, what percentage are successfully completed within the stated window? National parcel contracts often include financial penalties for time-window failures; regional carrier contracts increasingly follow the same structure. A time-window compliance rate below 92–94% on commercial or premium residential stops warrants routing-level investigation — is the sequence design realistic for the stated windows, or are the windows being set based on carrier preference rather than route feasibility?
Metric 6: Stem Mile Ratio
Stem miles are the miles driven from depot to first stop and from last stop back to depot — non-revenue mileage that contributes to vehicle cost but delivers nothing. Stem mile ratio is stem miles as a percentage of total route miles. For regional carriers, stem ratios above 18–22% typically indicate routing zones that are poorly matched to depot location, or that route zone boundaries are being drawn without accounting for depot proximity.
This metric matters more for carriers with multiple hubs or service areas that don't align neatly with depot locations. For single-depot operations, stem ratio tends to be more stable — but it's still worth monitoring for seasonal variation (peak volume often forces coverage into zones further from depot) and for evaluating depot location decisions over time.
Metric 7: Out-for-Delivery Scan to Delivery Completion Rate
This is the ratio of packages scanned "out for delivery" at the depot or sort facility in the morning to packages with a successful delivery scan by end of day. A ratio below 85% is cause for concern — it means more than 15% of packages that left the sort facility didn't reach recipients. Some of that is legitimate FFAD; some may be missed scans, data entry errors, or driver non-compliant handling that inflates your apparent FFAD rate.
Tracking this metric alongside formal FFAD tracking surfaces the data quality problem. If your out-for-delivery-to-delivery ratio is 84% but your dispatchers report only 11% explicit failed attempts, 5% of packages are disappearing from your tracking visibility between depot and delivery — and that's a different operational problem than route sequencing.
Metric 8: Residential vs. Commercial FFAD Split
Most regional operations mix residential and commercial stops on the same routes. These populations behave very differently — commercial stops in receiving hours have FFAD rates of 5–8%; residential stops without a home occupant have FFAD rates of 15–35% depending on zone. Running a combined FFAD metric obscures both.
Track residential FFAD and commercial FFAD separately. This immediately makes clear whether your re-delivery problem is route sequencing on residential stops (addressable through availability-aware sequencing) or structural access issues on commercial stops (addressable through scheduling, pre-notification, and access-code management). The interventions are completely different, and treating them as one problem leads to interventions that don't fit either.
Building the Metric Stack into Operations
The practical challenge isn't knowing these metrics exist — it's extracting them consistently from whatever TMS or dispatch system you're running. Most regional carrier TMS platforms log the raw data (scan events, attempt outcomes, delivery times), but the aggregation into actionable metrics often requires custom reports or export-to-spreadsheet analysis that doesn't happen daily.
The minimum viable practice: pull FADR, cost per stop, and stops per hour weekly, segmented by route zone. Those three numbers, reviewed consistently, will surface almost every routing-level problem worth investigating. The other five metrics inform specific investigations once a problem zone is identified. You don't need a real-time dashboard to manage by these numbers — you need consistent extraction and honest review.