HACCP and Pest Control: The Documentation a Food Business Needs

Every food business in Australia runs under a food safety program of some kind, and every one of those programs contains a pest control clause. It is usually a single sentence in the manual: effective pest control must be in place. Then the auditor asks for the evidence, and that is where programs succeed or fail.

This guide explains where pest control sits in a food safety system, what a HACCP-based program expects to see, and what documentation an auditor, a supermarket customer or an export certifier will actually inspect.

What HACCP is — and what it is not

HACCP stands for Hazard Analysis and Critical Control Point. It is a systematic method for identifying biological, chemical and physical hazards in a process, deciding where they must be controlled, and proving the controls work. The seven principles are standard across Australia and internationally, having come from the Codex Alimentarius framework.

The part that is often misread: HACCP is the critical-control layer, and it sits on top of prerequisite programs. Pest control is a prerequisite program. It is not normally a Critical Control Point, because you cannot set a measurable critical limit for "no rodents" at a process step — you manage pests by preventing entry and detecting activity, not by measuring a batch.

That distinction matters practically. If a pest issue is treated as a CCP, the paperwork becomes unwieldy and the wrong person owns it. If it is treated as a prerequisite program, it gets the right structure: a plan, a monitoring routine, corrective actions, verification and records.

What the Food Standards Code requires

Chapter 3 of the Australia New Zealand Food Standards Code sets out the requirements for food businesses in Australia. Standard 3.2.2 covers food safety practices, and it requires a food business to take all practicable measures to prevent pests entering food premises, to eradicate or destroy pests on the premises, and to prevent food from being contaminated by pests.

Practically, that means a business needs:

• Premises designed and maintained to exclude pests: sealed doors, intact screens, no unsealed penetrations
• A pest control program appropriate to the business, delivered by a competent provider
• Records of the program: the plan, the service reports and the corrective actions
• Staff aware of what to report and to whom

Notice what is not in that list: a particular product, a particular frequency, or a particular equipment brand. The regulator does not prescribe a method; it requires a demonstrable program.

Where pest control sits in the manual

A well-filed food safety program will have pest control documented in three places:

1. The prerequisite program section — a written policy stating the provider, scope, frequency, and responsibilities.
2. The monitoring and verification section — how activity is detected, how counts are reviewed, and how trends are assessed at a management review.
3. The corrective action section — what happens when evidence is found, who signs it off, and how closure is verified.

If pest control appears only as an invoice in accounts, the program has a gap regardless of how good the service is.

The documents an auditor wants

Auditors are consistent, because they are reading against a standard. The pest file should contain:

• A site pest management plan — the layout, the pest risks identified by area, and the control strategy for each.
• A monitoring point map — every station, insect light trap and bait point numbered and located on a floor plan.
• Service reports — dated, signed, with findings by zone and counts at each point.
• Trend data — counts over time, ideally by zone, so a management review can see direction of travel rather than individual visits.
• Corrective actions — what was found, what was done, who owns it, when it closed and the evidence of closure.
• Proofing recommendations — the structural fixes recommended and their status. Auditors in particular want to see that a recommendation was closed, or that a decision was made deliberately.
• Chemical records — products used, rates, areas, technician and licence details, plus current safety data sheets.
• Licences and insurance — the provider's EPA licence and public liability certificate.
• Verification — the annual review of the program, its effectiveness and any changes made.

That pack is what a retail customer, an export certifier, or a certification body (SQF, BRCGS, FSSC 22000) will sample from. The businesses that pass easily are simply the ones whose file is current rather than assembled in the week before.

Designing the monitoring program for a factory

A food facility needs more than stations along a perimeter. Practical design:

Insect light traps at entry points, over doorways and along internal transitions, positioned so they draw insects away from open product and are never mounted above a line, a bench or exposed ingredients. Tubes are replaced on a schedule, and catch counts are recorded by trap — that is the trend data most programs are missing.

Rodent stations on the external perimeter at intervals, numbered against a site plan, plus internal stations in dry storage, plant rooms, compactor areas and behind equipment. Internal baiting should be restricted or replaced with traps and monitoring blocks because a bait that can be dragged is a contamination risk.

Crawling insect monitoring in warm, damp areas: plant rooms, wash-down zones, drains, beneath equipment and behind wall panels in production areas.

Stored product monitoring in ingredient stores and packaging stores, with pheromone support where relevant.

Reporting by zone, not by building, so a problem in one room is legible as a problem in one room.

Corrective action and how to close it

The difference between a competent program and a compliant one is the corrective action loop.

1. Finding recorded — what, where, how many, photo.
2. Immediate action — clean, remove, treat, isolate affected stock.
3. Root cause — the door that does not seal, the pallet stored against the wall, the drain that is never cleaned.
4. Structural fix assigned — to maintenance, with a date.
5. Verification — the next visit checks that the fix held and the finding has not recurred.
6. Closure recorded — with evidence, and signed by the responsible person.

Most audit non-conformances in pest control are not about live pests. They are about findings that were recorded and never closed, or closures with nothing attached to prove them.

Chemicals in a food facility

A food facility is the strictest environment for pesticide use, and the constraints are practical:

• A restricted, approved list of products for the site, agreed with the customer
• No application over exposed product, food contact surfaces or packaging
• Application methods that eliminate the risk of residue and drift: gels, dusts in voids, crack and crevice, sealed stations
• Locked, segregated storage with current safety data sheets
• A no-spray-during-production rule for critical areas, or agreed shutdown windows
• Spill response and a documented disposal route

Where a facility operates to a customer standard, that standard may be stricter than the law. Read the customer's requirement as well as the label.

Verification and annual review

Verification is the step that shows the program is working rather than merely running. Once a year, at minimum:

• Review the trend data and the monitoring map, and adjust station numbers where the layout has changed
• Review all corrective actions and their closure
• Review the pest risk assessment — new lines, new packaging, new suppliers, new buildings
• Review the product list and the current safety data sheets
• Confirm licences, insurance and technician training
• Re-issue the plan with a version and a date

Then present it in management review, with records. That act alone satisfies several clauses in most certification standards.

Supplier approval for the pest contractor

When a facility audits its pest provider, it should ask the same questions its customer will ask of it:

• EPA licence number and class of work
• Public liability and professional indemnity insurance
• Technician qualifications and ongoing training
• Product range and safety data sheets
• Method statements, risk assessments and site inductions
• Reporting format, and how trend data is supplied
• Response time for an incident

Price per visit is the least useful comparison, because a cheap program whose records will not pass an audit is a cost, not a saving.

Small businesses: what a cafe or takeaway needs

A small food business does not need a 60-page manual. It needs the equivalent in a thin folder:

• A one-page plan naming the provider, the frequency and the responsible person
• The service reports, in order
• The current safety data sheets for anything stored on site
• A short corrective action log
• A note of what staff should report and to whom

That meets the substance of the requirement and takes an auditor fifteen minutes to verify, which is exactly what you want in a 30-minute inspection.

Common non-conformances

• Monitoring map out of date after a fit-out, with stations that no longer exist
• Counts recorded without any trend review
• Proofing recommendations open for twelve months with no decision
• Safety data sheets absent, out of date, or for products no longer used
• Bait stations unlocked or unnumbered
• Light traps mounted above a production line
• Corrective actions closed with an invoice as the only evidence

Every one of these is cheap to fix and expensive to explain at audit.

Pest risk assessment for a new line or fit-out

Pest risk changes when the operation changes, and most facilities never revisit the assessment. Two triggers deserve a formal update:

A new product or ingredient. Moving into bagged dry goods, nut products, chocolate, pet food or grain-based ingredients introduces stored product pest risk that a chilled operation does not have. New packaging can also arrive with its own harbourage, particularly corrugated cartons with flutes that hold eggs and larvae.

A new fit-out or extension. A new line, a relocated store, a new dock, or a walled-off area creates voids, changes traffic flow and shifts where product sits. The monitoring map is almost always out of date the day the builders leave.

Run the update before commissioning, not after: walk the space with the layout drawing, ask where goods enter, where they wait, and where waste leaves, then place monitoring against that flow rather than against the old plan.

Training and staff awareness

An auditor will often ask a production operator a simple question: what should you do if you see a mouse? If the answer is uncertain, the program is not embedded.

What staff need is genuinely short:

• What to look for: droppings, gnaw marks, webbing, live insects, greasy rub marks, feathers
• What not to do: do not move or clean up evidence before it is reported, and do not spray anything themselves
• Who to tell, and how quickly
• Where the log is, and who owns it

A five-minute toolbox talk at induction, refreshed annually, covers it — and it turns twenty sets of eyes into a monitoring system that runs between visits.

Records retention and access

Decide how long the pest file is kept and who can produce it. Most facilities keep service records for at least the period their customer standard requires, often five years, and the practical test is whether a piece of evidence can be located in under a minute during an audit. A digital folder by year, with the plan and the monitoring map at the top, passes that test.

How Accurate Pest Control can assist

We build documented pest management programs for food manufacturers, packers and food service businesses across Newcastle and the Hunter, with monitoring maps, trend reporting, corrective action tracking and chemical records prepared for audit.

• Food manufacturing pest control
• Commercial pest control
• Chemical legislation and labelling
• Pest control certification guide
• Get a quote