Reconditioning KPIs: the recon scoreboard every used-car department should track.

Average days in recon

Average days in recon is the headline number: the mean number of days a unit spends in the workflow, from intake to frontline-ready. Sum the recon days across completed units and divide by the number of units completed in the same period.

This metric gets attention because it rolls every handoff, approval wait, parts delay, and finishing step into one number. Measure it with the same clock on every completed unit, establish your own baseline, then set a target that fits the store and vehicle mix.

That gap isn't a moral failing; it's usually the sum of small, invisible delays — a car waiting on an approval, a part on backorder, a unit that's mechanically done but nobody moved it to detail. None of those show up in a single total until you measure it. Average days in recon rolls all of that up into one figure, which is exactly why it's the right place to start before you break the total into its parts. For the deep dive on measuring and trimming it, see average recon cycle time.

Total recon time vs time to sale-ready

These two terms get used loosely, so here are plain, vendor-neutral definitions. Total recon time measures acquisition to frontline-ready — the moment the car is mechanically and cosmetically done and could be sold. Time to sale-ready goes one step further: acquisition to fully merchandised and listed online, with photos and a price.

• Total recon time: acquisition date to frontline-ready date. The car is sellable, but not necessarily findable by a shopper.
• Frontline-ready stop: recon complete, photographed, priced, and merchandised/ready to list.

Both clocks matter because a short in-process cycle can hide a long wait before intake. Use the same frontline-ready stop for each: recon complete, photographed, priced, and merchandised/ready to list.

Step-level cycle time

A single average-days number tells you the total but hides the bottleneck. Step-level cycle time — dwell by stage — fixes that by measuring how long units sit in each stage: intake, mechanical, parts, body/detail, and photos. The formula is the same idea applied per stage: average the days each unit spends in a given step.

When you split the total this way, the volatile stages jump out. Parts and approvals are usually the spikiest, because they depend on something or someone outside the shop — a back-ordered component, an advisor who hasn't approved the work yet. Mechanical and detail tend to be steadier. Seeing dwell per stage is what turns "our recon is slow" into "our cars wait three days on parts approval," which is a problem you can actually work. This is the level of detail covered in average recon cycle time, and it maps directly onto each stage of the used-car recon process.

Reconditioning cost per unit

Recon cost per unit is the cost-side anchor of the scoreboard: total reconditioning spend divided by the number of units completed in the same period. What goes into "spend" is parts, technician labor, and any sublet or vendor work — the full bill to make a car frontline-ready, not just the headline repair.

There is no approved universal cost-per-unit range on this page. Build the target from completed units at your store, then segment it by vehicle mix so an older, higher-mileage book is not compared with late-model inventory as if the work were the same.

The reason it belongs on the board even though most managers fixate on time: cost per unit is what makes the time conversation financial. Track it over a few months and you'll see whether your spend is drifting up — a trend that's invisible on any single repair order.

Cost-to-market

Cost-to-market ties the time metrics and the cost metrics together. It's the total cost to get a unit frontline-ready: recon cost plus the holding cost accrued while the car moves through recon.

This is the KPI that connects most directly to front-end gross, because it captures something a flat recon bill can't. Two cars can carry the identical $1,200 recon cost, but if one cleared recon in 4 days and the other took 14, their cost-to-market is different — the slow one quietly absorbed ten extra days of holding cost per day. That difference comes straight out of gross when the car finally sells. Lowering recon days is the lever that lowers cost-to-market without touching the repair work itself.

Holding cost / aged-inventory exposure

Holding cost is the per-day carry on a unit you own but haven't sold. Its components can include floorplan interest, depreciation assumptions, fixed overhead, and opportunity cost. A NADA-hosted presentation gives a $35–$85 per vehicle per day total holding-cost planning range. That speaker-provided figure is not NADA-authored guidance and supports total context only; the honest move is to run your own inputs.

The reason holding cost belongs on a recon scoreboard is that every recon day adds a full day of carry to every unit in the pipeline — the cost compounds across the lot, not just on one slow car. If you want to put real numbers to your own store, the holding cost per day page goes deeper, and you can plug your own inputs into the ROI calculator rather than borrow someone else's stat.

Approval and parts wait time

This is the hidden tax on every other metric. Approval and parts wait time measures the hours or days a unit sits idle waiting on advisor approval or on a part to arrive — the time-stamp gap between when a request is made and when it's resolved. The work isn't happening; the clock is.

This delay is easy to miss because a waiting car can look the same as a car being worked on. Measuring the gap in isolation shows whether approvals or parts are material at your store. Do not assume the answer; compare the request-to-resolution time with your other stages.

Bottleneck / units-over-target

Units-over-target — sometimes called blocker rate — is the one leading indicator on the scoreboard. Every other metric is a lookback: it tells you what already happened. Units-over-target is a real-time count of how many active units are past their step target right now, divided by active units. Lower is better.

It earns its place because it predicts next week's average-days number before that number exists. If a dozen cars are sitting past target today, your average days in recon is already climbing; you just won't see it in the lookback metrics until the cars finish. The catch is that a leading indicator is only useful if the board is current — a stale whiteboard can't tell you what's over target this minute, which is why a low-friction way to keep status live makes this metric practical instead of theoretical.