Capture the customer's words first. Separate what the customer reports from what the advisor or technician assumes.
Communication boundary: This module teaches accurate intake, estimating, authorization and explanation. Prices, taxes, fees, warranty rules, disclosures and authorization requirements vary by business and jurisdiction. Use current shop policy and applicable law. Never promise a diagnosis or repair outcome before evidence supports it.
7 Mini-Lessons
Ask when, where, how often, hot/cold, speed/load, warning indicators, recent work and what changed. No-Op, Po-Op and Unwanted Operation are useful complaint families.
Document concern, conditions, requested work, vehicle state and authorization boundaries so the technician receives usable information.
Separate inspection/diagnostic authorization from confirmed repair work. Parts, labor, sublet, taxes/fees and contingencies should be understandable without pretending unknowns are known.
Explain what was tested, what was found, why it matters and what is recommended without drowning the customer in jargon or overstating certainty.
Record what was approved, declined or deferred and any changed estimate before additional work proceeds according to shop policy and applicable requirements.
Final communication should connect the original concern, verified cause, completed work, verification result and any remaining/deferred items.
8-Part Service-Writing Explorer
Customer words
Preserve the complaint before interpretation.
Operating conditions
Capture when and how the concern occurs.
Repair-order clarity
Give the technician a reproducible starting point.
Diagnostic authorization
Define the approved evidence-gathering scope.
Estimate structure
Separate known work, unknowns and contingencies.
Technician findings
Translate tests and root-cause evidence accurately.
Customer authorization
Document decisions and changes clearly.
Closeout & follow-up
Tie the final explanation back to the original concern.
Complaint → Estimate → Communication Lab
Normalized teaching indices are reasoning aids, not customer-satisfaction or legal-compliance scores.
Complaint clarity
—
Authorization clarity
—
Evidence alignment
—
Customer clarity
—
Choose a state.
6-Step Service-Writing Workflow
- Capture the customer's concern in their words
- Clarify operating conditions, history and requested outcome
- Write a technician-usable concern and establish authorization
- Receive and verify technician findings/evidence before presenting conclusions
- Build/explain the estimate and document approval, decline or deferral
- Close out with cause, correction, verification and remaining recommendations
4 Evidence-Gated Cases
Case 1: “My car is acting funny”
No operating conditions or specific behavior are recorded.
Best branch: Complaint-clarification branch. Ask what it does, when it occurs and under what conditions before handing the concern to the technician.
Case 2: Check-engine light — “needs an oxygen sensor”
The customer read a code elsewhere, but no diagnosis has been performed.
Best branch: Diagnostic-authorization branch. Record the customer's information as history, not as a confirmed cause; authorize testing before estimating a component replacement.
Case 3: Estimate changes after teardown/testing
New evidence reveals additional required work.
Best branch: Reauthorization branch. Explain the new evidence, revised scope and price; document the customer's decision before additional work according to applicable policy/rules.
Case 4: Repair complete, explanation says only “fixed”
The technician documented a failed circuit, repair and successful verification.
Best branch: Closeout branch. Translate the evidence into plain language: concern, cause, correction and how the result was verified.
Randomized 10-Question Knowledge Check
Instructor Practical Rubric · 6 Dimensions
Complaint intake
Rate 1–4 using observed evidence. Online completion does not equal workplace competency.
Repair-order clarity
Rate 1–4 using observed evidence. Online completion does not equal workplace competency.
Authorization discipline
Rate 1–4 using observed evidence. Online completion does not equal workplace competency.
Estimate/evidence alignment
Rate 1–4 using observed evidence. Online completion does not equal workplace competency.
Customer explanation
Rate 1–4 using observed evidence. Online completion does not equal workplace competency.
Closeout documentation
Rate 1–4 using observed evidence. Online completion does not equal workplace competency.
Depth profile: Foundation = distinguish customer complaint, technician finding and recommendation. Technician = write usable concerns, estimates and evidence-based explanations. Deep = manage ambiguous complaints, changed scope, authorization boundaries and technical-to-customer translation without overstating certainty.
Preserved supporting routes: Complaint Intake & Test Planning · Evidence, Root Cause & Verification