Clearing Codes, Running Monitors, and Verifying the Repair

The short version — Clearing codes is the last step after the repair is made, not a shortcut to make a light go off, and the job isn't done until you've watched the readiness monitors go from "not ready" back to "complete" with no code returning.

Why order matters: fix first, clear last

Clearing DTCs wipes out stored fault codes and freeze-frame data from the PCM/ECM, and it also resets the associated readiness monitors back to "not ready." That's exactly why this step only belongs after you've already found and fixed the root cause — never as an early diagnostic move. If you clear codes before you've nailed down the cause, you've just thrown away your best evidence and you're diagnosing blind.

Think about what freeze-frame data is for: it's a snapshot of engine conditions the instant the fault set. That freeze-frame data disappears the moment you clear codes, so if you need it for verification or warranty paperwork, record it with the scan tool before you clear anything. Once it's gone, it's gone — there's no getting it back to prove what conditions triggered the original fault.

What "verify the repair" actually means

The whole point of this task is confirming the repair actually solved the problem — meaning the original fault doesn't come back — and confirming the OBD II monitors have finished running their internal test routines. Both parts matter. A code not returning feels like success, but if the readiness monitors haven't completed, you haven't actually proven the repair under real operating conditions yet.

This isn't just good practice — it's often a legal requirement. In jurisdictions that check readiness status as part of an OBD II emissions inspection, the vehicle cannot pass unless the required monitors show complete/ready. So "verify repair" and "pass inspection" are tied directly together.

To verify, use the scan tool to check three things:

• The original DTC has not returned.
• Monitor status has changed from "not ready"/"incomplete" to "ready"/"complete."
• No new or pending codes have appeared — either from the repair itself or from whatever method you used to clear codes (battery disconnect, scan tool clear command, etc.).

The monitors themselves

OBD II readiness monitors are a fixed set of internal self-tests — think catalyst, oxygen sensor, oxygen sensor heater, EVAP, EGR, secondary air, misfire, fuel system, and comprehensive component monitors as examples. Each one runs only when its own specific enable criteria are met — meaning you can't force most of them, you have to drive conditions that satisfy the trigger for that particular test.

Here's the part that trips people up: clearing codes, or losing PCM memory some other way, sets all or most of these monitors back to "not ready." They stay that way until each one independently completes its own test sequence on its own — the tool doesn't restore "ready" status by itself, and neither does the code-clear command. The vehicle has to actually be driven through the right conditions for each monitor to run and report back.

The mistake that costs you the most

The single biggest error in this whole task is clearing codes too soon — before repair verification is complete. Here's why it bites you:

• It erases the freeze-frame data you needed to confirm you fixed the actual problem.
• If the fault is intermittent, and you clear codes and send the car out the door before the relevant monitor gets a chance to re-run, the fault can slip through undetected. The monitor needs a real shot at completing under the right conditions before you can call the repair verified — jump the gun and you might be handing back a vehicle that isn't actually fixed.

The safe sequence is always: diagnose → repair → record freeze frame/monitor status if needed → clear codes → drive to satisfy monitor enable criteria → confirm monitors ready and no code return.

Check yourself

Question: A technician wants to compare "before and after" conditions to prove a repair fixed an intermittent misfire. What should they do with the scan tool before clearing codes, and why?

They should record the freeze-frame data and monitor status before clearing anything, because clearing DTCs erases freeze-frame data from the PCM/ECM permanently — there's no way to retrieve it afterward, and it may be needed for verification or warranty documentation.

Question: Technician A says clearing codes is a good first step in diagnosing a hard-to-find fault, because it lets you see if the code comes right back. Technician B says codes should only be cleared after the root cause has been diagnosed and repaired. Who is right?

Technician B is right. Clearing codes resets readiness monitors to "not ready" and destroys freeze-frame data, so it should only be done after the repair is complete — not used as an early troubleshooting tool. Technician A's approach throws away diagnostic evidence and doesn't actually help find the root cause.

Question: After a repair, the technician clears codes, drives the vehicle around the block once, and tells the customer it's ready for state inspection. What's the risk here?

The readiness monitors were reset to "not ready" when codes were cleared, and each monitor only completes when its own enable criteria are satisfied during driving — one trip around the block usually isn't enough. If the monitors haven't finished, the vehicle will fail an OBD II inspection that checks readiness status, and an intermittent fault might not have had a chance to be caught by its monitor yet.