BRCGS Global Standard for Food Safety devotes a single clause, 4.14, to pest management, but it carries more sub-requirements than almost any other prerequisite programme in the standard. It is the clause where auditors spend real time: walking the perimeter, pulling the site plan, checking that station numbers on the map match stations on the wall, and asking the question that catches out more South African sites than actual infestation ever does "show me the trend."
This guide works through clause 4.14 sub-clause by sub-clause, with South African context layered in: what Act 36 of 1947 means for products your contractor may legally use, how SANS 10133 sets the application standard, and what a competent auditor looks for at each step. If you also certify to FSSC 22000, see FSSC 22000 pest control requirements for how the schemes differ.
Key takeaways
- Clause 4.14 is not a BRCGS "fundamental" clause, but it is among the most frequently non-conformed clauses in Section 4, treat it with fundamental-level rigour.
- BRCGS accepts a competent in-house resource or a contracted PCO, competence, not employment status, is what auditors verify.
- Trend analysis is explicit: service reports without a trended, actioned view by zone and species is the single most common non-conformance.
- Every device, bait station, EFK, pheromone monitor, must be mapped, numbered and reconciled between plan and floor.
- Every product applied must carry an Act 36 of 1947 L-number, aligned with SANS 10133.
Clause 4.14 in context: where pest management sits in
BRCGS's fundamental clauses cover senior management commitment (1.1), the food safety plan (2.1), internal audit (3.4), corrective and preventive action (3.7), traceability (3.9), and incident management/product recall (3.11). Clause 4.14, Pest Management, sits under Section 4, Site Standards, alongside housekeeping, waste management and equipment. It is not a fundamental clause, so a single 4.14 finding will not by itself force a "grade reduced" outcome the way a fundamental failure would.
That distinction matters less than it sounds. An active infestation or documentation collapse under 4.14 routinely triggers linked findings elsewhere, hazard analysis, housekeeping, building fabric. Auditors treat 4.14 as diagnostic: how it is run signals how seriously the site takes its prerequisite programmes.
Clause 4.14 sub-clause by sub-clause
4.14.1, Documented programme or contract
A documented programme covering every relevant pest: rodents such as Rattus norvegicus and Mus musculus, flying insects such as Musca domestica, stored-product pests such as Plodia interpunctella and Tribolium castaneum, and, depending on geography, birds and crawling insects. Where contracted, the SLA must define scope, frequency, responsibilities and the design standard. A properly structured pest control contract should hand you that SLA ready-made.
4.14.2, Competent resource: contracted PCO or in-house expertise
BRCGS does not mandate a third-party contractor; it requires whoever manages pest control, contracted or employed, to hold documented competence and current registration. In South Africa that means registration under the Fertilizers, Farm Feeds, Agricultural Remedies and Stock Remedies Act, Act 36 of 1947. BRCGS competence and South African law point the same direction, see Act 36 of 1947 requirements.
4.14.3, Site plan showing device locations, numbered and current
Every bait station, insect light trap, pheromone monitor and bird deterrent must appear on a current, numbered site plan matching physical tags on the devices. Auditors walk the plan against the floor; a station on one but not the other is an immediate finding, and any layout change must update the plan before the next audit.
4.14.4, Frequency of inspection appropriate to risk
Frequency must be justified by risk, not a generic monthly default. An intake bay next to open veld or a warm area favouring Blattella germanica should be serviced more often than a low-risk dry store, driven by the HACCP-compliant risk assessment.
4.14.5, Suitably located and installed devices
External bait stations must be secured, tamper-resistant, and positioned to intercept pests before building entry. Internal monitoring should favour non-toxic devices wherever food is exposed. EFKs (electric fly killers, insect light traps) must never sit above open product, auditors check the sightline from each unit.
4.14.6, Records of inspections, findings and treatments
Every visit needs a station-by-station record: findings, evidence of activity, products applied with L-number traceability, and technician ID. Gaps read as gaps in the programme, regardless of pest presence.
4.14.7, Trend analysis and use of data to drive improvement
The sub-clause most South African sites get wrong. Pest activity data must be analysed for trends, by zone, species and season, feeding decisions such as increased frequency, structural repair, or a hazard analysis update. A folder of signed slips with no graph and no narrative connecting activity to action does not satisfy this requirement, even if every visit was completed on time.
4.14.8, Storage and handling of pesticides
Where the site stores pesticide itself, storage must be secure, signed, separated from food and packaging, with current SDSs. Only products registered under Act 36 of 1947 for the target pest and site type may be used or stored.
4.14.9, Structural measures preventing pest access
Pest management is not only chemical. Auditors check door seals, air curtains, drainage grating and goods-receiving discipline as prevention in their own right, even though facilities, not the PCO, usually owns the fix.
4.14.10, Corrective action and verification of effectiveness
Every finding above threshold needs a corrective action with a responsible person, a deadline, and verification that it worked, not just that it was completed. A repeated finding without escalation reads as a failure of the preventive-action loop under fundamental clause 3.7.
Contracted PCO vs in-house vs mixed responsibility
Three models satisfy 4.14.2, provided competence is documented:
| Model | BRCGS expects | Common weakness |
|---|---|---|
| Fully contracted PCO | Act 36 certificates, SLA, training records, PI insurance | Site staff cannot answer basic questions in the contractor's absence |
| Fully in-house | Employed, Act 36-registered technician, contractor-level training | Registration lapses unnoticed; no independent oversight |
| Mixed (in-house monitoring, contracted treatment) | Written division of responsibility; staff trained on escalation | Ambiguity over who owns trending and sign-off |
ASC's registered PCOs work under Act 36 of 1947 and apply SANS 10133 regardless of the model a client runs, trained to hand auditors a defensible answer at every sub-clause above.
EFKs, pheromone monitoring and bait station mapping
Electric fly killers (EFKs / insect light traps) monitor and control flying insects such as Musca domestica and Calliphora species. Placement is scrutinised as heavily as performance, units must not be visible from outside or sit above open product, and catch trays must be checked on a defined schedule, not only when visibly full.
Pheromone monitoring targets stored-product pests including Plodia interpunctella (Indian meal moth) and Tribolium castaneum (red flour beetle), giving early warning before visible infestation. Counts must be logged and trended like rodent activity, a spike near a silo should trigger an inspection, not just a note on a service sheet.
Bait station mapping and numbering. Every rodent station and internal monitor needs a unique, permanent number appearing on both the device and the site plan. Numbering gaps or stations moved without an updated plan are among the fastest ways to generate a finding during the walk.
What auditors specifically look for
- Reconciliation between the site plan and physical devices on the floor.
- A trend graph, not just a stack of signed service reports.
- Evidence trend data changed something: frequency, a repair, or a hazard analysis review.
- Current PCO certificates matching the technician who signed the latest reports.
- SDSs and an Act 36 of 1947 product register accessible on site.
- Structural integrity at entry points: seals, drainage, roof lines, goods receiving.
- Closed-loop corrective actions with verification, not just a completed checkbox.
Common non-conformances and how to close them out
Frequently asked questions
Is BRCGS clause 4.14 a fundamental clause?
No. Clause 4.14 sits within Section 4 (Site Standards) and is not a fundamental clause. Fundamentals include senior management commitment, the food safety plan/HACCP, traceability and corrective/preventive action. A 4.14 finding does not alone trigger a reduced grade, but it frequently links to fundamental clauses in practice.
Can pest management be handled in-house rather than by a contracted PCO under BRCGS?
Yes, provided the person managing it has documented, verifiable competence equivalent to a contracted PCO. In South Africa this still means registration under Act 36 of 1947, since applying most professional pesticides legally requires it regardless of employer.
What is the most common BRCGS pest control non-conformance in South Africa?
A missing or superficial trend analysis, reports exist but are never converted into a trended, actioned view by zone and species. Site plan gaps, structural entry points and out-of-date PCO competence records follow closely behind.
