Recon Meeting Agenda: How to Run a Daily Reconditioning Standup
By EasyRecon · Last updated June 30, 2026
A recon meeting agenda is a short, repeatable structure for a daily reconditioning standup. Run it in about 10 minutes: review cars over cycle-time target first, name each car's blocker and owner, confirm parts and vendor ETAs, clear UCM approvals, then commit today's frontline-ready cars. Assign clear roles so no step is orphaned.
Why most recon meetings fail
Most recon standups run off a whiteboard or a spreadsheet that went stale overnight. By the time the team huddles up, half the meeting gets spent asking "where is this car?" instead of moving it. The agenda quietly turns into a status-collection exercise — everyone reads out what they already know — when it should be a decision and owner-assignment exercise. Status is something a good board gives you before the meeting starts; the meeting is for the calls only people can make.
You can name the symptoms once you look for them. Cars get discovered to be stuck only when somebody physically walks the lot. Vendor ETAs float around as "soon" with no date anyone can confirm. Approvals sit "waiting" for days because no one closed the loop. None of that is a software failure first — it is a process problem. The meeting has no spine, so it bends to whoever talks loudest, and the oldest, most expensive units are the ones that quietly slip. Fixing the agenda is mostly about deciding, in advance, what the meeting is allowed to be about and in what order.
The 10-minute daily recon standup agenda
Keep the daily standup to one job: move cars. Work the agenda top to bottom, decide as you go, and resist the urge to problem-solve anything that only one or two people need to be in the room for. Here is the five-item agenda, with the decision each item exists to force.
- Frontline review — aged units first. Start with cars over your cycle-time target; they cost the most every day they wait.
- Blockers and who owns the next step. For each stuck car, name the single blocker and the single person who owns clearing it.
- Parts and sublet/vendor ETAs. Confirm real dates, not "soon"; flag anything with no committed ETA.
- Approvals waiting on the Used Car Manager. Clear go/no-go and budget decisions on the spot so nothing sits.
- Today's frontline-ready commitments. End by naming which cars will hit frontline-ready today, with names attached.
That order matters. Aged units come first because they are the most expensive thing in the room and they tend to be the ones people avoid. Commitments come last so the meeting ends on a forward action, not a recap. If you want the math on why those aged days hurt, see recon holding cost, and to set the targets this agenda checks against, start with recon cycle time.
Daily vs. weekly cadence — what belongs where
The fastest way to kill a daily standup is to let it become the place where you also fix the process. The daily ten-minute meeting is for movement. The weekly review is for trends. Keep them separate and both survive; blend them and the daily meeting balloons to forty minutes, people start skipping it, and within a month it is gone.
Daily standup (~10 min)
- Aged units over your cycle-time target
- Each stuck car's blocker and named owner
- Parts and vendor ETAs that need confirming
- Approvals waiting on the used car manager
- Today's frontline-ready commitments
Weekly review (longer)
- Average cycle time and how it is trending
- Recurring bottlenecks — a vendor that is always late
- An approval step that keeps stalling
- Policy and target changes
- Staffing and capacity decisions
A simple test: if the answer is "we need to look at the pattern over time," it belongs in the weekly review. If the answer is "this specific car needs a specific person to do a specific thing today," it belongs in the standup.
Recon roles and responsibilities (RACI)
"Everyone's job" is how cars stall between handoffs — when a step belongs to the whole team, it belongs to no one. The fix is one named owner per step, agreed on before the meeting so the standup just confirms it. The table below is an example mapping using RACI — Responsible (does the work), Accountable (owns the outcome), Consulted (weighs in), Informed (kept in the loop). Treat it as a starting point and adapt it to how your store is actually staffed; these are example assignments, not a measured benchmark.
| Recon step | Used Car Mgr | Recon/Inventory Mgr | Service Advisor / Dispatch | Tech | Detail | Vendor / Sublet |
|---|---|---|---|---|---|---|
| Intake / triage | A | R | C | I | I | I |
| Recon cost + time estimate | A | R | C | C | I | C |
| Mechanical repair | I | A | R | R | I | C |
| Parts ordering | I | A | R | C | I | R |
| Sublet / vendor work | I | A | C | I | I | R |
| Detail | I | A | C | I | R | I |
| Photos / frontline-ready sign-off | C | A | R | I | C | I |
Notice the recon/inventory manager is accountable for most of the pipeline — that is deliberate. One person owning cycle time end to end is what keeps a car from falling into the gap between mechanical, parts, and detail. For how those steps connect, walk the full used-car recon process.
Recon team accountability — make "who owns the next step" impossible to lose
Roles on a chart only matter if they show up in the daily mechanics. The rule is simple: every car that comes up in the meeting should leave with a named owner and a due time for its next step. Not "service is looking at it" — a person and a time. That is the difference between a meeting that moves cars and one that re-describes them.
Accountability breaks down for a reason that has nothing to do with people not caring: you can't hold someone to a step nobody can see the status of. If the board is a day stale, the owner can honestly say the meeting had bad information, and they would be right. So accountability and visibility are the same problem. The status every department trusts has to be surfaced in the meeting, not buried in a system only managers ever open. When the next step is visible to the whole team — sales, service, detail, and vendors looking at the same thing — "who owns this?" stops being a question you ask and becomes a fact you can read.
How EasyRecon keeps the standup running on live truth
This is where the agenda above stops depending on someone manually freshening a whiteboard. With EasyRecon, the board stays current because techs, detail, and vendors just text updates — nobody has to log into software to keep the meeting's data accurate. That low-friction habit is the whole point: the easier it is to update, the more the board reflects reality when you huddle up. Your inventory feed connects once and cars flow onto the board automatically, so the team isn't re-keying units before the meeting can even start. And because sales and service see the same live board, "who owns the next step" is visible rather than asked.
To be straight with you: EasyRecon is early-stage software, and it doesn't recondition cars or make the process calls for you. What it does is keep the meeting honest — it shows the bottleneck and keeps updates moving so the standup runs on live truth instead of yesterday's board. The store still decides what to do about each car. If you want the broader picture of how a shared board works, see the live recon board.
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.
An early signal from one live store
In its first six live days, one store logged 1,011 work items and sent 484 advisor texts — so its standup ran off live data instead of a stale board. This is our single early-stage pilot, and we share it as an adoption signal that the texting habit gets used, not as a benchmark, an ROI figure, or a days-saved claim. One store is one store; your mileage will differ.
Free recon meeting agenda + roles template
Here is the take-home version, free to copy or print — no gate, no form to fill out first. It packages everything above into one page you can drop into your standup: the five-item agenda, the RACI roles table, and a blank "named owner + due time" tracker to fill in as you run the meeting. Copy the block below into your own doc and adapt the role names to your store.
1. Daily recon standup agenda (~10 minutes)
- Frontline review — aged units over cycle-time target first.
- Blockers — name the single blocker and the single owner per stuck car.
- Parts and sublet/vendor ETAs — confirm real dates; flag anything with no committed ETA.
- Approvals — clear anything waiting on the used car manager on the spot.
- Commitments — name today's frontline-ready cars, with owners attached.
2. Roles (RACI — adapt to your store)
- Recon/Inventory Mgr — accountable for cycle time end to end.
- Used Car Mgr — accountable for approvals and budget.
- Service Advisor / Dispatch — responsible for moving repair and parts work.
- Tech — responsible for mechanical repair.
- Detail — responsible for detail and photo prep.
- Vendor / Sublet — responsible for outside work and committed ETAs.
3. Named owner + due time tracker
| Stock # | Current step | Blocker | Owner | Due time |
|---|---|---|---|---|
Email is optional. The template above is already complete and free to copy — nothing is gated behind the form.
Common recon-standup pitfalls (and how to fix them)
Running off a stale board
If the board was last touched yesterday, the meeting argues about reality instead of acting on it. The fix is live status anyone can update in seconds — when a tech or vendor can change a car's state from where they're standing, the board is true at standup time and the meeting can trust it.
No named owner per car
"Service is on it" is not an owner. Cars stall in the space between departments precisely because no single person was on the hook. The fix is the rule from the accountability section: every car leaves the meeting with a name and a due time attached to its next step.
The meeting becomes a status readout
If the first five minutes are people reciting what everyone already knows, the agenda has inverted. The fix is to pre-load status on the board before the meeting so the ten minutes are spent on decisions — blockers, approvals, and commitments — not narration.
Vendors are invisible
Sublet and outside work is where ETAs go to die, because the people doing it aren't in your building or your software. The fix is to let vendors text their ETAs straight onto the board, so sublet stops being a black box and "no committed date" becomes something you can actually flag.
Most of these are the same fix wearing different clothes: make the next step visible and owned. For the playbook that turns that into fewer days, read speed up reconditioning.
FAQ
What should be on a daily recon meeting agenda?
A daily recon meeting agenda has five parts: review cars over your cycle-time target first, name each stuck car's blocker and owner, confirm parts and vendor ETAs, clear any approvals waiting on the used car manager, then commit which cars will hit frontline-ready today. Keep it to roughly ten minutes and decisions only.
How long should a reconditioning standup take?
A reconditioning standup should take about ten minutes. It works when it stays a decision meeting, not a status readout: pull aged units first, assign one owner per blocker, and confirm today's frontline-ready commitments. Save trend analysis, recurring bottlenecks, and policy changes for a separate weekly recon review.
Who is responsible for used car reconditioning?
Reconditioning is shared, but one person should be accountable for cycle time — usually the recon or inventory manager who runs the daily standup. The used car manager owns approvals and budget, while techs, detail, service advisors, and vendors own their steps. Naming one accountable owner per step is what keeps cars from stalling.
How often should you hold a recon meeting — daily or weekly?
Hold a short standup daily to move cars, and a longer review weekly to fix the process. The daily meeting covers aged units, blockers, and today's commitments in about ten minutes. The weekly review covers average cycle time, recurring bottlenecks, and policy changes. Mixing the two is why daily meetings bloat and stop happening.
How do you keep recon meeting data accurate?
Recon meeting data stays accurate when updating status takes seconds, not a login. If techs, detail, and vendors can simply text an update, the board reflects reality at standup time. EasyRecon keeps the board current this way and feeds inventory in automatically, so the meeting runs on live truth instead of a stale whiteboard.
What is a recon RACI / roles and responsibilities breakdown?
A recon RACI maps each reconditioning step to who is Responsible, Accountable, Consulted, and Informed. For example, the recon manager is accountable for cycle time, techs are responsible for repairs, and the used car manager is consulted on approvals. It removes the "whose job was that?" gaps where cars quietly stall between handoffs.