OBD-II primarily monitors emissions-related systems, but some monitored faults also affect starting, acceleration, fuel use, idle quality, or engine power. Other faults may illuminate the check-engine light without a noticeable change in how the vehicle drives.
Document both tracks
On the emissions track, preserve the code, readiness status, permanent-code status, failed Smog Check result, and emissions-warranty information. On the drivability track, describe any hesitation, misfire, stall, odor, reduced power, hard start, or fuel-consumption change. Do not add a symptom that was not experienced merely because it is commonly associated with a code.
California BAR states that a vehicle will not pass a Smog Check with the check-engine light on. BAR also explains how readiness monitors and permanent codes are evaluated. A failed inspection is important evidence of the vehicle’s state at that time, but it does not automatically decide warranty responsibility or a lemon-law remedy.
- Official Vehicle Inspection Report and test date.
- Code and monitor status before repair.
- Any manufacturer emissions-warranty booklet or coverage decision.
- Separate list of drivability symptoms actually observed.
- Post-repair test and monitor result.
Recall and complaint data are context, not a diagnosis
NHTSA lets drivers search recalls, investigations, complaints, and manufacturer communications by vehicle details. These materials may identify a safety campaign or diagnostic reference worth discussing with the facility.
They should be matched to the exact year, model, configuration, VIN eligibility, and symptom. Another owner’s complaint cannot establish what caused the warning in a different vehicle.
A record-first next step
Keep the Smog Check record, warranty decision, and repair order together while documenting drivability symptoms in a separate factual column. 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 Smog Check requirements
- California BAR On-Board Diagnostic Test Reference
- NHTSA recall, investigation, and complaint search
- 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 steady or flashing malfunction indicator light 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 catalyst, EVAP, and misfire monitoring, along with part numbers, software versions, road-test notes, and cannot-duplicate language. Preserve warning photographs with date and mileage 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.