How Should a Service Manager Handle Running a Fixed-Ops Twenty-Group Prep?

A service manager running a fixed-ops twenty-group prep should establish a repeatable meeting agenda that covers reconditioning inventory status, current ROs in process, staffing gaps, parts availability, and CSI metrics—then stick to it every single time, keeping the meeting to 20-30 minutes and rotating who presents so everyone owns the data.

What Is a Twenty-Group Prep and Why Does Your Service Manager Need to Run One?

A twenty-group prep is an internal fixed-ops operations meeting—not a peer-group benchmarking event, though the name gets confused that way. You're prepping your own team, your own numbers, your own bottlenecks before anything goes public or gets reported upstairs. Think of it as your service department's pre-game huddle.

Every dealership operates on different rhythms. Some run preps weekly. Some do it twice a week. The best-performing stores tend to run them before their actual twenty-group call (if they participate in one), which is why the name stuck,but the real value is internal alignment.

Why does this matter? Because a service manager who doesn't prep internally ends up blindsided in front of peers or ownership. You get asked "Why is your labor effectiveness down 3 points this month?" and you're fumbling for an answer when you should already know it's because you had a technician out on medical leave and your schedule wasn't adjusted accordingly. A prep is where you catch that story before you have to tell it.

Setting Up Your Fixed-Ops Twenty-Group Prep Meeting Structure

You need a consistent format. Not a free-form conversation. A format.

Same time, same day, every week , Monday morning before the service lanes even ramp up is ideal. Tuesday morning works. Friday afternoon does not. People will skip it, reschedule it, or half-pay attention if it drifts.
Same attendees , service manager, service advisor lead (or all advisors if you're small), tech lead, parts manager. Optional but valuable: your F&I manager (to catch trade-in condition surprises) and a delivery coordinator (to spot logistics jams). No more than 8 people or it becomes a meeting about the meeting.
Same agenda order , your brain will start to auto-load the data in this sequence, and so will everyone else's. Consistency beats perfection.
One person runs it , the service manager. Not rotating. You own it. Rotating presenters is smart (see below), but the meeting itself has a steady captain.
20-30 minutes, hard stop , this is non-negotiable. If you run 45 minutes, people will start checking their phones and mentally checking out. You're not solving every problem in this meeting; you're surfacing it so you can solve it offline.

What Data Points Should You Cover Every Single Meeting?

Here's the skeleton agenda. Customize it, but don't skip sections.

1. Reconditioning Inventory Status (5 minutes)

How many vehicles are currently in your reconditioning workflow? How many are stalled waiting on parts? How many are waiting on technician availability?

You need one number: days-in-reconditioning (DIR). A typical well-run service department keeps average DIR under 12 days. If you're running 15+ days average, something is broken and everyone in that room needs to know why.

Example: You have 7 vehicles in recon. One is a 2019 Pilot waiting on a timing belt (14 days so far,normal for that job). One is a 2011 Civic that's been there 9 days and nobody can tell you why because the RO got handed off three times. That's the one you solve in this meeting.

Have your parts manager or a tech lead bring the list. Not the service manager pulling it from memory.

2. Open RO Volume and Backlog (3 minutes)

How many ROs are open right now? How many hours per RO is your department averaging? Is backlog trending up or down?

You're looking for creep. If you were averaging 8.2 hours per RO last month and you're at 8.9 this month, why? Is it longer jobs? More CSI-driven re-work? Technician efficiency dropping?

Don't litigate it in the meeting. Just name it. "We're up 0.7 hours per RO. Service advisor team, can you pull the job mix by category and send it to me? Might be we're just getting more complex jobs this month."

3. Staffing and Availability (3 minutes)

Who is out? Who is coming back? Any gaps for the next two weeks?

A technician out for a week kills your throughput in ways that don't show up until the RO backlog does. You need to know this before Wednesday when a customer calls asking why their vehicle isn't ready.

If you're short, you make a call: Do you push some jobs to the next week, or do you bring in someone from another department, or do you tell the service advisors to be more selective about what goes on the board?

4. Parts Availability and Hold-Ups (4 minutes)

What parts are you waiting on? What are the ETAs? What's stuck at the supplier?

This is where a parts manager who shows up prepared is gold. Not "I don't know, probably next Tuesday." Actual ETAs. Actual tracking numbers.

If a part is taking longer than expected, you solve it here: Do you source it elsewhere? Do you call the customer and extend their timeline? Do you offer a loaner?

5. CSI Trends and Recent Complaints (3 minutes)

Pull last month's CSI if you're looking at historical, or pull this week's if you're forward-looking. What's the trend? Any patterns?

If you see a spike in "technician was rude" or "job wasn't explained clearly," that's a coaching conversation with your techs. If you see "parts quality issue" or "repair didn't hold," that's a training or process issue. Name it out loud so the team hears that you're paying attention.

CSI drives everything,your front-end retention, your word-of-mouth, your ability to upsell. It belongs in every prep.

6. Open Issues and Action Items (2 minutes)

What got assigned last week? What got solved? What's still hanging?

You need a running list. Not a mental one. A shared list,could be as simple as a notes doc everyone sees. "Service advisor training on menu-selling starts Tuesday." "Parts manager calling on that timing-chain kit sourcing." "Technician cross-training on hybrid systems starts next month."

When you close out an item, everyone sees it. When something drags, everyone sees that too.

How to Make Sure the Meeting Actually Sticks (and People Don't Check Out)

Rotate the presenters.

Don't let yourself be the only voice. One week the parts manager brings the parts update. Next week the tech lead brings the hours-per-RO analysis. Week after, a service advisor presents CSI trends.

Why? Because it keeps people sharp. Because they own the data instead of just hearing it. Because someone who's presenting is not scrolling their phone. And because you, the service manager, get to actually listen instead of narrate.

Also,and this is one of those opinions I'm willing to defend,if someone isn't prepared for their segment, you call it out in real time, gently but directly. "Parts manager, I don't have those ETAs yet, so let's grab them after the meeting and I'll send them to the group." Don't let sloppiness become the norm. A prep that's just people rambling is worse than no prep at all.

Keep the tone operational, not punitive. You're not in there to blame anyone. You're in there to see the truth, name it, and move. "Our DIR is high because parts are slow, not because techs are slow. So we adjust expectations with customers and we call the supplier." That's how you talk.

Using Your DMS and Tools to Feed the Prep With Clean Data

You can't run a solid prep on gut feel. You need actual numbers pulled from your DMS or service-management system.

DIR report , days in reconditioning by vehicle. Most systems can spit this out in seconds. If yours can't, your setup is broken.
Open RO report , count, average hours, breakdown by type (warranty, maintenance, repair, reconditioning). You need this weekly.
Tech hours and utilization , booked hours vs. available hours, wrench time vs. admin time. This tells you if you're under-scheduled or if techs are padding clock time.
CSI data , pull it directly from your survey platform or manufacturer portal. Don't paraphrase. Show the actual scores and comment themes.
Parts on-time delivery rate , what percentage of your parts orders arrived on the promised date? If it's below 85%, you have a supplier problem or a ordering problem.

This is the kind of workflow Dealer1 Solutions was built to handle,pulling clean operational data so you're not guessing. But whatever system you use, the principle is the same: real data, not memory. No exceptions.

What to Do When the Prep Uncovers a Real Problem

The prep isn't a problem-solving meeting. It's a problem-surfacing meeting.

You surface it. You assign it. You solve it outside the meeting with the relevant people.

Example: The prep reveals that a certain technician's jobs have a 12% re-work rate, which is double the department average. You don't address it in the meeting with 6 other people there. You pull that tech aside, you look at the ROs together, you find out if it's a skill gap, a rushing issue, or a parts-quality problem. Then you train, coach, or escalate. The meeting was just the early-warning system.

Same with a service advisor who's selling the same menu to every customer regardless of need. You see it in the prep, you don't publicly shame them, you schedule a one-on-one, you role-play, you improve. The prep was the data point that told you to pay attention.

How Often Should You Run Your Twenty-Group Prep?

Weekly is standard. Some stores do twice-weekly if they're large or running multiple locations. Some do biweekly if they're very small.

The rule: often enough that no single data point surprises you. If you're running weekly, you catch staffing gaps before they crater your schedule. If you're running monthly, you're always three weeks behind the story.

If you're genuinely short-staffed or running a one-person service department, at minimum you need a monthly sit-down with yourself and your numbers. Write them down. Review them. Decide what changes. That's still a prep.

Connecting Your Prep to Your Twenty-Group Benchmarking Call (If You Run One)

If you participate in an actual peer-group twenty-group benchmarking program, your internal prep is your dress rehearsal.

You run your internal prep on Monday. You look terrible. You see it coming. You make adjustments Tuesday and Wednesday. By Friday when you're on the call with other dealers, you've at least got a story ready. "Our DIR spiked last week because we had a tech out and a supplier delay on catalytic converters, but we've adjusted staffing and we're sourcing parts differently, so we expect to be back to normal by next week."

That's a prepared dealer. Not a dealer who gets on the call and says, "I don't know, we've been busy."

Frequently asked questions

Should the service manager always run the twenty-group prep, or can someone else lead it?

The service manager should own it. A lead technician or service advisor can present their section, but the service manager runs the agenda, keeps time, and makes the calls on what gets assigned and when. If the service manager doesn't show up or doesn't take it seriously, neither will anyone else.

What if we don't have the data to run a real prep because our DMS doesn't pull reports easily?

Start manual. Pull your numbers by hand for two weeks. Print them out or put them in a shared spreadsheet. Run the meeting with that. Then,and this is important,prioritize fixing your DMS setup or finding tools that work better, because you shouldn't be doing this manually long-term. A dealership that can't pull its own operational data is flying blind.

Can we combine the twenty-group prep with other meetings, like a team huddle or a sales meeting?

No. Keep them separate. A sales team doesn't need to sit through your parts availability discussion, and your service team doesn't need to hear about gross per unit. Different purposes, different people, different rhythms. A combined meeting becomes a meeting that serves no one well.

What's the best time of day to run a fixed-ops twenty-group prep?

Early morning, before the service lanes are in full swing. Monday through Thursday. Avoid Friday afternoons,people are checked out. Early morning gives you the whole day to act on what you learned. You see a problem at 8 a.m., you can usually fix it by noon.

How do we handle it if someone regularly comes unprepared to present their section?

Call it out directly after the first time. "I need you to pull those numbers before the meeting starts." If it happens again, make it a coaching conversation offline. "This is a priority for us, and I need you to treat it that way." If it keeps happening after that, you have a performance issue that goes beyond the meeting. But most of the time, one direct conversation fixes it.

Should customer-facing staff like service advisors attend the twenty-group prep, or is it just for managers?

Include at least one lead service advisor. They see the customer side of everything,they know which jobs get pushed back, which customers are complaining about timelines, which vehicles are causing repeat trips. That perspective is gold. And when advisors know the real constraints (parts delays, tech backlog, CSI issues), they can set customer expectations better and sell solutions instead of just saying "I don't know when it'll be ready."