HVAC warranty tracking: spreadsheet or software?

Published 17 October 2026. Updated 17 October 2026.

Plenty of HVAC and plumbing shops track warranty claims in a spreadsheet, and that is not a mistake. A sheet is free, everyone can open it and it does the job while claim volume is small. The question is when it stops doing the job, and what you would move to. This guide compares a spreadsheet, a field service platform with built-in warranty tracking, and a single-purpose tool such as WrenchClaim, and says plainly when the spreadsheet is the right answer.

What does tracking a warranty claim actually take?

Tracking is not the same as recording. Recording says a claim was filed. Tracking tells you, while there is still time, that a claim should be filed. For each failed part the shop has to hold five things in one place:

1. The identity of the equipment: brand, model and serial number, usually from the rating plate.
2. The install date and whether the equipment was registered, because many programs give a longer term to registered equipment. Check your brand's terms.
3. The date of the repair or failure.
4. The filing deadline, worked out from the terms and the repair date.
5. The status of the claim: not filed, filed, credited, short paid, lost.

Everything else, the narrative, the photos, the invoice number, belongs to the packet. The tracking question is whether anyone notices a deadline before it passes.

When is a spreadsheet enough?

A sheet is a sound choice when most of these are true:

• You file a few claims a month, not a few a week.
• One person, owner or office manager, enters and checks every row.
• Technicians reliably send the plate photo and notes the same day.
• You are comfortable setting a calendar reminder when a row is added.
• Your filing windows are long enough that a weekly look at the sheet is early enough.

If that describes your shop, do not buy anything. Spend the time on the checklist at the end of this guide instead.

Where does a spreadsheet break down?

The failures are rarely the sheet's fault. They are failures of the routine around it.

• Nothing happens by itself. A date column does not warn anyone. A conditional format helps only if someone opens the file that week.
• Retyping errors. Serial numbers are long and rating plates are often dirty or at an angle. A transposed digit can get a claim returned or make a coverage lookup find nothing.
• Version confusion. Two copies by email, one on a laptop, one in a shared folder. Claims are filed twice or not at all.
• Date math done by eye. Install date plus term, repair date plus filing window, with different terms for parts and labor. Formulas can do it, but someone has to build, maintain and trust them for every brand.
• Nobody checks the second time. The person who enters a row is usually the person who checks it. A wrong install date stays wrong.
• Single point of failure. The sheet works as long as one person keeps working it.

When does your field service platform make more sense?

If your field service or dispatch platform already stores equipment records and tracks warranty parts, it may be the best answer, because the data is already there and no one retypes anything. Ask these questions before relying on it:

• Does it store the install date, registration status and filing deadline per part, or only that a part is under warranty?
• Does it warn you before a deadline, or only list claims you already started?
• Does it produce the claim in the order and format your distributor wants, or do you still retype it?
• Does moving to it mean replacing the software your technicians already use? Some platforms are a large switch for what may be a small problem.

Platforms differ a great deal, so check what yours does rather than assuming. If yours handles all of this, you probably do not need anything else, including WrenchClaim.

How do the three approaches compare?

A checklist that works whichever way you track

1. Photograph the rating plate on the job and attach it to the job record the same day.
2. Record the install date and registration status the first time you see the unit.
3. Write the deadline in the row the day the repair is done, not later.
4. Look at every unfiled claim on a fixed day each week.
5. Keep one master copy, one owner and one place where it lives.
6. After filing, record the date, the reference and who filed it.
7. When a credit arrives, match it to the claim and note any short payment.
8. Once a quarter, list claims that were never filed and the reason.

How WrenchClaim does this step

WrenchClaim takes the place of the manual date work and the packet retyping, not the whole routine. You upload a job export (CSV, Excel, Word, PDF or a photo of it), technician notes and a rating-plate photo per job. Code checks the install date against the term and the repair date against the filing window, so no model does the date math. Each job gets a status: eligible with days left, lost, not eligible, unsupported brand or needs check.

It checks what you upload, when you upload it. It does not run on a schedule or send deadline reminders, so the weekly look in the checklist above still applies: upload your recent jobs each week.

For each eligible item, Claude drafts the failure narrative using only what is in your notes, and the packet is laid out in Ferguson's form field order. You also get a claims CSV and a 12-month report of claims whose window already closed, with a rough parts-cost estimate. A second, stronger AI model reviews every result and lists what is left for you to decide.

WrenchClaim does not file the claim for you and does not log into any manufacturer or distributor portal. The built-in terms for Carrier, Trane, Rheem and Goodman/Daikin are marked unverified until confirmed, Lennox is flagged as needs check, and you can upload your own terms table. It also does not replace your field service software. One upload of your export, notes and photos costs 12 credits, however many packets it drafts, with no subscription. See the mistakes checklist for what to watch on each job, or sign up to try it on your recent jobs.

Questions

Is a spreadsheet good enough for warranty claim tracking?

For a shop with a handful of claims a month and one person who owns the sheet, yes. It stops being enough when claims come from several technicians, when the filing window is short, or when the one person who keeps the sheet is away.

Can my field service software track warranty claims?

Some platforms track warranty parts and some do not. Check whether yours stores the install date, the registration date and the filing deadline per part, and whether it warns you before the deadline, not only that it records a claim.

What should a warranty tracking sheet contain at minimum?

Job number, brand, model, serial number, install date, repair date, part, the filing deadline, the date filed, the reference number and the date a credit arrived. Without the deadline column the sheet records history but protects nothing.