Pest Control Data Model — Setup | FieldCamp

How a pest control business runs in FieldCamp — recurring routes, bait stations, service agreements, and pesticide records on one connected set of records.

FieldCamp runs a pest control business on one connected set of records that works on day one and bends to how your routes actually run.

A property owner calls, you quote the plan, you schedule a recurring route, a technician services every device and logs every application, you bill, and you bring them back next quarter — that chain is modeled directly.

The core records carry most of it; a small specialized layer adds the parts pest control needs that no other trade does.

FieldCamp works for any size, from a single-truck operator to a multi-location franchise, residential or commercial — and everything here can be tailored.

What the core already gives you

About 70% of a pest control workflow is already covered by FieldCamp's core records, with no customization.

Customers hold the residential homeowner or commercial account, with separate property and billing addresses and a preferred technician built in.
Requests capture the inbound inquiry, the inspection booking, the quote tracking, and the win or loss before work begins.
Jobs set to recurring auto-generate the route Visits on a monthly, quarterly, or custom cadence — the visit history rolls up to the job.
Each Visit carries its own schedule, assigned team members, check-in and check-out location, photos, and a signature on completion.
Estimates & Invoices handle Good / Better / Best plan tiers, deposits, recurring billing, and the paid, partial, and overdue lifecycle.
The Price Book holds the catalog — initial, quarterly, and termite services, plus chemicals as priced products — with cost, price, and taxable flags.
Service Areas cluster routes by territory, and applicator licenses ride on team-member skills for assignment.

The pesticide application record itself stays on the core too.

It is structured on-site capture, so it is a job form attached to the recurring job, with answers stored on each visit — product name, registration number, quantity and unit, dilution rate, target pest, treatment location, date, and applicator sign-off.

The same form pattern covers the IPM inspection and conducive-conditions checklist with customer sign-off.

The pesticide application record and the IPM inspection are forms, not separate records. They attach to the recurring job, capture on site, and store their answers on the visit — exactly what holds the federal and state recordkeeping a pest control business has to keep.

What Pest Control adds

Two needs in pest control cannot be expressed as fields on a core record, so the setup adds them as custom objects built on FieldCamp's customization engine — each with its own fields, its own links to the core records, its own workflow, and its own record page assembled from building blocks.

A third object, the per-visit reading, sits under the device so each station carries a full service history rather than a single overwritten value.

Service Agreement — the recurring plan

A Service Agreement is the commercial contract that governs the plan. The recurring Job handles the visit cadence; the agreement is the term, the renewal, and the covered scope as a record in its own right.

It belongs to one Customer and governs many Jobs.

Field	What it holds
Account Type	Residential or commercial
Plan Frequency	Monthly, quarterly, bi-monthly, annual, or one-time
Covered Pests	One or more of ants, rodents, termites, roaches, mosquitoes, and more
Start Date / Renewal Date	When the plan begins and when it comes up for renewal
Term	Length of the plan in months
Plan Price	The agreed plan amount
Auto-Renew	Whether the plan renews on its own
Warranty / Guarantee Terms	The warranty or guarantee language
Signed Agreement	The signed plan document, attached to the record

Its record page is built from a header, a status banner, the plan fields, a related table of the Jobs under the plan, a contract picker and terms-and-conditions section, the signed file, and a timeline.

Device — bait station, trap, or monitor

A Device is the long-lived physical asset installed at a property — a rodent bait station, snap trap, glue board, insect monitor, or fly light. Each has its own identity, location, and lifecycle.

A Device belongs to a Customer's property and can link to the Service Agreement that scopes it.

Field	What it holds
Device Number / Barcode	The station's barcode or QR value, stored on the record
Device Type	Rodent bait station, snap trap, glue board, insect monitor, or fly light
Location / Zone	The area or zone where the device sits
Install Date	When the device was placed
Bait / Product Inside	Linked to the Price Book product loaded in the device
Last Serviced	The most recent service date
Notes	Free-form notes on the device

Its record page is built from a header, the device fields, a breadcrumb back to the Customer, a related table and service history of its readings, a location map, files and a photo gallery, and a timeline.

Device Service Log — the per-visit reading

A Device Service Log is one reading captured each time a technician services a device.

It is a child of the Device and links to the Visit it was captured on, so every station builds a complete, dated service history instead of a single overwritten status.

Field	What it holds
Service Date	When the reading was taken
Activity Level	None, low, moderate, or high
Capture / Catch Count	How many pests were caught
Bait Consumed %	Share of bait consumed, validated between 0 and 100
Condition	Ok, damaged, missing, or blocked
Action Taken	One or more of rebaited, cleaned, relocated, replaced, or none
Serviced By	The team member who serviced the device
Photo	A photo of the device and its condition

The reading is a separate record per service event, not a field that overwrites itself. That is what lets a commercial site trend activity across quarters and prove every station was serviced on every visit.

How these records connect

The specialized objects hang off the core records, not beside them.

A Customer holds a Service Agreement, a recurring Job, and the Devices installed at the property. The agreement governs the Jobs and scopes the Devices.

Each Job is scheduled as Visits, and each Visit produces a Device Service Log reading for every device it touches.

The agreement lifecycle

A Service Agreement moves through a renewal workflow. It opens as a draft, becomes active when the plan starts, and is flagged for renewal as its renewal date approaches — at which point an automation can send a renewal notification.

From there it renews, or it lapses or is cancelled.

The Device runs its own short workflow alongside it: a device is active, moves to needs-service when a reading flags it, and returns to active once serviced.

Damaged or removed are side routes, and on a commercial account the return-to-active step can require a service photo as proof.

Residential vs commercial

The model is one set of objects. An account-type field switches the behavior — there is no separate build for homes versus sites.

Residential

Few or no devices — a perimeter spray and maybe one or two exterior rodent stations, so the Device object is light or unused. The plan is a simple quarterly or monthly auto-renew, the service ticket is a short form, and a customer signature on completion is typical.

Commercial

Devices are the heart of the job — tens to hundreds of bait stations and traps per site, each serviced and logged every visit, with activity trended across quarters. The agreement carries site-specific terms and a longer duration, the IPM form is heavier for food-grade and audit accounts, and a service photo can be required as proof of each device deficiency.

The same agreement, device, and reading records serve both. Commercial accounts simply populate more fields, place more devices, and turn on the photo requirement that residential leaves off.

Built for any size. A one-truck operator and a multi-location franchise run on the same records. The recurring route, the agreement, the devices, and the per-visit readings are there whether you service one home a day or a hundred commercial sites a quarter.

Built on the customization engine

Everything in the specialized layer is built from the same toolkit every FieldCamp account has.

The Service Agreement, Device, and Device Service Log are custom objects and fields; the renewal and device workflows are stages and workflows you can rename or reroute; and each record page is arranged from a library of building blocks in record layouts.

Add your own fields, adjust the stages, and rearrange the pages so the model matches how your routes actually run.

Jobs

The recurring route at the center of the flow — line items, scheduling, and the visits it generates.

Visits

The field appointments under a route, with dispatch lifecycle, signatures, photos, and on-site forms.

Estimates & Invoices

Plan-tier quotes and the invoices and payments that follow.

Custom objects & fields

How the Service Agreement, Device, and reading records are built.

Coming from FieldRoutes

Most pest control shops on FieldRoutes can bring their structure into FieldCamp directly — customers, the service locations under them, the recurring plans, the routes, the appointments, the bait stations, and the chemical catalog all have a home here.

The difference is that in FieldCamp you own and shape the model, rather than fitting your shop to a fixed one.

In FieldRoutes	In FieldCamp	Notes
Customer	Customers	The party responsible for billing. FieldCamp keeps property, service, and billing addresses on one record, with a preferred technician built in.
Service location	A Property — as a custom object under the customer, or the customer's service address for a single-site home	FieldRoutes' one-customer-to-many-locations split; model it as its own record when an account has several sites.
Subscription / Service plan / Bundle	Service Agreements	The recurring contract — frequency, covered pests, term, renewal, and plan price — that brings the customer back each cycle.
Route	Service Areas	Territory that clusters recurring routes and drives area-based scheduling and assignment.
Work order	Jobs	The recurring job set to monthly, quarterly, or a custom cadence.
Appointment	Visits	Each scheduled stop on a route, with dispatch, check-in, photos, and sign-off.
Device / Bait station / Monitor	Bait Stations	Rodent stations, traps, and monitors as long-lived assets, each with its own per-visit service history.
Chemical / Pesticide usage	Chemicals	Products in the catalog, with the per-application record captured on the visit form.
Inventory (pesticides, materials)	Price Book	Initial, recurring, and termite services plus chemicals as priced products, with cost, price, and taxable flags.
Technician	Team Members	Carry applicator licenses as skills and territory as service areas.
Invoice	Estimates & Invoices	Plan-tier quotes, deposits, and the paid, partial, and overdue lifecycle.
Payment / AutoPay	Recorded on the Invoice	Partial and full payments, with overdue tracking.
Forms (WDO, IPM)	Job Forms	Pesticide application, inspection, and conducive-conditions forms that live on the visit for structured on-site capture and sign-off.
Tags	Custom fields	Add a select or multi-select field to label and filter records.

What you gain. In FieldRoutes the structure is fixed — the objects, their fields, and how they relate are set for you.

In FieldCamp every one of those records is yours to rename, extend, restage, and relayout, so you can match your old setup first and then go past it with custom objects & fields and your own stages & workflows.

One honest difference. FieldRoutes ships a built-in recurring billing and AutoPay engine plus route optimization that sequences each day's stops on its own.

FieldCamp models the plan itself as a Service Agreement that schedules the recurring Job and carries the renewal date and plan price; the recurring billing runs through the standard invoice flow, and routes are organized through Service Areas rather than a turn-by-turn optimizer.

If automatic billing cycles or daily route sequencing are central to how you run, plan those parts of the move deliberately.