Fault Codes & Diagnostics

Clearing Fault Codes vs Fixing the Root Cause: What Actually Stops Comebacks

19 November 2026 3 min read

The light’s off, the invoice says “fault cleared,” and the customer’s back in three days with the same light on. This is one of the most common comebacks in the trade, and it happens because clearing a code was mistaken for fixing whatever caused it.

A code is a symptom, not a diagnosis

Clearing a stored code doesn’t repair anything, it just erases the ECU’s memory of having seen the fault. If the underlying cause is still there, a leaking injector, a corroded connector, a worn sensor, the ECU detects it again the next time the relevant monitor runs, and the light comes back. Customers often assume the reset itself was the repair, and it’s worth being clear with them that clearing codes is a diagnostic step, not a fix, unless the actual cause has genuinely been addressed first.

When clearing codes is legitimately part of the job

  • After a genuine repair, replacing the faulty part, fixing the wiring, correcting the file, clearing the code and running the readiness monitors is the correct final step, confirming the fix worked rather than just hiding the symptom.
  • After a battery disconnect or ECU replacement, where codes may have set purely because of the disconnection itself and don’t reflect an ongoing fault.
  • Before a pre-purchase inspection or an MOT/TÜV/CT test, only once you’ve confirmed there’s no unresolved fault, since clearing codes purely to pass a test without fixing anything is both dishonest and, depending on jurisdiction, a compliance risk for the workshop doing it.

When it’s just delaying the comeback

If a code is cleared without any repair, any parts replaced, any wiring fixed, purely to get the light off and the car out the door, the fault is still there and will resurface, often at a worse moment for the customer than the one that first raised it. This is common under time pressure, a customer waiting in reception, a busy ramp schedule, but it costs the workshop more in the long run through comebacks, warranty claims and reputation than the time saved that day.

Readiness monitors and why they matter

After any code is cleared, the ECU resets its readiness monitors, the internal checks for things like catalyst efficiency, EVAP system integrity, oxygen sensor performance, and these need a specific drive cycle to run and report “ready” again. A car sent for an emissions or roadworthiness test with monitors still “not ready” can fail on that basis alone, regardless of whether the original fault was fixed. If you’ve cleared codes as part of a genuine repair, tell the customer they may need a proper drive cycle, cold start, mixed speeds, before certain monitors complete.

A quick checklist before clearing anything

  • Has the actual cause been identified and fixed, not just guessed at?
  • Has freeze frame and live data been recorded in case the fault returns?
  • Does the customer understand what was actually repaired, versus what was reset?
  • Will readiness monitors need a specific drive cycle before a test or inspection?

Say what you actually did

It’s also worth explaining to the customer, in plain terms, what was actually done, since “we cleared the code” and “we fixed the leaking injector that was causing the code” sound similar but mean very different things for how confident anyone should be that the car won’t be back next week. A short line on the invoice describing the actual repair, not just “fault rectified,” protects the workshop as much as it informs the customer if the same fault reappears later for an unrelated reason.

A repair that includes clearing codes as the last step, not the only step, is the difference between a job that sticks and one that boomerangs back next week. For the diagnostic groundwork that should happen before any code gets cleared, see our approach to engine management light diagnosis in the Fault Codes & Diagnostics category, and if a software fault turns out to be the root cause, the ECU Guides category covers getting it corrected properly.

Keep reading

More ECU guides