The First 90 Seconds of a Service Write-Up

Monday morning, 7:28 a.m. The drive is already stacking up. One customer is late for work, one has a warning light on, and one wants “just an oil change” but also mentions a noise that “started a while back.” The advisor has a phone tucked under one ear, a printer spitting out yesterday’s leftovers, and a porter asking where to park a waiter.

That is exactly when the whole day gets decided.

Not by the scan tool. Not by the technician. Not by the parts department. It starts in the first 90 seconds of the write-up. That short stretch is where the customer decides whether you’re listening, the advisor decides whether to slow down enough to get it right, and the repair order either becomes a clean path to the fix or a paper trail full of holes.

In a small service department, you do not have much room for sloppiness. One weak write-up can create a comeback, a parts delay, a technician argument, a cashier problem, and a customer who tells everybody in town you “never fixed the car.” That is why the first 90 seconds matter more than most stores admit.

The write-up is not paperwork

A lot of advisors treat the write-up like a form to get through so the “real work” can begin. That is backward. The write-up is the handoff that starts the repair.

If the concern is vague, the technician starts with guesswork. If the promised time is loose, the customer gets irritated. If the contact information is wrong, approvals get delayed. If the advisor never confirms transportation, price expectations, or warning lights, the day starts drifting before the car even reaches the shop.

A good write-up does three things fast:

• It makes the customer feel heard.
• It gives the technician something useful.
• It creates a record of what was requested, observed, and authorized.

That is not glamorous, but it is the difference between a smooth day and one long apology.

What a customer hears in the first minute

Customers are listening for more than words. They are trying to answer a few basic questions right away:

• Are these people organized?
• Is anybody actually listening to my problem?
• Do they care what I need today?
• Am I going to get surprised later?

The advisor does not need a fancy script. But tone, pace, eye contact, and a few consistent questions go a long way.

A solid opening sounds simple:

“Good morning. Tell me what brought you in today.”

Then be quiet long enough to hear the answer.

Too many write-ups get derailed because the advisor starts diagnosing before the customer finishes talking. Or worse, the advisor translates too early: “So it just needs a battery,” when the customer actually said the car died twice, the dash flickered, and it only happens after rain.

Your first job is not to be the hero. Your first job is to capture the concern clearly.

The best advisors slow down just enough

There is a difference between moving quickly and rushing. Good advisors know how to slow down for the right ten seconds.

They confirm the customer concern in plain language. They ask when the issue happens. They repeat back the main complaint. They walk around the vehicle if needed. They note visible damage. They verify mileage, warning lights, waiting status, and best contact number. They set a realistic next step instead of making a promise they cannot keep.

That might sound basic, because it is. Basic is what works.

Here are a few habits that tighten up the first 90 seconds:

• Write the customer’s concern as stated, then add clarifying details.
• Separate “customer states” from “shop recommends.”
• Confirm how and when the advisor will update the customer.
• Ask one transportation question every time: wait, ride, shuttle, or drop-off.
• Never promise completion before checking capacity.
• If the concern is a noise, vibration, or intermittent issue, pin down conditions: when, where, speed, hot or cold, turning or braking.

None of that takes long. But every bit of it saves time later.

Process → Procedure → Reference in the service lane

This is a good place to use the CBS framework.

Process: Decide how your service department will handle the first 90 seconds of every write-up.

That means management agrees on what must happen every time, no matter who is at the desk. In a small store, this matters even more because one person’s shortcuts become everybody’s headaches.

At minimum, the process should cover:

• Greeting the customer promptly
• Capturing the primary concern accurately
• Confirming vehicle, mileage, and contact information
• Establishing waiter/drop-off/transportation status
• Setting the next communication point
• Recording anything that protects the store and helps the technician

Procedure: Write the steps down so an advisor can follow them the same way every time.

A simple procedure might look like this:

1. Greet the customer by name if available.
2. Ask why they came in today and let them finish.
3. Repeat the concern back in plain language.
4. Ask follow-up questions to identify when and how the issue occurs.
5. Verify mileage, warning lights, and current vehicle condition.
6. Confirm contact number and transportation needs.
7. Set expectations for diagnosis or next update.
8. Review the repair order before the customer leaves.

That is not a training manual. It is a usable lane procedure.

Reference: Keep the records and forms that prove the process happened.

For this topic, your references may include:

• Repair order with clearly written customer concern
• Advisor write-up checklist
• Walk-around or vehicle condition form
• Contact and transportation confirmation notes
• Time-stamped customer update records

If it is not written down, the store ends up arguing from memory. Memory is a poor management system.

Start small and clean up one write-up at a time

You do not need to redesign your whole service lane by Friday. Start with one standard for every advisor: the first 90 seconds must produce a clear concern, verified contact information, transportation status, and a realistic expectation for the next update.

Print a one-page checklist. Listen to three live write-ups this week. Review a handful of repair orders for vague language like “check and advise” or “customer says noise.” Coach those up. Tighten the basics before you chase anything fancy.

Small service departments win with consistency, not theatrics. A clean write-up calms the customer, helps the technician, protects the store, and makes the whole day run better. All that, in the first 90 seconds.

That is a good trade.

Process → Procedure → Reference — Centennial Business Systems | Centennial Dealership Operating System