FieldCampJobs — The Work Order Record | FieldCamp
The FieldCamp Jobs record is the work order at the center of field service. See its fields, how it links to Visits, Invoices, and Customers, and its lifecycle.
A Job is the work order at the center of a field service business.
It represents a piece of work for one customer — a one-off repair, a multi-day install, or a recurring maintenance visit — and it ties together everything that work touches: the customer it is for, the team assigned to it, the line items it is priced from, the visits that carry it out in the field, and the invoice that bills it.
Every new FieldCamp account ships with the Jobs record already enabled, connected to the other core records, and running a default workflow, so a job can move from scheduled to invoiced to paid without any setup.
From there, the record bends to your business: you can add your own fields, redefine the stages, and rearrange the job page to match how your crews actually work.
What a Job captures
The Job page renders a focused, work-order-oriented set of fields. They group into a few natural categories — identity and routing, scheduling, the customer and site, pricing and money, and the field record.
The table below lists the fields that appear on a Job out of the box.
Identity and routing
| Field | What it is |
|---|---|
| Job number | The work order's identifier. |
| Job type | One-off, Recurring, or Multi-day. Required, and it determines how visits are generated. |
| Status | Where the job is in its workflow (Draft, Scheduled, In Progress, and so on). |
| Source | Where the job came from — direct, website, referral, AI agent, from an estimate, or from a request. |
| Priority | Low, medium, or high. |
| Assigned to | The team members responsible for the job. |
| PO number | The customer's purchase order reference. |
| Category | A free-text grouping for the job. |
Customer and site
| Field | What it is |
|---|---|
| Client | The customer the work is for. Required. |
| Job address | Where the work happens. |
| Job phone | The contact number for the site. |
Scheduling
| Field | What it is |
|---|---|
| Start | When the job begins. |
| End | When the job ends. |
| Schedule later | Marks the job to be scheduled at a future point. |
| Any time | The job is not tied to a specific time of day. |
| Recurrence | The repeat pattern for a recurring job. |
| Skills | Skills needed to do the work. |
| Equipment | Equipment needed for the work. |
Pricing and money
| Field | What it is |
|---|---|
| Subtotal | The total of the line items before discount and tax. |
| Discount | An amount taken off the subtotal. |
| Tax | Tax applied to the job. |
| Total | The full amount owed. |
| Required deposit | A deposit requested before work proceeds. |
| Balance | What remains to be paid. Read-only. |
| Amount paid | What has been paid so far. Read-only. |
| Labor cost | The labor portion of the job's cost. |
| Material cost | The materials portion of the job's cost. |
| Completion | How far along the job is, as a percentage. Read-only. |
| Line items | The priced products and services on the job, drawn from the Price Book. Read-only. |
Notes and the field record
| Field | What it is |
|---|---|
| Job instructions | Instructions for the crew, visible on the work record. |
| Internal notes | Notes for your team that stay internal. |
| Signature | A captured customer signature. |
| Signer name | Who signed. |
The fields above are the ones the Job page shows.
FieldCamp also keeps additional details behind the scenes for a job — such as service duration, billing type, and the estimate a job was created from — that power scheduling and billing without appearing as editable fields on the page.
How a Job connects
A Job sits at the hub of the field service data model. It belongs to one customer, is carried out as one or more visits, can be billed on one or more invoices, and is priced from the Price Book.
The diagram below shows the records a Job connects to directly.
Read the connections outward from the Job:
- One Customer can have many Jobs, but each Job is for exactly one customer.
- One Job is carried out as one or more Visits — the individual trips to the site.
- One Job can be billed on one or more Invoices, and can carry its own Tasks.
- A Job draws its line items from the Price Book, can have many Team Members assigned, and can reference the Equipment and Job Forms the work needs.
- A Job can be created from an Estimate and can hold a Deposit.
Because a Job is carried out through Visits, the field record lives on the Visit and rolls up to the Job. See Visits for how trips to the site are scheduled, staffed, and tracked.
The Job lifecycle
Every Job moves through a default workflow of nine stages, from Draft through to Paid or Closed. Some moves between stages are manual actions a dispatcher takes; others happen automatically as the work in the field progresses.
The flow below shows the default stages and the named actions that move a job between them.
Each stage has a clear meaning, and several have automations that fire as work moves through the field:
Draft
A new job starts in Draft. It must name a customer and a job type before it can move forward.
When the job is saved, FieldCamp automatically generates the visits that will carry it out, based on the job type — a one-off job gets a single visit, a multi-day job gets one visit per day, and a recurring job gets visits from its recurrence pattern.
Jobs can be created directly, or converted from a request or an estimate, with the source recorded on the job.
Scheduled
From Draft, the Schedule action moves the job to Scheduled. Team members are assigned and dates are set. A job marked to schedule later starts with an unscheduled placeholder visit until a time is set.
In Progress
The Start Work action moves a scheduled job to In Progress.
FieldCamp also moves the job to In Progress automatically as soon as any of its visits is on the way, has arrived, or is underway, so the job's status keeps up with the field without a dispatcher updating it.
On Hold
A job can be put on hold from Draft, Scheduled, or In Progress with Put On Hold, then returned to the flow with Resume, Schedule, or Back to Draft.
Completed
The Complete action moves a job to Completed and asks for a confirmation first. FieldCamp also completes a job automatically once all of its visits are completed. Customer sign-off is captured on the job through the signature field.
Invoiced
From Completed, the Invoice action — or the Create Invoice action on the job — generates an invoice and moves the job to Invoiced. A job can be reverted to Completed if needed.
Paid
When the resulting invoice is paid in full, FieldCamp moves the job to Paid automatically. Paid is reached through the invoice being settled rather than by a manual move on the job.
Closed and Cancelled
Close Job can be run from any stage; closing a job cancels any of its visits that are not already completed or cancelled, and writes the change to history. A job can also be cancelled from most active stages, and a cancelled job can be reopened as a draft or rescheduled. Both Closed and Cancelled are final.
Every move between stages is recorded, so the History tab on a job always shows who changed what and when.
On the Job page
This page comes with an out-of-the-box layout, built from building blocks. If you want to customize the blocks — reorder, add, hide, or group the sections below — you can. See Record layouts & building blocks.
The Job page is organized into tabs, with the Details tab open first. The Details tab has a wide main column for the work itself and a sidebar for the at-a-glance facts.
The other tabs gather the related records and the job's paper trail.
Details
The main column reads top to bottom as the work record:
- Header — the job number, a status pill, and the job's actions: Add Visit, Add Task, Duplicate Job, Generate Invoice, Collect Payment, Collect Signature, Manage Job Forms, and Close Job. Most actions are hidden once a job is closed or cancelled.
- At a glance — the key numbers: total value, number of visits, balance, and amount paid.
- AI summary — a written summary of the job.
- Scheduling — start and end, job type, timing options, duration, recurrence, the visits, and the job's invoicing and billing settings.
- Job instructions — instructions for the crew.
- Line items — the priced products and services on the job.
- Loadout sheet and an inventory shortage alert — what to bring and a warning when stock is short.
- Payment summary and customer signature — the money breakdown and the captured sign-off.
- Custom properties — any fields you have added to the Job.
The sidebar carries a Details group (job type, source, priority, assigned team, customer, job number, PO number, phone, category, skills, equipment), the job Address, and a Financial summary (subtotal, discount, tax, required deposit, balance, and total).
Visits
A table of the job's visits showing visit number, scheduled time, end time, the assigned team, and status.
Logs
A visit log of work and cost on the job. This tab is available with the job logs add-on.
Assets
Three related tables — the job's Invoices, Estimates, and Tasks.
Attachments
Files attached to the job.
Notes
The job's internal notes, kept separate from the crew-facing instructions.
History
A timeline of activity on the job, including every stage change.
Make it your own
The Job record is the starting point, not the limit. Each part of the record can be tailored without disturbing the connections underneath.
Add your own fields to the Job and they appear in the Custom properties section. An HVAC business can add a refrigerant type or a warranty date; a pest-control company can add a treatment plan.
Rename, reorder, add, or remove the job stages so the workflow matches your process — for example a "Quality Check" stage between Completed and Invoiced.
Rearrange the building blocks on the Job page, add sections, or move fields between the main column and the sidebar.
Built for any size
The same Job record serves a single-truck operator and a multi-location franchise. A one-person plumbing business uses the job record as-is: a customer, a one-off job, a visit, an invoice.
A growing electrical contractor adds a few custom fields and an extra stage. A multi-location or franchise operation runs the same job workflow across every location, with each location's jobs kept under its own structure.
Residential or commercial, the record is the same set of building blocks — ready on day one, and yours to tailor.
Related records
The customer a job is for. One customer can have many jobs.
The trips to the site that carry a job out. A job is scheduled as one or more visits.
A job can be created from an estimate and billed on an invoice; paying the invoice moves the job to Paid.
The catalog a job's line items are drawn from.
The people assigned to a job and staffing its visits.
See also
More in the FieldCamp data model.
How the core records connect, and how to make them your own.
The assets you install and service, tied to a customer.
Recurring contracts and maintenance plans.
The geographic zones your team covers.
Related guides
Hands-on, step-by-step guides from the rest of the FieldCamp documentation.
Customers — The Core Customer Record | FieldCamp
The FieldCamp Customers record holds every person and company you serve. See its fields, how it connects to Jobs, Estimates, and Invoices, and its lifecycle.
Visits — The On-Site Appointment Record | FieldCamp
The FieldCamp Visits record is the scheduled appointment where work happens on site. See its fields, how it links to Jobs and team members, and its lifecycle.