FieldCampVisits — 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.
A Visit is a single scheduled appointment where the work actually happens on site. Every Visit belongs to a Job: the Job is the work to be done, and its Visits are the individual trips that carry it out in the field.
A one-off Job has a single Visit, a multi-day Job has one Visit per day, and a recurring Job has a Visit for each occurrence.
Each Visit holds its own schedule, the team members who staff it, the time and cost logged against it, and the sign-off captured when the work is finished — and as the field crew moves through the appointment, the Visit keeps the parent Job's status in step automatically.
Every new FieldCamp account ships with the Visits record already enabled, connected to Jobs, and running a default workflow, so an appointment can move from scheduled to completed without any setup.
From there, the record bends to your business: you can add your own fields, redefine the stages, and rearrange the visit page to match how your crews work.
What a Visit captures
The Visit page shows a focused set of fields built around one appointment — its schedule, who is on it, and what was done. The table below lists the fields that appear on a Visit out of the box.
| Field | What it is |
|---|---|
| Status | Where the visit is in its workflow — Scheduled, In Transit, Arrived, Work in Progress, and so on. |
| Job | The Job this visit belongs to. Required, and it links the visit back to its parent work order. |
| Visit number | The visit's running number within its Job — 1, 2, 3, and so on. |
| Start date | When the appointment is scheduled to begin. |
| End date | When the appointment is scheduled to end. |
| Team | The team members staffing this visit. |
| Duration | How long the appointment is expected to take. |
| Priority | Low, medium, high, or urgent. |
| Schedule later | Marks the visit to be scheduled at a future point rather than now. |
| Any time | The visit is not tied to a specific time of day. |
| Notes | Instructions and notes for the appointment. |
| Signature | The customer sign-off captured when the work is finished. |
The fields above are the ones the Visit page shows.
FieldCamp also tracks details behind the scenes for each visit — such as travel, arrival, and completion timestamps, captured location, logged hours, and billing figures — that power the field record and roll up to the Job without appearing as editable fields on the page.
How Visits connect
A Visit sits one level below the Job in the data model. It belongs to exactly one Job, is staffed by one or more team members, gathers its own time-and-cost logs, and carries the Job Forms completed on site.
The diagram below shows the records a Visit connects to directly.
Read the connections outward from the Visit:
- One Job is carried out as one or more Visits, but each Visit belongs to exactly one Job.
- One Visit can be staffed by many team members, and a team member works many visits.
- One Visit gathers many Visit logs — the time, mileage, and cost recorded for the work done on that appointment.
- A Visit carries the Job Forms completed on site, with the answers stored against the visit.
Because the field record lives on the Visit and rolls up to the Job, the Job's totals — logged hours, visit count, balance — reflect what happens across its visits. See Jobs for how the parent work order ties everything together.
The Visit lifecycle
Every Visit moves through a default workflow that follows a crew across an appointment, from scheduled through arrival to completion. Some moves are manual actions a dispatcher or technician takes; others record the field crew's real progress.
The flow below shows the default stages and the named actions that move a visit between them.
Each stage has a clear meaning, and several record what the crew is doing in the field:
- Unscheduled — a placeholder appointment with no time set yet, created when a job is marked to schedule later. The Schedule action gives it a date and moves it to Scheduled.
- Scheduled — the appointment has a date, time, and assigned team. This is where most visits start. The Go for Visit action sends the crew on its way.
- In Transit — the crew is on the way to the site. FieldCamp records the travel start time and starting location when the visit enters this stage.
- Arrived — the crew has reached the site, with the arrival time captured. The Start Work action begins the appointment.
- Work in Progress — the work is underway. It can be paused and resumed as needed, and FieldCamp keeps a record of every pause and resume so the logged time stays accurate.
- Paused — work is temporarily stopped. Resume Visit returns it to Work in Progress.
- Completed — the appointment is finished. The Finish Work action records the completion time and asks for a customer signature and a confirmation before closing out the visit.
- Cancelled — the appointment will not happen. A visit can be cancelled from most active stages, and this is a final stage.
Two automations connect the Visit's progress to the Job above it.
As soon as any visit on a job is in transit, arrived, or in progress, FieldCamp moves the parent Job to In Progress — so the job's status keeps up with the field without a dispatcher updating it.
And once every visit on a job is completed, FieldCamp completes the Job automatically.
The check-in and check-out times that drive the field record are captured as the visit moves through these stages — travel start when the crew leaves, arrival when it reaches the site, and completion when the work is finished — so the logged hours and the job's progress reflect what really happened, not a manual estimate.
On the Visit 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 Visit page is organized into tabs, with the Info tab open first. The Info tab has a wide main column for the appointment itself and a sidebar for the at-a-glance facts.
The other tabs gather the field record and the visit's paper trail.
The Info tab reads top to bottom as the appointment record:
- Header — the visit number, a status pill, a link back to the parent Job, and the visit's actions: Mark Confirmed, Mark Extra Visit, Call, SMS, and Delete.
- At a glance — the key numbers: logged hours, visit income, photos, and forms completed.
- AI summary — a written summary of the visit.
- Scheduling — start, end, and the any-time option.
- Instructions — notes and directions for the appointment.
- Line items — the priced products and services on the visit, shown read-only.
- Voice notes — audio recordings attached to the visit.
- Payment summary — the bare money totals for the appointment.
- Location — the address, pulled from the parent Job.
- Customer signature — the captured sign-off, shown once the visit is completed.
- Custom properties — any fields you have added to the Visit.
The sidebar carries a Schedule group (priority, confirmed, extra-visit, and the assigned team) and a Contact group linking up to the parent Job.
The remaining tabs hold the rest of the record: Attachments for files, Logs for the editable visit log of time and cost, Job Forms for the forms completed on site, Assets for the related invoices, and History for a timeline of activity on the visit.
The Logs and Job Forms tabs depend on add-ons. When an add-on is not enabled, the tab shows a short prompt to connect it rather than the block itself.
Make it your own
The Visit record is the starting point, not the limit. Each part of the record can be tailored without disturbing the connection to the Job underneath.
The same Visit record serves a single-truck operator and a multi-location franchise, residential or commercial — a one-person plumbing business uses the visit record as-is, while a growing contractor or a multi-location operation adds the fields, stages, and screens each site needs without rebuilding the model.
The parent work order a visit belongs to. A job is carried out as one or more visits, and the visits keep the job's status in step.
Add your own fields to the Visit and they appear in the Custom properties section. An HVAC business can record a refrigerant reading; a pest-control company can log a treatment applied on site.
Rename, reorder, add, or remove the visit stages so the field workflow matches how your crews actually move through an appointment.
Rearrange the building blocks on the Visit page, add sections, or move fields between the main column and the sidebar.
See also
More in the FieldCamp data model.
How the core records connect, and how to make them your own.
The geographic zones your team covers.
The assets you install and service, tied to a customer.
Related guides
Hands-on, step-by-step guides from the rest of the FieldCamp documentation.
Jobs — 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.
Requests — The Lead Record | FieldCamp
The FieldCamp Requests record captures incoming service inquiries and leads. See its fields, sales pipeline stages, and how a request converts to work.