14.1 Completion Expectations & Progress Monitoring
Key Takeaways
- Shop Operations Tasks 9–10 require realistic completion expectations grounded in shop capacity, parts status, and diagnosis—not hopeful guesses sold to the customer
- Monitor repair progress against the promised timeline; when delays appear, update the customer with facts and a revised plan instead of going silent
- Never invent a ready time, parts ETA, or diagnostic conclusion—confirm with the technician, parts, or dispatch before you speak
- Coordinate continuously with dispatch so promised times match bay availability, tech skill mix, and real WIP status
- A completion expectation is a living commitment: reset it whenever scope, parts, authorization, or shop load changes
Shop Operations Tasks 9 and 10 sit in the production lane of the C1 exam: establish completion expectations, then monitor repair and service progress until the vehicle is ready. Customer Relations Task 9 (covered earlier) focuses on setting status and completion language at write-up. This Shop Operations pair asks whether you can keep that promise honest while the car moves through diagnosis, parts, authorization, and repair—and whether you update people when reality changes.
Shop Operations is only about 18% of scored C1 questions, but progress-monitoring items punish consultants who sell “ready by 5:00,” disappear until pickup, or invent parts ETAs. Excellence here protects CSI, reduces lobby confrontations, and keeps dispatch from being blindsided by promises the shop cannot keep.
Task 9: Establish completion expectations (shop-ops view)
A completion expectation is the best current estimate of when authorized work can finish, based on known constraints, not optimism. At write-up you may give a preliminary window; as a Shop Operations skill, you continually refine that window using live shop data.
| Input you must check | Why it changes the promise | Bad consultant habit |
|---|---|---|
| Diagnosis still open | Time cannot be firm until cause and parts needs are known | Promising a “brake job done by noon” before inspection |
| Parts on hand vs. ordered | ETA from vendor, not wishful thinking | Saying “parts are here” without verifying |
| Authorization pending | Work cannot start until the customer approves scope/price | Quoting a finish time as if approval already happened |
| Bay / tech availability | Dispatch owns load and skill mix | Promising around a tech who is already overloaded |
| Sublet or special tools | External clocks extend the timeline | Ignoring body-shop / machine-shop lead time |
| Comeback / safety priority | May bump other work—and must be explained | Hiding priority decisions that delay other ROs |
How to set an expectation the exam respects:
- State what is known (“We’re diagnosing a brake noise; no parts ordered yet”).
- Give a conditional timeline (“If pads/rotors are in stock and you authorize by 11:00, late afternoon is realistic”).
- Name the next checkpoint (“I’ll call by 1:00 with findings either way”).
- Record the promise on the RO/CRM so dispatch and the next shift see it.
Never treat “ASAP” or “end of day” as a plan. Those phrases create different pictures in the customer’s mind than in the shop’s. Prefer clock times or clear windows tied to conditions.
Task 10: Monitor repair/service progress
Monitoring means you actively compare promised state to actual state throughout the day—not only when the customer calls. Effective consultants build a rhythm:
| Checkpoint | What you verify | Typical action |
|---|---|---|
| After dispatch | RO is with the right tech; concern notes are clear | Clarify Three Cs with tech if needed |
| Mid-diagnosis | Findings, time remaining, parts likelihood | Update customer if diagnosis expands |
| Parts stage | Ordered? ETA? Special-order risk? | Reset completion if vendor slips |
| Authorization | Customer decision documented | Hold work until yes/no is clear |
| Mid-repair | Labor progress vs. remaining book time | Flag overtime risk early |
| Quality / road test | Tech sign-off; concern addressed | Confirm ready before calling “done” |
| Delivery prep | Invoice matches authorized work; keys/loaner | Avoid “ready” calls that strand customers |
When delays occur, status updates are mandatory. Delay sources include late parts, expanded diagnosis, waiting on customer authorization, tech illness, bay conflicts, and sublet slips. The exam-correct response is: (1) learn the factual cause, (2) estimate the new realistic window, (3) contact the customer with the cause and new plan, (4) document the update, (5) tell dispatch the revised promise so scheduling stays aligned.
Silence is not neutral. A customer who hears nothing assumes the shop forgot them. A short factual update—“Pads are special-order; vendor ETA tomorrow 10:00; I’ll confirm when they arrive and reset pickup”—preserves trust even when the timeline moves.
Never guess—confirm before you speak
Guessing is a Shop Operations failure mode the C1 loves to test. Do not invent:
- A ready time without checking WIP and dispatch
- A parts arrival time without checking the parts ticket or vendor
- A diagnosis (“it’s just pads”) without the technician’s findings
- That authorized work is complete without tech/quality confirmation
- That a comeback is “fixed” because the RO was closed
If you do not know, say so, then get the answer: walk to the bay, message the tech, call parts, or ask the dispatcher. Customers prefer “I don’t have confirmation yet—I’ll check and call you in ten minutes” over a confident wrong answer that collapses at pickup.
Coordinate with dispatch
Dispatch (or the shop foreman / lead in smaller stores) is the traffic controller for bays, skill routing, and priority. Your completion promises are inputs into that system. Coordination looks like:
- Before promising: Ask whether capacity exists for the work type and time window.
- When scope grows: Tell dispatch immediately so they can rebalance, not after the customer is already promised a miracle.
- When a customer escalates timing: Do not override the board by pulling a tech off a safety job without a plan—ask dispatch to re-prioritize deliberately.
- At shift change: Hand off open promises (who is waiting on a call, which ROs are late) so the next consultant does not start from zero.
Scenario A — Parts delay mid-day
A customer was told 4:00 p.m. for an in-stock water pump. At 1:30 the parts person reports the pump is damaged in the box; a replacement arrives next morning. Correct path: Confirm the vendor ETA, revise the completion expectation with dispatch (loaner / overnight if available), call the customer with the cause and new plan, document declined overnight options if any, and never leave the old 4:00 promise on the RO.
Scenario B — Customer asks “is it done?”
A friend in the shop said they saw the car “almost finished.” The consultant almost says yes. Correct path: Check the RO status and tech notes; if road test and quality checks are incomplete, tell the customer it is not ready yet and give a fact-based remaining window. Guessing “done” creates a wasted trip and a CSI hit.
Scenario C — Diagnosis expands
Brake noise write-up assumed pads. The tech finds a seized caliper and a damaged hose. Correct path: Pause the old completion story, present the new recommendation and revised time/cost, get authorization, update dispatch, and only then reset the finish expectation. Do not keep selling the original “pads by 3:00” story.
Exam framing
Choose answers that combine honest expectations, active monitoring, prompt delay communication, no guessing, and dispatch coordination. Reject answers that hide delays, invent ETAs, or promise times the shop load cannot support.
A customer was promised a 5:00 p.m. pickup for a battery and starter. At 2:00 p.m. the parts department reports the starter is on backorder until tomorrow noon. What should the service consultant do FIRST?
A walk-in customer asks whether their vehicle can be finished by lunch. The consultant has not checked bay load or parts. The BEST response is to:
A customer calls asking if the transmission diagnosis found a bad solenoid. The technician has not posted findings yet. The consultant should:
Why must the service consultant coordinate revised completion times with dispatch?