01 · Safety first
Document only when safe and lawful
Do not use a phone while driving, recreate a hazardous event, ignore a warning, or place yourself or others at risk to collect evidence. Follow the owner’s manual, displayed instructions, traffic law, and roadside guidance. Documentation should be created only when the vehicle is safely stopped and it is lawful to do so.
If the event requires immediate safety action, that action comes first. A later factual note can record what happened without a photograph. This resource does not provide operating or repair instructions.
02 · Observed event
Name the function and exact behavior
Potential categories include a warning that appears briefly, display or camera failure, charging interruption, suspension warning, reduced-power warning, electronic system unavailable message, or unusual vehicle behavior. These are organizational categories, not diagnoses.
Record the exact warning text and affected function. “Electrical problem” is less useful than a note identifying which display, camera, control, charging function, or vehicle behavior was observed.
03 · What to record
Capture event-level context
When safely practical, preserve an original photograph or video, date, time, mileage, approximate location, ambient conditions if relevant, and what happened immediately before the event. Note duration, whether a restart cleared it, whether it recurred, and whether a dealer later reproduced it.
Keep original files rather than edited compilations. A photograph may show a message at a moment in time; it does not prove the technical cause. Avoid adding captions that claim more than the file shows.
- Exact warning text and affected function
- Date, time, mileage, and approximate location
- Safe original photograph or video, if available
- Conditions and event immediately before
- Duration and restart effect
- Recurrence and dealer reproduction status
04 · Repair-order accuracy
Make the service record match the report
At drop-off, describe the actual symptom, warning, timing, frequency, and practical effect. If original media was provided, retain the sent message and ask that the order acknowledge it where appropriate. Do not pressure staff to use a diagnosis or legal phrase.
At pickup, compare the concern, dealer findings, correction, date, and mileage. If the condition was not reproduced, keep that outcome and the complete order. Then record the first recurrence accurately.
05 · Recurrence log
Use a log as an organizational tool
A recurrence log can connect events occurring between dealership visits. Use one row per event and avoid backfilling details from memory as though they were contemporaneous. Identify estimates and unknowns.
The log is not legal evidence guaranteed to establish a claim. It helps a reviewer locate original media, compare recurrence, and understand what was communicated to the dealer.
06 · Condition comparison
Do not merge every warning
Compare exact text, function, sequence, circumstances, and restart effect. Several warnings appearing together do not prove several failed components, and two visits carrying the same broad system label may involve different owner observations.
A qualified source should supply diagnosis. The consumer’s role is to preserve accurate observations and the dealer’s documented response.
07 · Continue the analysis
Use the vetted legal and system guides
The Dealer Cannot Duplicate and Repair Attempts guides address the approved California legal framework. The Electrical Problems and Software & Infotainment guides provide system-specific documentation prompts while maintaining the boundary between symptoms, dealer terminology, and VIN-specific facts.
Those links are more reliable than repeating legal rules here. This page remains focused on safe event documentation and record organization.