Test Drive Documentation Script for Technicians: Word-for-Word Language to Use

A solid test drive documentation script should follow this sequence: greet the customer, confirm the vehicle and mileage, describe what you're checking and why, perform the inspection while narrating observations, take photos of odometer and any concerns, and close with a clear summary that ties findings to next steps. Written-out language prevents rushed notes, keeps the RO clean, and gives your service advisor the exact material they need for the estimate conversation.

Why Test Drive Documentation Matters More Than You Think

You've probably heard a technician say something like "Yeah, it pulls a little to the left" and leave it at that. Two weeks later, the customer comes back saying the alignment issue was never explained, the estimate seemed random, and now there's friction over price. This happens constantly, and it's almost always a documentation gap—not a diagnostic gap.

The dealers who get this right treat the test drive like a mini-presentation. You're not just collecting data. You're building a paper trail (or digital trail) that proves what you found, why it matters, and what fixing it costs. When your write-up is vague, the service advisor has to guess, the customer has to ask clarifying questions, and your CSI scores drop.

Here's the pattern we see: dealerships with strong test drive documentation have fewer comeback complaints, faster estimate approvals, and technicians who spend less time re-explaining things. A typical scenario: a customer brings in a 2015 F-150 with 127,000 miles complaining about rough idle. A sloppy tech notes "rough idle—PO scan." A good tech notes "Rough idle at cold start; idles 800 RPM, drops to 650 when AC kicks on, DTCs P0300 and P0171 stored; confirmed with customer listening to engine during test drive." That second note sells the job.

Your job is to be the customer's translator. The customer doesn't speak "intake valve carbon deposit." But they do understand "Your engine's struggling to idle smoothly because it's not getting the right fuel mix,that's why we recommend the fuel system cleaning."

The Pre-Drive Script: Setting Up Clear Documentation

Before you even turn the key, nail the setup. This is where you prevent half the confusion that derails a good diagnosis.

Greeting and Vehicle Confirmation

Start with this exact sequence:

• "Good morning/afternoon. I'm [Your Name], the technician who'll be test driving your vehicle today. Before we head out, let me confirm a couple of things so I make sure we're checking the right stuff."
• "This is the [year, make, model], correct? And the current mileage shows [read from odometer]. Does that match what you're seeing?"
• "Perfect. So today you mentioned [repeat their concern,rough idle, pulling to one side, noise from under the hood, whatever]. Are there any other concerns, or is that the main thing you want us to focus on?"

This language takes 90 seconds and does three things: it builds customer confidence (you're thorough), it anchors the complaint in writing (no "they said something about a noise"), and it gives you permission to focus your inspection. If the customer says "Oh, and also the air conditioning isn't as cold as it used to be," you now have two documented concerns to investigate.

Explaining Your Process

Many technicians skip this. Don't.

"Here's what I'm going to do. I'll drive the vehicle under normal conditions first,city speeds, some highway if we can,and I'll listen and feel for the issue you described. If I can reproduce the problem, I'll note exactly when it happens and what conditions trigger it. I'll also check the basics like tire pressure and fluid levels, and I might plug in a diagnostic scanner if needed. I'll take some photos of the odometer and any concerns, and then I'll have a full write-up for your service advisor so you know exactly what we found and what it'll cost to fix. Does that sound good?"

This sets expectations. The customer knows you're not just joy-riding. They know you're documenting. And they know they'll get a clear answer, not a guessing game.

The During-Drive Script: Narrating Your Findings

This is where most technicians lose discipline. You've got the customer in the truck with you. You feel the vibration or hear the noise. And then you just... drive. Instead, narrate what you're observing.

Cold Start Observations

As soon as you start the engine, say this out loud (or say it to yourself if the customer isn't riding along, then document immediately after):

"Engine cranks normally. Startup is [smooth / rough / delayed]. Idle RPM is [reading]. Engine sounds [normal / rough / knocking]. Any abnormal smells? [Check]. Any warning lights on the dash? [Check]. AC compressor engaging? [Check]."

If you're alone, jot these observations on a notepad or your phone the second you're back inside. If the customer rode along, you've just walked them through what you found,no surprises later.

City Driving Portion

As you accelerate and brake through normal traffic:

"Transmission shifts smoothly through all gears,no hesitation, no harsh engagement. Steering feels [responsive / sluggish / pulling left/right]. Brakes engage smoothly,no noise, no pulsation. Suspension feels [tight / loose / clunking over bumps]. At this speed, the concern you mentioned [is / is not] present. Let me describe what I'm hearing/feeling [describe specifically]."

The key word is specifically. Not "the steering is weird." Instead: "The steering pulls about a quarter-turn to the left when cruising at 45 mph, but straightens out when I brake. This suggests a suspension or alignment issue on the driver's side."

Highway Portion (If Applicable)

"At 60 mph, the steering is stable, no vibration in the wheel. Engine sounds consistent, no knocking or pinging under load. No unusual noises from underneath. AC temperature is consistent. This confirms the pulling issue you mentioned is primarily at moderate city speeds, not highway speeds."

Again: tie every observation back to the customer's original complaint. This is how you build credibility and a clear narrative.

Reproducing the Problem

If you can trigger the issue, narrate that process:

"Cold engine, idling at a stoplight. Turning on the AC now,I can see the RPM drop from 850 to 650, and the rough idle becomes very noticeable. Customer can hear it too. This behavior is consistent with a fuel system problem or intake air leak, which is causing the engine to struggle when the AC load kicks in."

You've just documented: the condition (cold idle, AC on), the measurable result (RPM drop of 200), the symptom (rough idle), and your preliminary diagnosis. That's the anatomy of a solid RO note.

Photo Documentation: The Visual Proof

A picture prevents 100 bad conversations. Take these photos during or immediately after the test drive:

• Odometer , every single RO. This is your mileage baseline and timestamp.
• Warning lights on the dash , if any are illuminated, photograph the cluster clearly so there's no debate later about what was lit.
• Tire tread depth , use a penny or a tread-depth gauge; a photo with the gauge in frame is gold for the estimate conversation. "See here, the penny goes in past the hair on Lincoln's head,that means the tread's below 2/32, so we recommend replacement."
• Fluid levels , coolant, brake fluid, power steering. One photo of the dipstick or fluid reservoir with the level visible.
• Any visible wear or damage , cracks in belts, leaking fluids, worn pads, cracked hoses. Close-up photos from multiple angles.
• The odometer again at the end of the test drive , proves you actually drove the vehicle and how far.

Attach these to the RO (or to your notes in the DMS). When the estimate goes to the customer, the service advisor can show them: "Here's your odometer at the start. Here's your tire tread,see how shallow it is? Here's what that looks like compared to a good tire." That's not pressure selling. That's clarity.

The Post-Drive Documentation Script

The moment you're back in the service bay, write this down or dictate it into your phone before you forget:

The Summary Format

"Test drive completed at [mileage]. Vehicle exhibits [specific symptom] under [specific conditions]. Symptom is [reproducible / intermittent / confirmed by customer]. Likely cause is [your assessment based on what you observed]. Recommend [diagnostic step or repair]. Estimated labor/parts [if you have a ballpark]. Customer awareness: [what the customer heard/felt/saw during the drive]."

Real Example Script

Let's say you test drove a 2017 Honda Pilot with 105,000 miles, customer complaint: "rough idle."

"Test drive completed at 105,247 miles. Cold start idle is rough, RPM fluctuates between 650 and 900. Idles smoother once warmed up. AC engagement causes immediate RPM drop and noticeable surging. No DTCs stored currently, but this pattern suggests fuel trim issue,either a vacuum leak, fuel injector problem, or intake carbon buildup. Recommend fuel injector cleaning service ($180 labor, $60 product) as first step; if issue persists, recommend fuel pressure test and intake cleaning ($340 labor). Customer rode along on test drive and confirmed roughness, especially with AC on. Photos attached: odometer, fuel trim data, and engine bay."

Now your service advisor has everything they need. The estimate isn't a guess. The customer knows exactly what's wrong and why the recommended work makes sense.

Common Documentation Mistakes to Avoid

Don't write like this:

• "Runs rough" , rough when? Cold or warm? City or highway? What RPM? What does rough sound like?
• "Pulls to the left" , under braking? Cruising? How much? At what speed?
• "Noises underneath" , what kind of noise? Metal grinding? Rubber squeaking? Clunking? When does it happen?
• "Suspension is loose" , loose where? Clunking over bumps? Floating on curves? Knocking sound?

The pattern is clear: vague language creates confusion. Specific language creates clarity and confidence.

Also avoid these killers:

• Blaming the customer ("Customer wasn't specific about the problem") , your job is to be more specific than they were.
• Guessing without verifying ("Probably a transmission issue") , you don't know until you verify. Say "needs diagnostic."
• Rushing the drive ("Drove for five minutes, seemed fine") , a proper test drive takes 15–20 minutes minimum.
• Not confirming findings with the customer ("I heard something, they didn't") , if the customer can't hear it, the concern is different than what they reported.

How to Handle Customer Ride-Alongs

Sometimes the customer wants to ride along. This is actually a gift if you use the script right.

"I appreciate you coming with me,this way you can hear exactly what I'm hearing and confirm I've nailed the issue. Fair warning, I'm going to narrate what I'm observing out loud as we drive. That might seem like I'm thinking out loud, but it helps me stay thorough and gives you confidence in the diagnosis. Sound good?"

Then drive the script. The customer becomes a witness to your thoroughness. They'll say things like "Yes, that's exactly the noise I've been hearing!" or "It does that every time!" Those affirmations are documentation gold. Write them down.

"Customer confirmed rough idle occurs immediately upon cold start and worsens when AC compressor engages. Customer has experienced this for approximately two weeks. States it happens every morning. Has not noticed it during highway driving."

That level of detail,frequency, duration, when it started,transforms a vague complaint into a diagnosed condition.

Integrating Your Documentation Into the Workflow

The best documentation in the world doesn't help if it stays in your notebook. Get it into the DMS, the RO, or wherever your service team pulls estimates from. This is the kind of workflow Dealer1 Solutions was built to handle,your test drive notes flow directly into the estimate builder, so the service advisor doesn't have to re-interpret your scribbles.

If you're using a paper RO, be legible. Use a pen (not pencil). Leave space for the service advisor to add their own notes. If you're using a digital system, take your time typing. A rushed, typo-filled note reads like sloppy work.

Make it a habit: test drive → immediate documentation → service advisor review → customer estimate. No gaps. No guessing. No callbacks for clarification.

Frequently asked questions

Should I always take the customer on the test drive?

No. If you need to push the vehicle hard to diagnose a noise or feel a pulling issue, you might prefer to go alone for safety and focus. But if the customer's complaint is subjective (rough idle, transmission hesitation, squeaks), a ride-along builds credibility and gives you real-time confirmation. Offer the option; don't force it.

What if I can't reproduce the customer's complaint?

Document that honestly: "Test drive completed at [mileage]. Vehicle operates normally under all driving conditions. Complaint of rough idle not reproduced. Recommend diagnostic scan to check for stored or pending fault codes; if no codes present, this may be an intermittent electrical issue or sensor problem requiring further investigation." This isn't a failure; it's clarity. The service advisor now knows to suggest a diagnostic rather than guess at a repair.

How long should a test drive actually take?

Minimum 15 minutes if the vehicle is running normally. Longer if you're troubleshooting noise or performance issues. A quick five-minute loop around the lot is worthless. You need varied conditions: cold start, city speeds, highway, acceleration, braking, turning, AC on/off, radio off (so you can hear the engine). Budget the time and communicate it to the service advisor upfront so nobody's looking at their watch while you're diagnosing.

What if the diagnostic scanner finds codes but I don't feel any symptoms?

Document both: "Test drive completed,vehicle drives smoothly, no abnormal noises or performance issues noted. However, diagnostic scan reveals pending code P0171 (fuel system too lean). This code can be intermittent and may indicate early fuel pump wear or a vacuum leak. Recommend fuel system diagnostic ($95) before recommending expensive repairs." You're protecting the customer and yourself by being thorough.

How do I document safety concerns I find during the drive?

Clearly and urgently. "SAFETY CONCERN: Brake pulsation felt at full stop. Recommend immediate brake inspection before releasing vehicle to customer." Note this in the RO, flag it for the service advisor verbally, and follow up in writing. Don't release a vehicle with known safety issues; that's liability you don't want.

What should I do if the customer disagrees with my diagnosis?

Stay calm and reference your documentation. "I understand your concern. Here's what I observed during the test drive: the transmission delayed two seconds before engaging into drive, which is consistent with transmission fluid that's low or degraded. Here's the fluid color and level I photographed. Here's the diagnostic scan result showing a code for transmission pressure. This isn't a guess,three different observations point to the same issue. Would you like me to walk you through it?"

Your documentation is the bridge between what you observe and what the customer understands. Get it right, and you're not just a technician,you're the expert who explains the truck's problem in plain language. That reputation is worth more than you think.