AIB, BRC & HACCP Pest Control Requirements for Food Plants
Quick answer: AIB, BRC and HACCP auditors do not assess whether you have a pest control contract — they assess whether you can prove the programme is under control. That means a current site device map, dated inspection records, trend analysis showing action taken on rising counts, written threshold (action) levels, an approved chemical list with safety data sheets, technician competency evidence, and a closed-out corrective action log. Missing documentation, not visible pests, is the most common cause of pest-related findings.
Why pest control is a disproportionate audit risk
For food manufacturers in Pakistan supplying export markets or multinational buyers, pest management sits in a small group of clauses that can produce a critical or major non-conformance on their own. A single rodent sighting in a production area during an audit can put a certificate — and therefore a supply contract — at immediate risk.
The financial exposure is rarely the cost of pest control. It is the cost of losing the certification that permits you to sell.
What each standard expects
| Standard | Pest management focus | What auditors ask for first |
|---|---|---|
| AIB International | Integrated pest management as part of the overall food safety programme | Device map, inspection frequency records, trend data, corrective action closure |
| BRCGS Food Safety | Documented programme, competency of provider, defined action levels | Contract scope, technician qualifications, threshold levels, annual programme review |
| HACCP | Pest activity treated as a hazard requiring prerequisite controls | Prerequisite programme documentation, monitoring records, verification evidence |
| GMP / GMP+ | Hygiene and contamination prevention in manufacturing zones | Chemical approvals, application records, restricted-zone procedures |
The seven documents to have ready before any audit
- Site device map. A current plan showing every rodent station, insect light trap and pheromone monitor with a unique ID. It must match reality on the floor — auditors do walk the map and check numbering.
- Inspection and service records. Dated reports for every visit, listing findings per device, actions taken and the technician’s name.
- Trend analysis. Counts plotted over time per device or zone. This is the item most often missing. A record of activity is not enough; you must show that you analyse the direction of travel and respond to it.
- Defined action (threshold) levels. Written trigger points stating what count in which zone requires escalation, and what that escalation is.
- Corrective action log. Evidence that each finding was assigned, actioned and verified closed — with dates.
- Chemical approvals. An approved product list with safety data sheets, permitted application areas, and records of what was applied where and when.
- Competency evidence. Technician training and licensing records, plus professional oversight of the programme design.
Where pest-related audit findings actually come from
In our experience across Pakistani food plants, auditors raise far more findings about missing evidence than about visible pests. The chart below shows where findings cluster — and every one of the top three is a paperwork gap, not an infestation.
Relative frequency, not absolute counts. The practical takeaway: a plant with zero pests but no trend analysis is more exposed at audit than a plant with minor activity and complete records.
Data table
| Item | Value | Relative |
|---|---|---|
| No trend analysis | most common gap | 100 |
| Device map out of date | stations moved, map not revised | 82 |
| No written action levels | reactive, not controlled | 74 |
| Corrective actions left open | no closure evidence | 58 |
| Proofing defects unresolved | noted repeatedly, never fixed | 46 |
| Actual pest sighting | less common than paperwork | 28 |
Audit-readiness scorecard
Score yourself before the auditor does. If you cannot produce any one of these within a few minutes, that is your next priority.
Retrievability counts as much as existence — documentation you cannot produce during the audit becomes a finding in itself.
Data table
| Item | Value | Relative |
|---|---|---|
| Site device map | walked and checked on the floor | 95 |
| Trend analysis | proof of proactive management | 92 |
| Action levels | defines “under control” | 86 |
| Service records | dated, per device, signed | 80 |
| Chemical approvals + SDS | permitted zones recorded | 70 |
| Technician competency | training + licensing | 64 |
Where Pakistani facilities most often lose points
- Trend analysis absent. Service reports exist, but nobody has plotted or reviewed the data, so there is no evidence of proactive management.
- Device map out of date. Stations moved during maintenance or line changes and the map was never revised.
- No written thresholds. The programme reacts to problems rather than to defined limits, which auditors read as “not under control”.
- Proofing defects unresolved. Gaps under dock doors, damaged mesh on extract vents, standing water near external walls — noted repeatedly in reports but never fixed.
- Corrective actions left open. Findings recorded with no closure evidence.
- Records not retrievable. The documentation exists but cannot be produced quickly during the audit, which itself becomes a finding.
Building a programme that passes
An audit-ready programme is threshold-based rather than calendar-based: monitoring is continuous, treatment is triggered by defined action levels, and every step generates a retrievable record. It should also be designed around your zones — raw material intake, processing, packing and finished goods storage each carry different risk and different permitted controls.
Digital record-keeping matters more than it used to. When an auditor asks for eighteen months of trend data for a specific station, producing it in seconds carries far more weight than retrieving a folder of paper reports. Our IPMS compliance portal exists for exactly this reason. See also our industrial pest control programmes and IPM consultancy and audit support.
Frequently asked questions
What pest control documents does a BRC audit require?
At minimum: a documented pest control programme, a current device map, dated inspection records, defined action levels, trend analysis with evidence of response, an approved chemical list with safety data sheets, technician competency records, and a closed-out corrective action log.
How often should a food plant be inspected for pests?
Monthly service is the common baseline for food manufacturing, with higher-risk sites moving to fortnightly or weekly. Frequency should be justified by a documented risk assessment rather than chosen arbitrarily, because auditors will ask why your interval is what it is.
Can we manage pest control in-house?
Some standards permit it, but the burden of proof is higher: you must evidence technician competency, chemical controls, independent review and the same documentation an external provider would supply. Most export-facing facilities find third-party provision easier to defend.
What is an action level or threshold?
A written trigger stating that a defined level of activity in a defined zone requires a defined response — for example, any activity in a processing zone triggering same-day investigation. It demonstrates the programme is managed to limits rather than to complaints.
Does a pest sighting during an audit automatically fail the audit?
Not automatically, but evidence of pest activity in a production zone is treated seriously and may result in a major or critical finding depending on the standard and the location. Strong documentation and demonstrated corrective action materially affect how a finding is graded.
Book an audit-readiness assessment
We will review your current pest programme against AIB, BRC, HACCP and GMP requirements and give you a prioritised gap list.
