How to Write a Repair Story on the RO: Technician Script and Examples

Q: What if the customer reported no symptoms but you found something preventive during inspection?

Lead with that. 'Customer brought vehicle in for oil change; no reported symptoms. During inspection, I found X.' Then follow the same four-step structure. Preventive repairs need even clearer explanation of why they matter, because the customer didn't come in asking for them. Explain the consequence of ignoring the finding.

Q: How do I handle a repair story when the diagnosis isn't final yet?

Be transparent. Write: 'Initial diagnosis suggests [X], but I need to perform [additional test] to confirm. Estimated cost for diagnosis: [amount]. Once confirmed, I'll have a repair estimate for you.' This keeps the customer in the loop and prevents them from feeling blindsided by a second call.

A repair story on the RO should tell the customer exactly what problem you found, why it matters, and what you're recommending—in plain language, not tech-speak. Start with the symptom the customer reported, describe what you discovered during diagnosis, explain the root cause in one sentence they'll understand, and finish with your recommendation and labor estimate. The whole thing should take 30 seconds to read aloud.

Why Your Repair Story Matters More Than You Think

You know that moment when a customer calls the service line on day three of their vehicle being in the bay, and the advisor says, "Um, the tech found something with the transmission"? That's what happens when the repair story on the RO is missing or vague. The advisor can't explain it. The customer gets nervous. And suddenly you're fielding a call that should never have happened.

The repair story is your chance to own the narrative. It's not a novel—it's a bridge between what you discovered and what the customer needs to decide. Stores that get this right tend to see higher approval rates on estimates, fewer callback questions, and customers who actually feel informed rather than blindsided. A pattern we see across top-performing dealerships is that their technicians write repair stories that answer three things: What did I find? Why does it matter? What do we do about it?

Actually,scratch that. Make it four things. The fourth is the cost, and it matters because a customer who reads "water pump replacement, $1,200 labor plus part" knows exactly what they're approving. No surprises. No second-guessing.

The repair story also protects you. If a customer comes back three weeks later claiming you "missed something," you have a documented record of what you checked, what you found, and what you recommended. That's not paranoia,that's professionalism.

The Core Script: What to Write and When

Here's the framework. Use this every time you write a repair story on the RO, and you'll be consistent, clear, and defensible.

Step 1: Start with the Symptom (What the Customer Told You)

Write exactly what the customer reported, in their words if possible. Don't paraphrase. Don't add your interpretation yet.

"Customer reports brake pedal feels soft when coming to a stop."
"Vehicle pulls to the right under hard acceleration."
"Air conditioning not blowing cold; refrigerant level dropping."
"Check Engine light on; customer states occasional hesitation on highway."

This is your anchor. Everything that follows makes sense because you're solving the problem the customer actually complained about.

Step 2: Describe Your Diagnosis (What You Found)

Now write what you actually discovered. Be specific. Numbers, measurements, visual observations,these matter.

"During brake system inspection, discovered both front brake pads worn to 2mm; front rotors measured at 30mm (replacement minimum is 32mm). Rear pads at 4mm, still serviceable. No fluid leaks detected."
"Performed alignment scan; vehicle reads 1.2 degrees toe-in on driver's front (spec is 0.25 degrees). Tire pressure front left at 28 psi (spec is 32 psi). Adjusted tire pressure and performed four-wheel alignment."
"Recovered and measured A/C refrigerant charge: 2.1 lbs (spec is 2.4 lbs). Performed dye injection and UV inspection under hood; found micro-leak at compressor discharge line fitting. Leak rate approximately 0.3 lbs per month."

The specificity does two things. First, it proves you actually did the work. Second, it gives the customer confidence that you know what you're talking about. Vague repair stories sound like guessing.

Step 3: Explain the Root Cause (Why It Matters, in Plain English)

This is where you translate tech into customer-speak. One sentence. Maybe two. No jargon unless you define it on the fly.

"Soft brake pedal combined with low fluid level means the brake system is losing hydraulic pressure,basically, your brakes aren't as responsive as they should be, and that's a safety issue."
"Toe misalignment pulls the steering in one direction and causes uneven tire wear; over 10,000 miles, you'd see the driver's side tire wearing out 30% faster than it should."
"That micro-leak means you're slowly losing cooling capacity. By next summer, you'll have insufficient refrigerant to keep the cabin cool, and running the compressor dry will damage it,a $1,800+ repair instead of a $200 line replacement today."
"The hesitation on the highway is your oxygen sensor getting lazy,it's not telling the engine computer to adjust fuel mixture fast enough when you accelerate, so you feel that lag. Left alone, it'll eventually trigger a higher emissions code and an engine misfire."

Notice the pattern: problem statement, immediate consequence, future consequence if ignored. That's persuasive because it's truthful and it gives the customer a reason to decide.

Step 4: State Your Recommendation and the Price

Be direct. What are you recommending? Why? How much?

"Recommend: Replace both front brake pads and resurface front rotors. This restores braking performance and safety. Labor: 1.5 hours at shop rate ($85/hr = $127.50). Pads: $45 per axle ($90 total). Rotors: $65 each, resurfacing labor included. Estimated total: $282.50."
"Recommend: Perform four-wheel alignment. Labor: 1 hour ($85). This corrects the pull and prevents accelerated tire wear. No parts cost. Total: $85."
"Recommend: Replace compressor discharge line with new fitting and rebuild. Includes 1 lb refrigerant recharge to spec. Labor: 2 hours ($170). Line and fitting: $95. Refrigerant: $25. Total: $290."
"Recommend: Replace oxygen sensor (pre-catalyst). This will clear the hesitation and prevent the misfire code. Labor: 0.8 hours ($68). Part: $110. Total: $178."

The price has to be there. A recommendation without a price is incomplete. The customer doesn't know whether to say yes or no, and the advisor doesn't know how to present it.

Real-World Example: Timing Belt on a 2017 Honda Pilot at 105,000 Miles

Let's walk through an actual scenario using the four-step script. A 2017 Pilot rolls in on an oil change; customer mentions the vehicle now has 105,000 miles and wants to know if anything major is coming up.

Step 1 (Symptom): "Customer reports no current symptoms. Vehicle runs smoothly, no unusual noises. Bringing in for preventive maintenance discussion at 105k miles."

Step 2 (Diagnosis): "Reviewed manufacturer maintenance schedule. Timing belt replacement is recommended at 105,000 miles for this model year. Visual inspection of belt shows no cracking or fraying, but component is within the interval window. Serpentine belt is also original equipment, showing minor surface cracking."

Step 3 (Root Cause): "Timing belts on this engine are interference-type, meaning if the belt fails, the pistons will collide with the valves, causing catastrophic engine damage,we're talking $4,500 to $6,000 in engine machine work or replacement. At 105k, you're at the recommended replacement interval, and waiting even 10,000 more miles increases the failure risk significantly. The serpentine belt powers your alternator and water pump; when it goes, you lose charging and cooling, and you'll be stranded."

Step 4 (Recommendation and Price): "Recommend: Replace timing belt, water pump, and serpentine belt as a preventive package. This is the ideal time,the water pump and pulleys are already exposed when we do the timing belt. Labor: 4.5 hours ($382.50). Timing belt kit: $185. Water pump: $95. Serpentine belt: $35. Estimated total: $697.50. If the timing belt fails between now and 115k miles, you're looking at $5,000+ in engine damage."

That's a complete repair story. The customer understands the risk, knows the cost, and can make an informed decision. The advisor can present it without hesitation. And you have documentation.

Tone, Language, and What to Avoid

Write like you're texting a friend who's not a mechanic, but who you respect. You're not dumbing it down; you're just not using acronyms without context.

Avoid this: "Found excessive wear on the rotor hat. Measured TIR at 0.015". Recommend OEM replacements."

Write this instead: "Rotors are warped (measured runout at 0.015 inches; spec is 0.005). This causes the brake pedal to pulsate under hard braking. Replace both rotors to spec."

The second version tells the story. The first one is just jargon.

Also: avoid blame. Don't write, "Customer neglected oil changes" or "Previous shop did poor alignment work." Stick to what you found and what needs to happen next. Blame closes doors.

And one more thing: be honest about uncertainty. If you're not 100% sure about the root cause, say so. "Visual inspection suggests the alternator is failing (charging voltage at 12.8V on idle, should be 13.5V+), but I recommend we load-test it to confirm before ordering parts." That's better than guessing and ordering the wrong part.

How to Format It on the RO So Advisors Can Actually Use It

The repair story lives in your DMS, usually in a "findings" or "diagnosis notes" section. Format matters because the advisor is going to read this aloud to a customer or send it in a text message.

Use line breaks. One paragraph per step. Whitespace makes it readable on a phone screen.
Lead with the headline. Put the recommendation right at the top: "RECOMMEND: Replace front brake pads and rotors." Then the details below.
Use bold for numbers. Make the price, labor hours, and measurements stand out. $282.50. 1.5 hours. 2mm pad thickness.
End with a question, not a statement. Instead of "Customer needs to approve this immediately," write: "Would you like us to proceed with this repair, or would you prefer to think it over?" That's the advisor's cue to ask for approval, not demand it.

A well-formatted repair story on the RO is something the advisor can hand off to a customer or read over the phone without pausing to interpret. It's also something your service manager can glance at and know whether the recommendation is sound.

The Script You Can Copy and Paste

Here's a template you can adapt for any repair. Fill in the brackets and you're done.

CUSTOMER REPORTED: [What they said about the symptom or concern]

WHAT I FOUND: [Specific measurements, observations, and test results. Include numbers.]

WHY IT MATTERS: [One sentence connecting the finding to a safety, performance, or durability issue. Explain the consequence if ignored.]

RECOMMEND: [The repair or service. Labor hours and rate. Part costs. Total estimate.]

NEXT STEP: [Approval question or timeline.]

That's it. Four sections. Fills out in five minutes. Gives the advisor and customer everything they need.

This is the kind of workflow Dealer1 Solutions was built to handle,giving technicians a simple way to document their work so the whole team can move faster and customers feel informed instead of confused.

Common Mistakes Technicians Make When Writing Repair Stories

You might be thinking, "I've been writing RO notes for years. What's the difference?" Fair question. Here are the patterns we see in repair stories that don't work:

Skipping the symptom. You write "Replace water pump" without mentioning that the customer reported overheating or coolant leaking. Without context, the advisor has no story to tell. The customer wonders why they need this.
Forgetting the why. "Brakes are worn" doesn't explain why worn brakes are a problem. "Brakes worn to 2mm; safety hazard; stopping distance increases by 15-20%" does.
Burying the price. If the estimate is hidden in a paragraph, the advisor has to hunt for it. Put it front and center.
Being vague about diagnosis. "Transmission slipping" could mean ten things. "Transmission fluid dark red and smells burnt; torque converter not holding pressure under load; recommend rebuild" is actionable.
Assuming the customer knows your trade. Not everyone knows what a serpentine belt does or why timing belt failure is catastrophic. Your job is to explain it.

How to Train Your Team on This Script

If you're a service manager reading this, your technicians aren't going to adopt a new writing style overnight. Here's how to make it stick:

Post the template in the shop. Print it and tape it above each workstation. Make it muscle memory.
Review one RO per week in your team meeting. Pick a good repair story and a weak one. Compare them. Show your team why one works and one doesn't.
Give feedback on the RO, not the repair. If a tech's story is incomplete, say so. "I can't present this to a customer because I don't know why they need this repair." That's actionable.
Tie it to approval rates. Show your team the data: "Last month, repair stories that included the 'why' had an 87% approval rate. Stories without it had 64%. That's real money."
Make it part of your quality checklist. Before the advisor calls the customer, the RO review should include: Symptom clear? Diagnosis specific? Root cause explained? Price visible? If any answer is no, send it back.

Your technicians aren't lazy. They're just working fast and assuming the advisor will figure it out. The template removes that guesswork.

Frequently asked questions

How long should a repair story on the RO actually be?

Long enough to answer the four steps (symptom, diagnosis, root cause, recommendation) and short enough to read in under two minutes. Aim for 150–250 words for a standard repair. If you're writing more than 350 words, you're probably over-explaining; cut it down. The advisor has 30 seconds to pitch it to the customer, so clarity beats comprehensiveness.

What if the customer reported no symptoms but you found something preventive during inspection?

Lead with that. "Customer brought vehicle in for oil change; no reported symptoms. During inspection, I found X." Then follow the same four-step structure. Preventive repairs need even clearer explanation of why they matter, because the customer didn't come in asking for them. Explain the consequence of ignoring the finding.

Should I write different repair stories for different audiences (service advisor vs. customer)?

No. One repair story, written for the customer to understand. The advisor will adapt it for their communication style, but the core facts should be clear enough that anyone reading it gets the picture. If you're writing tech-heavy notes for "internal use only," you're creating confusion and forcing the advisor to translate.

What if the customer rejects the repair recommendation?

That's fine. Your repair story on the RO documents what you found and what you recommended. If they say no, note that in the RO as well: "Customer declined repair recommendation; vehicle returned as-is." You're protected. You offered the solution; they chose not to take it. That's their call.

How do I handle a repair story when the diagnosis isn't final yet?

Be transparent. Write: "Initial diagnosis suggests [X], but I need to perform [additional test] to confirm. Estimated cost for diagnosis: [amount]. Once confirmed, I'll have a repair estimate for you." This keeps the customer in the loop and prevents them from feeling blindsided by a second call.

Can I use this template for warranty work or recalls?

Absolutely. Warranty and recall work still needs a clear story. "Recall 23-V-456: seatbelt pretensioner can fail under impact. We'll replace the pretensioner assembly and reprogram the seat control module. No charge to you; covered under manufacturer recall. This takes 1.5 hours." Same structure, same clarity.