A pest sighting on its own rarely fails an audit. What fails an audit is a pest sighting with no trend history behind it, no closed corrective action attached to it, and no proof that the prevention programme was actually running before the pest turned up. Under FSSC 22000, BRCGS and ISO/TS 22002-1, the auditor is scoring the system that should have caught the pest early, not the pest itself.
A dead rat is not the finding. A blank trend log is.
Every food facility, no matter how well run, will see pest activity at some point. A moth in a light trap, a mouse dropping near a pallet, a fly on a window ledge. None of these are automatic nonconformances. What an auditor is actually looking for is whether the facility's own system flagged the same signal earlier, whether the trend showed a rising pattern before the sighting, and whether someone closed out a corrective action once it did. A programme that only produces paperwork after something has already gone wrong is, by definition, reacting, and reacting is not what a prerequisite programme is meant to do. This is the quiet distinction that separates a facility that treats pest control as a call out service from one that treats it as a food safety control point, and it is the difference an FSSC 22000, BRCGS or ISO/TS 22002-1 auditor is trained to look for.
Know the pest before choosing the control
Identification comes before intervention. A German cockroach, Blattella germanica, breeds fast in warm, humid voids close to food preparation and rarely travels far from its harbourage, so the fix is usually gel baiting and void treatment close to the source. An American cockroach, Periplaneta americana, prefers drains, basements and damp service ducts and needs a different approach entirely. Treat the wrong species with the wrong method and the facility burns time, budget and product tolerance while the real pressure point goes untouched. This is why a competent pest control operator starts with species identification and basic biology, not a chemical list, and why an auditor will ask what species was found and why that particular control was chosen for it.
Sanitation and harbourage removal, the first real control
Once the pest and its biology are understood, the first control is almost never a pesticide. It is removing the conditions that let the pest survive. A beverage filling line in Gauteng, for example, can carry a persistent drain fly problem that no amount of spraying resolves, because the flies are breeding in the biofilm inside the drains themselves, not in the open air where a spray would reach them. A structured drain cleaning and biofilm removal schedule, run on a fixed interval and logged, closes the breeding site rather than knocking down the adult flies that keep re-emerging from it. The same logic applies to a receiving bay where an unsealed dock leveller gives rodents a route in from outside: sealing the gap is the control, not the bait station next to it. This is the sanitation and exclusion layer that the BRCGS Global Standard for Food Safety, Issue 9, clause 4.14 expects a site to document, because a pest management programme built only on chemical response has nothing to show an auditor except a growing list of treatments.
Inspection and trend monitoring, what the log actually needs to show
ISO/TS 22002-1:2009, the prerequisite programme standard that FSSC 22000 certified sites are audited against, sets out pest control as a dedicated clause because a facility cannot manage what it does not monitor. In practice this means every bait station and monitor is numbered, mapped and inspected on a set schedule, with the result at each point logged over time so a trend becomes visible, rather than each visit being recorded as an isolated pass or fail. BRCGS Issue 9, clause 4.14, adds that the site must be able to show its own pest management inspections and that any recommendations made, whether by an in house team or a contracted pest control operator, were actually carried out and closed. A trend log that shows activity rising at one station over consecutive visits, followed by a documented corrective action, is exactly the kind of evidence that turns a pest finding into a demonstrated control, rather than a surprise.
Where pesticide application and fumigation actually fit
Chemical control and fumigation are real tools, not the default response. In South Africa, fumigant application is governed by SANS 10204, the national standard covering how fumigants may be applied, and general pesticide handling, storage and disposal falls under SANS 10206. Both sit alongside the registration requirement in the Fertilizers, Farm Feeds, Agricultural Remedies and Stock Remedies Act, Act 36 of 1947, which requires pest control operators to be registered with the Department of Agriculture before they may apply a registered remedy at all. Used this way, as a targeted, registered, properly recorded last step rather than a first response to every sighting, chemical control and fumigation support the prevention programme instead of standing in for it.
What an audit ready facility can show that a reactive one cannot
The practical payoff of building the system in this order, identification, sanitation, monitoring, then targeted control, is what a facility can hand an auditor on the day. A reactive programme can usually produce invoices. An audit ready one can produce a station map, a trend history per zone, a closed corrective action log, proof of registered operator status, and a fumigation or treatment record that shows exactly why that specific control was used and nothing more. That second set of documents is what actually satisfies FSSC 22000, BRCGS and ISO/TS 22002-1 auditors, because it demonstrates a system working over time, rather than a company that only shows up after something has already gone wrong.
ASC Pest Control designs pest management programmes around this same order for food, beverage and pharmaceutical facilities across Gauteng and the Eastern Cape. If your current programme cannot yet produce a trend log and a closed corrective action history at short notice, our audit readiness self assessment or a site gap assessment is a good place to start, alongside our dedicated food and beverage pest control programme.
Frequently asked questions
Does FSSC 22000 require a pest control contract?
FSSC 22000 does not name a specific contract format, but sites certified under it are audited against ISO/TS 22002-1, which sets pest control out as a dedicated prerequisite programme clause. In practice this means a documented, monitored pest management system is required, and most facilities meet that through a contract with a registered pest control operator rather than building the monitoring and record keeping in house.
How often should bait stations be inspected for an audit ready programme?
There is no single fixed number that applies to every site. BRCGS Issue 9, clause 4.14, expects the inspection frequency to be based on the site's own risk assessment, so a high risk area such as a receiving bay or waste yard is typically inspected more often than a low risk office space. What an auditor checks is whether the frequency is documented, justified and actually followed.
Does a pest sighting automatically fail an FSSC 22000 or BRCGS audit?
Not on its own. An auditor assesses whether the facility's system caught the activity, whether a corrective action was raised and closed, and whether trend data shows the programme working. A sighting with no supporting trend history, no corrective action and no evidence the prevention layer was in place is far more likely to be raised as a finding than the same sighting inside a documented, functioning system.
Do pest control operators need to be registered in South Africa?
Yes. Under the Fertilizers, Farm Feeds, Agricultural Remedies and Stock Remedies Act, Act 36 of 1947, pest control operators must be registered with the Department of Agriculture before they may apply a registered agricultural remedy. Facilities preparing for a food safety audit should confirm their contracted operator's registration status as part of that review.
