Multi-Point Inspections: Keep the Conversation Going After “Not Today”

Before asking for more pictures or more detailed forms, decide what makes a finding usable. A technician’s entry should identify the component and location, describe the observed condition, and include the measurement or evidence appropriate to that inspection item. The recommendation should follow from the finding rather than substitute for it. “Recommend replacement” leaves the advisor searching for the reason. A documented condition gives the advisor something concrete to explain and gives the shop a record it can evaluate later. Use current manufacturer instructions and your shop’s technical standards to define the required checks and supporting evidence.

Make room for uncertainty and incomplete inspection work. If an item couldn’t be inspected, the record should say so and explain the limitation. An unchecked field shouldn’t leave the advisor guessing whether the component passed, was overlooked, or wasn’t accessible. Likewise, separate an observed condition from a concern that needs additional diagnosis. The customer should understand whether you’re recommending a repair, further testing, or continued monitoring. That distinction also protects the return visit: the appointment team needs to know whether it’s arranging a defined repair or reserving time to establish what the vehicle actually needs.

Bring the foreman and advisors together around actual inspection records, including findings that were easy to explain and findings that required clarification. Ask whether someone who hadn’t seen the vehicle could accurately describe the concern from the record. Where they can’t, identify the missing detail rather than simply asking the technician to write more. A useful local standard might require a location, a relevant measurement, and a clear image for a particular condition. Keep those requirements specific to the inspection item, and make clarification possible before the advisor presents the recommendation to the customer.

The advisor’s job is to connect what the technician found with a decision the customer can make. ASE explicitly includes explaining inspection results and estimates, prioritizing recommendations, and understanding the technician’s diagnosis. In practice, that means presenting the finding, its significance, the recommended action, and the expected price and time together. Don’t make the customer assemble the explanation from a colored inspection report, a separate estimate, and an unanswered message. Before presenting, the advisor should be able to explain why the recommendation applies to this vehicle and what remains uncertain, if anything.

Photos and video can support that explanation when they make the condition easier to understand. In its August 2025 reporting, WardsAuto described personalized technician videos and also acknowledged the production time involved. That’s useful background, not proof that every finding needs a video. Set a purpose for each piece of evidence: orient the customer to the location, show the condition clearly, or explain a measurement. Then check that the image, written finding, and estimate describe the same concern. If the visual raises questions the estimate doesn’t answer, resolve them before asking for authorization.

Prioritization needs language the advisor can defend. Have the technician and advisor distinguish a condition requiring prompt attention from maintenance that can be planned or a condition to monitor, using applicable technical guidance. Explain the basis without making unsupported predictions about exactly when a component will fail. Ask what the customer needs to understand before deciding, and leave room for questions about cost, timing, or transportation. When the customer hasn’t viewed the report, a conversation may still be necessary. Sending evidence establishes that it was sent; it doesn’t establish that the recommendation was understood.

A declined-work entry becomes more useful when it preserves the customer’s decision rather than merely labeling the outcome. “Declined” may mean the customer needs the vehicle back, wants to plan the expense, needs clarification, or has already arranged the repair elsewhere. Those situations call for different next conversations. Ask a neutral question: “What would help you decide how to handle this?” Record the answer in plain language, without guessing at motivation. The goal is enough context for the next advisor to respond appropriately, not a personal account of the customer’s finances or circumstances.

Before checkout, confirm what was explained and what happens next. The invoice should distinguish work completed from work recommended and deferred, consistent with ASE’s service-consultant responsibilities. If the customer wants a later conversation, record the agreed timing, preferred contact method, and who will make contact. If they haven’t chosen a next step, document that accurately rather than implying an appointment or commitment. Any condition requiring a specific safety explanation should receive that explanation under your department’s procedures. A note about future contact must never replace clear communication about the finding at the current visit.

Give the department a consistent way to distinguish postponed work, unsuccessful contact, work completed elsewhere, and a customer who doesn’t want further outreach. Keep the finding connected to the original inspection and estimate so staff can retrieve its context. In an October 2011 archive article, WardsAuto described specific operation codes and repair details as a way to retrieve declined work. The underlying principle remains useful: a recommendation needs a dependable retrieval method. The article’s age matters, though. Treat it as process background, not current guidance for communications compliance or a specification for how your records must be configured.

Assign ownership while the visit is still open. The original advisor may be well placed to continue the conversation because they know what the customer asked and what was explained. The archived WardsAuto follow-up article makes that argument and also calls for management accountability. Your staffing may require another arrangement, especially when an advisor is absent or no longer with the store. Whatever you choose, identify both the responsible person and the coverage path. A shared work queue can help organize the work, but each open recommendation still needs someone responsible for deciding what happens next.

The follow-up should have a reason the customer can recognize. If the customer asked to discuss scheduling after checking their calendar, start there. If they needed clarification, answer the unresolved question before asking for the sale. Review the original evidence and the customer’s stated concern before making contact. Confirm that the recommendation and estimate remain applicable rather than reading an old total as though nothing could have changed. Respect the customer’s contact preferences and your store’s applicable consent and communications requirements. An unanswered message should be recorded as an attempt, without being treated as a completed conversation.

Review follow-up quality through the record of what happened. A useful manager review asks whether the assigned person reached the customer, learned anything that changes the next step, and updated the recommendation’s status. An appointment is progress, but the repair remains open until the outcome is confirmed. If the customer reports completion elsewhere, record that information and avoid repeatedly presenting the same work as untouched. If they ask for no further contact about it, preserve that request. These distinctions let you coach the handoff itself instead of relying on a call-completed notation that says little about the conversation.

A customer calling back about deferred work should reach someone who can find the recommendation and arrange a suitable next step. WardsAuto’s September 2026 reporting connects appointment handling with retention and notes that customers may prefer calling about more complicated work. It doesn’t establish that visual inspections caused the reported scheduling results. For your department, the practical question is narrower: can the appointment team see enough context to handle this call? They need access to the finding and estimate, a path to technical clarification, and a clear way to reconnect the customer with an advisor when needed.

Before confirming the visit, establish what needs to be verified. An older finding may require reinspection; an estimate may need updating; the customer may have completed related work since the original visit. Coordinate parts readiness and shop capacity with the actual job rather than assigning a generic maintenance appointment. Tell the customer if the return visit begins with confirmation or diagnosis instead of an already-defined repair. Discuss the likely vehicle commitment and transportation needs without promising a completion time the shop hasn’t supported. The customer’s willingness to return deserves a reservation built around the work being considered.

Close the loop after the visit by reconciling the original recommendation with the completed repair order. If the work was performed, update the open record so it doesn’t return as another follow-up task. If inspection changed the recommendation, preserve that explanation. If the customer deferred again, capture the current reason and next action rather than copying the previous note unchanged. A department review can follow a recommendation from the technician’s finding through presentation, deferral, contact, and final disposition. Wherever the context disappears is a practical place to improve the process, regardless of which forms or systems you use.

A useful MPI leaves the department with more than a completed form. It leaves a finding that can be explained, a customer decision that can be understood, and an open recommendation that someone owns. ASE’s task list supports those responsibilities; the operational details belong to your store. You don’t have to redesign the entire service drive to improve them. Look for the point where a recommendation loses its evidence, its customer context, or its next action, and make that handoff clear enough for another person to carry forward.

At your next department meeting, bring an actual deferred recommendation and walk it through with the technician, advisor, and appointment team. Ask each person to show what they can retrieve and explain what they would do next. Resolve the missing information together, then document the expectation where the work happens. Give the open recommendation an owner, confirm the customer’s agreed next step, and check that the return visit can be arranged appropriately. That gives your team a concrete place to start Monday: keeping a vehicle need understandable and actionable after the customer says, “Not today.”