A timeline is an index to the source documents, not a substitute for them. Its purpose is to make recurrences visible and help a reviewer move from one repair order, photograph, message, or towing receipt to the next.
Use one row per event
Create separate rows for the first warning, each service visit, each recurrence, each manufacturer contact, and each period the vehicle could not be used. Use exact dates and mileage from records whenever possible. If a date comes only from memory, label it as approximate rather than presenting it as documented.
For each row, record the warning status, code state, symptoms, operating conditions, facility, complaint, diagnosis, correction, verification, and link or filename for the supporting document. Count days out of service from the actual drop-off and return dates, noting any disagreement in the records.
- Event date and odometer.
- Observable warning and drivability symptoms.
- Pending, confirmed, or permanent codes.
- Repair-order number and warranty coverage shown.
- Open and close dates and transportation expenses.
- Date, mileage, and conditions of recurrence.
Avoid turning the worksheet into a legal conclusion
The worksheet should not announce that a vehicle is a lemon or that a particular statutory presumption applies. California law uses defined terms and fact-dependent standards. Current procedures may also differ depending on timing and manufacturer participation in statutory changes.
Keep the source files unchanged and give each a stable filename. The timeline can then cite “RO-03” or “Photo-2026-08-14” so the underlying evidence is easy to retrieve.
A record-first next step
Download or reproduce the evidence-toolkit columns and attach a consistent document identifier to every entry. 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 Civil Code section 1793.2
- California Civil Code section 1793.22
- California DCA Arbitration Certification Program
- California BAR On-Board Diagnostic Test Reference
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 failed emissions tests connected to the same fault history 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 wiring, connectors, and software calibrations, along with part numbers, software versions, road-test notes, and cannot-duplicate language. Preserve repair orders and post-repair verification 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.