The difference between a 5-day recon operation and a 15-day one is rarely shop capacity. It's scheduling discipline. Here are nine practices high-performing used car operations run every single day — and why each one works.
Recon scheduling isn't about working faster — the mechanical work on most vehicles takes hours, while elapsed time runs 7–15 days at untracked stores. The job of scheduling is to eliminate waiting between stages of the recon process. These nine practices do exactly that, roughly in order of impact.
The days-to-frontline clock starts at acquisition, whether you're watching it or not. A trade-in taken Saturday that isn't logged until Tuesday has burned three holding-cost days invisibly. Same-day intake logging is the cheapest recon improvement that exists: it costs nothing and recovers 1–3 days at most stores.
Every acquired vehicle gets a deadline for the retail/wholesale/auction decision — and the deadline is enforced by a rule, not a reminder. Borderline cars are where this matters: without a window they sit a week in "pending," depreciating daily, before getting wholesaled anyway. The window forces the call while the car is freshest and worth the most.
If your techs can turn six recon units a day, scheduling nine just builds an invisible queue. Capacity-based loading means the day's recon schedule reflects actual available hours — internal and vendor — so every vehicle scheduled is a vehicle that actually moves. Overloading doesn't speed anything up; it just hides which cars are waiting.
The single biggest source of lost recon days is the gap between stages: the car is done with mechanical, but detail finds out at tomorrow's huddle — or next week's lot walk. Every stage change should automatically notify the next team the moment it happens. No handoff should depend on someone remembering to mention it.
One short daily scan: which vehicles have been in each stage the longest, and why? That's it. A daily aging review catches a stuck vehicle 5–6 days earlier than the weekly inventory meeting. It only works when stage and elapsed time are tracked automatically per vehicle — you can't review a whiteboard that nobody updated.
Body shops, wheel repair, glass, upholstery — outside vendors are part of your days-to-frontline number whether you measure them or not. Every vendor job needs a pickup date, a promised return date, and an actual return date on the record. Slow vendors don't get better until their numbers are visible; once they are, the conversation gets easy.
A listing's first two weeks online generate its highest views and lead volume — that window starts when the photos go live, not when the car is ready. Batch photography ("the photographer comes Tuesdays and Fridays") costs every off-cycle vehicle 1–3 days of peak demand. Photograph same-day on detail completion, triggered by the stage-change notification from practice #4.
Estimate approvals stall when approving requires research. Give every vehicle a recon budget at disposition time, tied to its exit price, and log every cost against the VIN as it's incurred. Then approvals take minutes — the manager sees budget vs. actual on one screen — and overruns surface while they can still be stopped.
Once per week, look at average time per stage across all vehicles. One stage will be the bottleneck — fix that one, then re-measure. This is how 7-day stores become 5-day stores: not with a big overhaul, but by repeatedly finding and fixing the current slowest stage. Without per-stage data, every improvement effort is a guess.
The common thread: every practice above is a visibility-and-rules problem, not an effort problem. That's why they're nearly impossible to sustain on whiteboards and spreadsheets — and why recon software exists: AIRS enforces the holding windows, automates the handoffs and notifications, tracks vendor turnaround and per-VIN budgets, and produces the aging and stage-time reports — so the discipline survives busy weeks and staff turnover.
Related: The recon process, step by step · Days to frontline explained · What is recon software?
AIRS runs the holding windows, handoffs, vendor tracking, and aging reports for you — so the discipline doesn't depend on memory.
Request a Demo