The advisor owns the first C. A good concern line records the symptom in the customer's own words, when it happens, how often and since when, what has already been tried, and what the advisor verified at the car. With that, a technician can reproduce the problem, and the cause and correction can answer the concern the customer actually had.
The Three Cs and Who Owns Each
Every repair line tells a three-part story. The concern is what the customer experienced. The cause is what the technician found. The correction is what was done about it.
The advisor writes the concern and nothing else, but it is the part everything hangs on. A technician who gets "customer states noise" has to invent the rest: which noise, from where, doing what. If the invention is wrong, the cause and correction will be accurate answers to a question the customer never asked.
What a Technician Needs on the Line
Ask a technician what they want from a concern line and you will hear the same five things.
- The symptom, in the customer's words. What they hear, feel, see or smell. Not what they or the advisor think is wrong. If the customer asks for a part ("I need a battery"), write the request and then the symptom behind it ("slow crank on cold mornings").
- When it happens. Speed, temperature, cold start or warm, braking, turning, accelerating, over bumps, with the A/C on.
- How often and since when. Every time, a few times a week, once. Since last week, since the last service, since a pothole.
- What has been tried. Recent work here or elsewhere, anything the customer did themselves, a previous visit for the same thing.
- What the advisor verified. Heard the noise pulling into the lane. Warning light on at write-up. Could not reproduce it on a short ride with the customer. All three are useful.
On intermittent problems, add when the customer can be reached and whether they can ride along. Most of this comes out of the walkaround if the advisor asks (see how better walkarounds improve repair order accuracy). The question that produces the most is the simplest: "If I were riding with you, when would I notice it?"
Before and After
These are example lines written for this page, not taken from a store.
| Vague line | Line a technician can work from |
|---|---|
| Check brakes. | Customer states grinding noise from front when braking at low speed, for about two weeks, worse first thing in the morning. No pulsation in pedal. Advisor heard noise pulling into lane. |
| Customer states noise. | Customer states rattle from right rear over bumps under 30 mph, started after tire rotation here last month. Not present on smooth road. Customer can ride along until 9 a.m. |
| A/C inop. | Customer states A/C blows cold on the highway, turns warm at idle after 15 to 20 minutes, three times this week in hot weather. Recharged at another shop in June. |
| Check engine light on. | Customer states check engine light came on Tuesday after fueling. Steady, not flashing. No change in how it drives. Light on at write-up. Customer already retightened gas cap. |
| Car pulls. | Customer states vehicle drifts right on the highway with hands off the wheel since hitting a pothole last week. Steering wheel sits off center to the left. Tire pressures set at write-up, no change. |
The right-hand lines take about thirty seconds longer to get and to type. None of them contains a diagnosis.
What a Vague Line Costs
We have no verified figure for the cost of a poor concern line, and anyone quoting one is guessing. The mechanism is easy to follow in your own shop.
Technician time. The technician stops, walks to the advisor, and waits while the advisor calls the customer. On flat-rate, that time is the technician's loss.
"Could not duplicate." An intermittent problem with no conditions on the line is a problem the technician will not find. The car goes home unfixed and the customer has paid for a diagnosis that told them nothing.
The wrong fix. The technician finds something that matches a vague line, fixes it, and it was not what the customer meant. That is a comeback, at the store's expense.
The delivery. J.D. Power names "having work completed properly the first time" and "explaining the work performed" among the top performance indicators in its 2026 U.S. Customer Service Index Study (51,228 owners and lessees of one- to three-year-old vehicles, surveyed during 2025; read from an archived copy of the release). Both begin with the concern line. You cannot explain the work performed against a concern nobody wrote down.
The wider cost of lost detail between customer, advisor and technician is covered in why communication breakdowns cost dealerships.
Carrying the Story to Cause and Correction
When the repair order comes back from the shop, the advisor reads it as the customer will hear it.
- Does the cause answer the concern? If the concern was a rattle over bumps and the cause is a worn brake pad, something was lost. Ask before the customer does.
- Is the cause specific? "Found loose sway bar link, right rear" tells a story. "Found problem and repaired" does not.
- Does the correction say what was done and how it was checked? "Replaced link, road tested over same conditions, noise gone" closes the loop the concern opened.
Then the advisor translates. At delivery the three Cs become three plain sentences: here is what you told us, here is what we found, here is what we did and how we know it worked. An advisor who cannot say them from the repair order should go back to the technician first.
Documentation: Warranty, Invoices and Records
A repair order is also a record. For warranty work, the manufacturer decides what a claim must contain, and those requirements sit in each brand's warranty policy, which is not public. Follow your warranty administrator's standard. A concern that states the customer's symptom, with a cause and correction that match it, is the starting point.
State law adds its own requirements, and they differ. In California, for example, every job, including warranty work, goes on an invoice that lists service work and parts separately (Bus. & Prof. Code 9884.8, checked October 2026). Other states have their own invoice and authorization rules, summarized with citations in our page on repair estimate and authorization rules. This is general information, not legal advice. Confirm your own state's rules with counsel.
The record matters to the customer too. The FTC's consumer guidance on auto warranties tells vehicle owners that a warranty company could ask for maintenance records and that they should keep records of repairs and maintenance. A clear invoice from your store is one of those records.
How to Train and Audit It
Pull ten
For each advisor, pull ten recent repair orders at random that carry a customer concern (skip the maintenance-only tickets). Hand them to a technician or the shop foreman, not to another advisor, and ask one question per line: could you start work from this without finding the advisor? Then mark each line yes or no on the five elements: symptom in the customer's words, when, how often and since when, what was tried, what was verified.
Total by element as well as by advisor. If "what was verified" is missing on most lines across the team, nobody has been taught to write it.
Rewrite three
Sit with the advisor and rewrite three of their own weak lines. Where the information is missing, the advisor will say "I did not ask." That is the lesson.
Put the technician in the room
Have a technician tell the advisors, in ten minutes, what a bad line does to their day. Cross-department work with technicians is one of the advanced modules in Pinnacle's service advisor training, alongside the core work on active listening and explaining technical findings in plain language.
Repeat the pull monthly. Add the read-back to your lane observation scorecard so the concern is confirmed with the customer before it is typed, and watch comebacks by advisor as described in reading an advisor's numbers. If outside training is coming, the same pull is part of preparing your service department. More in the Service Advisor Training Resource Center.
Frequently Asked Questions
What are the three Cs on a repair order?
Concern, cause and correction. The concern is what the customer experienced, written by the advisor. The cause is what the technician found. The correction is what was done to fix it and how the fix was confirmed. Together they should read as one story that the customer would recognize as theirs.
Should the advisor write what the customer thinks is wrong?
Write what the customer asks for and what they experienced, and keep the two apart. "Customer requests alignment. States vehicle drifts right on the highway since last week." The request tells the technician what the customer expects. The symptom tells them what to verify before agreeing that the request is the right fix.
How long should a concern line be?
Long enough to cover the symptom, the conditions, the frequency, anything already tried and what you verified. That is usually two to four short sentences. A technician should be able to reproduce the problem from the line without a second conversation.
What should an advisor write when the problem cannot be reproduced at write-up?
Say so on the line, and record the conditions in more detail, because the technician will need them. Note when the customer last noticed it, what they were doing, and whether they can ride along or be reached quickly. "Not present at write-up" is useful information, not a failure.
Summary
The concern line is the one part of the repair order the advisor writes, and the cause and correction can only be as good as it is. Record the symptom in the customer's words, when it happens, how often, what was tried and what you verified. Read the finished repair order before delivery to see that the three parts connect. Audit by pulling ten repair orders per advisor, let a technician judge them, and rewrite the weak lines together.
