FieldCampData Model — How FieldCamp Is Built | FieldCamp
The FieldCamp data model: connected core records that work on day one, plus full customization of objects, fields, stages, and record layouts for any business.
New to FieldCamp? Start with Getting Started to set up and use the app. This section explains how it all works underneath, and how to make it yours.
FieldCamp gives every account a connected set of core records — Customers, Jobs, Visits, Requests, Estimates, Invoices, the Price Book, and Team Members — that work the moment you sign up.
They are already linked together the way a field service business runs, so a request can become an estimate, an estimate can become a scheduled job, that job becomes field visits, and the visits become an invoice.
On top of that working foundation, everything bends to your business: you can add your own objects and fields, define your own stages, set up automations, and arrange each record page from a library of building blocks.
This page is the map of how those pieces fit together.
The big picture
A brand-new FieldCamp org starts with a set of core records that are already connected. The diagram below shows the spine of the data model — the records you get on day one and how they relate to each other.
Each record links to the next so that work moves through your business without re-entering anything.
A Customer can submit Requests and have Jobs done; a Request can be turned into an Estimate, a Job, or an Invoice; a Job is carried out as one or more Visits in the field; the Job and its Visits are priced from the Price Book and assigned to Team Members; and the work is billed on an Invoice that receives Payments.
Read the same model as a flow — how a new lead becomes paid work — and the records line up into a single path from first contact to payment.
A Request can be quoted into an Estimate, turned straight into a Job, or billed directly as an Invoice. An approved Estimate also becomes a Job.
The Job is scheduled as Visits in the field, and once all of its visits are completed the Job is ready to bill. The resulting Invoice, once paid, marks the Job paid in return — closing the loop.
How to read this diagram
The notation is the same idea Salesforce uses for its data model, written in plain terms. The symbols at the ends of each line tell you how many of one record can relate to another.
| Notation | Meaning | Example |
|---|---|---|
| One-to-many (a single line branching to many) | One record on the left can have many on the right | One Customer can have many Jobs |
| Many-to-many (branches on both ends) | Records on both sides can have many of each other | One Job can have many Team Members, and a team member works many jobs |
| Conversion (a dotted line) | One record can be turned into another | A Request converts into an Estimate, a Job, or an Invoice |
When you read the diagram, follow a line from a Customer outward: a Customer submits Requests, requests work as Jobs, and is billed on Estimates and Invoices. Each of those records then has its own connections, which fan out into the rest of the model.
FieldCamp stores Estimates and Invoices as two faces of the same kind of record. They share the same fields, line items, and billing building blocks, which is why both connect to Customers and Payments in the same way.
Layer 1 — the records you get on day one
Every new account ships with a ready-to-use set of core records, already enabled and connected. You do not configure them to get started; they work out of the box.
The cards below link to the detailed page for each core record.
The people and companies you serve. A Customer owns its Requests, Jobs, Estimates, and Invoices, and carries contact, address, and account details.
The work to be done — a one-off, multi-day, or recurring job tied to a Customer, priced from the Price Book, and assigned to a team.
A single trip to the site. A Job is carried out as one or more Visits, each scheduled, staffed by team members, and tracked through the field.
Incoming work and inquiries before they become jobs. A Request can be inspected, quoted, and converted into an Estimate, Job, or Invoice.
Quotes and bills for a Customer. Estimates move from draft to sent to approved; Invoices move from unpaid to paid and receive payments.
Your catalog of services and products with prices and costs. Job, Estimate, and Invoice line items are drawn from the Price Book.
The people who do the work. Team members are assigned to Jobs and staff individual Visits.
These records come pre-wired with the connections shown in the big-picture diagram, sensible default fields, and default stages so that a request can flow all the way through to a paid invoice without any setup.
A few records that some businesses expect — such as tasks, equipment, service agreements, and service areas — are not part of the standard day-one set. They are added through customization or an industry setup rather than shipping by default.
For example, the HVAC industry setup layers a Property, Unit, and Equipment hierarchy on top of the standard Job and Visit records.
Layer 2 — make it yours
The core records are the starting point, not the boundary. Every part of the model can be tailored to how your business actually works, without touching the foundation underneath.
Add your own record types alongside the core records, and add your own fields to any record. A pest-control company tracking bait stations can create an object for them; an HVAC business can add fields for refrigerant type or warranty dates.
Each record moves through stages — for example a Job runs Draft, Scheduled, In Progress, Completed, Invoiced, Paid. You can rename, reorder, add, or remove these stages so the workflow matches your process.
Set up rules so that when something happens, FieldCamp does the next thing for you. By default, when every visit on a job is completed the job moves to Completed, and when an invoice is fully paid its job moves to Paid.
Every record page is assembled from building blocks — a header, key numbers, scheduling, line items, addresses, financial summaries, and more — arranged into tabs and sections. Rearrange them, add sections, or build a layout for a custom object.
Because these four kinds of customization sit on top of the same core records, you can adapt FieldCamp gradually.
Start with the records and stages you get on day one, then add a field here, a stage there, or a whole new object as your business needs it.
Built for any size
The same data model serves a single-truck operator and a multi-location franchise. A one-person plumbing business uses the core records as-is: a Customer, a Job, a Visit, an Invoice.
A growing electrical contractor adds custom fields and a few extra stages. A multi-location or franchise operation keeps the same records and connections at every site, adding custom fields, stages, and objects where a given location needs them.
Use the core records out of the box. A Customer requests work, a Job is scheduled as a Visit, and an Invoice gets paid — no setup required.
Add custom fields, extra stages, and new objects as the business grows, without rebuilding what already works.
Run many locations on the same records and connections, tailoring the fields and stages each site needs without rebuilding the model.
Whether you run residential or commercial work, the records, fields, stages, and screens described here are the same building blocks — ready to use on day one, and yours to tailor.
See how the Jobs record captures work, connects to Visits and Invoices, and moves through its lifecycle.
See how an HVAC or plumbing business runs end to end on the FieldCamp data model.
See also
More in the FieldCamp data model.
The assets you install and service, tied to a customer.
Recurring contracts and maintenance plans.
The geographic zones your team covers.
Run many locations on the same data model.
Plain-language definitions of every term.
Related guides
Hands-on, step-by-step guides from the rest of the FieldCamp documentation.