Most guidance on passing a pest control audit is written from the auditee's chair. This one is written from ours. ASC Pest Control is part of a food safety consultancy whose people sit on the auditing side of the table for a living, we assess pest programmes against HACCP, FSSC 22000 and BRCGS, and we know exactly where the findings come from. What follows is the checklist we mentally run when we open your pest file, reordered as ten practical tips you can act on before we, or your certification body, arrive.
Key takeaways
- Auditors judge a pest programme on documentation and thinking, not on whether pests exist, a site with activity that is trended, actioned and closed out scores better than a "clean" site that cannot prove it.
- The recurring findings are the same everywhere: absent trend analysis, map-to-floor mismatches, unregistered chemicals, expired PCO certificates and corrective actions that were opened but never closed.
- A mock audit run by real auditors surfaces every one of these before audit day.
The 10 tips
1. Lead with trend analysis, not service slips
The first thing an experienced auditor looks for is not a pile of visit reports, it is the trend. Can you show rodent, crawling-insect and flying-insect activity graphed over twelve months, by zone, with the story of what you did when a line spiked? Raw slips are data; trends are evidence of a managed system. Absent or superficial trending is the most common single finding under ISO 22002-1 clause 12 and BRCGS clause 4.14.
2. Walk your own station line before we do
Take the station map and walk it. Every numbered rodent point, insect light trap and pheromone monitor on the map must exist, be secured and be in the right place, and every station on the floor must appear on the map. Auditors reconcile map, floor and records; you should find the mismatches first.
3. Keep an approved chemical register with L-numbers
Every product used on site must be registered under Act 36 of 1947 and listed with its L-number, target pest, application area and dilution. An unregistered product, or a registered product used against a pest not on its label, is a legal contravention, not merely an audit finding. We check L-numbers against the actual products on the shelf.
4. Have current SDSs at the point of use
Safety data sheets for every product on the register must be current and accessible to first aiders and the emergency team on site, not filed only at the contractor's office. We ask for the SDS of a product we just saw in the register; a delay is a finding.
5. Match PCO certificates to the signatures on the reports
Pest control operators must be registered with the Department of Agriculture under Act 36 of 1947. We cross-check the name signing your service reports against a current PCO registration certificate. Expired registrations and mismatched names are common and easily avoided.
6. Prove your corrective actions were closed out
Opening a corrective action is easy; closing it is what auditors verify. Every finding, a gnawed bait block, a gap under a door, a fly count spike, needs a responsible person, a deadline and photographic or documented close-out evidence. An open action with no close-out reads worse than no action at all.
7. Trend your EFK / insect light trap counts
Electric fly killer (EFK) and insect light trap catches are a quantitative early-warning signal. Count and identify the catch at each service, trend it, and set action thresholds. A rising fly-count trend with no response is a classic finding; a documented investigation into a spike is a mark of a mature programme.
8. Know your contractor SLA cold
Your service level agreement should define covered pests, service frequencies, callout response times and the standard the programme is designed against (for example R638 and SANS 10133). Auditors check that actual service frequency matches the SLA, a monthly contract with a six-week gap is a documented breach of your own control. If your current agreement cannot pass that test, our pest control contract page sets out what a defensible SLA looks like.
9. Fix root causes, not just the pest
This is where good programmes separate from average ones. Killing the mouse is not control; finding and sealing the gap it came through is. When we see the same pest recurring in the same zone, we look for evidence of root-cause analysis, proofing, sanitation and structural fixes, in the file. A HACCP-based IPM approach is built around this distinction.
10. Run a mock audit with real auditors
The single most effective preparation is a mock audit conducted by someone who genuinely audits pest programmes. It reproduces the real questions, and the real scrutiny, before the real auditor arrives, surfacing gaps in trending, registers, certificates and close-outs while there is still time to fix them. This is precisely the service a food-safety-owned pest control company can provide that a conventional contractor cannot.
Pre-audit self-check
| Can you, in under five minutes… | If no… |
|---|---|
| Produce 12 months of trended pest activity by zone? | Expect a finding under clause 12 / 4.14. |
| Reconcile every station on the map to the floor? | Walk and correct the line first. |
| Show an L-number for every product on site? | You may be in breach of Act 36 of 1947. |
| Show close-out evidence for the last five findings? | Close your open corrective actions. |
| Match every report signature to a current PCO cert? | Verify registrations before we do. |
Frequently asked questions
What is the single most common pest control audit finding?
Missing or superficial trend analysis. Auditors expect twelve months of pest activity trended by type and zone, with documented actions for spikes fed back into the hazard analysis. Sites that keep slips but never trend them pick up the most findings under clause 12 and clause 4.14.
What do auditors check when they walk the bait station line?
They reconcile the map against reality, every number on the map exists on the floor, every station on the floor is on the map, stations are secured and correctly placed, and records show each being checked. Mismatches are an immediate red flag.
How do mock audits improve pest control readiness?
A mock audit run by real auditors reproduces the actual questions before audit day, surfacing gaps in trending, registers, certificates and corrective action close-out while there is still time to fix them.
