Comeback work: the work no one pays for.

Count it before disputing it

Comeback work is seldom in the figures, as it’s rarely invoiced and thus rarely documented in accessible reports.

This means most garages are discussing an issue of unknown scale. The solution is simple: record every return visit linked to prior work, noting hours spent and parts used, regardless of charges.

A quarter of that data usually resolves the issue. Comebacks tend to cluster in a few job types, making them fixable rather than a widespread standard-of-work problem.

The common causes are tediously specific.

When the log exists, a few causes account for most of it.

• A part that wasn’t the cause, fitted because the diagnosis halted at the first plausible answer.
• A related item not replaced simultaneously, which then failed and appeared to be the same fault.
• Something disturbed during the job and not reassembled properly, which customers find most damaging to trust.
• A low-quality part selected for cost on a job where it was the wrong choice.
• The customer was never informed what to expect, so normal behaviour post-repair appears as a failure.

That last one deserves separation, as it’s not a technical comeback and can be resolved with a sentence rather than a process.

Diagnose to a cause, not a plausible part.

The costliest comebacks arise from replacing something reasonable that wasn’t actually at fault.

It occurs under time pressure, and it seems rational: the part is a common cause, it’s in stock, and the alternative is more diagnostic time the customer may not wish to pay for. The cost appears later, as a second visit, a second part, and a customer now paying twice for one fault.

The defence is charging properly for diagnosis rather than absorbing it. A workshop that gives away diagnostic time is under pressure to guess, and guessing is what produces comebacks.

Set expectations at handover.

A significant share of returns are vehicles with no faults.

New brakes need bedding in, a replaced part may emit a smell when first heated, and a fault that masked another means the second becomes apparent later. None of this is a failure, but it appears so to a customer who was not informed.

Thirty seconds at handover clears most of these issues. It also helps distinguish genuine comebacks, as the customer describing a problem has already ruled out the usual issues you warned them about.

Address the genuine ones promptly and generously.

When a comeback is genuine, disputing it costs more than resolving it.

The cost of rework is often less than the cost of a customer sharing their experience, and a workshop that visibly rectifies its mistakes often gains more trust than one that never errs.

This requires a pre-agreed rule, so front-of-house doesn’t need to negotiate: comebacks take priority in the schedule, they are diagnosed by someone other than the original technician where possible, and the customer isn’t asked to justify themselves.

Incorporate it into work processes.

A comeback log that goes unread is merely a longer record of the same issue.

Quarterly reviews, focusing on trends rather than individual cases, typically yield two or three specific changes: a job type needing more time in the schedule, a part that shouldn’t be purchased on price, or a step that should be on a checklist rather than in someone’s memory.

That's the full return on measuring it. The point was never the figure, but knowing which two or three things to adjust.