Miya Bholat
Nov 16, 2026
Comparing fleet downtime fairly across locations means using one clock definition, one denominator, and similar vehicle groups before ranking sites. Effective fleet performance management measures unavailable scheduled time and separates repair delays from problems local managers control.
Otherwise, the wrong depot gets the budget, the wrong manager gets blamed, and the real bottleneck, often parts or approvals, remains hidden.
A depot with 60 vehicles has more breakdown exposure than one with 15, especially if its trucks are older or work harder. Raw downtime totals measure lost capacity, not management performance.
ATRI's 2026 trucking analysis reported rising truck age and mileage in 2025 alongside an 8.6% increase in repair and maintenance costs. Age and workload therefore matter, although cost trends do not directly measure downtime.
Three factors can inflate a site's raw total:
Standardize events, divide by scheduled capacity, then compare peers.
Two sites may report identical totals despite measuring different periods. One starts at the driver's defect report; another waits for shop arrival. Fix these rules before ranking.
Start when a vehicle first becomes unavailable for assigned duty, whether through a defect report, failed inspection, breakdown, or shop arrival. Stop at confirmed release to service, not repair completion. Digital vehicle inspections help record reported defects consistently.
For audits, preserve both the original defect time and the later workshop arrival. Otherwise, a depot can appear faster simply by recording failures later.
Classify scheduled maintenance performed on its planned date as planned. Classify any event disrupting an assigned duty as unplanned, even if a work order is scheduled afterward. Apply one fleet downtime management process everywhere.
Record hours, not rounded days. A three hour interruption is not a full shift of lost capacity. A spare may cover the route, but the original vehicle stays unavailable until released. Track route coverage separately.
| Definition | Common Local Variation | Standard Rule to Adopt |
|---|---|---|
| Clock start | Shop arrival instead of first defect | First time unavailable for assigned duty |
| Clock stop | Repair completion | Confirmed release to service |
| Planned vs unplanned | Classification changed afterward | Follow scheduled assignment impact |
| Partial days | Any interruption rounded to one day | Record exact unavailable scheduled hours |
| Spare coverage | Clock stops when spare arrives | Keep original vehicle's clock running |
A week of downtime could mean extensive repairs or six days waiting for parts. One long delay can inflate a site average. Track stages to find the actual obstacle.
Record four mutually exclusive stages whose timestamps reconcile to total downtime:
Approvals usually belong to supervisors or customers, parts waits to purchasing and suppliers, and repairs to shops or vendors. The Technology & Maintenance Council's spring 2026 survey ranked technician shortages second among maintenance concerns, reinforcing why some delays extend beyond a depot's control.
AUTOsist's fleet maintenance work orders support status updates and repair details. Require staff to timestamp each transition; a status label alone does not establish elapsed waiting time.
Require a clear handoff at each stage. If two stages overlap, assign the elapsed time to the blocking cause rather than counting it twice.
Compare mean time to repair only after removing approval and parts queues from the active repair period.
Use downtime percentage of scheduled vehicle days to measure the share of planned service capacity lost.
Downtime % = (Downtime vehicle days / (Vehicles × Scheduled operating days)) × 100
Convert unavailable scheduled hours using consistent shift lengths. For differing schedules, sum each vehicle's scheduled hours instead. Equipment fleets may prefer downtime per 1,000 scheduled operating hours; downtime per vehicle ignores operating days.
Do not benchmark city vans against heavy service trucks. Apply vehicle type performance comparison principles to downtime and keep peer groups stable.
Group vehicles using four attributes:
The 2026 ATRI operational cost study reports 2025 repair and maintenance at 21.5 cents per mile, up 8.6%, with regional averages from 22.1 cents in the Northeast to 19.4 cents in South Central states. These are cost figures, not downtime targets.
Consider local service constraints and compare each site with its own baseline. Understand why fleet productivity varies by location before setting targets.
Consider 65 scheduled operating days in one quarter. Site A has 60 vehicles (20 vans, 40 heavy trucks), average age nine; Site B has 25 vans, average age four; Site C has 15 mixed vehicles, average age six.
| Site | Raw Downtime Days | Scheduled Vehicle Days | Downtime % |
|---|---|---|---|
| A, urban hub | 312 | 3,900 | 8.0% |
| B, suburban branch | 117 | 1,625 | 7.2% |
| C, rural yard | 59 | 975 | 6.1% |
The normalized rates are A: 312 / 3,900 = 8.0%, B: 117 / 1,625 = 7.2%, and C: 59 / 975 = 6.1%. A exceeds B by just 0.8 percentage points; van comparisons reverse the story.
| Site | Vehicles | Light Van Downtime % | Parts Wait Share |
|---|---|---|---|
| A | 60 | 52 / 1,300 = 4.0% | 30% |
| B | 25 | 117 / 1,625 = 7.2% | 58% |
| C | 15 | Mixed fleet, n/a | 35% |
A's vans lost 52 days and heavy trucks 260. B's comparable vans lost a greater share of scheduled capacity; parts waiting accounts for 58% of B's downtime. Investigate sourcing before blaming technicians. Small Site C needs a longer baseline.
Raw totals might send funds to A while hiding B's van problem. They could also shift blame from purchasing to technicians.
Avoid firm monthly rankings with fewer than 10 to 15 vehicles per peer group. Compare 90 day or 12 month rolling results with each site's baseline. One long breakdown can sharply move a 12 vehicle yard's percentage.
Report median and average event duration together. A few stuck jobs can inflate the average while leaving the median relatively steady. Investigate extremes instead of deleting valid events. NIST/SEMATECH guidance on outliers emphasizes examining unusual observations in context.
A Monthly Site Downtime Review Workflow
Repeat these seven steps monthly and resolve disputed records before deciding on corrective action.
Read the dominant delay bucket as a diagnostic clue:
Use parts inventory management data to test stocking gaps before ordering more.
Compare recurring patterns over several reviews. A single unusual repair should trigger investigation, not an immediate change to the location's staffing target.
Rankings can encourage delayed check ins and early closeouts. Audit timestamps, reward baseline improvement alongside peer performance, and use regional fleet reporting to share effective practices without assigning blame.
Fair comparison directs staffing, replacement budgets, and supplier changes toward actual causes. An apparent repair problem might instead need faster approval or better sourcing.
A 2026 FMCSA analysis cited industry vehicle downtime costs of $448 to $760 per day. Use fleet downtime cost measurement for financial decisions; begin the next review by fixing clock rules and locating controllable delays.