A pest control programme is only as good as the file that proves it happened. On the factory floor the stations may be immaculate, the technician diligent, the fly counts low. None of that matters at the audit table if the evidence is scattered across paper slips, a shared inbox and a contractor's head office. The auditor scores the documented system, and the documented system is what you can produce, complete and legible, in the room, on the day.
This guide walks through the complete documented pest control file, element by element, the way we assemble it for food and beverage manufacturers in Gauteng and the Eastern Cape. It covers what each document has to show, how long to keep it, and where digital records earn their keep. Blank versions of most of these documents are on our free checklists and forms page.
Key takeaways
- A defensible file has nine core parts: risk assessment, station map, SLA and scope, service records, trend analysis, an Act 36 chemical register with L-numbers, safety data sheets, PCO and training certificates, and corrective actions with close-out.
- Retention is set by product, not habit: keep records for shelf life plus 12 months, and never less than two years.
- Digital records are not just accepted; a controlled system such as myASConline is usually stronger evidence than paper because it timestamps entries and blocks backdating.
Why documentation drives the finding, not the pest
Across food safety audits in South Africa, pest management is one of the most cited prerequisite programmes, and the majority of those citations are documentation gaps rather than live infestations. The logic is simple. An auditor cannot verify a service that has no record, cannot accept a chemical with no registration, and cannot confirm a finding was closed without evidence. The file is the audit trail, and a broken trail is a non-conformance regardless of how clean the site is. Our food safety audit tips for pest control cover how auditors read that trail; this article is about building it so there is nothing to read into.
The nine parts of a defensible pest control file
1. Site-specific risk assessment
The foundation document. It records the pests reasonably expected on your site, the conducive conditions (the maize mill next door, the wetland behind the packhouse, wooden pallets at raw intake), and it justifies the station layout and service frequency that follow. A generic template that could describe any factory is a finding in itself, because it proves nobody assessed your building. The assessment must be dated, signed, and reviewed at least annually or whenever the site changes.
2. Bait station and monitor layout map
A numbered plan showing every rodent bait station, break-back trap, insect light trap, pheromone monitor and bird deterrent. The rule auditors apply is reciprocal: every number on the map exists on the floor, and every device on the floor appears on the map. They walk the perimeter with the map in hand, so an undocumented station or a missing physical unit is caught in minutes.
3. Service level agreement and scope
The contract defines what is covered: target pests, service frequencies by zone, callout response times, and the standard the programme is designed against. For food premises that means naming Regulation R638 and the relevant SANS codes. Scope disputes at an audit almost always trace back to an SLA that never spelled out the frequencies or the response commitment.
4. Service records
Every visit, every station inspected, every finding, every product applied, dated and signed by the technician. These are the spine of the file. Gaps in the sequence read as gaps in the programme, so a missed month with no explanation is worse than a documented callout for a real problem.
5. Trend analysis
The most requested and most commonly missing element. Individual service slips are raw data; a chart of rodent activity or fly counts by zone across twelve months is information a quality manager can act on. BRCGS explicitly expects pest activity to be trended and fed back into the hazard analysis. Trending is also what turns a repeat finding into a documented pattern that justifies proofing or structural work.
6. Approved chemical register with Act 36 L-numbers
Every pesticide, rodenticide and insecticide used on site must be registered under Act 36 of 1947 and listed on a controlled register showing the product name, its L-number, the target pest, the areas of application and the dilution or dose. Using an unregistered product, or a registered product against a pest not on its approved label, is a legal contravention under the Act, not merely an audit finding. The register is where an auditor cross-checks that what the technician applied is legal for the use.
7. Safety data sheets
A current SDS for every product on the register, held on site and accessible to the first aid team and emergency responders, not filed only at the contractor's office. The SDS supports the site's chemical safety, spillage and first aid procedures, so it belongs in the pest file and cross-referenced in the health and safety file.
8. PCO registration and training certificates
Pest control operators must be registered with the Department of Agriculture under Act 36 of 1947. The file must hold current certificates, and the auditor will check that the registered operator is the same person signing the service reports. Expired registrations and mismatched signatures are common, avoidable findings.
9. Corrective actions with close-out evidence
Every meaningful finding needs a corrective action record: what was found, the root cause, the action taken, the responsible person, a deadline and photographic close-out. A finding raised and never closed is an open loop that an auditor will follow. Our companion article on corrective action and root cause analysis explains why closing the symptom is not the same as closing the finding.
Retention: how long to keep each record
Retention is set by the product you make, not by an arbitrary habit. The controlling principle in food manufacturing is shelf life plus a margin, so that a batch traced from the market can be matched to the pest control conditions in the factory when it was produced. The table below sets out practical minimums.
| Record | Minimum retention | Why |
|---|---|---|
| Service records and trend analysis | Shelf life plus 12 months, never less than 2 years | Traceability of production conditions per batch |
| Risk assessment (superseded versions) | Life of contract plus 2 years | Shows how the programme evolved with the site |
| Chemical register and SDS (withdrawn products) | At least 5 years after last use | Supports historical service records and incident review |
| PCO and training certificates | Current plus superseded for 2 years | Proves who was competent to service at any past date |
| Corrective action records | With the related service records | They are only meaningful alongside the finding |
Digital versus paper
SANS 10133, FSSC 22000 and BRCGS are all neutral on media. Records may be paper or electronic, provided they are legible, retrievable, controlled against unauthorised change, and protected from loss. Paper meets the letter of that requirement, but it fails often in practice: slips go missing, the trend graph lags, signatures are illegible, and nobody can prove a record was not written the night before the audit.
A controlled digital system removes those failure points. In myASConline, our paperless portal, the technician captures each station on a mobile device during the service, so entries are timestamped and cannot be backdated. The risk assessment, station map, chemical register, SDSs and certificates are held as controlled versions, and the whole pack, including trend graphs, is generated on demand. That is the difference between a file you assemble under pressure and a file that is always audit ready. Our article on the one-click audit pack in myASConline shows how it comes together in a single document.
Build your file before the auditor asks
The fastest way to close documentation gaps is to assemble the file against a checklist now, in a quiet week, rather than in the twenty minutes before a surveillance audit. Blank versions of the risk assessment, service record, chemical register and corrective action log are downloadable from our free checklists and forms page. If you would rather the file be built and maintained for you, that is what our food and beverage pest control programme does as standard.
Frequently asked questions
What documents make up a complete pest control file for a food safety audit?
A site-specific risk assessment, a numbered station and monitor map, the SLA and scope, at least 12 months of dated service records, trend analysis, an Act 36 chemical register with L-numbers, current safety data sheets, PCO and training certificates, and corrective actions with close-out evidence. Auditors treat these as a set, so one missing element still attracts a finding.
How long must pest control records be kept in South Africa?
Schemes expect at least 12 continuous months at the audit. Best practice is shelf life plus 12 months, never less than two years, with chemical registers, SDSs and certificates kept for the life of the contract plus the retention period.
Are digital pest control records acceptable to auditors?
Yes. The standards are neutral on media provided records are legible, retrievable, controlled and protected. A controlled system such as myASConline is usually stronger than paper because it timestamps entries and prevents backdating.
