Why pest activity is a documentation event

On a regulated site, a pest sighting is two events at once. The first is operational: something was seen, and something must be done. The second is documentary: a line has opened in the record, and that line now has to be carried to a close.

Most contracts handle the first event reasonably well. The second is where sites get hurt. A capture that was dealt with promptly but recorded vaguely is, for audit purposes, barely distinguishable from a capture that was ignored. The reviewer was not there. The record is all that attends the audit on the site's behalf.

Treating activity as a documentation event changes the questions asked at the time. Not only "what do we do?" but: where exactly was it, what does the history of that point show, who owns the corrective action, what priority does it carry, and when will it be reviewed? Each answer becomes a line the site can later stand behind.

It also changes what good service looks like. A contractor who attends quickly but documents thinly is solving the operational event and quietly enlarging the documentary one. Over a contract year, the gap compounds: a folder of visit sheets that prove presence, and very little that proves management.

The discipline is not onerous. It is one structured way to record a finding, one register that carries it forward, and one review that closes it. But it has to run every time, because the record is only persuasive when it is unbroken.