The Dealer Visit Report That Actually Gets Read

Field staff visit dealers, observe, and write a report. The report goes to the dealer, to a regional manager and into a system, and in most networks very little follows from it.

The failure is rarely in the observation. It is that a report describing a situation is a different document from one that produces a change.

Why reports do not produce action

No owner. A finding with no name attached belongs to nobody.

No date. "Should be addressed" is a wish.

Too many findings. A report with fourteen recommendations produces none. The dealer reads it as an assessment rather than as a plan.

Nothing was agreed in the room. A report containing conclusions the dealer first sees in writing is a report they have no commitment to.

No follow-up. If nothing happens between visits, the report is a record of a visit.

And the same findings recur. A report repeating last quarter's items unchanged tells the dealer that nothing follows from it, which is accurate.

What makes one act

Three findings, not fourteen. Chosen by consequence, not by completeness. The rest can be listed as observations, clearly separated.

Agreed before you leave. The most important structural change: the conversation produces the actions, and the report records them. A dealer who agreed to something in the room is committed in a way that a dealer who received a document is not.

A named owner at the dealer, agreed with them, not assigned by you.

A date.

And what support you will provide, if any. A finding that requires something from the manufacturer and does not say so will stall.

Structure

What we agreed — three items, owner, date. First, because it is the only part that matters.

What we looked at — the scope, briefly, so the reader knows what the visit covered.

What we found — observations with evidence, including what is working. A report that is entirely deficiencies is read defensively and acted on less.

What was outstanding from last time, with status. This is the item that makes the process a process rather than a series of visits.

One page, plus detail behind it for anyone who wants it.

Evidence rather than assertion

Numbers where they exist. "Productivity is 61% against a group average of 72%" is arguable in a useful way; "productivity is low" is not. See the three ratios.

Photographs, for physical observations.

Specifics. "Three of eight technicians are certified for this operation, and two are due to expire in Q3" produces action. "Certification levels need attention" does not.

And say where the number came from, because the first response to an unflattering figure is to question it.

Preparing the visit

Most of the quality is decided before arriving.

Look at the data first. Time data, comebacks, warranty rejections, certification status, training completion. Arrive knowing what to ask about rather than discovering it.

Know what was agreed last time, and open with it.

Have two or three hypotheses, and be willing to drop them. A visit that confirms what you decided in advance found nothing.

And ask what they would fix if they could. The dealer usually knows, and the answer is frequently something a manufacturer could help with.

The relationship problem

Worth naming, because it shapes everything.

A field visit is an inspection and a support call at the same time, and those pull in opposite directions.

If the report feeds a scorecard, the dealer manages the visit rather than using it. Findings get minimised, problems get hidden, and the visit produces a good report and no improvement.

Be clear which it is. A support visit whose report goes into a compliance assessment without anyone saying so is the arrangement that destroys trust fastest.

Where both are required, separate them — different visits, or clearly separated sections, with the dealer knowing which is which.

Following up

Something between visits, however brief. A short message at the agreed date asking about the agreed item.

Close items explicitly. Done, or not done and why. An item that quietly disappears teaches that agreement is optional.

And escalate the pattern rather than the incident. One dealer with one outstanding item is a conversation; a region with the same item outstanding everywhere is a network problem and probably not the dealers' fault.

The short version

Three agreed actions with owners and dates, not fourteen findings.

Agree them in the room. The conversation produces the actions; the report records them.

Evidence rather than assertion, with the source of every number.

Open with what was outstanding from last time, or the process is a series of visits.

And be clear whether this is support or assessment — a support visit that quietly feeds a scorecard destroys the thing that makes it useful.

For established quality-management methods relevant to field reporting, see ASQ quality resources.