The count
Ask anyone who has won one of these fights what did it, and the answer is never a magic sentence. It is a record: dates, names, claim numbers, visit outcomes, promises with timestamps. The administrator's system is also a record — theirs is just written by the side that profits from your count being low. This page is the format that beats it.
Between visits, keep the second log: every occurrence of the fault, dated, one line — "Oct 3, 2pm: fridge 54°F, ice cream soft, photo taken." Occurrences are the evidence that converts "no fault found" from an ending into a misdiagnosis pattern, and they are the spine of a regulator complaint's chronology. A month of dated one-liners outweighs an hour of arguing.
The kit's repair log is this format as a printable, structured workbook — with the classification column (counted / excluded / disputed) pre-built, because the classification is where logs go to win.
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 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.
One payment, yours to keep. We never ask for your store or plan-portal password — you file everything yourself. See everything inside the kit →