Your Pest Control Contract Does Not Prevent Pests

Routine attendance is essential to an audited site. It is not the same thing as prevention, and treating the two as one changes what gets measured, what gets fixed, and what an auditor finds.

A monthly pest control visit does not make a rodent less likely to enter a building. Done well, it makes the rodent more likely to be found, identified and dealt with before its presence becomes a non-conformance. Both outcomes matter, but they are different outcomes, and audited sites often treat them as one.

The difference is between probability and duration. Prevention reduces the likelihood that activity occurs at all. Detection reduces the time between activity starting and somebody knowing about it. Resolution reduces the time between discovery and removal of the cause. A competent programme needs all three. Many contracts are nonetheless specified, priced and compared almost entirely on the second: visit frequency, device counts and response times.

What actually changes the odds

The likelihood of pest activity is set largely by the building and the way it is run. The relevant factors are unglamorous: gaps beneath dock levellers, damaged strip curtains, doors propped open at shift change, service penetrations never sealed after an installation, redundant drain runs and missing drain covers, spillage beneath racking, waste compounds sited against the building line, and stock left undisturbed long enough to become harbourage.

Proofing addresses some of this directly. Proofing, the physical exclusion of pests by sealing the gaps and entry points a building offers them, is genuine prevention, whether the pest management provider or the site's own maintenance team carries it out. The rest sits with the site. No contractor can correct a door culture, a cleaning schedule or a stock rotation policy from a monthly inspection.

This is not a criticism of the contractor. It is a statement about where the levers are. A programme that locates prevention entirely with the pest provider has placed responsibility with the party least able to discharge it.

What monitoring does well

None of this diminishes monitoring. Non-toxic monitoring, which detects activity without laying poison so that toxic control is used only where the evidence justifies it, is the site's early-warning system. A trained technician can distinguish fresh activity from old, identify the species and its likely route, judge whether a sighting is incidental or established, and escalate before a single droppings finding becomes a contamination event.

Its value is time. The shorter the gap between activity beginning and a defined response, the smaller the problem that has to be resolved. That value, however, depends on what happens next.

When recurrence becomes a signal

Some recurrence is legitimate. Rodent pressure rises as autumn turns cold, as neighbouring fields are harvested, or when adjacent premises change use. Activity at a boundary device during those periods may indicate that the monitoring is doing its job rather than that the programme is failing.

Recurrence at the same point, without explanation and without a change in response, is something else. As a working diagnostic: if the same device or location records activity on three consecutive visits and the intervention has not changed, the site is receiving repeated documentation of a problem rather than a response to it. Three is not a law of nature. The principle is that escalation should be defined in advance. Pest thresholds, the agreed activity levels at which a defined response is triggered, exist precisely so that recurrence prompts investigation rather than another entry in the log.

The recommendation is part of the control system

The weak point in many programmes is not detection. It is what happens to the finding once it has been written down.

A recommendation to seal a penetration, repair a drain cover or relocate a waste bin is only useful once it becomes a corrective action: the recorded step that closes out a finding and evidences that it was resolved. That requires an owner, a date, confirmation of completion and some check that the fix worked. Without those, a recommendation is a comment.

The complete loop runs from activity to detection, to investigation of cause, to a recommendation, to assigned ownership, to completion, to verification, and finally to measurement of whether activity at that location actually fell. Most programmes perform the first two stages reliably. The remainder is where control is either established or quietly lost.

Audit standards have made this gap more visible. BRCGS, the globally recognised food-safety standard widely used by manufacturers and specified across major retail and supply chains, expects pest control records to be maintained, findings to be acted upon, results to be analysed for trends, and an in-depth survey of pest control measures to be carried out at a frequency based on risk. In practice, an auditor reading the file is not only asking whether the contractor attended. They are asking whether the site responded.

That response frequently falls between departments. A structural defect raised in a pest report belongs to maintenance; the report belongs to technical or quality. An open recommendation can sit for months in the space between the two, owned by neither, visible to both. Supplier performance review is the natural point at which this should surface, provided the review looks at outcomes rather than attendance.

Measures worth reporting

If visit completion is the headline metric, the programme will be managed as a visit schedule. More useful measures describe whether risk is moving:

• Repeat activity by location, so persistent points are visible rather than averaged away.
• Recurrence after intervention, which shows whether a response worked.
• Time from detection to resolution, the clearest single indicator of control.
• Age of open recommendations, because an eleven-month-old proofing recommendation is itself a finding.
• Recommendation closure rate, separated by owner, so it is clear where actions stall.
• Structural defects by category, which turns individual reports into a maintenance picture.
• Repeat findings without escalation, the measure most likely to predict an uncomfortable audit.

None of these requires more devices or more frequent visits. They require the existing information to be read as a sequence rather than filed as a series of separate reports.

What changed because somebody attended

Attendance is the precondition for pest management, not its product. A contractor should be able to demonstrate that it visited, inspected and recorded. A programme should be able to demonstrate something more: which risks were identified, which were closed, and whether activity fell where action was taken.

A useful test for any audited site is to take the last twelve months of pest reports and trace each recommendation to its conclusion. If the file shows attendance clearly and outcomes vaguely, the programme is detecting the problem without managing it.

What changed because somebody attended
Stratton reviews pest management records for audited sites, tracing each recommendation raised over the past twelve months to its owner, its closure, and whether activity at that location fell afterwards. The result is a clear account of where control is established and where it is only being recorded.

Request a records review: https://www.strattonem.com/contact