The Service Manager's Checklist for Writing Up a Repair Order

A solid repair order write-up starts with listening to the customer's complaint, documenting the vehicle condition on arrival, then matching the problem to the right service code and parts need before handing it to the technician. The best service managers use a consistent checklist to catch missing details, reduce comebacks, and keep labor hours accurate. This prevents ROs from bouncing between the service desk and the bay, saves your technicians' frustration, and protects your CSI scores.

What should be on a service manager's repair order checklist?

A working checklist isn't fancy—it's systematic. Every RO that leaves your service desk should pass these gates before it hits the bay:

Customer information complete and correct. Name, phone, email, address. Verify the vehicle VIN matches the customer file. This sounds obvious, but a typo in the phone number means you can't reach them about that warranty denial or parts delay.
Vehicle condition noted on arrival. Mileage, fuel level, exterior damage (dents, scratches, paint chips), interior condition (stains, odors, wear). This protects you if a customer claims you caused damage during service. A one-sentence note beats a lawsuit.
Complaint documented in customer's own words. Not abbreviated dealer-speak. "Noise from engine on cold start" not "noise." "Steering wheel pulls left above 50 mph" not "pulls." Technicians need enough detail to reproduce the issue.
History checked. Look at prior ROs. Has this customer had the same complaint before? Did a previous repair fail? Is there a warranty campaign or technical service bulletin that applies? A $150 TSB fix beats a $1,800 diagnostic.
Diagnostic approach decided. Don't hand a technician a vague complaint and a blank diagnostic code. Decide: Is this a direct repair (you already know it's a belt) or a diagnostic (you need to find the root cause)? How many hours are you authorizing for diagnosis?
Authorization level confirmed. If the repair will exceed the customer's verbal approval or warranty coverage, flag it now. Don't let a technician spend 6 hours on a job that will never get authorized.
Parts availability checked. Before the RO goes to the bay, confirm critical parts are in stock or on order. A typical $3,400 timing belt job on a 2017 Pilot at 105,000 miles is straightforward—but only if the belt and seals are on the shelf. If you're waiting on parts, the customer needs to know the timeline.
Customer contact preference noted. Phone call, text, email? Do they want daily updates or only when the job is done? Respecting this saves you callbacks and keeps CSI scores high.

How do you fill out the customer complaint section properly?

This is where most ROs fall apart. A rushed write-up here creates a cascade of problems downstream.

The customer complaint is not a summary,it's a transcript. When a customer says their car is making a grinding noise, ask follow-up questions:

When did it start? (This week? Last month?)
When does it happen? (Cold start only? Every time? Only when turning?)
How loud? (Barely noticeable or can't ignore it?)
Does it get worse or better? (Worse with miles, better as it warms up?)

Write those answers on the RO. A technician who reads "customer says grinding noise, happens on cold start, gets better after 2 minutes" can actually diagnose the problem. One who reads "grinding noise" is guessing.

If the customer can't describe the symptom clearly, ride along. A 10-minute test drive with the customer and the service advisor,or better yet, with the technician who will work on the car,is worth an hour of back-and-forth guessing. You hear the noise, you feel the vibration, you see exactly when it happens. Problem solved.

What vehicle condition checks prevent comeback complaints?

Documenting the car's condition on arrival is not paperwork theater. It's insurance and evidence.

Before the RO is written, have someone (the service advisor or a lot attendant) walk around the vehicle with the customer and note:

Exterior: Any dents, scratches, paint chips, rust, hail damage, missing trim pieces. Take photos if your DMS supports it.
Interior: Stains on seats, rips in upholstery, broken trim, cracked glass, odors (pet, smoke, mold).
Tires: Tread depth, uneven wear, sidewall damage, current pressure.
Fluid leaks: Any puddles under the car or stains in the engine bay.
Mileage: Record the odometer reading. Non-negotiable.
Fuel level: Note whether you're delivering the car on empty or full. Some shops have a policy (e.g., "we return all cars at the fuel level they arrived at").

This takes 3 minutes. A customer dispute about a scratch they claim you made takes 40 minutes and tanks CSI. Document first, defend later.

How do you match the complaint to the right service code?

Service codes exist so you can track labor hours, parts usage, and customer trends. But they only work if you use them correctly.

A common mistake: bundling multiple problems under one code. If a customer brings in a car for an oil change, a tire rotation, and a brake inspection, those are three separate ROs or three separate line items on one RO. Each one gets its own code and labor hours. Why? Because when you analyze hours per RO or parts per code, you need accurate data. If you're mixing jobs, your reporting is garbage.

Match the code to what's actually being done:

Warranty work: Use the warranty code, not a regular maintenance code. Your warranty department needs to see the real numbers.
Recalls and TSBs: Use the recall/TSB code. This tracks your compliance and helps you spot patterns.
Diagnostic labor: Separate it from the repair. A customer needs to know you spent 1.2 hours diagnosing before you charge them for the actual fix.
Preventive maintenance: Keep it distinct from repair work. Your reporting should show maintenance separately so you can track attach rates.

One strong opinion: if your DMS doesn't make it easy to use the right codes, push back. A system that's hard to use gets circumvented, and circumvented systems produce useless data. Dealer1 Solutions was built with code clarity in mind because bad codes kill your ability to manage.

What authorization steps prevent job hold-ups?

Authorization delays are a silent killer of throughput. A job sits in the bay waiting for approval while the technician moves on to something else, your CSI clock keeps ticking, and the customer gets a call asking for permission.

Before the RO hits the work queue:

Confirm what the customer has already approved. Did they call ahead? Did they mention a budget? Did they authorize a full diagnostic or just a inspection? Document it on the RO.
Set a clear authorization threshold. Many shops say "anything under $500, tech can proceed; over $500, call the customer." Make this explicit. Technicians need to know the rule.
If a repair will exceed the customer's budget, call them before the work starts. Not after. A 15-minute call upfront saves a 45-minute argument later.
For warranty work, confirm coverage before the RO is written. Check the warranty module, verify deductibles, note any exclusions. If the customer will owe a deductible, tell them now.
For insurance work, get the claim number and adjuster approval in writing. Don't start a repair on a promise of payment.

How do you structure the RO so technicians actually follow it?

A repair order is a contract between the service manager and the technician. It has to be clear.

Use your DMS to make the RO readable. This is the kind of workflow Dealer1 Solutions was built to handle,line-by-line clarity so nothing gets missed. But even in a basic system:

Put the customer complaint at the top in plain language.
List what needs to happen, in order (diagnostic first, then repair).
Flag any special instructions (use OEM parts, call customer before starting, this is a warranty case).
Note which parts are on hand and which are on order.
Include the authorization limit and approval status.
Set an expected completion time. Not a guess,a real target based on the job and the bay schedule.

If the RO is a wall of text or scattered across three screens, technicians will miss something. Make it scannable.

What's the final review step before an RO goes to the bay?

The last check is yours. Before that RO leaves the service desk, you should be able to answer these questions in 30 seconds:

Do I know what the customer's actual problem is?
Do I know how much this will cost and has the customer approved it?
Do I have the parts or do I know when they'll arrive?
Is the technician clear on what to do?
Will I be able to reach the customer if I need approval?

If you can't answer all five in 30 seconds, the RO isn't ready. It goes back to the service advisor or the customer.

This sounds rigid, but it's not. It's the minimum standard. Stores that get this right tend to have fewer comebacks, faster cycle times, higher technician efficiency, and better CSI scores. The checklist isn't slowing you down,it's saving time by preventing rework.

Frequently asked questions

Should the service manager or the service advisor write the repair order?

The service advisor takes the initial complaint and begins the RO; the service manager reviews and finalizes it before it goes to the bay. This division of labor works best because the advisor stays focused on the customer interaction while the manager ensures accuracy and completeness. In smaller shops, one person may do both, but the checklist stays the same.

What should you do if a customer disputes the vehicle condition notes later?

This is exactly why you document condition on arrival. If a customer claims you scratched their bumper and your RO shows the scratch was already there, you have proof. Photos are even better. Without documentation, it's your word against theirs, and you'll lose the dispute and the customer.

How detailed should the customer complaint section be?

Detailed enough that a technician who wasn't present can understand the symptom and attempt to reproduce it. "Grinding noise on cold start, goes away after 2 minutes" is good. "Noise" is not. If you can't describe it in 2–3 sentences, you need to ride along or have the technician test drive with the customer before work begins.

Can you combine multiple service codes on one repair order?

Yes, but use separate line items for each service code. An oil change, tire rotation, and brake inspection should each have their own code and labor hours on the same RO. This keeps your reporting accurate and lets you track which services drive profitability and customer attachment.

What's the best way to handle a repair that might exceed the customer's budget?

Call the customer before the technician starts work. Explain what you found, what it will cost, and what the options are (repair fully, repair partially, defer). A customer is always happier when they're involved in the decision before the job begins, not surprised by the bill afterward.

Should you write a new repair order or add to an existing one if a customer brings the car back for the same issue?

Create a separate RO that references the original RO number. This preserves a clear history and shows that the first repair didn't solve the problem. It also protects you if a warranty claim or customer complaint arises,you have documentation of both visits.