Uptime is the number your operations team feels every day and almost nobody calculates. Ask three fleet managers what their uptime was last month and you will get three different definitions, two of which exclude the days that hurt the most.
Define it, break it into its parts, and the work of improving it stops being vague. Most of what you get back is not mechanical. It is time spent waiting.
Define uptime so the number means something
Uptime percentage = (total fleet vehicle-days minus downtime vehicle-days) divided by total fleet vehicle-days, times 100.
The definition that matters is downtime: every day the vehicle could not do its assigned work, counted from when the defect was reported to when it was back in service and available. Not from when the shop opened the ticket. Not excluding weekends. If a van broke down Friday afternoon and came back Tuesday, that is four days, not one.
Count scheduled PM (preventive maintenance) days separately from unscheduled repair days. They behave differently and you manage them differently. Scheduled downtime you can plan around; unscheduled downtime is the one that costs you a route.
Work out where your downtime actually goes
Take a 60-vehicle fleet over a 30-day month: 1,800 available vehicle-days. Say you lose 42 vehicle-days. That is 97.7% uptime, which sounds fine until you break the 42 days open.
Split every downtime event into four segments:
- Defect reported to shop arrival, which covers triage, approval to move, towing, and finding a shop with capacity.
- Shop arrival to work started, which is the shop's queue and your estimate approval.
- Work started to work finished, which is actual labor plus parts waiting.
- Work finished to vehicle available, which is invoicing, payment, and somebody driving over to collect it.
Run this on twenty repair orders and the shape is usually the same: labor is hours, everything around it is days. Nine of those 42 days might be wrench time. The other 33 are queues, callbacks, and approvals sitting in somebody's inbox.
That matters because it tells you what to fix. Buying better parts or a stricter PM schedule does nothing to the 33. Fixing how fast an estimate gets reviewed and approved does.
The levers, in order of how fast they move the number
Cut approval latency first
This is the cheapest day you will ever get back, because it costs a policy decision rather than money. Set a dollar threshold under which repairs are pre-approved and nobody waits for a human. Set a second threshold that routes to a named person with a defined response window, including evenings and weekends. The failure mode you are removing is the vehicle that sat from Friday at 4pm to Monday at 10am because a $340 estimate needed a signature.
Route on shop performance, not proximity
The nearest shop is often the slowest one for your vehicle class. Build a scorecard from your own repair history: average cycle time by repair category, comeback rate, and estimate adjustment rate. Send the urgent work to the shops that turn it fast and the routine work to whoever is cheapest and available. Keep the shops you already trust in the mix; a good relationship you built over five years is worth more than a marginal rate improvement.
Fix intake so defects arrive the day they happen
Every day between a driver noticing something and a repair order existing is a day of downtime you have already spent. Make reporting take under a minute, from the cab, with a photo. Telematics fault codes cover part of this but not the cracked mirror, the door that will not latch, or the vibration under braking. Track median days from defect reported to repair order opened and treat anything over two as an intake problem.
Use PM compliance to convert unscheduled days into scheduled ones
You cannot eliminate downtime, but you can move it into slots you chose. PM compliance rate is services completed inside their due window divided by services due, times 100. Track it monthly by location. A fleet with high compliance still has downtime; it just knows when.
Handle parts availability before it happens
Parts waiting is the segment most fleets treat as weather. It is not entirely. Stock the fast-moving consumables for your dominant platforms, and ask shops to quote parts lead time as part of the estimate rather than discovering a three-week backorder on day four. For a mixed fleet, standardising platforms is a slow lever, but it is the one that eventually shrinks this segment for good.
Manage driver behavior for the wear, not the theatre
Harsh braking and acceleration events correlate with brake and tire spend, and that is a real return over quarters rather than weeks. Coach on the two or three behaviors that map to your actual repair history. Scorecards that track eleven metrics get ignored by everyone including the person who built them.
Benchmarks to set for yourself
Rather than chasing an industry figure that will not match your duty cycle, set internal targets and watch the trend.
- Uptime percentage, tracked monthly, split scheduled and unscheduled. The split matters more than the headline.
- Average unscheduled repair cycle time in days, from defect reported to vehicle available.
- Approval latency in hours, from estimate received to decision sent.
- Defect-to-repair-order lag in days, median rather than mean.
- Repeat repair rate: repair orders reopened for the same complaint within 30 days.
Set a baseline this month and a target for the next quarter on each. Against the 60-vehicle example, moving average cycle time from 5 days to 3.5 on unscheduled work is worth about 12 vehicle-days a month, which is most of a vehicle you did not have to buy.
FAQ
What counts as a good fleet uptime percentage?
It depends entirely on duty cycle and vehicle age, which is why a borrowed benchmark is close to useless. Measure your own number monthly, split scheduled from unscheduled, and compare it against your own trend and against similar vehicle classes inside your fleet. A stable headline number hiding a rising unscheduled share is a worse position than a slightly lower number that is trending the right way.
Should scheduled maintenance count against uptime?
Track it, but separately. A vehicle in for a planned PM service is still unavailable, so excluding it flatters the number and hides a real capacity constraint. Reporting the two figures side by side shows you whether your total downtime is falling or just moving between categories.
What is the fastest way to improve fleet vehicle uptime?
Approval latency, in almost every fleet. It requires no capital, no new vendor, and no vehicles: a pre-approval threshold plus a named escalation path with a response window. Fleets that time their repair segments usually find more idle days sitting in approval queues than in shop bays.
How do telematics help with uptime?
They are good at fault codes, odometer capture for PM triggers, and location for dispatching a tow. They are not good at the physical defects a driver sees, and they do nothing about the days lost after a vehicle reaches a shop. Treat telematics as an intake improvement, not an uptime program.
Does a spare vehicle pool make sense?
Run the arithmetic before assuming it does. A spare costs depreciation, insurance, registration, and its own PM. If your unscheduled downtime is 42 vehicle-days a month across 60 units, a couple of spares covers a lot of it, but so does cutting cycle time by a third, and the second option does not add an asset. Compare the annual cost of the spare against the value of the days you would recover by fixing cycle time instead.
Where ServiceUp fits
ServiceUp is the agentic repair platform for modern fleets. Your FMS (fleet management system) manages your fleet. We manage your repairs. Agents take the intake, route each vehicle to the right shop, audit estimates against your pricing, warranty, and maintenance policies so approvals happen in seconds rather than days, and monitor repairs in progress so a slipping job surfaces while you can still act on it. Across the fleets running repairs on the platform, that comes out at 32% faster cycle times, which is the segment of downtime most fleets have the hardest time reaching. More on how it works for fleets.
.avif)

.png)

.png)


