Why does it take so long to get a repair approved?

What actually happens between the estimate and the approval?

A vehicle is diagnosed. The shop writes an estimate. Then the estimate has to reach someone who can say yes.

That person needs to confirm the vehicle is theirs, look at what was done to it last time, judge whether the price is reasonable, check the amount against whatever threshold applies to them, and sometimes get a second signature. Each of those steps is reasonable. Together they take days, because the information needed for them lives in different places and none of it is where the estimate is.

Meanwhile the vehicle sits. The bay it occupies can't be sold to anyone else. The shop can't order parts, because ordering parts against unapproved work is how shops end up eating the cost. And the fleet can't plan around a return date that doesn't exist yet.

Why is the delay invisible?

Because no system records it.

The shop's work order shows when the job started and when it finished. The fleet's invoice shows what was paid. Neither captures the gap between the estimate being written and the estimate being approved — which is frequently the largest single block of time in the whole event.

That invisibility has a specific consequence. A fleet looking at a slow repair sees a slow shop. It has no way to see that the vehicle spent three of its five days waiting for one of its own people to respond. So the wrong lever gets pulled: shops get pressured on turnaround they don't control, and the actual delay is untouched.

What does approval delay cost?

Two things at once, and only one of them is obvious.

The vehicle. A day waiting for a signature costs exactly what any other down day costs — between $500 and $1,500 for most fleets, depending on what the vehicle earns. The cause of the delay makes no difference to the price of it.

The people. Chasing approvals is a real job that nobody is hired to do. On the fleet side it's the calls and the follow-ups and the reconstruction of what was agreed. On the shop side it's the unbilled time spent answering "any update?" — and the work that stopped while someone went to find out.

Why doesn't the industry fix it?

Because each individual relationship works well enough.

A fleet with a single shop can run approvals on a phone call. The trouble is that a fleet of any size uses dozens of shops, and every one of those relationships is bilateral, manual and slightly different. There are more than 300,000 independent repair shops in the United States, according to IBISWorld and Cox Automotive data, and no two of them work the same way. Nothing that holds together at one shop holds together at forty.

So the delay doesn't come from anyone being slow. It comes from a coordination problem that only appears at scale — and appears in a form that no single party can see all of.

The short version

Approval delay is downtime that costs full price and shows up nowhere. It's produced by the distance between the people who write estimates and the people who authorise them, and it grows with the number of shops a fleet uses. Measuring it is the first step, and most fleets currently can't.

Autograff is being built around this gap. ShopOS is our product for repair shops and FleetOS is our product for fleet operators.

Key facts

• Approval delay is frequently the largest single block of time in a repair event, and no standard system records it.
• A day waiting for authorisation costs the same as any other down day — $500–$1,500 per vehicle for most fleets.
• Work orders capture start and finish; invoices capture cost. Neither captures the gap between estimate and approval.
• Because the delay is invisible, slow approvals are commonly misread as slow shops.
• The problem scales with the number of shops a fleet uses: there are 300,000+ independent shops in the US (IBISWorld, Cox Automotive), and each relationship is run separately.