Service Manager's Checklist for Running a Fixed-Ops Twenty-Group Prep

A service manager's twenty-group prep checklist should cover vehicle inventory staging, technician assignments by skill level, parts availability verification, RO template setup, CSI protocols, and communication handoffs before the meeting starts. Success hinges on having accurate data pulled 24 hours before, technician rosters locked down, and a clear agenda that respects everyone's time—because a disorganized twenty-group is just expensive theater.

What Is a Fixed-Ops Twenty-Group Prep, and Why Does It Matter?

A twenty-group is a regional peer-benchmarking meeting where service managers and their teams gather to share metrics, swap war stories, and hold each other accountable for fixed-ops performance. You're looking at CSI scores, hours per RO, gross profit per repair order, technician efficiency, and customer retention rates getting dissected in front of your peers. The "twenty-group" name comes from the typical group size—roughly 20 dealerships competing in the same region, usually organized by manufacturer or independent groups.

For a service manager, prepping for this isn't just about showing up with last month's numbers. It's about walking in with a narrative. You need to know which metrics you're crushing, which ones need explaining, and what you're planning to do differently next month. Dealers that show up unprepared look sloppy in front of their peer group. Worse, they miss the chance to learn from stores that are outrunning them on gross profit or CSI.

The prep meeting,usually held at the dealership the day before or morning-of the actual twenty-group,is where you brief your team on what data matters, align on talking points, and make sure nobody gets blindsided by bad numbers in front of the group.

How Do You Organize Your Metrics and Data Before a Twenty-Group Meeting?

Start pulling your numbers 48 hours before the meeting, not the night before. You need time to spot anomalies, ask questions, and correct entry errors.

• CSI (Customer Satisfaction Index) scores. Pull the last 30 days of survey responses. Know your overall score, your breakdown by technician, and whether any service advisor is consistently driving down the number. If you're at 82 and the group average is 87, you need to know why and have a plan.
• Hours per RO. This is your efficiency metric. Are you wringing out the hours you should be? A typical RO that should take 2.5 hours is taking 3.2? That's a conversation waiting to happen. Pull this by technician, not just the department average.
• Gross profit per RO. Total service gross divided by total ROs for the month. This tells you if you're selling the right work at the right price. If you're at $280 per RO and the group is at $340, you're either underpricing or not selling enough supplemental work.
• Technician labor absorption. What percentage of your labor hours are billable versus admin, training, or rework? If that number is slipping, it shows up in your numbers.
• Customer retention (repeat visit rate). How many of your customers came back for a second service visit in the last 90 days? This is the metric nobody watches until it's too late.
• Parts gross margin. Are you selling OEM at list, or are you discounting? Know your actual blended margin.

Create a one-page summary sheet with your top 5–7 metrics, last month's numbers, year-to-date trend, and the group average if you have it from the previous meeting. This becomes your talking points document.

What Should Your Pre-Meeting Agenda Cover with the Team?

Block 45 minutes the morning of the twenty-group (or the day before, depending on timing). Get your service manager, lead service advisor, and ideally one senior technician in the room.

Review the Numbers Together

Don't ambush people. Walk through each metric and explain what it means. "Our CSI is 84. That's down from 86 last month. Three of those points came from a transmission rebuild that didn't hold its warranty. We've got that vehicle back in and we're doing it right this time." That's transparency. Your team knows what you're walking into.

If someone on the team has underperformed, that's a coaching conversation you have before the twenty-group, not after. "Your last five ROs averaged 3.8 hours when the standard for your skill level is 3.0. I need to understand what's happening. Are you running into complicated vehicles, or is something else going on?" Give people a chance to explain, not defend themselves in front of the group.

Agree on Your Narrative

You're going to get asked: "What happened last month? What are you doing about it?" Have an answer ready. Bad answer: "We had some complications." Good answer: "We had a surge in warranty work that compressed our capacity for paid maintenance. We've adjusted our appointment scheduling to buffer for that next month, and we're running an oil-change promotion to drive preventive-maintenance volume back up."

Even if your numbers are good, you need a narrative about what's driving them and what you're focused on next. "We hit 88 on CSI, which is above group average, because we implemented a post-service follow-up call within 24 hours for every customer who has a warranty concern. We're measuring that separately to see if it's sticky."

Assign Roles for the Actual Meeting

Who's talking about what? Usually the service manager leads, but if a technician or advisor has a win to share (like a process change that cut RO time), have them ready to speak for 90 seconds. It builds credibility and shows the group that your improvements are team-driven, not top-down mandates that might not stick.

Which Data Points Are Non-Negotiable to Have Ready?

Some metrics matter more than others at twenty-group time. Here's what you absolutely cannot show up without:

1. Month-to-date and YTD service gross profit. This is the headline number. Your general manager cares about it first. Service managers live and die by gross, not by hours or labor absorption (even though those drive gross).
2. CSI score and your rank in the group. You will be asked. If you're below 85, you're already explaining. If you're above 90, you're leading the conversation.
3. Hours per RO, broken down by category. Maintenance ROs should average 1.2–1.8 hours. Warranty claims should average 1.5–2.5 hours. Repairs should average 2.0–3.5 hours depending on complexity. If your blended average is 3.2 and the group is 2.8, you're pricing incorrectly or staffing inefficiently.
4. Your biggest profit driver this month. Did you sell a lot of transmission fluid exchanges? Did a recall drive a surge? Did a tire promotion work? Know what moved the needle and be ready to say it.
5. One metric you're struggling with and your plan to fix it. Showing vulnerability and a plan is better than showing up defensive or unprepared. "Our repeat-visit rate dropped 2 points because we had a service advisor transition. The new advisor is ramping up on relationship-building calls, and we expect to see improvement next month."

Pro tip: If you don't have this data automated or pulled into a dashboard, that's the real problem you're solving. Manual data-gathering the night before a twenty-group is a waste of your time and a source of errors. This is the kind of workflow that benefits from a real operations platform where you can pull accurate numbers in 10 minutes instead of an hour of spreadsheet hunting.

How Do You Handle Difficult Conversations About Underperformance Before the Group Meets?

You've pulled your numbers and discovered that your gross is down 8 percent, your CSI is in the basement, and you lost a technician last week. Now what?

First: Don't spin it. Going into a twenty-group with a story that doesn't match your numbers gets you exposed fast. Your peer group has seen this movie before. They know what a bad month looks like, and they know what denial looks like too.

Second: Separate the one-off from the systemic. A technician leaving? That's a one-off. But if you've lost two technicians in three months, that's systemic. You need to address it: "We've had some staffing turnover. We're adjusting our scheduling to prevent overtime burnout, and we've got two techs in the pipeline."

Third: Come with a plan, not an excuse. "Our CSI dropped because we had a quality issue on a transmission rebuild" is an excuse if you're still doing the same thing. It's a plan if you're saying "We're now doing a final pressure-test on every transmission rebuild before delivery, and we've seen a 3-point CSI improvement in the last two weeks as a result."

Now, here's the thing: sometimes your numbers are bad and you genuinely don't know why yet. That's okay. You can say it. "Our hours per RO went up last month. I don't have the full answer yet, but we're pulling RO-level data this week to see if it's a mix issue, a scheduling issue, or a quality issue. I'll have a clearer picture by next month's group." That's honest. That's credible.

What Checklist Should You Walk Through the Day Before or Morning Of?

Use this as your actual pre-meeting checklist. Print it if you need to.

Data & Reporting (Complete 24 Hours Before)

• Pull all month-to-date and YTD service metrics into one document
• Verify CSI scores are accurate (spot-check 3–5 survey responses)
• Calculate hours per RO for maintenance, warranty, and repair separately
• Pull your top 5 profit drivers for the month (parts, labor, specific service types)
• Identify your worst-performing metric and draft an explanation with a 30-day action plan
• Compare your numbers against last month and year-ago same month (trend matters)
• If your group publishes peer averages, pull those and flag where you're above/below

Team Alignment (Complete 4 Hours Before the Meeting)

• Schedule the 45-minute prep meeting with your service manager, lead advisor, and one technician
• Walk through each metric and explain the story behind it
• Identify which team member will speak about what (if anything)
• Role-play the tough questions: "Why did CSI drop?" "What are you doing about hours per RO?" "How are you competing on price?"
• Agree on one win and one challenge you're willing to share openly
• Make sure nobody's blindsided by bad numbers in front of the group

Logistics (Complete Day Before)

• Confirm your attendance at the twenty-group meeting and the location/time
• Print your one-page summary sheet with top metrics
• Bring last month's group average data if you have it (to show trend)
• Bring a second copy of your summary for the group facilitator if required
• If you're presenting a process improvement or win, have any visuals or handouts ready
• Get a good night's sleep so you can think clearly in the meeting

What Are the Red Flags That Mean You're Not Ready?

If any of these are true, you're not ready for the twenty-group:

• You're still pulling data the morning of the meeting
• You don't know your CSI score off the top of your head
• Your service advisor or technician has no idea what the metrics mean
• You have an explanation for bad numbers but no plan to fix them
• You're planning to blame the DMS, the customers, or corporate for your performance
• You haven't had a conversation with your team about the numbers before walking into the room
• You're hoping the group doesn't ask about a specific metric because you know it's bad

Any one of these is a sign you need another day or two to get your house in order. A twenty-group is not the place to wing it. Your reputation in that peer group builds month after month. Show up unprepared once, and you're the manager people remember as the one who didn't have his stuff together.

How Do You Use Twenty-Group Feedback to Improve Next Month?

The prep isn't just about showing up. It's about leaving with ideas.

When another service manager talks about a process that moved their CSI or gross, write it down. Ask the clarifying question: "How long did it take you to implement that?" "What pushback did you get from your team?" "Did you measure the ROI?" Take at least one idea from every meeting and pilot it for 30 days. That's how peer groups work,you're borrowing best practices from stores running similar operations.

The day after the twenty-group, do a debrief with your team. "We heard that Store X is running a 48-hour warranty turnaround guarantee. Let's spend 15 minutes next week thinking about whether that's possible for us and what we'd need to change." This kind of follow-through is what separates managers who get value from the group and managers who just show up for the meeting.

Frequently asked questions

How far in advance should I start prepping for a twenty-group meeting?

Pull your data 48 hours before the actual group meeting, then schedule your team alignment meeting 4–6 hours before you walk into the room. This gives you time to spot errors, ask clarifying questions, and brief your team without rushing. If you're waiting until the night before to pull numbers, you're already behind.

What if my dealership doesn't track hours per RO or I'm not sure how to calculate it?

Total billable labor hours divided by total repair orders for the month. If your DMS doesn't spit this out automatically, you're losing visibility into one of your most important efficiency metrics. Start tracking it manually if you have to,pull it from your RO backlog for the last 30 days,but get this number. It's non-negotiable for twenty-group performance.

Should I bring my general manager or finance manager to the prep meeting?

Your service manager prep should be a team-alignment meeting, not a full dealership staff gathering. The GM might sit in if they want to understand your talking points, but keep it tight,you, your lead service advisor, maybe a technician. The goal is alignment, not approval. Your GM should trust you to represent the service department accurately.

What if we had a legitimate crisis last month (technician quit, major recall, supply chain issue) that tanked our numbers?

Own it, explain it clearly, and share your mitigation plan. "We lost a senior tech mid-month, which compressed our capacity and pushed hours per RO up 0.4. We've hired a replacement and they start next week. We expect hours to normalize by month-end." Your peer group has faced the same crises. They respect honesty and a plan far more than spin.

How do I know if my metrics are actually competitive compared to the group?

Your twenty-group should publish peer benchmarks,usually distributed the week before or at the start of the meeting. If they don't, ask for them. You need to know where you stand. A CSI of 86 is good, but is it good relative to the group? If the group average is 88, you're below average. If it's 82, you're leading. Context matters.

What should I do if I realize mid-meeting that my data had an error?

Speak up. Correct it. "We reported 88 CSI, but I just realized we had a data entry error. It should be 85. Here's why it happened, and here's how we're preventing it next month." Your peers will respect the correction far more than discovering the error after the meeting and losing credibility.