Service Department Reporting That Leads to Better Decisions

An advisor comparison becomes more useful when you can see what each person had an opportunity to handle. Express maintenance, diagnostic work, warranty repairs, and customer-pay repairs create different conversations and different production demands. Put work mix beside sales and effective labor rate before drawing conclusions about selling performance. NADA’s current management guidance identifies advisor sales effectiveness, technician production, completion time, and capacity as connected management concerns. That gives you a sound starting point: examine the advisor’s result alongside the conditions under which the department produced it.

Build the report around a reporting period your team can explain. Decide whether a sales comparison includes closed ROs, and keep open work visible separately so unfinished jobs don’t quietly change the meaning of the result. Document how you’ll handle discounts, corrections, and shared advisor responsibility. These are local reporting rules, not universal standards, but everyone reviewing the report needs to understand them. Otherwise, a change in posting practice can look like a change in performance, and a coaching conversation can turn into an argument about whose numbers are right.

When a result deserves attention, pull the underlying ROs with the advisor before choosing the remedy. Look at the customer’s original request, the inspection findings, what was presented, what was authorized, and what prevented completion. You may find a conversation that needs coaching. You may find that a promised completion time left no room for additional work, or that parts availability stopped an approved repair. Keep the sales result on the report, but record the operating explanation and the person responsible for addressing it. That makes the next review more useful than another ranking.

Before you total lost sales, decide which events belong in that category. A documented recommendation that a customer declines is different from work that was never presented. Work the customer wants but cannot complete because a part is unavailable needs a different response again. Keep those statuses distinct rather than placing every unfinished recommendation in a single declined-dollar total. Your report should preserve the path from finding to recommendation, presentation, customer decision, and eventual outcome. That structure gives the manager something to investigate and gives the follow-up owner a usable starting point.

The record needs enough detail for someone other than the original advisor to understand the recommendation. Include the vehicle, the recommended repair or maintenance, the estimate presented, the customer’s stated reason for deferring, and any timing discussed. Don’t infer a price objection when the customer said they needed the vehicle back. Assign a follow-up owner and a next action that respects the conversation already held. If the customer asked to revisit the work at a later service visit, preserve that instruction instead of treating the record as an invitation for repeated generic calls.

Keep the original recommendation connected to whatever happens next. If the customer later approves the work, the earlier decline should no longer sit on an active follow-up list as though nothing changed. If only part of the recommendation is completed, leave the remaining work identifiable. Separate the value originally declined from revenue actually posted on the completed repair, and don’t add them together as recovered sales. In the review meeting, ask which records remain unresolved, why they remain open, and whether the assigned action happened. A smaller, accurate working list is easier to manage than an impressive total with uncertain contents.

A menu sales report tells you what customers bought. It doesn’t establish whether appropriate maintenance was explained to customers who bought nothing. NADA’s undated guide to handling the morning service rush places menu presentation after the walkaround and connects recommendations to vehicle mileage and condition. It also includes review of the work, estimate, and promise time. That is useful process guidance, but it doesn’t supply a presentation-rate formula. Your department still has to define which visits are eligible and what evidence supports a recorded presentation before comparing advisors on compliance.

Write an eligibility rule that reflects the process you actually expect advisors to follow. Explain how the report treats recently completed maintenance, return visits, and appointments where the vehicle’s condition or service history changes what should be recommended. Then define presentation as an observable customer interaction, supported by a record of the applicable recommendations and the customer’s response. A printed menu alone doesn’t demonstrate that conversation. Neither does a maintenance sale prove that the complete applicable menu was reviewed. Keep eligibility, presentation, and acceptance as separate fields so you can see where the process stopped.

Use a sample of underlying visits to check whether the report reflects the actual conversation. Review the maintenance history, the recommendations, and the notes with the advisor. The purpose is to learn whether the record supports the reported status, not to create paperwork for its own sake. If menus are being presented but customers frequently defer the work, examine the explanation, estimate, and available completion time. If presentations aren’t happening, look at the write-up workflow and the information available to the advisor. Those findings call for different coaching, even when the sales totals look similar.

Appointment reporting deserves a view of phone handling separate from online booking. WardsAuto’s September 2026 coverage of a scheduling study examines phone and online effectiveness, time to reach an advisor, appointment availability, and whether callers obtain an appointment. It reports an average of 38 seconds to get an advisor on the line at independent shops versus 66 seconds at dealerships. That is a study comparison, not a universal target for your store. Its practical value is the question it raises: can a customer reach someone who can help, even when your booked appointment count looks healthy?

Map the appointment record from the initial request through booking, confirmation, arrival, and completed RO. Keep those stages distinct, and preserve whether the request came through the phone or online. A reschedule should remain connected to the original request rather than appearing as unrelated new demand. Likewise, repeated calls about the same visit shouldn’t inflate the count of customers seeking service. You may need to reconcile records manually while definitions settle. The immediate goal is a report you can explain, including what it excludes and where the record is incomplete.

Read appointment exceptions against actual shop capacity. Customers who couldn’t reach a scheduler need a different response from customers who reached someone but couldn’t get a suitable opening. A booked visit that never arrives creates another question; an arrived vehicle waiting on authorization or parts creates another. Give each exception an owner in the relevant workflow, rather than assigning every problem to the scheduling team. During review, follow a request through to its outcome. That lets you distinguish access problems, calendar problems, customer changes, and production constraints without treating every uncompleted appointment as the same failure.

Your reports depend on consistent definitions at the repair-order line. If similar work carries unrelated codes, or a general code covers several different events, the reporting loses detail where you need it most. WardsAuto’s archival 2011 article on op codes describes identifying declined repairs, recording inspection findings, and distinguishing marketing campaigns. It also emphasizes repair detail in cause or corrective-action fields and accountability for follow-up. Treat that as a useful process concept, not current system-specific instruction. The management task is to make the code and its supporting description understandable to everyone who uses the record.

Create a controlled code dictionary with a clear owner. For each reporting-relevant code, document its purpose, when it should be used, and the information that belongs with it. Include rules for bundles, replacements, and obsolete codes so cleanup doesn’t make historical comparisons misleading. Bring advisors, dispatch, parts, and accounting into decisions that affect their work. A code that produces a tidy management report but creates confusion during posting will be difficult to maintain. Before changing the dictionary, trace how the affected codes appear on customer documents, operating reports, and follow-up lists.

Then test the reporting chain with actual records. Start with a recommendation and check whether you can find its presentation status, customer decision, follow-up ownership, and any later completed repair. Check that campaign identification doesn’t overwrite the description of the work itself. Where a connection depends on someone remembering the story, improve the record or the matching rule. This is also where the reports come together: advisor results explain the sale, menu records explain the presentation, appointment records explain access, and op codes help you retrieve the work consistently. Keep unresolved exceptions visible until someone can explain them.

A useful reporting meeting ends with a customer record to resolve, a process to adjust, or a coaching conversation to hold. Totals still matter, but the department needs a dependable route from those totals to the work underneath them. The Dealer Data Dashboard brings advisor performance, appointment trends, lost sales, menu presentations, and op-code tracking into one set of reports. Whatever reporting method you use, keep definitions, supporting records, and responsibility close enough that the people reviewing a result can explain what should happen next.

On Monday, bring the people who create and use the records together around a report that regularly raises questions. Trace a sample back to the appointment, RO, recommendation, or customer conversation. Write down where definitions differ and where ownership disappears. Agree on the recording rule, name the person responsible for the next action, and return to those same records at the next review. Build from there. You’re establishing a management habit in which the department can see a problem clearly, respond to it, and verify what happened.