The short answer: Measure fleet downtime from the first signal that something is wrong (a fault code, a driver report, a missed service interval) to the moment the vehicle is back doing revenue work, not from the shop appointment to the repair. Split that time into waiting to be scheduled, waiting at the shop, and repair time. Price only the hours the vehicle was actually needed and unavailable, not every hour it was parked. Then track one more number: the share of repairs that were scheduled in advance versus done after a breakdown.
Why most downtime numbers are wrong
Downtime rarely shows up on a P&L, so most fleets estimate it. The estimates tend to go wrong in two directions.
Too short. Many fleets start the clock at the shop appointment. That misses the days between a fault code appearing and anyone booking the repair, which is often the longest stretch.
Too expensive. Other fleets multiply every day out of service by full daily revenue per vehicle. That overstates the cost. A van with a minor issue may still be running jobs, a spare may cover the route, and some "downtime" in the records is really a driver call-out or an empty schedule.
An honest number avoids both mistakes.
Define the clock
Use four timestamps for every unplanned repair:
- First signal. The fault code, warning light, driver complaint, or the date a service became overdue.
- Booked. The date a repair was scheduled.
- In service. The date the vehicle was handed to the shop or mechanic.
- Back on the road. The date it returned to normal work.
From these you get three durations: signal to booked (your coordination time), booked to back on the road (the shop's time), and the total.
Price it honestly
For each vehicle out of service, ask two questions:
- Was it needed? If a spare covered the work or there were no jobs, the cost is lower.
- What did it actually cost? Lost jobs, rental vehicles, overtime for other crews, and missed contract penalties are real. Full theoretical revenue per day usually is not.
Many fleets find the true cost is smaller than vendor ROI calculators claim, but concentrated in a few vehicles and a few long repairs. Those are the ones worth fixing first.
The number that predicts downtime
Track the scheduled versus reactive ratio: of all repairs in a month, what share were booked in advance (preventive maintenance, planned repairs) versus done after a breakdown. Fleets that move this ratio toward scheduled work see fewer surprise outages, because planned work happens when the vehicle is not needed.
How HoneyRuns helps
HoneyRuns' AI agent, Riggs, watches telematics and service intervals, so the first signal is captured when it happens rather than when someone notices. It books the repair and follows up with the shop until the vehicle is back, which shrinks the signal-to-booked time that most fleets never measure.
Frequently Asked Questions
Q: How do you measure fleet vehicle downtime? A: Record when the problem first appeared, when the repair was booked, when the vehicle went to the shop, and when it returned to work. Measure the total from first signal to back on the road, not just the shop visit.
Q: How much does fleet vehicle downtime cost per day? A: It depends on whether the vehicle was actually needed. Count lost jobs, rentals, overtime and penalties for the days it was needed and unavailable. Multiplying every idle day by full daily revenue overstates the cost.
Q: What is a good scheduled vs reactive maintenance ratio? A: Fleets generally aim to have most repairs scheduled in advance rather than done after breakdowns. Track the ratio monthly and work to move it toward scheduled work.
Q: Why focus on cost of downtime instead of cost of maintenance? A: Cutting maintenance spend can raise downtime a few months later, when skipped service turns into breakdowns. Watching both shows whether savings are real.
Q: Where does most fleet downtime come from? A: Often from the time between a problem appearing and a repair being booked, and from waiting at the shop for estimates, approvals and parts, rather than from the repair work itself.
Get Started with HoneyRuns
Connect your telematics and see how long open issues have been waiting to be booked. Get started.
HoneyRuns gets fleet maintenance done. It watches mileage, intervals, and telematics, books the repair with the shops and vendors you already use, stays on the driver and the shop until the vehicle is back, and logs the completed service in the system you already run. Your team approves repair estimates before work goes ahead. Founded by fleet operators who manage 70 vehicles across three fleets today.