FieldCampService Agreements — Recurring Contracts | FieldCamp
The FieldCamp Service Agreement record holds recurring service contracts and maintenance plans. See its fields, how it connects to Customers, Jobs, and Visits.
A Service Agreement is the recurring contract behind a maintenance plan — a quarterly HVAC tune-up, a monthly pest-control route, an annual fire-safety inspection.
It captures the standing terms you have agreed with a customer and the language that should appear on the paperwork that bills against it.
Because the same agreement carries from one billing cycle to the next, it is the backbone of recurring revenue: the work it covers comes back on a schedule, and each round of work is run as a recurring Job that breaks down into the Visits your crews actually drive to.
FieldCamp works for any size operation, from a single-truck shop with a handful of plans to a multi-location franchise running thousands, and for residential or commercial work alike.
Service Agreements are not part of the standard day-one set of records. They are added through customization or an industry setup, alongside the core Customers, Jobs, and Visits that every account ships with.
The terms language an agreement holds is what surfaces on Estimates and Invoices through the Contract section of those records.
What a Service Agreement captures
A Service Agreement is a reusable contract you define once and apply to the documents that bill recurring work. It holds a name, the full contract text, and a few flags that control where it is used by default.
The table below lists what an agreement carries.
| Field | What it is |
|---|---|
| Name | The label for the agreement — for example "Annual Maintenance Plan" or "Quarterly Service Contract". |
| Contract text | The full terms and conditions language of the agreement, shown to the customer on the documents that use it. |
| Default for estimates | Marks this agreement as the one applied to new estimates automatically. |
| Default for invoices | Marks this agreement as the one applied to new invoices automatically. |
| Master agreement | Flags the agreement as your primary, standing contract. |
| Order | The position of the agreement in your list, so the ones you reach for most sit at the top. |
| Status | Whether the agreement is active and available to apply, or set aside. |
Keep one agreement marked as the default for estimates and one as the default for invoices. New documents pick those up without anyone choosing a contract by hand, which keeps your recurring billing consistent across every plan and every location.
How Service Agreements connect
A Service Agreement is owned by your organization, not by a single customer — you define it once and reuse it across every plan that shares the same terms.
It connects to the work indirectly: the recurring Job that delivers a maintenance plan generates the repeat Visits your crews drive to, and the Estimates and Invoices that bill that work reference the agreement for their terms language.
The diagram below shows how those records relate.
Read the diagram from two directions. From the work side, a Customer has recurring Jobs, and a recurring Job is scheduled as the individual Visits that make up the plan — the quarterly stops, the monthly routes.
From the billing side, the Estimates and Invoices raised for that customer reference the Service Agreement so its terms appear on the paperwork. The solid lines are ownership and scheduling; the dotted lines mean an Estimate or Invoice draws its contract terms from the agreement.
One Service Agreement can supply its terms to many Estimates and many Invoices.
That is the point of defining it once — every document that bills a plan on those terms points back to the same agreement, so a change to the language lives in a single place.
On the Service Agreement record
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 contract text you write on a Service Agreement is what your customers read. It reaches them through the Contract section that sits on Estimate and Invoice pages, below the line items and alongside the Terms & Conditions section.
On those documents you pick which agreement applies, and its terms render in place — no retyping the same language onto every quote and bill.
Because an agreement is a reusable piece of contract language rather than a full record page of its own, you manage the agreements themselves in one list: name them, write their terms, set the defaults and the master flag, and reorder them so your go-to plans are first.
From there they are ready to drop onto any document that bills the recurring work.
Make it your own
A Service Agreement gives you the standing terms; the recurring Job and its Visits give you the work those terms cover. You can shape both sides to your business:
Write the agreements your plans actually use — an annual plan, a quarterly contract, a commercial master agreement — and set which one is the default for new estimates and which for new invoices.
Set up the recurring Jobs that deliver each plan, and let them generate the repeat Visits on the cadence you serve — monthly, quarterly, yearly, or on your own pattern.
Add custom fields and your own stages to the records that run the work, so an agreement's renewal date, plan tier, or coverage details live exactly where your team looks for them.
The people and companies you serve. A Customer owns the recurring Jobs and the Estimates and Invoices that bill a maintenance plan.
The work behind a plan. A recurring Job repeats on a schedule and generates the Visits that deliver the service.
Each trip to the site. A recurring Job breaks down into the individual Visits your crews complete on the plan's cadence.
Rename, reorder, add, or remove the stages the work moves through, and add the custom fields a maintenance program needs.
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.
Related guides
Hands-on, step-by-step guides from the rest of the FieldCamp documentation.
Equipment — The Assets You Service | FieldCamp
The FieldCamp Equipment record tracks the units you install and service — model, serial number, install date, warranty — tied to a customer and visits.
Chemicals — Track Every Application | FieldCamp
How a pest-control business tracks chemicals and applications as a custom object in FieldCamp — product, EPA number, rate, target pest, areas treated.