A used vehicle can clear inspection by 10:00 a.m. and still be sitting in the same service lane three days later, waiting on a decision nobody realizes is theirs to make. Why do repair approvals stall? Usually not because the repair itself is complicated. They stall because the dealership has allowed a decision that affects gross, turn, and holding cost to live in a text thread, on a handwritten repair order, or in one manager’s memory.
Every day a vehicle waits for approval, the clock keeps running. The unit is not getting detailed, photographed, merchandised, or moved to the front line. A small repair decision can become a get-ready bottleneck that holds up thousands of dollars in inventory.
Repair Approval Delays Usually Start Before the Approval
Most dealerships label the problem as a slow approval process. The real issue often starts earlier, at intake or inspection. If the buyer, used car manager, service advisor, and technician do not have the same expectation for the vehicle, the estimate arrives without context.
Is this a retail unit, a wholesale candidate, or an uncertain acquisition? What was the target recon budget? Is the concern safety-related, required for certification, cosmetic, or a judgment call on marketability? When those facts are not visible with the repair request, a manager has to stop, investigate, and ask questions that should have been answered before the unit entered the shop.
That delay may look reasonable one vehicle at a time. Across 40, 80, or 150 used units, it becomes a serious cycle-time problem. The store is not losing time because people are lazy. It is losing time because the workflow does not force a clean handoff from inspection to decision.
The estimate is incomplete or hard to trust
A vague note such as “needs front end work” is not an approval request. Neither is an estimate with no labor breakdown, no photos, no diagnostic detail, and no explanation of whether the condition affects safety, retail quality, or certification.
Managers delay decisions when they do not trust the information in front of them. That is rational. Approving a $1,800 repair on thin documentation can damage a deal. But sending the vehicle back and forth for clarification creates more work and leaves the unit parked.
The answer is not to approve every estimate faster. It is to require a decision-ready repair ticket. The request should show the vehicle, the concern, the recommended correction, estimated cost, supporting notes or images when useful, and the person requesting approval. A manager should be able to make a call without hunting through a repair order, calling the shop, and finding the original buyer.
The wrong person has the authority
Approval authority is often assumed rather than documented. A service manager may believe the used car manager owns the decision. The used car manager may think anything above a certain dollar amount goes to the GM. The GM may assume the buyer already approved a recon budget at acquisition.
When authority is unclear, everyone protects themselves by waiting. No one wants to approve an expense outside their lane, especially if the unit later gets wholesaled or the deal exceeds its planned cost.
Set approval levels that match how your store operates. A fixed dollar threshold can work for routine repairs, but it should not be the only rule. Safety issues, certification requirements, bodywork, and repeated diagnosis may need separate paths. The key is that the request routes to one named decision-maker, with an escalation path if that person has not acted by a defined time.
Why Do Repair Approvals Stall Between Departments?
The used-car department owns the inventory, service performs the work, parts may control the availability, and an outside vendor may handle glass, tires, keys, bodywork, or alignment. Each department has valid priorities. The problem begins when no one owns the entire vehicle’s path to front line ready.
A technician can complete an inspection quickly, but the repair still waits if the estimate is not communicated. The used car manager can approve it immediately, but the unit still waits if a part must be ordered and nobody updates the expected arrival. A vendor can finish the work, but the vehicle can remain stuck if detail or photography never receives the handoff.
This is where phone calls, verbal updates, and separate spreadsheets break down. They may work when one manager is personally chasing every vehicle. They do not scale across multiple departments, days off, vacations, shifting schedules, or a dealer group with several rooftops.
The dealership needs one visible status for every unit: what stage it is in, what is blocking it, what decision is needed, who owns the next step, and how long it has been waiting. Without that, the loudest vehicle gets attention while the quiet units age unnoticed.
No timestamp means no urgency
If an approval request has no timestamp, it is easy to say it was sent “earlier this week.” If no one can see the age of the request, there is no objective way to distinguish a normal queue from a stalled unit.
Timestamps change the conversation. A manager can see that a $325 brake approval has waited 26 hours, while a $2,100 transmission decision has waited four. That makes prioritization possible. It also exposes whether the bottleneck is inspection quality, manager availability, parts delays, or poor follow-up.
That which is measured improves. The goal is not to embarrass a department. It is to identify the exact handoff where a vehicle stopped moving and correct it before holding cost turns a profitable acquisition into a compromised retail decision.
Build an Approval Process That Moves Units
A workable process does not need more meetings or a new layer of paperwork. It needs clear operating rules and a shared place to see the work.
Start at acquisition. Record the intended retail strategy and expected recon budget when the vehicle enters inventory. That does not eliminate unexpected repairs, but it gives the approving manager a baseline. An estimate that pushes the unit beyond plan should trigger a different decision than one that falls within the anticipated budget.
At inspection, separate findings into categories that support fast judgment: safety and compliance, mechanical reliability, certification requirements, cosmetic condition, and discretionary improvements. A tire that fails inspection is not the same decision as paintless dent repair on a vehicle already priced aggressively. Combining everything into one total estimate slows the conversation because the manager may agree with some work and question the rest.
Then assign one owner to every pending approval. Not a department. Not “management.” A named person. If the primary approver is unavailable, the workflow should automatically identify the backup or escalate to the next level. Waiting for a manager to return from a meeting is sometimes unavoidable. Discovering two days later that nobody knew the manager was out is not.
Set a service-level expectation for response time. The right target depends on the store, volume, and complexity of the unit, but routine repair decisions should not sit open overnight without a reason. Use alerts for aging approvals, not just new requests. A notification when the request is created is helpful; an alert when the unit has been idle for eight or 24 hours is what prevents silent delays.
Finally, track the outcomes. Look at average approval time by department, manager, repair category, and vendor. Review the units with the longest approval delays and ask a direct question: was the delay caused by missing information, unclear authority, a legitimate business decision, or lack of follow-up? Those are different problems and require different fixes.
Visibility Is Not Micromanagement
Some stores resist central tracking because they do not want another system for employees to update. That concern is fair. A complicated tool that adds duplicate data entry will fail on the service drive and in the recon lane.
But the alternative is not no process. The alternative is an invisible process built on calls, texts, whiteboards, and personal memory. That approach gives leadership no reliable report of where vehicles are aging or why.
A dealership-native get-ready platform such as AutoGetReady gives the used car manager, service team, vendors, and leadership a shared view of the same unit. Repair tickets, status changes, assignments, alerts, and timestamps make the next required action visible. The platform does not make a difficult repair decision for the store. It makes it harder for a necessary decision to disappear.
The trade-off is accountability. When every task has an owner and every status has a timestamp, the store can no longer explain away delays with general statements about being busy. For a Dealer Principal or GM, that is the point. You cannot manage reconditioning cycle time from a weekly verbal update.
A repair approval should be a short, documented decision in the path to retail, not a parked vehicle waiting for somebody to remember it. Put the facts in front of the right person, assign the next step, measure the wait, and make aging units impossible to ignore. The front line will reflect the discipline of the process behind it.
