Your Progress
0 of 7 lessons complete (0%)
Lesson 7 · RO Discipline · 7 min read

Handoff and Follow-Up

A BG recommendation is only as strong as the handoff around it. If the tech note is vague, the advisor presentation is loose, or the declined service is not documented, the next visit starts from zero.

Lesson Objective

Learn the technician-to-advisor handoff, RO documentation, and follow-up habits that turn BG maintenance into a consistent process.

The Clean Handoff

RoleWhat they ownExample
Technician Clear finding, test result, and system context. "Brake fluid dark, copper strip positive. Recommend BG brake fluid service with pad replacement."
Advisor Customer translation and menu placement. "Since we are doing pads, I recommend handling the fluid side too. I put that in Better."
Manager Coaching consistency and audit trail. Reviews whether BG recommendations are tied to evidence, not thrown on every RO.

Document the Reason, Not Just the Service

A declined BG service should not read like a mystery six months later. Use notes that explain why it was recommended.

Strong Declined Service Note

"Customer declined BG cooling system service today. Coolant tested acidic and vehicle is over 30k since last coolant exchange. Review again next service or if temperature concern returns."

Weak Declined Service Note

"Declined coolant flush." No trigger, no urgency level, no next step.

Follow-Up Windows

Advisor Self-Audit

The Dyer Standard

Every BG recommendation should survive the next advisor picking up the RO. If the reason is clear, the follow-up is easy.