Lemon Law Blog

Building an Intermittent Car Defect Lemon Law Case When the Dealer Says It Cannot Reproduce It

A dealership’s inability to reproduce a problem does not erase the problem; it means the case has to be built around repeatable evidence, precise repair-order language, and a record showing how often the defect affects normal use. The goal is to make each visit add something concrete to the file, even if the technician cannot trigger the warning light, noise, loss of power, electrical failure, or other symptom during a short test drive.

Start documenting the defect before the next appointment, then bring the same written description to every visit. This approach also matters where the issue may be tied to repeated remote fixes, such as a software update lemon law question, because a service record should identify what update was installed and whether it changed the symptom.

How an intermittent car defect fits a lemon law record

An intermittent car defect lemon law claim is usually stronger when the paperwork shows a pattern rather than a single unexplained event. A repair order that says only “customer states vehicle acting weird” gives little detail. A repair order stating “at 42 mph after 18 minutes of driving, steering wheel vibrates and lane-assist warning appears for 10 to 15 seconds” gives the dealer, manufacturer, evaluator, or attorney something specific to compare across visits.

Do not wait for a dramatic breakdown before creating a paper trail. A defect that appears twice a week for three months, even if it vanishes during a 20-minute dealer test drive, can be documented through dates, mileage, conditions, photographs, videos, messages, and repair orders. The useful question is not simply whether the technician saw it once; it is whether the record shows that the vehicle repeatedly fails to perform as expected.

Intermittent defects are especially common with electrical systems because conditions can change from one drive to the next. A loose battery terminal, corroded ground connection, failing wheel-speed sensor, weak fuel-pump control module, moisture in a connector, or software communication fault may appear only after heat, vibration, rain, a cold start, or a certain length of drive. The dealer may need the right conditions and enough time to see it, but the owner can preserve those conditions in the written record.

Create a defect log the dealership can actually use

Keep a single log in a notebook, spreadsheet, or phone note. Each entry should include the date, odometer reading, outside temperature if displayed by the vehicle, approximate speed, trip length, fuel level if relevant, warning lights, sounds, smells, dashboard messages, and what happened immediately before and after the symptom. A one-line entry is better than relying on memory two weeks later.

For example, write: “March 8, 12,460 miles, vehicle sat overnight, 47°F shown on dash, started normally, after 6 minutes the instrument cluster went black for about 8 seconds, radio continued playing, power steering remained normal.” If the vehicle has a screen message, record the wording exactly. “Driver assistance unavailable” is more useful than “warning came on.”

Video can fill gaps that a repair order cannot. Safely record the instrument panel only when a passenger can do it or when the vehicle is parked; never handle a phone while driving. A 30-second video showing the odometer, warning light, date on the phone, and the symptom can establish that it happened, while a longer clip can show whether the problem lasts 5 seconds or 5 minutes.

Check one simple fact at home today: photograph the odometer and every illuminated dashboard warning light with the vehicle parked. If the warning disappears after a restart, take a second photo after restarting. Those two images can show both the mileage and the fact that the condition was intermittent rather than imagined or permanently displayed.

Make every repair visit produce useful paperwork

Book a visit promptly after the defect occurs, but do not rely on a verbal description at the service counter. Hand over a short written symptom sheet and ask that its substance be placed on the repair order. Keep the wording factual: when it occurred, how long it lasted, what warning appeared, what vehicle functions changed, and whether the issue has happened before.

Before leaving, read the repair order. Confirm that the mileage is correct and that the concern is not reduced to “no problem found” before anyone has inspected the vehicle. If the advisor writes “could not duplicate,” that may be accurate after testing, but the customer concern should still appear separately, such as “customer reports intermittent loss of audio, rear camera blank, and warning message occurring four times since last visit.”

Ask for the final repair invoice or closed repair order every time, including when no repair was performed. Look for technician notes, diagnostic trouble codes, software version references, test-drive distance, parts replaced, and whether a bulletin or factory technical assistance line was consulted. A record stating “scanned system, no current codes, drove 12 miles, unable to duplicate” is still evidence of a reported defect and a repair opportunity.

Keep originals or clear scans in date order. A practical file might contain the purchase or lease paperwork, warranty booklet, every repair order, tow or roadside invoice if one exists, screenshots of appointment requests, the defect log, photos, videos, and communications with the manufacturer. Rename digital files with dates, such as “2025-03-08_dash-warning_12460-miles.jpg,” so they can be found later.

Give the dealer conditions that make reproduction more likely

Describe the trigger instead of merely naming the failed part. “Transmission jerks” is broad. “After 25 to 35 minutes of stop-and-go driving, a hard shift occurs from second to third gear at about 22 mph, followed by a wrench warning symbol” gives the technician a usable test plan. The same applies to a rattle that occurs only between 1,800 and 2,200 rpm, a brake squeal after the vehicle sits for 48 hours, or a screen freeze when a phone is connected by cable.

If the defect happens after the vehicle has been parked overnight, ask that the vehicle not be moved before evaluation if the service department can accommodate that request. If it appears only after a long drive, state the approximate time or distance needed: 30 minutes, 60 miles, or after the engine reaches its normal operating temperature. If it occurs in wet conditions, say whether the issue began during rainfall, after a car wash, or after driving through standing water.

Do not diagnose the vehicle for the technician or insist on a particular repair. The useful task is documenting the observable failure and the conditions around it. A technician may find a different root cause than expected, and the repair record will be more credible if it distinguishes the symptom from the proposed explanation.

Preserve the pattern if repairs, updates, or denials continue

A pattern can include unsuccessful repairs, repeat complaints after a repair, long periods out of service, and repeated “cannot duplicate” findings. Make a timeline with one row per event: date, mileage, symptom, dealership visit, action taken, days the vehicle remained there, and whether the defect returned. If the vehicle stayed at the dealer from Monday morning until Thursday afternoon, record the four calendar dates rather than writing only “several days.”

After a repair, test the vehicle in the same ordinary conditions that previously triggered the problem. If a new battery was installed, for example, note whether the no-start condition returns after sitting 10 hours. If a camera module was replaced, note whether the image still drops out while reversing. Do not create unsafe conditions to force a failure; ordinary, documented use is enough.

Keep communications calm and specific. A message saying “the vehicle is unsafe and nobody will help” may express frustration but does not identify the event. A message saying “the rear camera displayed a black screen on April 14 at 8,104 miles; this is the third occurrence since repair order 57291; attached is a 22-second video” adds an identifiable event to the record.

If the defect continues, gather the complete file before seeking individualized legal advice. The most useful file is not a stack of complaints; it is a dated sequence showing the same defect, the attempts to evaluate or repair it, the vehicle’s mileage at each step, and what happened after each attempt.