Shop Foreman Repair Order Script: Word-for-Word Examples for Writing Up ROs

A shop foreman should use a script that starts with vehicle confirmation, moves through a methodical systems check, explains findings in plain language, presents labor and parts costs separately, gets customer approval on each section, and closes by confirming the next steps and timeline. The script below follows this structure so technicians and advisors can write consistent, complete repair orders that reduce callbacks and customer disputes.

Why a Standardized RO Script Matters for Your Shop

Every time a foreman or tech sits down to write a repair order, they're either following a repeatable system or winging it. The difference shows up in your callback rate, your CSI scores, and the number of hours you spend re-explaining work to upset customers.

A solid RO script does four things: it ensures nothing gets missed, it documents what you found and why you recommend it, it gets the customer to actively agree before you turn a wrench, and it creates a paper trail (digital or physical) that protects both you and the customer if a dispute comes up later.

Stores that get this right tend to see their hours-per-RO stabilize, their first-pass approval rates climb, and their follow-up phone calls drop. That's not because the script is magic. It's because consistency in how you write up work removes the guesswork for your service advisor and your customer.

The Core RO Script: Vehicle Confirmation and Initial Greeting

Start here, every time. Don't skip it.

"Good morning/afternoon, [Customer Name]. I'm [Your Name], the shop foreman here at [Dealership Name]. Before we go any further, I want to confirm the vehicle we're looking at. You're driving a [Year/Make/Model], correct? And the current mileage is [#] miles. Is that right?"

Wait for confirmation. Write it down. This step takes 30 seconds and eliminates the scenario where you're talking about the wrong car or the customer thought you were looking at their spouse's vehicle instead.

Then move straight into the reason they're here:

"Your service advisor tells me you came in today because [customer's stated concern]. Is that the main thing you want us to address, or is there anything else you've noticed?"

Listen. Let them add. Then confirm you've got it right.

The Inspection Section: What You Found and Why It Matters

This is where most ROs fall apart. Foremen and techs jump straight to "needs new brake pads" without explaining what they saw or why it matters to the customer.

Use this framework for every finding:

1. State what you inspected. "I put the vehicle on the lift and performed a full multi-point inspection, starting with the brake system."
2. Describe what you found in simple terms. "The front brake pads are worn down to about 2mm of material. The factory specification calls for a minimum of 4mm before they need replacement."
3. Explain the consequence if ignored. "If we don't replace them soon, the metal backing will start grinding on the rotor, which damages the rotor and makes the repair more expensive."
4. Recommend the fix. "I'm recommending we replace the front brake pads and inspect the rotors for wear."

Here's how it sounds in practice:

"Your front brake pads are down to about 2mm. That's pretty thin—we like to see at least 4mm. If we wait much longer, the metal backing will hit the rotor and you'll end up needing new rotors on top of pads, which doubles the cost. I'd recommend we do the pads now, and we'll also take a close look at the rotors to make sure they're still good."

Document findings in your DMS in the same order you explain them. Don't scatter observations across the RO. A typical $3,400 timing belt job on a 2017 Pilot at 105,000 miles should read: "Timing belt shows cracking and separation at tooth edges. Manufacturer interval is 105,000 miles; vehicle is at odometer reading now. Water pump shows minor seepage and should be replaced as preventive measure while timing belt is removed. Serpentine belt is glazed and slipping on pulleys; recommend replacement. Labor: timing belt, water pump, serpentine belt, and all fluids. Parts: OEM timing belt, OEM water pump, OEM serpentine belt, new coolant, new oil." Not scattered notes that the advisor has to piece together later.

The Labor and Parts Breakdown: How to Present Costs Without Sticker Shock

Separate labor from parts. Always. And always present them in the same order on every RO.

"For the front brake pad replacement, here's what we're looking at. Labor is [#] hours at our shop rate, which comes to [total labor]. The OEM brake pads are [price]. Your total for this repair is [total]. Does that work for you?"

If the customer hesitates, don't cut the quality of the repair. Instead, ask clarifying questions:

"I understand that's more than you expected. Would it help if we split this into two visits—do the brake pads now and the rotor inspection in a few months? Or would you rather we hold off and schedule this for next month?"

The goal is to get a customer decision, not to pressure them. A customer who says no to a repair they need will come back when they're ready. A customer who feels pressured will take their car somewhere else and leave you a bad CSI score.

The Approval Section: Getting Customer Sign-Off on the RO

This is non-negotiable. Before any work starts, the customer needs to explicitly approve the repair order.

Walk them through the RO on screen or on paper, line by line:

"Here's the RO we're putting together. At the top, we have your vehicle info and your contact number. Under that, the reason you came in. Under that, the brake pad repair with the labor cost and the parts cost. The total is [amount]. I'm going to have you initial here, which confirms you've reviewed this repair and you're authorizing us to proceed. Sound good?"

Don't rush this step. If they have questions, answer them now, not when they pick up the car. If they want to add another repair, add it to the RO and get approval again. If they want to decline a recommended repair, document that too: "Customer declined rotor inspection at this time." This is the kind of workflow Dealer1 Solutions was built to handle,getting approval line by line and building a complete audit trail so there's never a question about what was agreed to.

The Timeline and Next Steps: When Will It Be Ready?

End every RO conversation with a clear timeline.

"We're going to get this car into the bay this afternoon. Brake pads typically take about an hour, so you should be ready to pick up by [time] today. We'll call you when it's done. If we find anything else while we're working,something unexpected,I'll call you before we do any additional work. Is that number still [phone number]?"

And if they're dropping the car off:

"We'll have this done by [time] tomorrow. How would you like us to get in touch,call, text, or email?"

Confirm their preferred contact method. Write it on the RO. Stick to it. A callback that comes when you said it would come builds trust faster than perfect work that shows up unannounced.

Handling Multiple Repairs: The Prioritization Script

If your inspection turns up more than one issue, don't dump all of it on the customer at once. Prioritize.

"I found three things. The first is your brake pads, which I'd say needs attention soon,probably this month. The second is your serpentine belt, which is starting to crack. That's a 'next month' item. And the third is your transmission fluid. It's dark but not burned, so I'd recommend we do that in the next two months. Here's what I'd suggest: let's do the brake pads today while you're here. Then schedule the serpentine belt for next month. The transmission fluid can wait until after that. Does that make sense?"

This approach,urgent/soon/later,gives the customer a roadmap and prevents sticker shock. And it keeps them coming back instead of taking all three repairs somewhere else.

Write this prioritization on the RO so your service advisor and your next technician both know the customer's preference. "Customer approved brakes today. Serpentine belt approved for next month visit. Transmission fluid approved for Month+2."

The Language Rule: Speak Like a Human, Not a Manual

This is where a lot of foremen get tripped up. They write like they're reading a service bulletin instead of talking to a person.

Don't write: "Recommend replacement of front friction material assemblies due to dimensional variance from OEM specification."

Write: "Front brake pads are worn down. They need to be replaced."

Don't write: "Vehicle exhibits squealing noise upon brake pedal depression."

Write: "The brakes are making a squealing noise when you stop."

Your customer doesn't speak technical. Your service advisor shouldn't have to translate what you wrote. The RO should read like a conversation, not a diagnostic code.

And here's the kicker: when you speak plain English on the RO, disputes drop. Customers feel like you're being straight with them instead of using fancy words to hide something.

Frequently asked questions

What should you do if a customer disagrees with your repair recommendation?

Don't argue. Acknowledge their concern, explain your reasoning one more time in plain terms, and then ask what they want to do. If they decline, document it on the RO: "Customer declined [repair] at this time. Advised customer of potential consequences. Customer chose to proceed without this repair." This protects you both. If something goes wrong later, you have proof you recommended it.

How detailed should your RO findings be?

Detailed enough that another technician could read it and understand exactly what you found, but simple enough that a customer without mechanical knowledge can follow along. Aim for 2-3 sentences per finding. Include what you checked, what you found, and what you recommend. That's it.

Should you include a parts estimate on the RO before you know for sure what's needed?

Yes, but label it clearly as an estimate. Write "Estimated parts cost: $[amount]" so the customer knows it's not final. If the actual cost comes in higher or lower, call the customer before you proceed. Never surprise them with a bill that's $200 higher than what you quoted.

What's the best way to handle warranty work on the RO?

Treat it the same way you'd treat a paid repair, but note at the top of the RO: "Warranty work,no charge to customer." Document everything you did, all the parts you replaced, and all the labor hours. Your warranty claim depends on a complete, accurate RO. If you skimp on documentation, you won't get reimbursed.

How do you write up a repair order when the customer isn't present?

You still follow the same script, just with your service advisor as the go-between. Write the RO clearly, have your advisor present it to the customer over the phone or in person, get written or digital approval, and confirm the timeline. If the customer isn't available, don't start work without approval. That's how you end up with a $2,000 repair the customer didn't want.

Should you include recommendations for future maintenance on the RO?

Absolutely. If you see something that's not urgent but will need attention in 3-6 months, mention it and ask if the customer wants you to note it for their next visit. This keeps them coming back and shows you're thinking ahead about their vehicle's health, not just the work in front of you today.

The script above isn't a one-size-fits-all template,it's a framework. Your foreman will adapt it based on the repair, the customer's tone, and the urgency of the work. But the bones stay the same: confirm the vehicle, explain findings clearly, present costs separately, get approval, and confirm the timeline.

The shops that use a consistent script see fewer callbacks, shorter conversations, and higher approval rates on recommended work. That's not a coincidence. It's the difference between writing ROs on the fly and running a controlled process that your whole team understands.

---