Reconditioning KPIs: the recon scoreboard every used-car department should track.
By EasyRecon · Last updated June 30, 2026
The core reconditioning KPIs dealers should track are average days in recon, total recon time vs time to sale-ready, step-level cycle time, recon cost per unit, cost-to-market, holding cost, approval and parts wait time, and units-over-target. Together they form a recon scoreboard — each one has a simple formula and an honest benchmark range you can measure your store against.
Why the recon scoreboard matters
Every day a unit sits in reconditioning is a day of carry plus a day of lost frontline turn. Yet most stores still manage recon on gut feel or a whiteboard that's already out of date by lunch — nobody can say with confidence how many days the average car is actually taking, or where those days go. A scoreboard turns recon from a black box into a managed process: a short list of numbers you can calculate, compare against a benchmark range, and act on. You can't manage what you don't measure, and in recon the thing worth measuring most is time, because time is where the holding cost per day quietly accumulates on every unit in the pipeline.
The 8 recon KPIs at a glance
Here is the full scoreboard in one view. Each row gives the KPI, what it measures, a plain-English formula, and an honest benchmark range drawn from commonly published industry figures — not EasyRecon data. Treat the ranges as planning references, then measure your own store.
| # | KPI | What it measures | Formula | Honest benchmark range |
|---|---|---|---|---|
| 1 | Average days in recon | Mean days a unit spends in the recon workflow | Sum of recon days ÷ units completed | Goal commonly cited 3–5 days; reality often 8–15 days industry range |
| 2 | Total recon time vs time to sale-ready | Acquisition → frontline-ready vs acquisition → merchandised/online | Date frontline-ready − acquisition date; date listed online − acquisition date | Strong total recon time ~3–5 days; time to sale-ready adds ~1–2 days industry range |
| 3 | Step-level cycle time | Days spent in each stage (intake, mechanical, parts, body/detail, photos) | Days in stage per unit, averaged by stage | Varies by stage; parts/approval stages most volatile industry range |
| 4 | Recon cost per unit | Average reconditioning spend per car | Total recon spend ÷ units completed | Commonly cited ~$500–$1,500/unit (mix-dependent) industry range |
| 5 | Cost-to-market | Total cost to get a unit frontline-ready | Recon cost + holding cost to frontline | Rises sharply with every extra recon day industry range |
| 6 | Holding cost / aged exposure | Per-day carry on unsold units | Days in inventory × holding cost per day | ~$32–$40/day typical; higher on pricier units industry range |
| 7 | Approval & parts wait time | Hours/days lost waiting on advisor approval or parts | Time-stamp gap between request and resolution | Often the single largest hidden delay industry range |
| 8 | Units-over-target (blocker rate) | How many active units are past their step target now | Count of units past step target ÷ active units | Leading indicator; lower is better industry range |
KPI 1 — 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. The formula is simple — sum the recon days across completed units and divide by the number of units completed in the same period.
The reason this metric gets so much attention is the gap between goal and reality. Industry sources commonly cite a 3–5 day target industry range, while the everyday number at many stores runs closer to 8–15 days industry range. 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.
KPI 2 — 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.
- Time to sale-ready: acquisition date to listed-and-merchandised online. The car is sellable and discoverable, with photos and price live.
Both matter because a car can be mechanically frontline-ready yet still off the market — done in the shop but waiting on photos or pricing. If you only track one, you miss the stall that happens after recon and before the listing. Watching both shows where units get stuck on the merchandising side, not just the mechanical side.
KPI 3 — 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.
KPI 4 — 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.
Commonly published figures land somewhere around $500–$1,500 per unit industry range, but the real number swings hard with your inventory mix; an older, higher-mileage book costs more to recondition than a lane of late-model lease returns. 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.
KPI 5 — 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. The formula is recon cost + holding cost to frontline.
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.
KPI 6 — Holding cost / aged-inventory exposure
Holding cost is the per-day carry on a unit you own but haven't sold. Its components are floorplan interest, depreciation as the market moves, fixed overhead, and the opportunity cost of capital parked in metal. A commonly used planning figure is roughly $32–$40 per car per day industry range, running higher on pricier units. The formula for exposure is days in inventory × holding cost per day.
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.
KPI 7 — 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.
It's often the single largest hidden delay in recon industry range, and it's the easiest to miss because a waiting car looks the same as a car being worked on. Measuring this gap in isolation is how you find the cheapest wins on the board: an extra day of approval lag costs nothing to fix once you can see it, but it inflates average days, cost-to-market, and holding cost all at once until you do.
KPI 8 — 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.
How to calculate your recon KPIs
None of these formulas need a finance background — just a consistent period and honest inputs. Here are three short worked examples with round numbers. Each is an illustrative example, not store data.
Average days in recon (illustrative example, not store data): 20 units completed this period, 160 total recon days across them. 160 ÷ 20 = 8.0 days average.
Recon cost per unit (illustrative example, not store data): $24,000 total recon spend across the same 20 completed units. $24,000 ÷ 20 = $1,200 per unit.
Cost-to-market (illustrative example, not store data): $1,200 recon cost plus 8 days of holding at $35/day. $1,200 + (8 × $35 = $280) = $1,480 cost-to-market per unit.
Run the same three formulas on your own completed units for a month and you'll have a real baseline to measure against the benchmark ranges above.
Why the whiteboard and the spreadsheet disagree
When a store first measures these KPIs honestly, the numbers usually come in higher than the gut estimate — and that surprise is worth understanding, because it's not a sign anyone is doing a bad job. A whiteboard reflects what someone remembered to write down. A live board reflects what's actually happening. The two drift apart the moment a car waits on something nobody updated: the unit is still listed as "in mechanical" on the board long after it quietly moved to a parts hold.
So the measured number runs higher than the remembered one because memory rounds down and forgets the waits. That's the whole point of building a scoreboard from real time stamps instead of recollection — not to assign blame, but to replace an optimistic estimate with a number you can act on. The gap between the two isn't a scare statistic; it's just the difference between what we think is happening and what the clock says is happening.
What always-current recon data looks like
One honest, first-party data point on what low-friction capture looks like in practice, framed as an early adoption signal — not a turn-time, days-saved, or ROI result.
In its first 6 live days, one live store logged 1,011 work items and sent 484 advisor texts. The board stayed current because the team simply texts updates as work happens, with no separate data-entry step to fall behind on.
That's a single-store, early-stage adoption signal of low-friction data capture — it shows the team will actually keep the board live, which is the precondition for every KPI above. It is not a claim about days saved, turn time, or return on investment.
Turning the scoreboard into action
A scoreboard is only worth building if it changes what the team does on Monday. Three practical imperatives turn the numbers into fewer days:
- Set a target age per step. Give every stage — mechanical, parts, detail, photos — a number to beat, so "over target" means something specific.
- Work the oldest and most-stuck units first. The cars past target are the ones bleeding holding cost; clear them before starting fresh ones.
- Make status visible before you change the process. You can't fix a bottleneck you can't see; measure first, then adjust the handoffs that are actually slow.
Those three moves are the backbone of how to speed up reconditioning, and they work in that order: visibility first, prioritization second, process change last.
Where the scoreboard lives
These metrics only stay useful if they stay current, which is the hard part. EasyRecon puts the whole scoreboard on a single always-current recon board that sales and service both see. Your inventory feeds in automatically once connected, so cars land on the board without anyone re-keying them. And the numbers stay live because techs and vendors just text updates as work moves — low-friction enough that the board actually reflects reality instead of last week's memory. The software shows the bottleneck; the store still makes the process call.
a real person follows up, usually within one business day; no setup fees, month-to-month, cancel anytime.
No setup fees. Month-to-month, no long-term contract.
FAQ
What are the most important reconditioning KPIs to track?
The most important reconditioning KPIs are average days in recon, total recon time vs time to sale-ready, step-level cycle time, recon cost per unit, cost-to-market, holding cost, approval and parts wait time, and units-over-target. Together they form a recon scoreboard that shows where time and money leak, and each one has a simple formula you can apply today.
What is total recon time, and how is it different from time to sale-ready?
Total recon time is the elapsed time from acquiring a vehicle to it being frontline-ready for sale. Time to sale-ready goes one step further: acquisition to fully merchandised and listed online with photos and price. A car can be mechanically frontline-ready yet still off the market, so tracking both shows where units stall after recon.
What is a good average days-in-recon benchmark?
Industry sources commonly cite a 3-to-5-day goal for average days in recon, while the everyday reality at many stores runs closer to 8 to 15 days. Treat these as published industry ranges, not a guarantee. The gap usually comes from approval lag, parts waits, and status that nobody can see in real time.
How do you calculate reconditioning cost per unit?
Reconditioning cost per unit is total recon spend divided by units completed in the same period. Include parts, technician labor, and any sublet or vendor work. For example, $24,000 of recon spend across 20 completed units is $1,200 per unit. Tracking it over time shows whether your cost is drifting up.
What is cost-to-market in used-car recon?
Cost-to-market is the total cost to get a vehicle frontline-ready: reconditioning cost plus the holding cost accrued while the car moves through recon. It matters because two units with identical recon bills can have different cost-to-market if one sat longer. Lowering recon days lowers cost-to-market and protects front-end gross.
Which recon metric should a dealer start tracking first?
Start with average days in recon. It is simple to calculate, it rolls up the effect of every bottleneck, and it ties directly to holding cost and turn. Once you can see the total, break it into step-level dwell time to find where the days actually pile up, then set targets per stage.