Lemon Car Lawyers: How to Track Defect Recurrence

If your car is in the shop over and over for the same problems, you’re probably wondering what counts as a “recurring defect” and how to document it in a way that helps your California lemon law claim. At ZapLemon, we help consumers understand what the law looks for and how to build a clean record of what’s been happening with their vehicle. Below, we explain what typically qualifies as a recurring defect under California’s lemon law and how to track repair attempts so your story is clear, consistent, and supported by paperwork.

What Counts as Recurring Defects Under CA Lemon Law

Under California’s Song-Beverly Consumer Warranty Act (often called the California lemon law), a “recurring defect” generally means a problem covered by the manufacturer’s warranty that the dealer or manufacturer has not fixed after a reasonable number of attempts. It doesn’t have to be the exact same error code every time; it’s usually about the same underlying condition or symptom continuing despite repairs. Think of a transmission that keeps shuddering, an EV battery range that drops abnormally, brakes that squeal and lose bite, or an infotainment system that repeatedly reboots and locks up.

California’s lemon law presumption (sometimes referred to as the Tanner presumption) looks at specific benchmarks early in ownership, like problems within the first 18 months or 18,000 miles. While every situation is different, the presumption often considers whether the manufacturer had a reasonable number of chances to fix the issue—such as multiple repair attempts for the same problem, two or more attempts for a defect that could cause serious injury or death, or the vehicle being out of service for an extended period due to warranty repairs. These are not hard limits for every case, but they’re common guideposts courts and manufacturers recognize.

Not every annoyance is a qualifying defect. Wear-and-tear items, damage from accidents or modifications, or issues outside warranty coverage may not count. That said, patterns matter: a persistent “check engine” light with varying codes, repeated ADAS (driver-assistance) malfunctions after software updates, or recurring coolant leaks in slightly different spots may all point to the same unresolved defect. If you repeatedly experience similar symptoms—hesitation on acceleration, strong fuel smell, stalling, or warning chimes—documenting those patterns is essential.

How to Log Repairs and Build a Strong Paper Trail

Start by keeping a simple, consistent log. Each time the defect appears, note the date, mileage, outside temperature or conditions, what you were doing (highway merge, stop-and-go traffic, charging session), dashboard lights or messages, and exactly what you observed (e.g., “Vehicle shuddered at 45–55 mph, check engine light flashed, reduced power”). Save photos and short videos when safe to do so. After each service visit, staple the repair order to your log and make sure it lists your complaint in your own words, the odometer reading, the technician’s findings, and the parts and software versions used.

Always request and keep copies of every repair order and invoice, even if the dealer says “we couldn’t duplicate the concern.” Those “no problem found” documents still show that you tried to get the defect fixed. Track how many total days the vehicle is out of service for warranty repairs, including time waiting for parts or software updates. If you receive a loaner or rental, keep those agreements and receipts; they help verify downtime.

Communicate in writing when possible. A short follow-up email to the service advisor after drop-off—recapping the symptoms and when they occur—creates a time-stamped record that supports your repair order. If the manufacturer opens a case number, write it down and save any letters, emails, or texts. For technology-heavy vehicles, capture software update release notes and write down version numbers before and after service. You can also ask the dealer to include diagnostic codes (DTCs) and any technical service bulletins (TSBs) referenced in your repair file. These small steps create a clear, credible story of defect recurrence.