The warranty question nobody can answer on site
A tech is standing in front of a failed compressor, a dead water heater, a generator that won't start. The customer asks the question that decides the whole visit: "Isn't this still under warranty?" And nobody knows. The install date is on a paper file back at the office, or in someone's memory, or gone. So the tech guesses — and a guess goes one of two bad ways. Quote the repair as billable and it turns out the unit was covered, and now you've either overcharged a customer who'll find out later or you eat the cost to make it right. Tell the customer it's covered when it isn't, and you've promised something you can't deliver. Either way the warranty question, answered by a shrug, costs you money or trust or both.
The root problem is that warranty status lives on the unit, but most operations track work on the job. You know you serviced an address last spring; you don't know that the furnace at that address was installed three years ago with a five-year warranty and has eighteen months left. The fact that decides whether a repair is billable is exactly the fact you don't have in front of you when you need it.
Track the unit, not just the visit
The fix is to make every piece of equipment you service a record in its own right — registered once, then carried forward through every visit. When you install or first service a unit, you capture what it is and when its warranty runs out. From then on, every tech who touches it sees that fact immediately, and the warranty question stops being a guess. This is the same shift that tracking equipment and assets at customer sites makes for service history generally — but warranty is the part of that record that most directly changes what you charge.
A unit-level record also fixes the quieter problem: the customer whose warranty is about to lapse. If you can see that a unit's coverage expires in three weeks, that's a reason to reach out — get the covered service done now, or offer a service agreement before the safety net disappears. Warranty data isn't just a defense against mischarging; read forward, it's a prompt for the right conversation at the right time.
How Hosting Field handles equipment warranty
Hosting Field models this with equipment records — one record per physical unit, attached to the customer's site. You capture the make, model, serial number, install date, warranty expiry, and any notes, and from then on that unit has a permanent home. The piece that does the work on site is the live warranty badge: the platform computes status from the expiry date and shows it as in-warranty, expiring-soon (30 days or less), or expired — so the tech sees the answer to "is this covered?" the moment they pull up the unit, before a single number gets quoted.
The history compounds the value. You tag each job to the unit it services right on the job form, and every unit carries its own per-unit service history — every job on that equipment, newest first, with status and the technician who did it. So a tech walking up to a five-year-old furnace doesn't just learn it's still under warranty; they see it's been serviced twice, what was done, and by whom. And because deleting a unit never deletes a job, that history is preserved even if the equipment is retired — the record of work you did survives the thing you did it to.
The honest scope: Hosting Field tracks your record of the warranty — the expiry date you entered and the badge it computes from it. It doesn't file manufacturer warranty claims for you or pull coverage status from a manufacturer's system; it's the source of truth you maintain so your techs and your office are working from the same fact. Keep the install dates and expiry dates accurate going in, and the badge is right going out. The system does the date math and surfaces it at the right moment; you keep the dates honest.
Making it work
- Register the unit at install, not at the first failure. The cheapest time to capture make, serial, and warranty expiry is when you put the equipment in. Wait until something breaks and you're reconstructing it from a label in a dark crawlspace — capture it once, up front, and every future visit inherits it.
- Trust the badge, but keep the dates clean. The expiring-soon and expired badges are only as good as the expiry dates behind them. A wrong date produces a confidently wrong badge, which is worse than no badge. When a tech spots a date that's off, fix it then.
- Read the expiring-soon badge as a sales signal. A unit thirty days from losing coverage is a reason to call. Get the covered work done while it's still free to the customer, or have the service-agreement conversation before the warranty lapses and the calculus changes.
What to measure
- Mischarged-warranty incidents. How often you bill for covered work or eat the cost of a misjudged warranty call. With a live badge in front of the tech before they quote, this should fall toward zero — and tracking it proves the equipment records are actually being checked.
- Repeat-unit visibility. What share of jobs are tagged to a known unit versus logged against just an address. The higher this is, the more your first-time fix rate benefits, because a tech who can read a unit's history shows up knowing what's been tried.
- Expiring-warranty follow-through. How many expiring-soon units you actually reach out about before coverage lapses. This turns a passive data field into active revenue — and is the clearest sign you're reading warranty data forward, not just defending against it.
The warranty question gets asked on every other visit, and answering it with a shrug is how you bleed money and trust in equal measure. Register each unit once with its install and expiry dates, let Hosting Field compute the in-warranty, expiring-soon, and expired badge live, and put it in front of the tech before they quote. Tag every job to its unit so the service history follows the equipment, and read the expiring-soon badge as the sales prompt it is. The warranty question stops being a guess at the truck and becomes a fact on the screen — and that's the difference between a visit that builds trust and one that quietly costs you. See it alongside the rest of the feature set.