Need a pest sighting record that leads to action? Explore our food safety and quality consulting support or contact AFVA for free initial guidance.
A food pest sighting log in NZ should help the next person understand what was found, which area or stock may be affected and what happened next. A note saying “pest contractor called” leaves those questions unanswered.
This guide is for owners, managers and food teams organising routine observations and follow-up. It proposes a practical record structure, not a compulsory national form, a pesticide method or a replacement for your actual Food Control Plan or National Programme.
Quick answer: Record the observation precisely, act through your applicable food-safety procedure, identify affected food and packaging, and assign follow-up. Connect the sighting to any contractor report, premises repair and product decision. Close the issue only when the agreed actions and checks are evidenced; a service visit alone is not that evidence.
Food pest sighting log: start with the actual requirements
For businesses subject to National Programmes, Part 2 of the Food Regulations 2015 applies to NP1, NP2 and NP3 unless stated otherwise. Regulation 51 requires pest inspections, appropriate corrective action and a prompt record of pest type and infestation extent. That scoped duty does not prescribe the table below for every business.
MPI’s National Programme 1 guidance, December 2025 describes regular pest checks, affected-area cleaning and disposal of contaminated food or packaging. Its pest card calls for records of the amount and types found. If you use a Food Control Plan or another system, follow its own applicable instructions.
Our broader food safety compliance checklist helps place pest records within the wider system. Keep inspection frequency, responsibilities and escalation arrangements consistent with that system rather than copying another site’s calendar.
Protect food and record what was actually observed
Use the relevant incident procedure immediately. Identify the affected area and anything that could have been exposed, including food-contact surfaces and packaging. Keep potentially affected stock controlled while the appropriate assessment is made. Follow the required food-disposal and affected-area cleaning steps; removing the pest is not clearance of the stock.
Write a factual description: location, approximate amount, condition and the time observed. If identification is uncertain, say so and obtain competent help. A photograph can support the description when safe to take, but should not delay control or spread contamination. Avoid changing an uncertain observation into a confident species diagnosis.
Record who was informed and when. Urgent findings need the appropriate immediate contact, rather than waiting unread in a register until the next scheduled visit. This article does not set a universal response time or instruct staff to handle pests, apply chemicals or improvise a cleaning method.
Build a log another person can use
AFVA recommends linking the following fields through a unique issue reference. They organise the work beyond the minimum information discussed above. Adapt them to your premises, staff and applicable requirements; a small business can use a clear paper or electronic record.
On a small screen, swipe sideways to view all columns.
Use a shared location reference in the site log, contractor documents and maintenance request. Do not merge an ordinary staff sighting with a formal trap count without preserving how each observation was obtained. Different methods and inspection effort can affect what the numbers mean.
Connect the contractor report with site responsibilities
The Codex General Principles of Food Hygiene, section 11.2 recommends reviewing outsourced monitoring reports and acting on findings. This is international technical guidance, not a substitute for New Zealand requirements. It supports a useful question: who has checked the report and completed the site’s part of the response?
Ask which findings concern activity, entry routes, harbourage or waste, and which need specialist action. Agree who communicates an urgent change. Keep the service report linked to the sighting, but record site actions separately when needed: a door repair, waste-area change or cleaning task is not completed merely because it appears as a recommendation.
For premises questions, the commercial kitchen setup guide gives broader context. This log should point to a repair or review rather than becoming an unqualified building or treatment specification. Use competent specialists for the work and protect food during it.
Review recurring findings before closing the issue
Review the records by area, observation type and action status. A repeated finding beside one door may justify checking the entry route and whether an earlier repair worked. Fewer reported sightings can also reflect fewer checks or poor reporting; do not call that proof of pest elimination.
Keep the product decision, treatment or repair completion and follow-up check distinct. The person closing the issue should be able to identify what was done and which observation supports the conclusion. Where evidence is incomplete, retain the open action and next step rather than entering “resolved” to tidy the register.
Hypothetical example: An operator records suspected droppings near unopened ingredient cases, controls the potentially affected stock and contacts the responsible person. A specialist assessment and the applicable food procedure determine the response. A damaged door seal is repaired and follow-up observations are recorded. Each action is linked; the example does not diagnose the pest or declare the stock safe.
Use a short review checklist
- Can another staff member find the exact observation location and relevant stock?
- Are immediate controls and any product decisions recorded separately?
- Does each outstanding action have an owner and a realistic next step?
- Have contractor recommendations reached the person responsible for the site task?
- Does closure refer to actual completed work and follow-up evidence?
Avoid vague location names, guessed identification, unsigned verbal promises and closing an issue solely on an invoice. Keep records accessible to the people who need them, with the retention arrangements applying to your business.
Frequently asked questions
Make one record trail work from observation to follow-up
Access Food Verification & Auditing Limited’s consulting service includes pest-control records, procedure review and corrective-action support. We can discuss a defined review of how your records connect with the work. This is food-safety system support, not a pest-eradication service or a guarantee that a particular treatment is suitable.
Contact AFVA with your current record, the issue and the support you need. Consulting does not replace registration, independent verification or the work of an appropriate specialist.
Official and technical references
- Food Regulations 2015: National Programme application and pest-control provisions
- MPI, National Programme 1 Guidance, December 2025, version 2 (council-hosted copy)
- Codex General Principles of Food Hygiene: pest-control systems
General information only: Requirements depend on the complete food activities, products, processes, locations and sales model. Follow the requirements applying to your business and obtain appropriate advice for an actual incident. This guide does not authorise product release, pest treatment or a regulatory outcome.
Need Practical Food Safety Support for Your Business?
Contact us for free initial guidance. We provide practical, plain-English food safety support for New Zealand food businesses across all service areas.
This article provides general information only and is not a substitute for professional advice specific to your situation. Contact us for guidance based on your actual food activities and requirements.