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 used-car-manager approvals, then commit today's frontline-ready cars. Assign clear roles so no step is orphaned.
The template is free to copy or print — nothing is gated behind a form.
Many stores already use a whiteboard, spreadsheet, or daily huddle to keep recon moving. The common challenge is getting fresh status in front of the group before the meeting starts. When the board handles the readout, the team can spend its time on decisions, blockers, owners, and today's frontline commitments.
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.
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.
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.
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.
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.
"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. 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.
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.
Illustrative example — the exit rule applied to one car.
This is where the agenda above can rely less on someone manually freshening a whiteboard. EasyRecon gives configured techs, detail staff, and vendors a text-friendly way to update status without opening the app. That lower-friction habit makes the board easier to keep useful for the next huddle.
Your inventory feed connects once and cars land on 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.
Illustrative board view, not customer data. The standup reads straight down this list: oldest unit, blocker, owner, decision.
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 list, and a blank "named owner + due time" tracker to fill in as you run the meeting. Copy the block below into your own doc, or print it — the print version strips the page down to just this template.
| Stock # | Current step | Blocker | Owner | Due time |
|---|---|---|---|---|
Nothing here is gated — the template above is complete and free to copy. Printing (or saving as PDF from the print dialog) gives you a clean one-pager for the huddle board, or email us and a real person will send the template back to you.
If the board was last touched yesterday, the meeting argues about reality instead of acting on it. The fix: give configured team members and vendors a low-effort way to share supported status updates, so the group has a more useful starting point for the standup.
"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: the rule from the accountability section — every car leaves the meeting with a name and a due time attached to its next step.
If the first five minutes are people reciting what everyone already knows, the agenda has inverted. The fix: pre-load status on the board before the meeting so the ten minutes are spent on decisions — blockers, approvals, and commitments — not narration.
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: let configured vendors send supported ETA updates by text, so sublet is easier to review and "no committed date" becomes something you can 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.
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.
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.
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.
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.
Recon meeting data is easier to review when status updates take less effort. Configured techs, detail staff, and vendors can text supported updates, which can help the board stay useful at standup time. An inventory feed can also land units automatically after it is connected, while the store remains responsible for timely updates and meeting decisions.
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.
Month-to-month. No long-term contract. EasyRecon keeps the board fresh between meetings, so your ten minutes go to decisions — blockers, approvals, and today's commitments — instead of a status readout.