Glossary — FieldCamp Data Model | FieldCamp

A plain-English glossary of the FieldCamp data model — records, fields, stages, and a Salesforce and ServiceTitan crosswalk for buyers migrating field service.

This is a plain-English reference for the words used across the FieldCamp data model docs — the core records every account starts with, the fields and stages that describe them, and the customization terms that let you tailor FieldCamp to any trade or size.

If you are coming from Salesforce Field Service or ServiceTitan, the crosswalk near the end maps their vocabulary to FieldCamp so you can read the rest of these docs without translating in your head.

Every FieldCamp term below is grounded in the actual data model; the Salesforce and ServiceTitan equivalents are approximate analogies to orient a migration, not claims of identical behavior.

How the model fits together

The core records are already connected the way a field service business runs.

A Customer submits Requests and has Jobs done; a Request can be turned into an Estimate, a Job, or an Invoice; a Job is carried out as Visits and billed on an Invoice.

The diagram below is a compact recap of how the records the glossary defines connect to each other.

Read the same records as a path — how a new lead becomes paid work — and the terms in this glossary line up into a single flow from first contact to payment.

A Request can be quoted into an Estimate, turned straight into a Job, or billed directly. An approved Estimate becomes a Job, the Job is carried out as Visits, and once every Visit is completed the Job is ready to bill.

Paying the resulting Invoice marks the Job paid in return. For the full picture, see the data model overview.

For the records at the center of the flow, see Jobs and Visits.

Key terms

These are the building blocks of the model — the general concepts first, then each core record.

Model concepts

Term	What it means
Record	A single saved entry — one Customer, one Job, one Invoice. The rows of your business.
Object (record type)	A kind of record, with its own fields and stages. Customers, Jobs, and Visits are each an object. You can also add your own.
Field	One piece of information on a record — a job number, a phone number, a total. Fields are grouped into sections on the record page.
Stage	A named step in a record's progress, such as a Job being Draft, Scheduled, or Completed. The set of stages for an object is its workflow.
Workflow	The full set of stages a record can move through, and the named actions that move it between them. See stages and workflows.
Automation	A rule that does the next thing for you when something happens — for example, completing a Job once all of its Visits are completed, or marking a Job paid when its Invoice is paid in full. See automations.
Building block	A reusable section of a record page — a header, a line-items table, a scheduling panel, a files list. Pages are assembled from blocks.
Record layout	How the building blocks are arranged into tabs and sections on a record page. Every object has an out-of-the-box layout you can rearrange. See record layouts.
Custom object	A record type you add alongside the core records — for example, a pest-control company creating a Bait Station object. See custom objects and fields.
Custom field	A field you add to any record. An HVAC business can add a refrigerant type or warranty date to a Job. See custom objects and fields.

Core records

Every FieldCamp account ships with these records already enabled and connected. They are the day-one foundation of the model.

Record	What it means
Customer	The person or business you do work for. One Customer can have many Requests, Jobs, Estimates, and Invoices. In FieldCamp the company and its primary contact live on the same record. See Customers.
Job	A work order — the unit of work you schedule, perform, and bill. A Job belongs to one Customer, is carried out as Visits, and is billed on an Invoice. See Jobs.
Visit	A scheduled stop on a Job — a single trip to the site. A Visit is a child of a Job and is staffed by Team Members. See Visits.
Request	An incoming work request or lead, before it becomes a Job. A Request can be inspected, quoted, and converted into an Estimate, a Job, or an Invoice. See Requests.
Estimate	A quote sent to a Customer for approval. An approved Estimate can be converted into a Job or an Invoice. See Estimates & Invoices.
Invoice	A bill issued to a Customer for completed work. An Invoice receives payments and moves from unpaid to paid. See Estimates & Invoices.
Price Book	Your catalog of the products and services you sell, each a priced item. Job, Estimate, and Invoice line items are drawn from the Price Book. See Price Book.
Team Member	A user or technician. Team members are assigned to Jobs and staff individual Visits. See Team Members.
Tax Rate	A master tax rate that is applied to a Job, Estimate, or Invoice and captured on the record when it is created.

Estimates and Invoices are two faces of the same kind of record. They share the same fields, the same line-item structure, and the same billing building blocks — which is why both connect to Customers and to payments in the same way.

This is worth knowing if you are mapping documents over from another system.

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.

When these docs mention them, they are described as custom or advanced, not as core records.

Stages you will see in these docs

Each core record that moves through a process has a default set of stages. These are the real defaults, and you can rename, reorder, add, or remove them — see stages and workflows.

Record	Default stages
Customer	New Lead, Active Client, Inactive Client, Archived
Request	New Request, Unscheduled, Overdue, Inspection Scheduled, Inspection Complete, Quote Created, Quote Sent, Converted, Lost, Cancelled, Duplicate
Job	Draft, Scheduled, In Progress, On Hold, Completed, Invoiced, Paid, Cancelled, Closed
Visit	Unscheduled, Scheduled, In Transit, Arrived, Work in Progress, Paused, Completed, Cancelled
Estimate	Draft, Sent — and an approval status of Pending, Approved, or Declined
Invoice	Unpaid, Partial, Paid, Overdue, Canceled
Price Book item	Available, Unavailable

The canonical Job lifecycle reads Draft → Scheduled → In Progress → Completed → Invoiced → Paid. The Jobs page walks through each stage and the named actions and automations that move work along.

The diagram below shows that default Job workflow with the actions that move a job between stages.

A job starts in Draft and is scheduled, started, and completed; completing a job lets you invoice it, and once the invoice is paid in full the job moves to Paid on its own.

A job can be put on hold and resumed, reopened from Completed, or cancelled, and Close Job ends it. Closed and Cancelled are both final.

Coming from Salesforce or ServiceTitan

If you are migrating, the table below maps the vocabulary you already know to FieldCamp. The FieldCamp column is authoritative.

The Salesforce and ServiceTitan columns are conceptual anchors to help you read these docs — they are approximate analogies, not assertions of identical features.

Records

FieldCamp	ServiceTitan	Salesforce	Notes
Customer	Customer	Account + Contact	FieldCamp keeps the company and its primary person on one Customer record. Salesforce splits these into Account and Contact; FieldCamp does not by default.
Request	Lead / Call Booking	Lead	An inbound, pre-qualification record. It converts into a Job, an Estimate, or an Invoice.
Job	Job	Work Order (Field Service) or Opportunity	A field-service work order. The closest single match is the ServiceTitan Job; on the Salesforce side it is nearest the Field Service Work Order, not a CRM Opportunity. Map this one with care.
Visit	Appointment	Service Appointment	A child of a Job — the scheduled stop. The ServiceTitan Appointment is the cleanest analogy.
Estimate	Estimate	Quote	A direct conceptual match on both sides.
Invoice	Invoice	Invoice or Order	A direct conceptual match. In FieldCamp it shares its underlying structure with the Estimate.
Price Book item	Pricebook Item / Service	Product	A catalog item you sell. The ServiceTitan Pricebook is the cleanest analogy.
Team Member	Technician / Employee	User	The person who does the work. No default workflow of its own.
Tax Rate	Tax Rate	Tax setting	A master rate captured onto a record when it is created.

Concepts

FieldCamp	ServiceTitan	Salesforce	Notes
Object (record type)	Custom data / forms	Custom Object	A kind of record. You can add your own beyond the core set.
Field	Custom field	Field	One piece of information on a record.
Stage / workflow	Job Status / status workflow	Stage / Path	The steps a record moves through. Per-object and fully configurable.
Named action	Status change	Path step / Stage change	A move between stages, such as a Job's Schedule or Complete action. Some are gated and ask for confirmation.
Automation	Workflow / Trigger	Flow / Process Builder	A rule that runs an action automatically when a record changes.
Record layout	Form / Page layout	Lightning Record Page	How a record page is arranged.
Building block	Form section / tile	Lightning component	A reusable section placed on a record page.
Organization	Account / Business Unit	Org	The account boundary that keeps each business's records separate. A multi-location business runs its locations inside one organization, on the same records. See multi-location.

The Salesforce and ServiceTitan columns are migration aids, not feature-parity claims.

The strongest differences to keep in mind: FieldCamp keeps a Customer's company and primary contact on one record where Salesforce splits Account and Contact; FieldCamp's Estimate and Invoice share one underlying record; and FieldCamp's Job is a field-service work order with no clean Salesforce CRM equivalent.

Field types in plain language

When you add a custom field, you choose what kind of information it holds. These are the available field types, described without code. For the full guide, see custom objects and fields.

Field type	What it holds
Text	Free-form words — a note, a name, a label.
Number	A plain number, such as a count or a reading.
Currency	A money amount.
Date	A calendar date.
Checkbox	A yes-or-no choice.
Dropdown	One choice from a fixed list.
Email	An email address.
Phone	A phone number.
Website link	A web address.
Address	A street address.
Signature	A captured signature.
Image	A picture, such as a site photo.
Link to another record	A connection to a related record, such as linking a piece of equipment to a Job.
Calculated	A value worked out automatically from other fields — a subtotal, a rolled-up count, or a looked-up value from a linked record.

Built for any size

The same vocabulary describes a single-truck operator and a multi-location operation. A one-person plumbing business uses the core records and their default stages exactly as they ship.

A growing electrical contractor adds a few custom fields and an extra stage. A multi-location business runs the same records, fields, and stages at every site, tailoring each location where it differs.

The terms in this glossary mean the same thing across all of them — which is what lets these docs describe one model that works out of the box and bends to any business. See multi-location for how the model scales.

Where to go next

Data model overview

The full picture — how the core records connect and how a lead becomes paid work.

Jobs

The work order at the center of the model, its fields, connections, and lifecycle.

Custom objects & fields

Add your own record types and fields to fit any trade.

Stages & workflows

Rename, reorder, and reshape the stages each record moves through.

Hands-on, step-by-step guides from the rest of the FieldCamp documentation.

Key concepts

The core building blocks, in plain terms.

Lead to payment

See the records in action across one flow.

Glossary — FieldCamp Data Model | FieldCamp

On this page