Service Department Reporting: Connect the Numbers to the Work

Start an appointment review with the customer’s request rather than the calendar entry. What work did the customer need, when did they want to come in, and what could your department actually offer? A maintenance opening doesn’t necessarily represent available diagnostic capacity. Separate the requested visit date from the earliest suitable appointment offered, and distinguish a successful booking from an inquiry that ended without one. Where your records allow, keep the booking channel visible as well. That gives you a way to investigate telephone access without assuming the website experience tells the same story.

The September 2026 WardsAuto coverage of a service scheduling study makes that distinction worth examining. It reported that independent shops connected customers with an advisor in an average of 38 seconds, compared with 66 seconds at dealerships. Earliest appointments averaged 1.3 days at independents and 2.9 days at dealerships. Those are findings from that study, not targets for your shop. Their practical value is the question they raise: does your appointment report show how readily a customer can reach you and secure suitable service, or does it show only the appointments that survived the booking process?

Carry the appointment record forward to arrival and the resulting repair order. A cancellation, a missed visit, an arrival without an opened RO, and a completed visit need distinct treatment if you want to understand what happened. Then review exceptions with whoever controls scheduling and shop loading. If diagnostic requests remain unbooked while maintenance slots stay open, investigate the capacity and booking rules behind that pattern. If customers book but don’t arrive, examine confirmation and rescheduling records. Assign the next action to the person who can change that part of the process, rather than leaving the explanation attached to a calendar total.

An advisor scorecard should help you decide what to observe and coach. Before comparing results, establish which repair orders belong in the comparison. Customer-pay maintenance, diagnosis, warranty work, and internal work create different conversations and selling opportunities. Repair-order volume and assigned customers matter, too. Keep those categories visible instead of treating a department-wide average as a complete explanation of individual performance. You can still review total production, but pair it with the work mix that produced it. That makes the conversation more specific and gives the advisor room to explain what the report can’t show.

NADA’s May 2026 article, “How Do I Fix My Service Department?,” includes advisor sales effectiveness alongside effective labor rate, technician measures, throughput, and completion time. It also points to scheduling, dispatching, and capacity as areas to examine. That is a useful boundary for your scorecard: advisor results belong inside the operating system of the shop. If recommended work couldn’t be scheduled, or a needed part wasn’t available, the sales outcome deserves that context. Keep those barriers visible without using them to excuse an unclear recommendation or a customer conversation that never happened.

When a result raises a question, review the underlying ROs with the advisor before setting a coaching objective. Look at the recommendation, estimate, presentation record, customer response, and shop’s ability to perform the work. Ask the advisor to explain how the conversation unfolded. You may find a need for clearer explanations, better estimate preparation, or a more dependable handoff to parts. Agree on a behavior to practice and a record you’ll revisit to check progress. A ranking can show where to look; the actual work tells you what coaching is appropriate.

A useful lost-sales report needs more than an amount and a customer name. Define the conditions that stopped the work: the customer declined an explained recommendation, the customer postponed it, parts were unavailable, capacity prevented acceptance, or the recommendation was never presented. These categories describe different management problems. An unpresented repair shouldn’t look like a customer refusal. Work waiting for parts shouldn’t automatically enter the same follow-up routine as work declined over price. Establish the meaning of each status with the people entering it, including what evidence belongs in the repair-order notes.

Keep the individual recommendation identifiable as its status changes. A repair that moves from declined to scheduled and then completed should retain its history without remaining an open opportunity. Likewise, a repeat visit shouldn’t automatically create another lost sale for the same unresolved repair. Decide how your department will recognize a continuing recommendation and how completion will be confirmed. If your current reporting can’t connect those records reliably, reconcile the follow-up list against later repair orders before contacting customers. That review protects the usefulness of the list and helps avoid asking a customer to authorize work you’ve already performed.

The reason code should determine who acts next. An advisor may need to clarify a declined recommendation; parts may need to resolve availability; the service manager may need to address capacity or an estimate that never reached the customer. Record the responsible person, the next action, and the condition that closes the item. Treat any estimated lost-sales value carefully, especially when the job was interrupted or only partly authorized. Keep the underlying recommended work visible, and don’t describe an open estimate as recovered revenue until the completed repair order supports that conclusion.

Menu sales can tell you what customers bought. They can’t, by themselves, tell you whether advisors consistently presented appropriate maintenance. NADA’s historical guide to effective service management includes menu package sales and repair-order analysis worksheets, making it a useful background reference for sold-work reporting. It doesn’t establish a presentation audit. To build that view locally, define an eligible visit and a completed presentation separately. Eligibility should reflect the vehicle’s needs, available history, and the purpose of the visit. Otherwise, the report can treat an unsuitable recommendation as a missed opportunity or reward a presentation that didn’t fit the vehicle.

Agree on what evidence shows a presentation actually occurred. Generating a menu may be a preparation step; your definition can require a record that the advisor reviewed the appropriate work and price with the customer. Preserve the distinction between presented and accepted, presented and declined, not presented, and not applicable. Give advisors a practical way to explain an exception without writing a long narrative for every visit. Then compare presentation activity against eligible visits, rather than every RO indiscriminately. That denominator is a local management decision you should document before interpreting differences between advisors.

Review presentation records alongside the estimate and final invoice. A sold package may have changed because of prior service, a substitution, a pricing exception, or a customer’s decision to authorize only part of the work. Those changes need enough explanation to make the report understandable. When you see a presentation gap, examine whether the advisor had the right history and a usable menu before assuming a selling problem. When presentations are recorded but purchases differ, review the actual explanation and customer response. Keep coaching centered on an appropriate recommendation the customer can understand, including why the work is due and what it will cost.

Op codes sit underneath many of the comparisons you want to make. If similar work lands in unrelated categories, or a broadly used code covers very different jobs, the report becomes harder to interpret. Assign responsibility for a code dictionary that explains each code’s purpose, reporting category, and use. Include how special pricing, declined work, and campaign activity should be represented where applicable. Ask advisors, dispatch, parts, and accounting to review the definitions together. The goal is a shared understanding of what a code means when someone enters it and when someone later reads the report.

WardsAuto’s archival 2011 article, “Use Op Codes for Marketing,” describes dedicated codes for declined repairs, preserving repair details in cause or corrective-action fields, and using campaign codes to connect revenue with marketing activity. That is background process advice, not evidence of current functionality in your system. Before adopting a similar approach, confirm what your existing tools support and how those entries affect reporting. A declined-work marker needs enough detail to identify the actual recommendation. It also needs a clear path out of the open follow-up population when the customer completes the work or the recommendation no longer applies.

Treat code cleanup as a controlled change rather than deleting labels that look untidy. Determine how duplicate or obsolete codes map to the categories you want to report, and preserve the meaning of historical comparisons. Review questionable records with the person responsible for the code dictionary before changing a definition. Then bring the reports together around actual work: can you trace an appointment to an RO, a recommendation to a decision, and an open item to closure? Where the connection breaks, identify the missing field or handoff. That gives the next reporting change a specific operational purpose.

The most useful reporting routine leaves you with a clearer explanation and an assigned action. You should be able to distinguish an access problem from an arrival problem, an advisor presentation gap from a shop constraint, and a customer decline from work awaiting parts. You should also know whether an open recommendation is still open. Those distinctions give your meetings substance. Instead of debating whose total is correct, you can examine the work, agree on what happened, and decide who can move it forward.

On Monday, bring an appointment record, its repair order, and the related recommendation history into a discussion with the people who handled the work. Trace the records together. Mark any point where the status, code, ownership, or outcome becomes unclear, then choose a reporting definition or handoff to correct. Document the change in language the department can use and decide how you’ll verify it on later work. Start with a connection you can make dependable, and build the reporting routine from there.