Pest Control Records and Inspections for Food Businesses

Australian food businesses generally must take all practicable measures to keep pests out of the premises and to eradicate and prevent harbourage, under Standard 3.2.2. Keeping clear records of pest inspections and treatments is how you demonstrate that control is working. Standard 3.2.2A adds record-keeping duties for certain critical controls at higher-risk businesses, and good pest records support that wider program. Whether you use a licensed contractor or check internally, log dates, findings, actions and follow-ups, and confirm exact requirements with your local council and state food regulator, as they vary. Key takeaways: Standard 3.2.2 generally requires you to take all practicable measures to prevent pests entering the premises and to eradicate and prevent their harbourage; clear records demonstrate you are meeting that duty.. Inspection frequency is risk-based, not fixed by the Code; many food businesses use periodic professional servicing (often quarterly) plus routine internal checks, adjusted for site, climate and pest pressure.. A useful pest record captures the date, who inspected, what was found (evidence and location), what chemicals or devices were used, and the corrective and follow-up actions.. Keep contractor service reports, a pest sighting log and a device map together so an environmental health officer can see the full picture quickly.. A contractor does not remove your legal responsibility — you still control cleaning, proofing, deliveries and daily monitoring, so pair professional servicing with an internal program.. Pest inspection frequency (risk-based): Check type, Typical frequency. Professional servicing — Commonly quarterly for general food service; often monthly for high-risk or problem sites. Internal staff checks — Daily scans of high-risk zones; a documented weekly walk-through. After triggers — Promptly after any sighting, neighbouring outbreak, building works or seasonal surge. Schedule review — At least annually, and increase whenever the log shows repeated activity. Why pest records matter under the Food Standards Code Pests carry pathogens, contaminate food and food-contact surfaces, and damage a business's reputation and stock. Under Standard 3.2.2 (Food Safety Practices and General Requirements), a food business generally must take all practicable measures to prevent pests entering the food premises and to eradicate and prevent the harbourage of pests on the premises and in food-transport vehicles. Standard 3.2.3 (Food Premises and Equipment) generally requires premises to be designed and constructed so they can be kept free of pests. The Code does not mandate a specific record format, but records are how you evidence that this ongoing control effort is actually happening. Records turn a claim ("we control pests") into evidence an environmental health officer (EHO) can verify. They reveal trends — recurring sightings in one area point to a proofing or hygiene gap. They protect you if a complaint or audit questions your due diligence. At higher-risk businesses captured by Standard 3.2.2A, a documented pest program supports the wider food safety controls the standard expects you to manage. How often should you inspect for pests? The Code does not set a single mandatory inspection interval. Frequency is risk-based and depends on your location, climate, the food you handle, building age and condition, and your history of pest activity. A common approach in Australian food service is scheduled professional servicing (many sites use quarterly, some monthly for higher-risk or problem premises) layered over frequent internal checks by staff. Warm, humid regions and premises near waterways, bins or vacant lots typically need more frequent attention. Professional servicing: commonly quarterly for general food service, more often (e.g. monthly) for high-risk sites, food manufacturing, or premises with recurring activity. Internal staff checks: daily quick scans of high-risk zones (bins, deliveries, dry store) and a documented weekly walk-through. After triggers: inspect promptly after any sighting, droppings, a neighbouring outbreak, building works, or seasonal surges. Review the schedule at least annually, and increase frequency whenever your log shows repeated activity. Contractor versus internal pest control Most food businesses use a licensed pest management technician for treatments and structural advice, while running their own daily monitoring. Both have a place, and neither alone is enough. A contractor brings licensed chemical use, device servicing and a documented service report; your team brings eyes on the premises every day. Pesticide application by professionals is regulated by state and territory laws — for example, licensing and record-keeping rules administered by state health or environment authorities — so leave chemical treatment to licensed technicians unless you are separately trained and permitted. Use a licensed contractor for: chemical treatments, rodent baiting programs, insect-control units, bait-station mapping, and expert proofing advice. Keep internally: daily and weekly monitoring, a sighting log, cleaning and waste routines, and delivery-inspection records. Check your contractor holds the correct state or territory licence and provides a written service report each visit. Remember: engaging a contractor does not transfer your legal responsibility under the Food Standards Code — you remain the food business proprietor. What to record for every inspection A pest record only helps if it is specific. "All clear" with no detail is hard to defend at audit. For each internal check and each contractor visit, capture enough that someone who was not there can understand what happened and what needs following up. Consistency matters more than length — use the same fields every time so trends are easy to spot. Date and time of the inspection or treatment. Who carried it out (staff name, or technician name and licence number). Areas inspected and the condition found (clean, sealed, evidence present). Type and location of any pest activity (e.g. rodent droppings near dry store, cockroaches behind the dishwasher). Devices checked: bait stations, insect-light traps, monitors — and their condition. Any chemicals or controls used, including product name and where applied. Corrective actions taken and recommended (proofing, cleaning, repairs). Follow-up date and who is responsible. Reading and filing contractor service reports Every professional visit should generate a service report. Do not just file it — read it, act on the recommendations, and record what you did. A report that recommends sealing a gap or fixing a fly screen becomes your evidence trail only once you complete and note the work. Keep the reports together with your internal log and a site plan showing device locations so the whole program can be reviewed in one place. Check the report lists activity found, products used, devices serviced and clear recommendations. Action the recommendations promptly and record the completion date against each one. Keep a current bait-station and device map — commonly expected at audit and a hallmark of a well-run program. Store reports so they are quick to retrieve during an inspection — a labelled folder or a digital record both work. How long to keep pest records Retention periods can differ by state and by the type of record. As a general rule, keep pest inspection logs, service reports and corrective-action notes long enough to show an ongoing program — many businesses retain at least 12 months so seasonal patterns are visible. Records made under Standard 3.2.2A generally must be kept for a minimum of three months (a period linked to pathogen incubation and outbreak investigation); while pest control is not itself one of that standard's prescribed provisions, aligning your retention with it is sensible. Licensed pest technicians have their own pesticide record-keeping obligations under state law, which can be longer. Confirm the specifics with your council and state regulator. Keep internal logs and contractor reports together and in date order. Retain records at least long enough to show trends across seasons (12 months is a practical minimum). Standard 3.2.2A records generally must be kept for at least three months. Pesticide-application records held by your contractor are governed separately by state pesticide laws. Building an integrated pest management (IPM) program Records are one part of integrated pest management — an approach that prevents pests rather than just reacting to them. IPM combines exclusion (keeping pests out), restriction (denying food, water and harbourage), and destruction (treatment) with ongoing monitoring. Strong records feed the monitoring loop: they tell you whether your exclusion and hygiene measures are actually working, so you can fix root causes instead of repeatedly baiting the same corner. Exclusion: seal gaps, fit door sweeps and fly screens, screen vents and drains, keep external doors closed. Restriction: manage waste and bins, clean spills promptly, store food off the floor and sealed, fix leaks. Destruction: licensed treatment and correctly placed, serviced devices. Monitoring: internal checks plus contractor servicing, all logged, with trends reviewed regularly. Worked examples: Acting on a contractor's report: A restaurant's quarterly service report recommends sealing a gap near the dry store and fixing a fly screen. Instead of just filing it, the manager arranges the work, records the completion date against each recommendation, and stores the report with the internal sighting log and a current bait-station map, so the whole program can be reviewed in one place at audit. Checklist: Documented, risk-based inspection schedule (internal checks plus licensed servicing). Standard inspection record with fixed fields used every time. Current bait-station and device map for the premises. Contractor service reports read, actioned and filed — not just stored. Corrective actions recorded with a responsible person and follow-up date. Sighting log where any staff member can report activity immediately. Records kept together in date order and retained at least 3 months (12 months is safer). Contractor's pest management licence current and on file. Common mistakes: Filing contractor reports without reading or acting on the recommendations. Logging "all clear" with no detail, so trends and warning signs are invisible. Relying on a contractor alone and skipping daily internal monitoring. Placing bait stations or insect units above food-preparation surfaces where killed pests or pesticide could contaminate food. Using a fixed interval regardless of climate, season or a rising number of sightings. Treating the symptom (baiting repeatedly) instead of fixing the entry point or hygiene cause. Assuming a pest contractor removes your legal responsibility under the Food Standards Code. Discarding old logs too soon, leaving no evidence of an ongoing program at audit.