Every device, every visit, with its own history.

Exterior rodent stations, interior stations, snap traps, insect light traps and pheromone monitors are usually numbered, positioned and inspected on a route. On paper each of them is a tick in a grid, and the grid is filed.

Treated as records instead, each device holds its own location, its own inspection outcomes and its own history. The question "has station 14 been active before?" stops requiring someone to go and find last quarter's sheets.

• Device and inspection records that persist between visits.
• Barcode and scan workflows for moving through a route quickly.
• Unit-level inspection context so a finding lands at the right place in the property.

The reason to scan a barcode is not novelty. It is that a technician working a route of sixty devices on a cold loading dock will transcribe a number wrong eventually, and a wrong number quietly corrupts the history of two devices at once.

Scanning the device pulls up the right record, shows what it is and where it is, and puts the finding against the correct history without anyone typing an identifier.

A single inspection result means very little on its own. Activity at one station on one visit is noise; the same station active four visits running is a structural problem with the building, and that is the finding worth acting on and worth reporting.

Consistent device-level records are what make that comparison possible. They are also what a commercial customer's quality manager is really asking for when they ask for documentation — not proof that you attended, but evidence of what the site is doing over time.

In ServOS the scans a technician records on site feed the same work order and service history the office and the customer see. The inspection route, the treatment records and the service report are stages of one record, so the documentation is a product of doing the work rather than an evening spent writing it up.