The count

"No fault found." Three words that erase your visit from the count.

The tech came, plugged in a diagnostic, found nothing, and left. Your fridge still dies every few days. What you may not know: at Lowe's, that visit expressly does not count as a repair under the plan's lemon clause — you can collect five of those visits and be no closer to a replacement than the day you bought the plan. This sentence is the most expensive line in either store's document. Here is what it means and how to fight it with paper.

The sentence, in the terms' own shape

Lowe's Terms & Conditions define the lemon count over covered repairs — and then exclude from that definition: diagnosis, customer education, telephone troubleshooting, alignments, cleanings — and a "no fault found" diagnosis. Read it as the administrator reads it: intermittent faults — the kind that vanish when a tech is standing there — generate visits that cost you weeks and buy you nothing on the count. The holder who reports "six service calls and still no replacement" is usually living inside this definition.

Home Depot's brochure uses different words — it counts "service repairs" — and a nothing-done visit's status there is arguable rather than excluded. The defense in both stores is identical: documentation that turns "we found nothing" into a dated record of a reported, recurring failure.

The documentation protocol

  1. Before the visit: record the fault yourself — phone video of the symptom, the error code, the temperature log on a fridge. Intermittent faults become undeniable when they arrive with evidence.
  2. During: show the tech the recording. Ask that the reported symptom be written on the visit record in your words, not summarized away.
  3. After: get the visit summary in writing (portal, email, or the paper slip) the same day. Write your own one-line log entry: date, company, tech's finding, the symptom as it continues.
  4. Between visits: keep logging occurrences with dates. A pattern of dated occurrences is what converts the next "no fault found" into a misdiagnosis argument — and what a regulator complaint grades.

When the pattern is the product

If the same symptom has produced two or more no-fault visits, escalate in writing with the occurrence log attached and ask a specific question: "Given N documented occurrences of the same failure, what will the next visit do differently?" A question that specific, in writing, changes desks. The checker counts your real repairs separately from these visits so you always know your true number.

Count your own case. The free checker takes your store, your plan date, your repair history, and your dates — and returns your lemon count, your live clocks, and the money the plan owes. Run the checker →

The working papers for this fight

The pages above are the map. The kit is the paperwork: the repair log that proves the count, the script for your administrator, and the complaint pack for when the stall continues.

Included in the $39 ProtectionPlanDecoded Kit

  • The lemon-proof repair log: occurrence logging + visit classification, built for the intermittent-fault fight
  • The misdiagnosis escalation wording — the occurrence log presented the way a reviewer grades it
  • The regulator complaint pack, no-fault-found edition
Get the $39 ProtectionPlanDecoded Kit

One payment, yours to keep. We never ask for your store or plan-portal password — you file everything yourself. See everything inside the kit →

Keep reading