3.2 Vehicle Status & Completion Expectations

Customer Relations Task 9 asks you to establish vehicle status and completion expectations. In plain terms: before the customer leaves the service drive (or finishes a phone write-up), they should understand what will happen next, roughly when work may finish, and how they will hear from you if that plan changes. Missed expectations are one of the fastest ways to create complaints—even when the repair quality is excellent.

What “status” and “completion expectations” mean

These two ideas travel together but are not identical.

Task 9 is not a guarantee engraved in stone. It is a shared plan based on known facts. The exam rewards consultants who set expectations with contingencies, then communicate changes. It punishes consultants who say “it’ll be ready at 5:00” with no basis, then go silent when the car is still on the rack.

Build expectations from real inputs

Before you quote a completion window, gather the facts you can know at drop-off:

1. Nature of the visit — quick maintenance menu vs. intermittent electrical diagnosis vs. collision-related sublet.
2. Shop load — number of jobs ahead, technician availability, express lane vs. heavy repair.
3. Parts posture — on-hand, same-day local, overnight order, backorder.
4. Authorization risk — customer available by phone? Fleet needs PO? Waiting spouse approval?
5. Borrowed time factors — road tests, battery charging, software updates, wait for specialist.

Scenario — Maintenance express: Customer drops off at 8:15 for oil, tire rotation, and multi-point. Parts and supplies are on the shelf; express lane has capacity. A fair expectation: “We should have you ready mid-to-late morning. I’ll text when it’s finished, and I’ll call if inspection finds something that needs a decision.”

Scenario — Noise diagnosis: Customer drops off a squeak that happens “only after rain.” You cannot honestly promise a 10:00 a.m. pickup. Better: “We’ll need time to duplicate the condition and diagnose. I won’t have a firm completion time until the technician reports findings—likely late morning for an update. Keep your phone on; we may need authorization before any repair starts.”

Communicate the plan in customer terms

A strong Task 9 conversation includes five elements. Leave one out and expectations fracture.

Confirm contact details as part of expectations: mobile number, permission to text, alternate contact, and whether a voicemail is enough or they need a live conversation for authorization. A beautiful completion estimate fails if you call a disconnected number all afternoon.

Status language the lane should share

Shops use different boards and DMS statuses, but consultants should translate them consistently:

• Checked in / awaiting dispatch — vehicle accepted; not yet being worked.
• In diagnosis / waiting on tech findings — concern being investigated; no repair authorization yet beyond diagnostic fee if applicable.
• Waiting on authorization — findings ready; clock depends on the customer’s decision.
• Waiting on parts — repair approved; completion tied to parts ETA.
• In repair — parts and approval in place; work underway.
• Quality check / ready — work complete; vehicle can be picked up after final review and invoice explanation.

Exam trap: Telling a customer the car is “almost done” when it is still waiting on parts. Status honesty is part of Task 9.

Resetting expectations when reality changes

Establishing expectations is not a one-time speech. When something material changes, update the customer before the original promised time expires.

Common reset triggers:

• Diagnosis finds additional required work.
• Quoted part is incorrect or superseded; reorder needed.
• Technician illness or emergency job reshuffles the board.
• Customer delays authorization past the parts-cutoff time.
• Sublet vendor (glass, transmission, alignment specialty) pushes ETA.

Scenario — Parts delay: You told the customer “ready by 4:00 if we authorize rotors.” At 11:30 the parts department reports the correct rotors arrive tomorrow 10:00 a.m. The professional move is an immediate call: explain the delay, give the new ETA, offer options (wait, temporary alternate transportation reminder, aftermarket alternative if policy and quality allow), and document the new expectation on the RO notes.

Waiting until 4:05 to confess is how CSI scores collapse.

Balancing hope, honesty, and shop production

Service consultants feel pressure from customers who need the car tonight and from managers who want the bay productive. Task 9 ethics favor honest capacity. If the shop cannot finish today, say so at drop-off. Offer alternatives: prioritize safety repair today and schedule remaining work, arrange shuttle/rental per shop policy, or book a morning drop when parts will be staged.

Also separate diagnostic completion from repair completion. Many exam questions hinge on that distinction. A vehicle can be “done with diagnosis” at noon and still not “ready for pickup” until parts and authorization finish the story.

Link to later shop-operations tasks (without mixing them up)

Later C1 Shop Operations tasks cover monitoring progress and establishing completion expectations during production. Customer Relations Task 9 is the first handshake: set the expectation at intake and keep the customer aligned. Production monitoring is how you keep that handshake true. On Communications questions, choose answers that emphasize clear initial expectations and timely updates—not blaming the technician or inventing a finish time to close the write-up quickly.

Quick checklist before the customer walks away

1. Restate concern and authorized starting work (diagnosis or menu).
2. State current status in plain language.
3. Give a completion window or a firm update time if completion is unknown.
4. Confirm contact method and decision-maker.
5. Explain what would change the plan (parts, findings, approval).
6. Invite questions: “Does this timing work for your day?”

If you can check those six boxes, you have practiced Task 9 the way ASE intends—and the way real customers remember your professionalism.