HACCP pest control: what food-safety auditors expect

An auditor at a food premises is not assessing whether the site has pests; they are assessing whether the site has a functioning pest management programme and can evidence it. That distinction reframes the whole engagement. Finding activity is not a failure — finding activity that nobody recorded, trended or acted on is. A site with a live rodent hit properly logged, escalated and closed out will audit better than a site with a clean sheet and no evidence anyone looked.

The evidence has a predictable shape: a documented programme, a map of where the devices are, a record for each device on each visit, findings written down with someone responsible for them, and a demonstrable trend over time. An auditor works through those in order, and weaknesses compound — if the device map is out of date, every visit record referencing it is suspect, and the trend built on those records is worthless.

The provider carries more of this than most realise. The food business owns the food-safety programme, but the pest control provider supplies most of the documentation the auditor will read, and a provider whose paperwork lets a client down loses the contract regardless of how good the actual pest control was.

Every monitoring and control device at an audited site must be uniquely numbered and shown on a site map, and that map must be reviewed, dated and signed at least annually. The map is the reference every other document points at: a service record listing station 14 means nothing unless station 14 has a fixed, agreed location that both parties recognise.

Unique identification means each device carries a number that is not reused, is physically present on the device, and matches the map and the records. Devices move — a pallet racking reconfiguration relocates six external stations, a kitchen refit removes two — and the discipline that separates a good programme from a poor one is whether those changes flow back to the map on the visit they happen, rather than at the next annual review.

Treat each device as a tracked object with a history rather than a row on a checklist. Its identifier, type, location including a map reference or GPS position, install date, and the full timeline of readings against it are what let you answer the questions an auditor actually asks: how long has this station been showing activity, when was it last replaced, and why is there a device here at all.

A food-grade service visit is complete when every device on the map has been serviced and given a result, and everything observed has been recorded against a responsible party. Partial service is worse than no service from an audit perspective, because a device with no reading for a month leaves a gap in the trend that nobody can explain later.

The elements below are what a compliant food-grade visit produces. They are also, not coincidentally, the structure of the service report the client will hand to their auditor.

The sanitation and proofing observations — conditions conducive to pest activity — are the part of the file auditors scrutinise hardest and providers execute worst. A condition conducive is anything about the premises that makes pest pressure more likely: a gap under a delivery door, standing water behind equipment, waste held too long, product stored against a wall, a damaged seal, poor rotation in a dry store.

Providers do this badly in a specific and recognisable way. The observation gets written as a generic note — 'housekeeping requires attention' — with no location, no recommendation and, critically, nobody's name against it. That note is useless to an auditor and worse than useless to the client, because it establishes that the condition was known without establishing that anybody was asked to fix it.

What an auditor wants to see is a chain: an observation tied to a location, a specific recommendation, a named responsible party, and a status that changes over subsequent visits. The named party is the load-bearing element. It converts an observation into an assigned action, and it protects the provider — a condition raised six visits running and assigned to the client each time tells a very different story about who failed than the same condition noted vaguely and never followed up.

It also changes the commercial relationship for the better. Conditions conducive that sit with the client and are visibly tracked are the strongest argument a provider has for why the site still has pressure, and the most persuasive evidence at contract renewal that the programme is being run properly.

Trend analysis is what turns a stack of visit reports into a programme, and audited sites are expected to have it. The requirement is not a chart for its own sake — it is the ability to answer whether pest pressure at this site is increasing or decreasing, where it is concentrated, and whether the actions taken have worked.

The useful cuts are catch counts by device, by area and by date; activity by species; and corrective actions raised against actions closed. Each answers a different audit question. Counts by device reveal hot spots and dead devices. Counts by area point at causes — a spike confined to goods inwards is a different problem from one spread across the production floor. Species trends explain seasonality that would otherwise look like a service failure. Actions raised against actions closed is the honest measure of whether the programme is functioning at all.

This only works if the per-device readings are structured data captured at the time. A trend reconstructed from PDFs at the end of the year is a reporting exercise; a trend that updates as the technician records each station is a management tool, and it is visible to the auditor as one.

An audited food site expects a single folder — physical, electronic or both — holding the whole pest management programme, and expects it to be current on the day of the audit rather than assembled in the week before. The provider supplies most of its contents.

The folder holds the service contract and the agreed service schedule; the licences of the technicians who attend the site, in date; the provider's insurance certificates; the Safety Data Sheets for every product that could be used there; and the site risk assessment. Alongside that sit the operational records: the device map, the per-visit service reports and device logs, the pest sighting register, the trend analysis, and the open and closed corrective actions.

The pest sighting register deserves particular attention because it is the one document the client fills in rather than the provider. It records what site staff saw between visits, and an empty register at a busy site is not reassuring to an auditor — it usually means nobody told staff it existed. Setting it up, explaining it and reviewing it on each visit is a provider responsibility in practice even when it is a client document on paper.

The single most common failure here is a licence that expired between visits, sitting in a folder that nobody re-checked. It is trivially avoidable and it undermines everything filed behind it.

HACCP and the AIB standards are the two frameworks most Australian food-premises audits sit under, and neither can be summarised safely from a secondary source. HACCP is a hazard analysis and critical control point methodology applied to food production, under which pest management is a prerequisite programme rather than a critical control point itself. The AIB standards are a separate, independently published audit scheme with its own scoring approach and its own expectations of pest management documentation.

Which framework applies to a given site is the client's decision, driven by their customers and their certification, and it changes what the auditor weights. Ask at the outset which scheme the site is audited under and to what version, because designing a service around the wrong one is expensive to discover during an audit.

Obtain the authoritative text from the publisher. We describe the categories of requirement in our own words here deliberately; the standards are copyright documents, and a paraphrase circulating between providers is exactly how a programme ends up built on a version of a requirement nobody can trace.

This guide is general information about how the Australian pest control industry is regulated. It is not legal advice, it is not a substitute for the legislation or the standard it describes, and requirements change. Confirm the current position with your state or territory regulator, and get the authoritative text of any standard from its publisher.