An intermittent warning may disappear before the appointment or fail to recur during a short road test. A “cannot duplicate” line does not erase what the driver experienced, but it also does not prove a defect. Better records give the facility a reproducible starting point and preserve what was actually reported.
Describe conditions that can be tested
Replace conclusions such as “the computer is bad” with observable details: cold or hot start, outside temperature, fuel level, vehicle speed, grade, stop-and-go traffic, recent charging or refueling, warning color, loss of power, rough running, or unusual odor. Record how long the event lasted and whether restarting changed it.
If it is safe, a timestamped photograph or short video of the cluster and odometer can corroborate timing. Never handle a phone while driving; a passenger can document the display, or the driver can stop safely first.
- Appointment date and mileage when the symptom was reported.
- The driver’s exact complaint as written on the intake repair order.
- Codes in history even when the warning is no longer illuminated.
- Road-test length, test conditions, and diagnostic steps listed by the technician.
- Whether the condition returned and under what conditions.
Preserve each opportunity to repair
California warranty analysis commonly depends on whether an authorized facility received a meaningful opportunity to address a covered nonconformity. A final invoice marked “could not duplicate” can still be important when it accurately records the complaint, mileage, time held, tests, and outcome.
Do not combine several visits from memory. Obtain the actual repair orders and communications. The sequence may reveal that the same warning, code family, or drivability condition was reported repeatedly even when no single visit reproduced it.
A record-first next step
Create a reproducibility note for the next appointment and ask the adviser to attach it to the repair order rather than summarize it as a generic warning light. 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 Civil Code section 1793.2
- California DCA Arbitration Certification Program
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 misfire, stall, hesitation, or reduced power 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 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.