Somewhere between Isando and Wadeville, a QA manager is scoping a pest control tender that will sit inside her FSSC 22000 system for the next three years. The document she signs will be read by certification auditors, by AIB inspectors, by Woolworths and Shoprite technical teams, and, if something goes wrong, by a Department of Health environmental health practitioner. Yet most pest control contracts circulating in Gauteng are written as cleaning-style service agreements: a price, a visit count, and a signature.
This guide is written for the people who have to defend that contract in an audit room: QA managers, procurement officers, plant managers and SHEQ teams across Johannesburg, Pretoria, Ekurhuleni, Midrand, Centurion and the Vaal Triangle. It sets out what a compliant contract must contain, the red flags that cheap contracts hide, and the questions to put in your RFQ before you award anything.
Key takeaways
- A pest control contract for a certified food facility is audit evidence, not a supplier agreement; FSSC 22000, BRCGS and buyer auditors read it against your risk assessment and site plan.
- The non-negotiables: documented scope, risk-based frequency, mapped and numbered stations, trend analysis with action thresholds, corrective action SLAs, emergency callout terms and clear record ownership.
- Red flags in cheap contracts include unmapped stations, tick-box service sheets, no trending, undisclosed subcontracting and technicians without verifiable PCO registration under Act 36 of 1947.
- ASC's contracts are drafted by accredited food safety specialists and delivered through myASConline, so the paperwork is structured the way the auditor will read it.
What a compliant pest control contract must contain
Start with scope: the contract must name the buildings, zones and pest groups covered (rodents, crawling insects, flying insects, stored-product insects, birds where relevant) and tie them to a site-specific pest risk assessment. Service frequency must be justified by that risk assessment, not by a standard package; see our guide to service frequency for food facilities for how auditors test this.
The contract must then commit to the machinery of a managed programme: monitoring stations mapped and numbered against a current site plan; trend analysis with defined action thresholds; corrective action service levels (how fast a rising trend or a sighting is investigated and closed out); emergency callout terms with a response time in hours, not "best effort"; and explicit documentation ownership, so that service records, maps and trend data remain accessible to you if the relationship ends. Finally, it must record the provider's PCO registration under Act 36 of 1947 and alignment with SANS 10133, because your auditor will ask for both.
Red flags in cheap contracts
Gauteng is a fiercely price-competitive market, and low bids usually save money in the places auditors look first. Watch for: unmapped stations ("bait boxes as required" with no numbered plan); tick-box service sheets that record "checked, OK" with no counts, no species and no findings; no trending clause, which means twelve months of paper and zero analysis; undisclosed subcontracting, where the company you contracted is not the company on site and technician registration cannot be verified; and contracts that are silent on callouts, so every sighting becomes a billable negotiation. Each of these maps directly onto a documentation nonconformance you will carry, not the contractor.
How auditors evaluate the pest programme
Whether the standard is FSSC 22000, BRCGS, ISO 22000, AIB or a buyer audit from Woolworths or Shoprite, the method is the same: the auditor triangulates the contract, the risk assessment, the station map and the trend data, and looks for daylight between them. The table below shows why each clause exists.
| Contract clause | Why auditors demand it |
|---|---|
| Documented scope & pest groups | Proves the programme covers every risk identified in the site assessment, with nothing excluded by omission |
| Risk-based service frequency | Shows visits are justified by risk, not by a sales package; R638 and FSSC 22000 both expect this logic |
| Mapped, numbered stations | Lets the auditor walk the floor and reconcile physical stations against the plan and the records |
| Trend analysis & thresholds | Demonstrates the programme is managed, not merely performed; trending is the first request in most BRCGS audits |
| Corrective action SLAs | Evidence that findings are investigated to root cause and closed out within defined timeframes |
| Emergency callout terms | Shows an incident (a rodent sighting on a production line) triggers a defined response, in hours |
| Record ownership & access | Guarantees audit history survives a change of provider; auditors treat missing history as missing evidence |
| PCO registration & SANS 10133 | Confirms legal competence of every technician under Act 36 of 1947 and a recognised service standard |
Questions to put in your RFQ or tender
Structure the RFQ so weak providers disqualify themselves. Ask for: the PCO registration numbers of the technicians who will actually service the site; a sample station map and a sample trend report from a comparable facility (redacted is fine); the corrective action SLA in hours; whether any work is subcontracted; how records are delivered during an unannounced audit; and which named person reviews trends quarterly with your QA team. A provider who cannot answer these in writing will not survive your next certification audit either. For a scoring framework, see our companion guide on choosing a contractor for certified facilities.
Contract onboarding: the first ninety days
Awarding the contract is the halfway point. A professional onboarding runs: a full site survey against your zoning and product flow; station mapping with every device numbered, barcoded and placed on a signed site plan; a documented HACCP-designed IPM programme file for your food safety system; and a baseline trend built over the first quarter so that thresholds reflect your site, not a generic template. From ASC's Randburg office we run this onboarding across every Gauteng corridor, from Kempton Park and Boksburg to Midrand, Centurion and Vanderbijlpark, for manufacturers and food and beverage plants alike. Once the contract is scoped, benchmark the number with our 2026 Gauteng contract pricing guide.
Frequently asked questions
What should a pest control contract for a food manufacturer include?
A documented scope, risk-based service frequency, a site-specific risk assessment, mapped and numbered stations, trend analysis with action thresholds, corrective action SLAs, emergency callout terms and clear record ownership, plus confirmation of PCO registration under Act 36 of 1947 and SANS 10133 alignment, because auditors verify both.
How do FSSC 22000 and BRCGS auditors evaluate a pest control contract?
They read it as evidence the programme is designed, resourced and managed: scope reconciled against the risk assessment, frequency justified, stations mapped to a current plan, trending with corrective actions, and valid PCO registration for the technicians on the service reports. Gaps generate nonconformances even when no pests are found.
Why does it matter that ASC is owned by food safety specialists?
ASC is part of the ASC Food Safety Consultants group, the only SA pest control company owned by accredited food safety specialists. Contracts and documentation are structured the way an auditor reads them, and myASConline produces a one-click audit pack, which measurably reduces documentation findings.
