FieldCampChemicals — 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.
A Chemical record is one pesticide application — the product a technician used on a property, how much went down, on what pest, in which areas, and who applied it.
It is the line a pest-control business has to be able to produce on demand for federal and state recordkeeping.
The core records already carry the work and the trip. A Job is the recurring route, a Visit is the stop your technician makes, and a Customer is the property owner.
None of those, on their own, hold the structured product-level detail a regulator asks for — brand and EPA registration number, quantity, rate, target pest, treated site, date, and the certified applicator.
Chemicals is a custom object you create to hold exactly that. Each record is one application, linked to the visit it happened on, so a treatment history builds up under every customer and every route without anyone keeping a separate logbook.
Chemicals is not part of the standard day-one records. It is something a pest-control business builds with the customization engine, the same way Bait Stations and Service Agreements are built.
See Pest Control setup for how the whole specialized layer fits together.
What a Chemical record captures
A Chemical record holds the identity of the product and the facts of the application — what was used, how much, where, on what, when, and by whom.
The fields below map to real FieldCamp field types, so the record validates the data as it is entered.
| Field | Field type | What it holds |
|---|---|---|
| Product name | Text | The brand or trade name of the product applied, such as "Termidor SC." Required. |
| EPA registration number | Text | The product's EPA registration number — the identifier a regulator matches the application against. |
| Active ingredient | Text | The active ingredient and its percentage, such as "Fipronil 9.1%." |
| Application method | Single select | How it went down — spray, granular, bait, dust, fog, or injection. |
| Rate or dilution | Text | The mix rate or dilution used, such as "0.06% finished solution" or "1 oz per gallon." |
| Target pest | Multi-select | The pests the application targeted — ants, termites, roaches, rodents, mosquitoes, and more. |
| Areas treated | Multi-select | Where the product was applied — perimeter, kitchen, attic, crawl space, exterior, or named zones. |
| Quantity used | Number | The total amount of product applied in the unit below. |
| Unit | Single select | The unit the quantity is measured in — ounces, gallons, pounds, or grams. |
| Application date | Date | The day the application was made. |
| Applicator | Link to a team member | The certified team member who made the application. |
| Visit | Link to a visit | The visit this application was captured on. |
| Notes | Long text | Conditions or observations — wind, temperature, or anything the trade or a state requires. |
The customer and the property do not need to be retyped onto the Chemical record. They come from the visit the application is linked to, so every record rolls up to a real customer and a real address on its own.
The EPA registration number and quantity-with-unit fields are the load-bearing ones for compliance.
Keeping the unit as its own single-select beside the quantity means every record reads in a consistent measure, which is what makes a treatment history exportable as a clean list rather than free text.
How Chemicals connect
A Chemical record hangs off the work that produced it.
It is captured on a Visit, the visit belongs to a Job, and the job belongs to a Customer — so each application traces back to a real stop, a real route, and a real property owner.
The applicator is a team member, linked so the certified person on the record is the same roster entry assigned to the visit. The diagram below shows the records a Chemical application connects to.
Read the connections outward from the Chemical record:
- A Visit can have many Chemical records — a single stop often applies more than one product across different areas — but each Chemical record belongs to exactly one visit. That keeps every application dated to the trip it actually happened on.
- A Visit belongs to a Job, and a Job belongs to a Customer, so each application rolls up the chain to one route and one property owner without re-entering either.
- Each Chemical record names the team member who applied it, drawn from the same roster the visit is staffed from.
Because applications attach to visits and visits roll up to customers, a treatment history assembles itself.
A returning technician — or anyone pulling records for an audit — can read every product ever applied at a property, with dates, rates, and pests, straight from the customer.
A customer's recurring job is scheduled as visits, each visit captures the chemical applications made on it, and those applications build the treatment history that the next visit and the next audit read from.
How it is built in FieldCamp
Chemicals is a custom object with the fields in the table above. It links to a visit and to a team member, so each application sits on the trip that produced it and names the person who made it.
Its record page is assembled from building blocks — a header, the application fields, a breadcrumb up to the visit, and a files block for any product label or safety sheet.
You can reorder, group, or hide those blocks so the page reads the way your applicators work.
If you want applications to move through states — say, recorded then reviewed before a record is final — you can give the object a short workflow. See stages and workflows for how to add stages and the transitions between them.
FieldCamp captures and retains the application record, and you can export it as a list. It does not generate or e-file state-specific pesticide-use submissions, and it does not roll usage up into a pre-formatted state report on its own.
The data needed for those reports lives in the records and is exportable, but the filing itself happens outside FieldCamp.
See also
More in the FieldCamp data model.
How chemicals, bait stations, agreements, and recurring routes fit together.
How the Chemical record and its fields are built.
The stop each application is captured on, and where the field detail comes from.
The certified applicator named on every Chemical record.
How the core records connect, and how to make them your own.
Service 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.
Bait Stations — Custom Object Example | FieldCamp
Model bait stations as a custom object in FieldCamp — station number, placement, bait type, condition, and last-checked status, sitting under a property and checked each visit.