Clearing codes may be a normal step after diagnosis or repair, but it changes the data available to the next technician. The goal is not to prevent legitimate service; it is to make sure the condition found before the reset remains documented.
Capture the pre-repair state
Ask the service facility to record all codes and relevant diagnostic results in the repair order before clearing. When available, request the scan report showing pending, confirmed, and permanent codes, MIL status, readiness monitors, freeze-frame values, and vehicle identification. A consumer scan screenshot can supplement but should not replace the facility’s diagnosis.
If the warning is visible before drop-off, photograph it and the odometer while safely parked. Preserve the appointment message describing the symptom and confirm that the intake repair order includes the same concern.
- Dashboard warning and mileage photograph.
- Full scan report with code state and timestamp.
- Freeze-frame or failure-record data.
- Readiness-monitor status.
- Battery-disconnect, software-reset, or clearing operation shown on the invoice.
- Post-repair verification and return of the warning.
Understand what a reset does not prove
BAR explains that readiness monitors must rerun after a battery disconnect or certain repairs. A warning that remains off before those monitors complete does not necessarily show that the monitored systems have completed their self-tests. Permanent codes, where supported, follow separate clearing behavior.
Preserving the before-and-after state helps later reviewers understand whether the repair was verified, whether the same condition returned, and how the vehicle behaved between visits.
A record-first next step
Ask for a pre-clear scan printout and a final invoice that states why data was cleared and what verification occurred afterward. Use the topic-specific evidence toolkit to organize the chronology, compare it with the site guide library, and review the primary-source notes. A question about an individual vehicle requires a case-specific review; the case-review page is the appropriate starting point.
Primary sources
- California BAR On-Board Diagnostic Test Reference
- California BAR Smog Check requirements
- California Civil Code section 1793.2
Attorney Advertising. This educational article is not legal advice. A diagnostic code, repair count, symptom, recall, or days-out-of-service figure does not by itself establish a claim. Laws, procedures, records, warranties, and facts vary. No result is promised or guaranteed, and submitting a form does not create an attorney-client relationship.
How to make this record case-specific
Apply this guide to the actual vehicle rather than a general online pattern. For each occurrence, record the date, mileage, operating conditions, exact warning or symptom, and whether the vehicle could be driven safely. A phrase such as pending, confirmed, or permanent diagnostic codes should be tied to what the driver observed and what the repair order says. Do not treat a code, warning, forum report, recall, or service bulletin as a confirmed diagnosis unless the vehicle-specific repair file supports that conclusion.
Then compare the complaint, cause, and correction lines across visits. Look for recorded testing or work involving sensors and monitored emissions systems, along with part numbers, software versions, road-test notes, and cannot-duplicate language. Preserve Smog Check or towing records when applicable with the warranty booklet, purchase or lease documents, dealer communications, photographs, towing or rental records, and a calculation of the days the vehicle was unavailable. These details help an attorney distinguish repeated observations from repeated repair attempts and evaluate the history under the current warranty and California law.
Before requesting a review, check that each final repair order uses accurate complaint language and dates. Keep later messages showing that the condition returned. The purpose is not to force the facts into a preset rule; it is to create a reliable chronology for the individual vehicle. Continue through the defect evidence hubs and manufacturer document hubs for the record paths applicable to persistent check-engine lights and onboard diagnostic faults.