Pest-control documentation for BRCGS, IFS and HACCP audits
In a food-site audit, the pest-control records are checked as closely as the site itself. These are the things auditors ask for most often.
Contract and scope of service
A written scope: which pests, how often visits happen, the response time to a call-out, who the client's contact is, and who is responsible for what. Visit frequency should follow from a risk assessment of the site, not from habit.
Station location plan
An up-to-date plan of the site with numbered bait stations, glue boards and insect lights, and a legend. This is one of the most frequent non-conformities: the plan does not match what is on the walls because stations were moved or removed and the plan was never corrected. The number on the plan should match the number on the point's label.
A report from every visit
After every visit, a report in the folder: date, technician, the points checked and their condition, catches, products used with quantities, recommendations and signatures. Details in what a pest-control service report must include.
Trend analysis
Pest activity over time, at least once a year and after every significant problem, drawn from the monitoring points. In practice auditors want to see at least 12 months of history, and insect-light catches broken down by species.
Biocides
A list of the products used, with their authorisation numbers and safety data sheets, and a register of their use. Toxic rodenticide inside areas with open food is usually not accepted outside an active infestation; where it is used, it needs a justification.
Missing and temporary stations
Every missing or damaged station has to be recorded and explained. Stations added during an infestation should have their placement and their removal recorded, including the removal of the bait.
Contractor qualifications and insurance
Technicians' qualifications with expiry dates (in the UK: a Level 2 certificate and CRRU stewardship or CPD for professional rodenticides, a glue-trap licence where glue boards are used) and the company's liability insurance. The auditor checks that the documents are valid on the day of the audit.
Recommendations and corrective actions
What the technician recommended to the client (for example, sealing a dock door or moving pallets away from a wall), when, and whether it was done. Open recommendations with no due date or status are a weak spot in an audit.
How Pestnode handles it
Pestnode builds the reports, the pesticide register and the trends from visit data, keeps the company's documents with their expiry dates and assembles a site's whole folder into one ZIP file for the auditor. The client can open it in their portal. See pest control software.
This is a practical guide, not an interpretation of the standards. What a particular audit requires depends on the version of the standard and on the client.