4.1 Repair Order Accuracy, Authorization & the Three Cs
Key Takeaways
- The Three Cs on a repair order are Concern (customer symptom in their words), Cause (technician diagnosis), and Correction (work performed to fix it).
- Confirm repair-order accuracy before work begins: customer identity, vehicle ID, concerns, authorized lines, contact numbers, and payment source.
- Any work beyond the approved scope requires fresh customer authorization—regardless of how small the dollar amount is.
- Declined or deferred recommendations must be documented on the repair order with risk explained; never perform unauthorized work or erase the recommendation.
- Authorization is informed consent: the customer understands scope, price (or not-to-exceed), and timeline before signing or approving.
On the ASE C1 Automobile Service Consultant exam, Customer Relations Task 10 is a documentation and consent checkpoint: confirm accuracy of the repair order and obtain repair/service authorization. A repair order (RO) is not a casual scratch pad. It is the legal and operational record of what the customer requested, what the shop agreed to do, what the technician found, and what was actually performed. Errors on the RO create wrong diagnoses, unauthorized charges, warranty claim failures, and CSI complaints. Task 10 asks you to catch those errors before they become disputes.
Why accuracy comes before the wrench turns
Before a vehicle is dispatched, walk the RO as if you were the technician reading it cold and the customer reading it at pickup. Ask: Would a stranger know exactly what to check? Would the customer recognize every authorized line? Common accuracy failures include wrong phone number (stalls additional authorization), misspelled concern (“pulls left” written as “pulls right”), VIN/year mismatch, missing mileage, or a labor line that does not match what the customer approved. The exam loves scenarios where a consultant “saves time” by skipping verification—then a cheap add-on or a miswritten concern blows up later.
| RO field to verify | Why it matters | Typical trap |
|---|---|---|
| Customer name & contact | Reach for status and add-on authorization | Old number from a prior visit |
| Vehicle ID (VIN, plate, year/make/model) | Correct parts, history, warranty | Assumed year from appearance |
| Mileage / hours | Maintenance intervals and warranty | Left blank or guessed |
| Concern lines | Technician can duplicate the symptom | Consultant’s diagnosis written as the concern |
| Authorized operations & prices / NTE | Collectibility and consent | Verbal “go ahead” never recorded |
| Payment source | Warranty, fleet, cash, service contract | Assumed customer-pay on a warranty visit |
The Three Cs: Concern, Cause, Correction
Industry standard repair-order writing uses the Three Cs. ASE-style questions treat this as vocabulary you must know cold.
Concern
The Concern is the customer’s problem or request, recorded in customer language plus conditions that help the technician duplicate it. Good concern writing answers: What happens? When? How often? Under what conditions (cold/hot, speed, gear, weather, load)?
- Weak: “Noise” or “Check brakes.”
- Strong: “Customer states grinding noise from front when braking at city speeds; worse when cold; started after overnight rain.”
Do not replace the concern with your opinion (“worn pads”). Opinion belongs nowhere until diagnosis exists—and even then, diagnosis is Cause, not Concern. Capturing exact words also protects you when the customer later says, “I never said that.”
Cause
The Cause is the technician’s diagnosis: the verified reason for the concern. It should be specific enough to justify the correction and support warranty or policy review.
- Weak: “Brakes bad.”
- Strong: “Front inner brake pads worn to 2 mm; rotors below discard thickness; measured pad wear and rotor thickness documented.”
Cause comes after inspection/diagnosis, not at write-up. At intake you may authorize diagnosis time; you do not invent Cause before the tech has findings.
Correction
The Correction is what was done to resolve the concern: parts replaced, adjustments made, software updated, fluids serviced, or “no problem found” with verification steps listed. Correction must match Cause and the authorized scope.
| Three C | Who owns it | Timing | Example |
|---|---|---|---|
| Concern | Customer (consultant records) | Write-up / intake | “AC blows warm after 20 minutes highway” |
| Cause | Technician (consultant may translate) | After diagnosis | “Low refrigerant; leak at condenser O-ring” |
| Correction | Technician / shop | After authorized repair | “Replaced condenser O-ring; evacuated/recharged; leak-tested OK” |
Exam trap: Mixing the Cs—writing a part name in the Concern line, or leaving Cause blank on a completed RO—signals incomplete documentation. Warranty administrators and shop managers expect all three completed when work is finished.
Confirming accuracy as a consultant habit
Read the RO back to the customer before they leave: “You’re authorizing diagnosis of the warm AC after highway driving, and we’re starting with a performance check and leak inspection, not-to-exceed $X unless we call you.” That read-back catches wrong concerns and wrong price expectations in seconds. Also confirm how to reach them during the day and who else may authorize work (spouse, fleet manager, lease company).
Authorization: scope, not just dollars
Authorization means the customer has approved specific work (and related charges) before it is performed. Many state consumer laws and shop policies require written authorization or a documented oral approval with time, amount, and name. For the C1 exam, internalize this rule:
Any work beyond the approved scope needs new authorization—regardless of price.
A $12 hose clamp, an extra half-hour of labor, a “while we’re in there” fluid flush, or a related part the tech “just went ahead and did” all require a call and documented approval if they were not on the original authorized estimate. Dollar thresholds (“only call if over $50”) are a classic wrong answer. Scope controls authorization; price is what you quote when you ask for that new approval.
Practical authorization flow
- Write accurate Concern(s) and estimate for diagnosis and/or known services.
- Obtain authorization (signature, electronic approval, or documented phone approval with not-to-exceed).
- Dispatch work within that scope.
- When the technician finds additional needs, stop, call the customer, explain findings in plain language, quote options, and get new authorization before proceeding.
- Update the RO with the new authorized lines and the contact record (who approved, when, amount).
Scenario: “It’s only a few dollars”
A customer authorizes front brake pads and rotors. Mid-job the technician finds a seized caliper slide that needs a caliper hardware kit (~$18 parts, 0.3 hr labor). Consultant A installs it without calling because “it’s cheap and keeps the brakes safe.” Consultant B calls, explains binding risk and price, gets approval, and notes the RO. Consultant B is correct. Cheap unauthorized work is still unauthorized; if the customer disputes it, the shop may lose the charge and the CSI score.
Declined and deferred work: documentation hooks
When the customer says no—or “not today”—to a recommendation, Task 10’s accuracy duty includes leaving a clean paper trail that later chapters (declined-service documentation in Shop Operations) will reinforce:
- Leave the recommendation on the RO/history; do not delete it to “clean up” the ticket.
- Mark it declined or deferred with date and consultant initials.
- Explain risk in plain language (safety, breakdown, higher future cost) without coercion.
- Offer to revisit at a future appointment if appropriate.
Never perform declined work “for their own good.” Never refuse to release the vehicle solely because a non-mandatory service was declined (safety-critical hold policies are shop/legal exceptions you follow by management direction—not by improvising repairs).
Realistic write-up checklist (Task 10)
Use this mental checklist before the customer walks away and again before closing the ticket:
- Concern lines match what the customer said and the conditions of the symptom.
- Vehicle and customer identifiers are correct and contact info was reconfirmed today.
- Authorized lines match the estimate the customer approved (ops, parts quality, NTE).
- Additional findings triggered a new authorization call, documented on the RO.
- Declined items remain visible with decline notation.
- Three Cs will be completable: Concern now; Cause/Correction after diagnosis and repair.
Exam traps for Task 10
| Trap wording | Why it fails | Better action |
|---|---|---|
| “Authorization needed only above $X” | Ignores scope | Authorize any out-of-scope work |
| “Write the likely failed part as the concern” | Biases diagnosis | Record customer symptom + conditions |
| “Tech can add related items without calling” | Unauthorized work | Call and document approval |
| “Erase declined brake flush so RO looks clean” | Destroys history/protection | Document decline and risk |
| “Manager approval replaces customer approval” | Wrong party | Customer (or authorized payer) must approve |
Task 10 sits between intake and sales: you already gathered concerns; later you will present estimates and close. Here the skill is precision and consent. Accurate ROs with complete Three Cs and scope-based authorization keep work collectible, technicians informed, and customers protected—exactly what C1 Communications rewards.
On a repair order, the Three Cs stand for:
A customer authorized front brake pads only. The technician finds a damaged brake hose that should be replaced for about $25 in parts. What should the service consultant do?
Which Concern line BEST supports accurate diagnosis and Task 10 documentation?