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.

A Bait Station record is one monitoring device installed at a property — a rodent bait station, a snap trap, a glue board, an insect monitor, or a fly light — with its own number, its own placement, and its own service history.

A commercial site can hold tens or hundreds of them, and a technician services every one on each recurring route.

Pest control needs the station as a custom object because it is a thing the business tracks in its own right, not a detail you could type onto a Job or a Customer.

Each station has its own identity, its own condition, and a reading captured every time a crew comes back.

A Bait Station is a child object: it sits under a property (the Customer record) so every station belongs to one specific site, and it is checked on each Visit the route generates.

What a Bait Station captures

A Bait Station record holds the identity and current standing of one device — what it is, where it sits, what is loaded in it, and how it read on the last service.

The table below lists the fields on the record and the field type each one uses.

Field	Field type	What it holds
Station number	Text	The barcode or QR value on the device, used to find and identify it in the field. Required.
Device type	Single choice	What kind of device it is — rodent bait station, snap trap, glue board, insect monitor, or fly light.
Placement / zone	Text	The area or zone where the station sits, such as "loading dock, north wall."
Bait / product inside	Link	Links to the Price Book product loaded in the device.
Install date	Date	When the station was placed at the property.
Last checked	Date	The most recent date the station was serviced.
Activity / condition status	Single choice	The current standing — clear, activity found, damaged, or needs service.
Notes	Long text	Free-form notes on the station and its placement.

The owner and the site are not typed onto the station. They come from the Customer record the station sits under, so a station always rolls up to a real property without re-entering the address.

The activity status pill — clear, activity found, damaged, or needs service — is the at-a-glance health of the device. It is what tells a route technician which stations need attention before they walk a site with hundreds of them.

How Bait Stations connect

A Bait Station sits under a property and links across to the work that services it. It belongs to a Customer, is checked on the Visits the route generates, and rolls up to the Job that drives those visits.

Read the connections outward from the Bait Station:

One Customer can hold many Bait Stations — a residential home a couple, a commercial site hundreds — but each station belongs to exactly one property.
A Job set to recurring is scheduled as Visits, and each Visit is where a crew checks the stations on the site.
A Bait Station builds its service history from Visits — each check adds a dated reading, so the station's record gets richer every route.

Because a station is checked through Visits and Visits belong to a Job, the Job is how a route knows which stations it covers, and the visit done in the field is what writes back to each station's record.

The inspection cycle

A station is checked, refilled, and logged on each recurring visit. The cycle below is the on-site sweep for one device.

Open the station

The technician finds the station by its number — searched on the device record — and opens it to see its placement, what is loaded inside, and how it read last time.

Inspect and act

The technician checks for activity, refills or rebaits if needed, and notes the condition — clear, activity found, damaged, or needs service.

Log the reading

The reading is recorded against the visit, and the station's last checked date and activity status update so the next route sees current standing.

Move to the next

The technician moves on to the next station, repeating the sweep until every device on the site is checked and logged.

The recurring schedule that brings a crew back each month or quarter comes from a recurring Job, not from the station itself. The Job generates the Visits; the station is what each visit checks.

How it is built in FieldCamp

A Bait Station is a custom object set up as a child of the property, carrying the fields in the table above.

It is the same kind of object as Equipment — a physical asset on a customer's property with its own record — modeled for a pest-control route.

Its record page is assembled from the same library of building blocks as every other record: a header with the activity-status pill, a breadcrumb back to the property, the station fields, a related table and service history of its readings, a location map, files, and a timeline.

Reorder, add, hide, or group those blocks so the page reads the way your technicians work.