Miya Bholat Miya Bholat

Nov 16, 2026


Key Takeaways

  1. Raw totals mislead. Larger and older fleets accumulate more downtime even when their comparable vehicles perform better.
  2. Lock the clock rules. Standardize start, release, planned work, partial days, and spares.
  3. Separate waiting from repair. Diagnosis, approvals, parts, and repair need different owners.
  4. Normalize before ranking. Compare scheduled vehicle days within similar classes, ages, and workloads.
  5. Protect small sites. Use longer windows and investigate extreme events.

Why Raw Downtime Totals Punish Your Hardest-Working Sites

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:

  • Fleet size: More scheduled vehicles create more possible downtime days.
  • Age and condition: Older units can require more frequent or complicated repairs.
  • Duty intensity: Heavy assignments expose vehicles to more service demands.

Standardize events, divide by scheduled capacity, then compare peers.

Lock the Downtime Clock Before You Compare Anything

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.

When the Clock Starts and Stops

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.

Downtime timeline from first defect report to confirmed release to service

Planned vs Unplanned: One Rule for Every Site

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.

Partial Days and Spare Swaps

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.

Downtime Definitions to Standardize Across Sites

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

Split Every Downtime Event Into Wait Time and Wrench Time

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.

The Four Delay Buckets

Record four mutually exclusive stages whose timestamps reconcile to total downtime:

  • Triage and diagnosis: From the initial report until the fault and repair plan are established.
  • Approval: Time awaiting an authorized repair decision.
  • Parts wait: Time blocked because necessary parts are unavailable.
  • Repair: Active work by the internal technician or outside vendor, including final checks.

Who Owns Each Bucket

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.

Normalize Downtime So Sites Compete on Equal Ground

Pick the Right Denominator

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.

Build Peer Groups by Class, Age Band, and Duty Cycle

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:

  • Class: Light vans, heavy trucks, or comparable equipment types.
  • Age band: 0 to 5 years, 6 to 10 years, and over 10 years.
  • Duty cycle: Similar loads, mileage, and operating intensity.
  • Schedule: Comparable working days and shift hours.

Account for Regional Cost Differences

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.

Worked Example: Three Sites, Raw vs Normalized

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.

Raw vs Normalized Downtime by Site

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.

Peer Group and Parts Wait Comparison

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.

Handle Small Sites and Outliers Without Distorting the Ranking

Set a Minimum Sample Before Ranking a Site

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 Medians, Then Investigate the Long Tail

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.

Monthly site downtime review comparing delay buckets across depots

A Monthly Site Downtime Review Workflow

Repeat these seven steps monthly and resolve disputed records before deciding on corrective action.

01 Collect events. Export work order and inspection incidents by site, class, age, and schedule.
↓
02 Audit timestamps. Verify unavailability and release times; resolve gaps.
↓
03 Split delays. Reconcile diagnosis, approval, parts, and repair durations.
↓
04 Calculate rates. Compile data using customizable fleet reports and dashboards, then calculate site and peer group percentages.
↓
05 Flag weak samples. Mark small groups and investigate long events.
↓
06 Find the bottleneck. Identify the leading delay bucket and accountable team.
↓
07 Assign and revisit. Name an owner and action for each site, then review next month.

Reading the Patterns

Read the dominant delay bucket as a diagnostic clue:

  • High parts wait: Review stocking policies, suppliers, and delivery promises.
  • High approval time: Examine decision rights and authorization limits.
  • High repair time with repeat failures: Check repair quality and diagnostic capability.
  • Low recorded downtime with missed PM: Investigate possible underreporting.

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.

Keep the Comparison From Turning Into a Blame Game

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.

What Fair Site Comparisons Unlock for Your Fleet

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.

Frequently Asked Questions

  1. How do you compare downtime between depots with different operating schedules?
    Divide unavailable scheduled vehicle hours by total scheduled vehicle hours, then multiply by 100. Compare vehicles within similar classes, age bands, and duty cycles.
  2. Does vehicle downtime stop when a spare vehicle takes over?
    No. The original vehicle remains in downtime until it is released back to service. Track spare vehicle coverage separately.
  3. Should parts and approval delays count toward fleet downtime?
    Yes. Both count while the vehicle remains unavailable. Record these delays separately from active repair time to identify who should resolve them.
  4. How should small fleet locations be compared with larger depots?
    Use rolling 90 day or 12 month data for small peer groups, particularly those with fewer than 10 to 15 vehicles. Compare their performance against their own history and similar vehicles rather than relying on monthly rankings.
  5. Why is average vehicle downtime much higher than the median?
    A few unusually long repair events can push the average above the median. Investigate those events for parts shortages, approval delays, or extended repairs before judging site performance.



Related Blogs & Articles

See how AUTOsist simplifies fleet Management

Schedule a live demo and/or start a free trial of our Fleet Maintenance Software