How to run the perfect recon meeting

The fastest dealerships in recon don’t run longer meetings. They run shorter ones, more often, and they always start with the same two numbers: how many cars entered the shop the day they arrived, and how long it took to approve the work. Everything after that is bottleneck management.

That’s the core of a recent All Things Recon episode, where hosts Josh and Bobby broke down what a recon meeting should actually cover, who needs to be in the room, and how long it should run. Their take: the dealers who do recon best almost always have one thing in common. They meet regularly with the service manager, recon manager, and used car manager, and they look at the process as it’s been running and as it’s about to run.

Who belongs in the room

Keep it to the people who directly touch the process: an internal advisor or service liaison, the used car manager, and a lead tech or shop foreman if you have one. You don’t need a big committee. Josh and Bobby both said a solid recon meeting can run 10 to 30 minutes, and the first one or two sessions usually take longer simply because the team is looking at its reporting together for real the first time.

The bigger point is cadence, not length. A tool that flags a problem within hours instead of weeks means you’re having a short conversation now instead of an “emergency meeting” three weeks later, after a car has sat cooking on the lot and burned through a month of holding costs.

Start with two metrics

Before you touch reporting, dashboards, or individual technicians, look at two things:

• Day zero. Did the car enter the shop, or at least the process, the day it became available? If cars are sitting a day or two before anyone touches them, that’s the first fix.
• Approval time. How long does it take you to approve work once an estimate lands? Josh made the point directly: used car managers have no business chasing recon speed if they’re slow to approve work themselves. A delayed approval doesn’t just cost you a day. It pushes a technician into the next car, misses a parts cutoff, and by the time the approval comes back, you’re waiting on parts you could’ve ordered two days earlier.

One dealer example that came up: a customer’s first reporting review showed it was taking eight hours after inspection just to decide what happened to a car next, and 10 to 12 hours to get approvals through, before anyone even looked at technician performance. That’s the pattern to watch for. Fix the controllable steps first, the ones with a clear, definable expectation, before you go digging into variables like a tech’s experience level or the mix of makes and models coming through the shop.

Then work the bottlenecks

Once those two are in shape, the rest of the meeting is workflow review: what’s aging in each step, what’s stuck waiting on approval, and what pattern is repeating. Are keys going missing regularly? Are cars parked somewhere techs can’t find them? Are used car techs getting pulled onto the main line? A tool that shows you which units are aging out step by step gives you a starting point instead of a guessing game.

The second half of the meeting is reporting, reviewed together, over whatever window makes sense (a week, a month). The goal here isn’t to find the weak link. It’s accommodation: figuring out what the team needs to keep units moving. Meetings built around blame make people defensive and inflate tickets. Meetings built around a shared view of the same data, where everyone already knows they’re accountable for their own step, get honest a lot faster.

The money conversation

A live audience question during the episode asked about pre-approved dollar limits for recon work, letting service move on anything under a set amount without prior sign-off. Josh and Bobby called it a double-edged sword and a real best practice, but only once trust is established. Set the threshold too early, before service and used car are actually aligned, and tickets tend to inflate toward whatever the limit allows.

One idea from the episode worth stealing: tie a piece of the service team’s bonus to used car gross. If the internal team’s pay plan moves with the profit on the cars they’re reconditioning, they’re incentivized to get the used car department into better cars faster, not just to turn more hours. It’s a way to build alignment into the pay structure instead of relying purely on relationship and goodwill between two departments that are naturally pulling in different directions.

Build the meeting around real-time data

None of this works without visibility into where a car actually is in the process, right now, not last week. Rapid Recon Pro’s real-time tracking gives every step of the process an owner and a timestamp, so a recon meeting starts with facts instead of guesswork about who’s holding up which car. When the team can see the same aging report at the same time, the meeting stops being a status update and starts being the fix.

If you’re still running recon off a whiteboard or a spreadsheet, the meeting structure above still applies. You’ll just spend more of it hunting for the numbers instead of acting on them.