Warranties — Custom Object Example | FieldCamp

Track warranties as a custom object in FieldCamp — provider, coverage type, dates, terms, and claim status linked to the equipment a warranty protects.

A Warranty is a record an HVAC, appliance, or equipment business adds to track the coverage on the assets it services — who backs it, what it covers, when it starts, and when it runs out.

It is a worked example of a custom object: a record type FieldCamp does not ship by default, built on the same engine that powers every core record.

Once it exists, every warranty lives in one list your dispatchers and techs can search, instead of scattered across spreadsheets and filing cabinets.

A Warranty links to the Equipment it protects, belongs to the Customer who owns that asset, and gets referenced on a Job when a claim is made — so a tech on site can see in seconds whether the unit in front of them is still covered.

Warranties are not part of the standard day-one set of records. They are added through customization or an industry setup, on top of the core Customers, Jobs, and Visits every account ships with — and alongside the Equipment layer they cover.

What a Warranty captures

A Warranty record holds the identity of the coverage — the provider behind it, what kind of work it pays for, the window it runs for, the terms in writing, and where the latest claim stands.

The table below maps each field to the type it is built from.

Field	Field type	What it holds
Warranty name	Text	A plain label for the coverage, such as "Compressor — 10yr parts" or "Whirlpool extended plan".
Provider / manufacturer	Text, or a link to a Provider record	Who backs the coverage — the manufacturer (Carrier, Trane, Whirlpool) or a third-party warranty company.
Coverage type	Single choice	What the warranty pays for: Parts only, Labor only, or Full (parts and labor).
Plan type	Single choice	Manufacturer, Extended plan, or Home-warranty — the kind of coverage.
Start date	Date	When the coverage begins, usually the install or purchase date.
End date	Date	When the coverage runs out.
Coverage length (months)	Number	The length of the term, useful when the end date is derived from the start.
Terms	Long text	The written terms — what is covered, what is excluded, deductible, and conditions.
Coverage document	File	A scan or photo of the warranty certificate or contract.
Claim status	Single choice	Where the latest claim stands: None, Open, Filed, Approved, or Reimbursed.

The coverage type — Parts, Labor, or Full — is the field a dispatcher reads before quoting. It is what tells the office whether a repair is billable cash work or claimable against the provider, which changes how the Job is priced.

The owner and the protected asset do not need to be re-typed onto the Warranty. They come from the records it links to: the Equipment the coverage protects and the Customer who owns that equipment.

How Warranties connect

A Warranty sits between an asset and its owner, and gets pulled into a job at the moment of a claim.

It covers one piece of Equipment, belongs to the Customer that equipment rolls up to, and is referenced on a Job when a claim is made against it.

Read the links outward from the Warranty:

A piece of Equipment can be covered by more than one Warranty — a base manufacturer warranty on parts, plus an extended plan on labor — and each Warranty protects one asset.
Every Warranty belongs to the Customer who owns the protected equipment, so coverage always rolls up to a real account and a real site without re-entering either.
When work is done under coverage, a Job claims against a Warranty. A job can reference the warranty the work draws on, and one warranty can be claimed against on more than one job over its life.

The link to Equipment is what makes a Warranty worth tracking.

A tech opening the Equipment record on arrival sees its coverage right there — provider, what is covered, and the end date — so the call about billable-versus-claimable happens on site, not after the fact.

Coverage and claims

A Warranty carries two simple lifecycles: where the coverage itself stands, and where a claim against it stands. Both are built as stages on the record.

Coverage moves from Active to Expired as the end date passes, with Expiring soon as the window in between.

A claim runs its own short approval path when work is done under coverage, so a claim cannot move forward until the right details are captured.

Moving coverage to "Expiring soon" automatically across every record is a gap — be clear-eyed about it. FieldCamp's calculated fields work on a single record's own fields — for example, deriving an end date from a start date plus a coverage length on the same warranty. They do not watch the calendar across your whole list and flip a status when a date approaches.

So a warranty shows its end date and you can sort or filter on it, but "alert me 30 days before this coverage lapses" is a time-based rule that belongs to FieldCamp's separate workflow automation product, not to the warranty record itself.

The record stores and displays the date; the proactive reminder is configured alongside it.

How it is built in FieldCamp

A Warranty is a custom object linked to Equipment — built on the same engine as every core record, not a one-off.

You define its fields once (the table above), point it at the equipment it protects and the customer who owns that asset, and it gets its own list, its own place in navigation, and its own record page.

That record page is assembled from the same building blocks as every other record — a header with the coverage status, a field group for the provider and dates, a files section for the certificate, and a link up to the protected equipment.

See record layouts for how to reorder, add, hide, or group those sections, and stages and workflows for how to shape the coverage and claim lifecycles to the way your shop works.

A few honest limits to set expectations. A custom object like Warranty does not auto-number its records the way Jobs and Invoices do, so a claim or policy number is entered by hand.

And FieldCamp does not enforce that two warranties carry a unique serial or policy number — the field accepts the value, it does not dedupe across records.

Make it your own

The Warranty above is a starting point, not a ceiling. Because it is a record like any other in the FieldCamp data model, every part of it bends to your trade.

Custom fields

Add the fields your coverage actually needs — deductible amount, authorization number, transferable flag, or a labor-rate cap — and they appear alongside the provider and dates.

Your own coverage stages

Rename or reorder the coverage and claim stages, and add guardrails — require the coverage document before a claim can be filed, or a reason before one is closed.

Record layout

Rearrange the blocks on the Warranty page so the provider, the dates, and the certificate read the way your office works a claim.

The same Warranty record serves any size of operation. A single-truck HVAC shop tracks a short list of manufacturer warranties and checks one before quoting a repair.

A multi-location franchise runs the same coverage layer at every site, tailoring the fields and stages each location needs without rebuilding the model.

Equipment

The asset a warranty protects. One piece of equipment can be covered by more than one warranty.

Customers

The owner of the equipment a warranty covers. Every warranty rolls up to one customer.

Jobs

The work order that references a warranty when a claim is made against it.

Custom objects & fields

How the Warranty record is created and the field types it is built from.