A service van goes into a shop on Monday morning for a brake job and a sensor calibration. The mechanical work takes four hours. The van leaves the lot the following Monday.

For six of those days, the van was just waiting.

When you ask where the time went, the answers tend to sound alike. The estimate sat in an inbox for a day. The service advisor called the fleet manager and got voicemail. A supplement needed a second approval from someone who was traveling, and when the work was finally done on Friday afternoon, nobody came to get the van until Monday. No one person dropped the ball. The van simply had nobody whose job it was to keep it moving.

That kind of downtime rarely shows up in a budget, because from the office it looks like a busy inbox rather than a van off the road.

Why Parts Get Blamed for Fleet Downtime

The working definition I use is simple: administrative downtime is every hour a vehicle is out of service while nobody is working on it. Total time out of service splits into the hours someone had a wrench on the vehicle and everything else.

Most fleets know the total, but very few can split it into those two parts.

Our research at ServiceUp found that roughly 72% of fleet operators hit maintenance and repair problems weekly or monthly. When we asked what frustrates them most, half named parts availability. I'd push back a little on our own survey here. My read is that parts get named so often because they're the easiest delay to see.

A parts delay comes with a tracking number, a supplier, an ETA and someone to call, so it leaves a record. Most of the other waiting doesn't. Think about the van that sat for a day and a half before it reached a shop, the estimate that went back for a second approval once the shop opened things up, or the truck that was finished and then sat in the lot because nobody was told. None of that gets written down anywhere. When someone reconstructs a bad repair after the fact, they count what left a trace, so parts end up taking the blame even though much of the waiting was within the fleet's control.

Fleets have spent a decade building visibility into their vehicles. A manager can tell you how long a truck idled on Tuesday and how hard the driver braked coming off a specific ramp. The record of a $4,200 repair that took nine days is a phone call, three emails and a PDF on someone's laptop. Closing that gap starts with writing down a handful of times.

10 Repair Timestamps Every Fleet Should Track

Most fleets record two moments in a repair: when the vehicle went out of service and when it came back. Many add a third by accident, the invoice date, which tells you when the shop got around to billing and very little else. The useful information lives in between.

These are the timestamps I'd capture on every repair, in order:

Add a timestamp for every supplement: when the shop asked, and when you answered. Supplements restart the approval clock in the middle of a repair, and fleets almost never measure them.

You don't need software to start. A shared spreadsheet with ten date columns will do, as long as one person owns keeping it current and your shops know you're tracking it. In my experience, shops move faster once they know someone is watching the clock.

Where Fleet Approvals Stall

Once fleets start recording these times, the same five choke points show up. The first is the initial estimate. It usually lands in a shared inbox, or on the phone of a manager who's out in the field all day, and the shop can't order parts or start work until somebody answers. Every hour it waits is an hour added to downtime.

Supplements come next. A shop opens up a brake job and finds a seized caliper, or pulls a bumper and finds a cracked bracket, and now there's a second estimate sitting at the back of the same queue the first one waited in. That's how a four-hour job turns into a three-day one.

Then there's the second signature. Plenty of fleets route approvals through a fleet management company and an internal manager, or send anything over a dollar limit to finance. Each handoff adds another queue, and the people involved usually can't see each other's.

The calendar matters more than most people expect. An estimate that shows up at 4:30 on a Friday will usually wait until Monday, which adds two days to a repair that hasn't changed at all.

Finally, there's pickup. The shop finishes, leaves a voicemail, and the vehicle sits in the lot. Strictly speaking that isn't an approval problem, but it's administrative downtime all the same, and it's the gap fleets most often forget to measure.

Warranty and manufacturer authorizations belong on the list too. They run on someone else's schedule, so the best you can do is start them on day one.

How to Speed Up Fleet Repair Approvals

A lot of approval delay comes from making the same decision from scratch every time an estimate arrives. It's faster to make it once, in writing, ahead of time.

A pre-approved menu is the easiest place to start. Oil changes, tires, brakes and other routine work with predictable pricing shouldn't need anyone's signature below a set dollar amount, so give shops the list and the limit and let them proceed.

Above that, set dollar tiers. One common setup has a fleet coordinator approving up to a mid-range figure and a manager approving anything above it. The right numbers depend on your vehicles and margins, but every estimate should have exactly one owner the moment it arrives.

Each tier also needs a clock. If an estimate goes unanswered for a set number of business hours (four is a reasonable starting point), it should move to the next person automatically. Without that, a tier system mostly tells you whose inbox the estimate is stuck in.

Every approver should have a named backup, too. Vacations, field days and flights are predictable, and a process that stops whenever one person is out was built wrong.

It also helps to write a supplement rule. For example, you might approve any supplement under a set percentage of the original estimate automatically, as long as the shop documents it with photos, and send bigger ones through the normal tiers.

Review all of it once a quarter. Look at what got approved under each threshold and whether anything went wrong. If nothing did, raise the limit, and if something did, you'll know which rule to tighten. Nobody should wave through a $14,000 collision estimate, but routine decisions shouldn't be eating a manager's week either. Clearing them off the pile is how the dozen or so estimates a month that need judgment finally get it.

Grading Shops on More than Wrench Time

Most shop reviews come down to price and workmanship. Those matter, but they won't tell you why one shop returns vehicles in two days and another takes six for the same job.

The timestamps above give you a better scorecard:

When you run these by shop, the rankings often flip. A shop with excellent technicians and a slow front desk can cost you more days than an average shop that answers its phone, and that's fixable once you can show the shop its own numbers.

Run them on your own team too. The time between estimate submitted and estimate approved belongs to you, and shops will take your scorecard more seriously once they see you measure yourself the same way.

Try our calculator below and bookmark this page to use it again in the future. Or keep scrolling to keep reading!

The 20-Repair Fleet Downtime Audit

You can do all of this without waiting for a new system. Block out an afternoon and work backward from records you already have.

1. Pull your last 20 completed unscheduled repairs. Leave out routine preventive maintenance, which tends to follow its own schedule and will flatter the results.
2. For each repair, write down three dates: when the vehicle went out of service, when the shop finished the physical work, and when the vehicle returned to service. Add the billed labor hours from the invoice. It's an imperfect stand-in for wrench time, but it's one you already have.
3. Calculate total days out of service and compare it with the labor hours. A repair with six billed hours and nine days out has a story worth finding.
4. For each repair, write one line on where the biggest gap came from: waiting on approval, waiting on parts, waiting in the shop's queue, or waiting for pickup. If nobody can reconstruct it, write “unknown.” That's a finding too, and usually the most common one.
5. Sort the list and look for patterns, such as a shop that's always late, an approver whose name keeps coming up, repairs that stall whenever they hit a weekend, or supplements that add two days apiece.
6. Fix the biggest category first, then run the same audit on your next 20 repairs about 90 days later.

One Last-Mile Fleet's Numbers

We pulled these timestamps for a last-mile delivery operator we work with, a fleet of about 80 vans. We looked at the 1,221 repairs it sent to shops in the 12 months ending September 2026.

The typical repair kept a van off the road for four days. Nearly a third ran past a week, which pulled the average to 7.4 days.

Most of that time went to waiting that nobody owned. On average, a van spent about a day and a half between being reported down and getting to a shop. Almost half of the repairs (48%) needed more than one round of approval, and each extra round restarted the wait partway through the job. Where shops gave a completion date, they met it only about one time in four.

The longest stretch, from approval to finished work, averaged five and a half days. That stretch holds parts, the shop's queue and the repair itself, and the fleet's records didn't separate the three.

The first approval was the one step that moved quickly. The fleet answered a first estimate in under four hours on average, and the typical one cleared within minutes, which didn't do much good once everything after it slowed down.

For this fleet, the next steps have little to do with approval speed. It needs to hold shops to the dates they give, add parts-ordered and parts-received timestamps so that five-and-a-half-day stretch can be broken down, and cut the time it takes a van to get to a shop. Your own numbers will probably look different, which is the whole reason to measure them.

Where to Start Reducing Downtime

Everything here can run on a spreadsheet. The harder part is deciding that the time a vehicle spends waiting is as much your responsibility as the time it spends on a lift.

So pull your last 20 repairs this week and compare the day the shop finished the work with the day each vehicle went back on the road. If those dates line up, your process is in good shape. If they don't, and they usually don't, the gap between them is where your downtime is hiding.