What Auditors Actually Check in Your Pest Control File

The uncomfortable truth about audit failures

In our experience supporting restaurants, hotels and food factories through third party audits, most pest control findings are not about live pests. They are about documentation: missing service records, unmapped bait stations, no trend data. A site can be genuinely pest-free and still fail because it cannot prove it.

Auditors work from checklists, and the pest control section of those checklists is remarkably consistent across schemes. Here is what they open first.

The station map is the foundation

Every bait station, trap and insect light monitor on your site should appear on a numbered plan, and the numbers on the plan must match the numbers physically on the devices. Auditors walk the floor with the map and check. A station on the floor that is not on the map, or the reverse, is an instant finding.

Maps must also be current. If you moved racking or renovated an area, the map needs the same revision date discipline as any other controlled document.

Service records and the story they tell

Each visit should generate a record showing what was checked, what activity was found, what was applied and at what rate. Auditors read several months of these in sequence, and what they look for is the narrative: was activity found, was action taken, did the activity decline?

A file showing activity at station 14 for four consecutive visits with no escalation is worse than a file showing an infestation handled decisively. Auditors do not expect zero pests. They expect response.

Trend analysis, licences and product data

Higher-tier audits expect trend reports: catch counts over time, usually charted, with corrective actions noted against spikes. Ask your provider for these quarterly; producing them at audit time from raw records is painful.

Keep copies of your provider’s business licence and technician certifications in the file, along with labels and safety data sheets for every product used on site. An SDS binder that matches the service records is one of the quietest ways to signal a well-run programme.

If your current file could not survive this walkthrough, the fix is not complicated, but it does need to start months before the audit date. Documentation cannot be backfilled honestly, and experienced auditors can tell when it has been.