Installation Software — Data Model | FieldCamp

How an installation business runs in FieldCamp — multi-day install jobs on the core records, plus tracking each installed unit as an asset with its warranty.

An installation business sells, schedules, and installs a product — an appliance, a fixture, a smart-home panel, a piece of equipment — and then the thing it just put in becomes something a crew may come back to service for years.

Most of that work runs on FieldCamp's core records the day you sign up: the quote, the install job, the field crew, the bill.

The part that makes installation its own trade is the layer on top — tracking the installed unit as an asset, with its serial number and warranty, so the next call already knows what is on site.

This works whether you install one unit a day or run multi-day crews across a region, and everything here can be tailored to how your shop actually sells and installs.

What the core already gives you

An installer uses most of FieldCamp's core records exactly as they ship, with no rebuild.

Customers — the homeowner or the business, with separate property and billing addresses, lead source, and preferred crews, so a buyer and the site they bought for live in one place.
Requests — the inbound inquiry, online booking, or showroom hand-off, with one-click convert to an estimate, job, or invoice.
Estimates & Invoices — the quote, including the Good / Better / Best option set for "which model" and "with or without the upgrade", plus deposits, payment terms, and card capture.
Jobs — the install work order. A simple drop-in is a one-off job; a larger install is a multi-day job, which lays down one Visit per day automatically.
Visits — each trip to the site: the measure, the install day, the return for a back-ordered part. Every visit carries crew assignment, check-in location, a captured signature, and photos.
Price Book — the units and the labor with cost and price, plus truck stock, reorder thresholds, vendor pricing, and purchase orders for the gear going out.

On-site capture — the pre-install site check, the measure sheet, the install QA checklist, and the customer sign-off — is handled by job forms on the visit, not by extra fields on the job.

A multi-day install is a single Job with the job type set to multi-day.

FieldCamp lays down one Visit per day, rolls the job to In Progress when the first visit starts, and to Completed when the last one finishes — so the schedule and the status keep themselves in sync without a separate project for everyday installs.

What installation adds

Core covers the sale, the schedule, and the field work. What it has no home for is the thing you installed — the specific unit, with its own serial number and warranty, that outlives the job that put it in.

That installed unit is added as an asset record built on FieldCamp's customization engine, and its coverage is tracked alongside it. For larger or longer installs, an optional install project sits above the jobs.

The installed unit as an asset

The asset is the central record of the trade after the sale — the individual unit you installed, tracked across its life so the next crew on site already knows what it is dealing with.

This is exactly the Equipment record: a single piece of gear with its own model and serial number, its install date, and a service history built from every visit performed against it.

It belongs to the Customer who owns it and the property it sits on, and it links to the many Jobs that service it over the years — starting with the install job itself.

A technician opening the asset on arrival sees the specs, the warranty standing, and the prior service in one place — so a callback under coverage is settled on site, not after the fact.

The warranty on what you installed

The coverage on the installed unit is its own record — who backs it, what it covers, and when it runs out — so a callback is settled as billable cash work or claimable against the provider before a crew is even sent.

This is the Warranties custom object, linked to the Equipment it protects and the Customer who owns it. A single unit can carry more than one — a base manufacturer warranty on parts, plus an extended plan on labor.

The asset and its warranty are what turn a one-time install into a relationship.

The install job creates the asset; the warranty rides on it; and every return visit lands on the same record — so years later a crew still knows the model, the serial, and whether the unit in front of them is still covered.

An install project, for the bigger jobs

For a single-unit drop-in, the multi-day Job is the whole story — no project needed. For a larger install that runs across delivery, prep, and several install days with its own approval and sign-off, an optional Install Project can sit above the jobs.

It is a standalone custom object that owns the arc from a signed estimate to a closed-out install: it carries the project name, the site, the contract value, and target dates, and it links to the Customer, the signed Estimate, the Jobs it produces, and the Equipment installed under it.

Most installers never need it; reach for it only when one install is more than one job.

How these records connect

The Equipment sits at the center after the sale: a Customer owns it, the install Job (or the project's first install job) creates it, it builds its service history from the Visits performed against it, and it carries the Warranties raised on it.

The catalog item it was drawn from stays in the Price Book — the Equipment record is the specific unit, not the type.

The install project is optional. For everyday installs the multi-day Job carries the whole thing, and the Equipment hangs off the customer directly — no project record in between.

Add the project only when an install runs long enough to need its own lifecycle and sign-off, the way a solar or general-contracting job does.

The install flow

A standard install moves from a quote to a scheduled job to an installed, covered asset. The path below is how those records line up — built entirely from core, with the asset created at the end.

Quote the install

A Request becomes an Estimate — often a Good / Better / Best option set so the customer picks the model and the upgrades, with a deposit on approval.

Schedule the install job

The approved estimate converts into an install Job. A drop-in is a one-off job; a larger install is a multi-day job that lays down one Visit per install day.

Install on site

Crews run the Visits — measure, deliver, install — with check-in location, photos, the install QA job form, and a signature-gated finish.

Record the installed unit

The unit goes on the customer as an Equipment asset — model, serial, install date — and its Warranty is recorded against it, so the next call starts with the full picture.

Bill it

The completed job creates an Invoice; a fully paid invoice marks the job paid in return, closing the loop.

One-off installs vs ongoing service

The same records serve a clean one-day install and a long relationship with the unit you put in. The difference is how much of the asset layer you use — not a separate set of records.

One-off install

A single appliance or fixture goes in on a one-day Job, the customer pays by card on site, and that is the transaction. Recording the Equipment asset is still worth a minute — it is what makes a future callback a known unit rather than a cold start.

Install plus ongoing service

The installed unit is the start of a service relationship: it carries a Warranty for the callback window, builds a service history from every return Visit, and can sit under a service agreement for recurring maintenance. The asset record is what every one of those later calls reads from.

Because the split is how far you carry the asset — not a duplicate record tree — an installer can start by just booking jobs and add the equipment and warranty layer as the service side of the business grows.

Built for any size. A single-truck installer recording a handful of units a week and a multi-crew operation running deliveries and multi-day installs across a region run on the same backbone. The install Job, the Equipment asset, and the Warranty are there whether you install one unit or fifty a day.

Built on the customization engine

Everything above is built from the same engine that powers the rest of FieldCamp — nothing here is a one-off feature.

The install lifecycle is the core Job and its stages and workflows; the installed unit and its coverage are custom objects and fields — Equipment and Warranties — and the optional install project is one more; and each record page is assembled from building blocks.

That means the model is a starting point, not a ceiling: add your own fields to the asset, rename the install stages, or arrange each page to match how your shop runs.

A couple of honest limits. A custom object like Equipment or Warranty does not auto-number its records the way Jobs and Invoices do, so a registration or policy number is entered by hand.

And "alert me 30 days before this warranty lapses" is a time-based rule that belongs to FieldCamp's separate workflow automation product — the record stores and shows the date, the proactive reminder is configured alongside it.

Jobs

The install work order — one-off or multi-day, with line items, crews, and the draft-to-paid lifecycle.

Equipment

The installed unit as a serviceable asset — model, serial, install date, and a service history.

Warranties

The coverage on what you installed — provider, what it covers, and when it runs out.

Estimates & Invoices

The Good / Better / Best quote for the model and upgrades, and the invoice that follows.

Custom objects & fields

How the installed-asset and warranty records are built on FieldCamp's engine.

Coming from Jobber

Most installers on Jobber can bring their structure into FieldCamp directly. The records you run an install on — the client, the quote, the job, the visits, the invoice — line up almost one for one.

The job side maps cleanly. What FieldCamp adds on top is the installed unit itself, tracked as an asset with its own warranty, so the relationship does not end when the install does.

In Jobber	In FieldCamp	Notes
Client	Customers	The homeowner or business, with separate property and billing addresses on one record.
Property	The customer's service address — or a Property as a custom object when one client has several sites	A single-site install rides on the customer's address; model it as its own record when a client owns multiple locations.
Request	Requests	The inbound inquiry or online booking, with one-click convert to a quote, job, or invoice.
Quote	Estimates & Invoices	Quoting with Good / Better / Best options, deposits, and approval.
Job (one-off or multi-day)	Jobs	The install work order — one-off for a drop-in, multi-day for a larger install.
Visit	Visits	Each trip to the site, with crew assignment, check-in location, photos, and a signature gate.
Invoice	Estimates & Invoices	The bill that follows the job, with partial and full payments and overdue tracking.
Products & Services	Price Book	The units and labor with cost and price, plus truck stock and vendor pricing.
Team	Team Members	Carry skills and service areas, and are assigned to jobs and visits.

Jobber covers the install job, the quote, and the bill. What it does not hold as a record is the unit you installed.

In FieldCamp that unit becomes Equipment — a single asset with its model, serial number, and install date — and its coverage is tracked as a Warranty on it, so the next call already knows what is on site and whether it is still covered.

What you gain. In Jobber the structure is set for you.

In FieldCamp every record is yours to rename, extend, restage, and relayout with custom objects and fields and your own stages and workflows — so you can match your old setup first and then add the asset and warranty layer on top.

The move is near one for one for the job itself — the client, the quote, the visits, and the invoice all have a direct home.

The difference is what comes after the install: FieldCamp tracks the installed unit as an Equipment asset and its Warranty as records, which Jobber does not keep as assets.

That is the layer that turns a closed-out install into a unit you can come back to and service for years.