Choose a log staff will actually use
Use a single agreed place for observations. It might be a paper sheet at the supervisor's desk or an existing shared document. Avoid creating a complicated new system if staff already use an incident register. The important feature is that the person responsible for pest follow-up can find every entry, including those made outside their own shift.
Give the log a short instruction at the top: record an observation, notify the nominated person and follow the site's immediate response procedure. Staff should not have to complete a long form before raising a concern. Separate urgent communication from later administrative detail. A photograph can be added after the responsible person has been told, provided taking it is safe and does not interfere with the site's response.
Decide who can edit entries and who reviews them. If everyone can overwrite the last row, useful history can vanish. Preserve the original observation and add a dated update when details change. A small business does not need elaborate software to do this well. It needs a consistent location, a responsible reader and a record that retains what was originally reported.
Name locations consistently
Draw a simple plan of the premises and assign ordinary names to the relevant areas. Rear delivery door, dry stock shelf beside the office and staff kitchenette under-sink cupboard are useful descriptions. A broad label such as kitchen or warehouse often leaves the contractor searching a much larger area than the witness intended.
Match location names to fixed features rather than movable stock. The shelf near yesterday's delivery may mean something different tomorrow. Doorways, wall corners and equipment identifiers usually make better reference points. If your contractor already uses a site map, ask whether staff can use the same labels. Do not invent new labels for pest devices without checking the existing map.
Record whether the observation was inside or outside and whether it was on a floor, shelf or visible wall surface. Staff should not climb racks, move industrial equipment or enter service voids to make the description more precise. If the exact position cannot be seen safely, note the nearest reliable reference. A bounded observation is more useful than a guess presented as a confirmed location.
Describe the evidence without naming the species
Write what was actually seen. For an insect, useful observations may include its approximate appearance, whether it was moving and the surface it was on. For possible rodent activity, describe the visible evidence or sound without assuming which animal caused it. The professional can assess identity and significance; the witness's job is to preserve the observation accurately.
Photographs are helpful when taken from a safe position, but staff should not handle pests, droppings, carcasses or bait devices to improve them. Avoid close contact with unknown insects or animals. A wider image showing the location and a closer image of safely visible evidence can serve different purposes. Keep the original image rather than applying filters or drawing over the only copy.
Record uncertainty directly. Possible insect beneath shelving is an honest description if the witness only saw a brief movement. If several people discuss the event, distinguish the original witness from later interpretation. This reduces a common problem in shift-based businesses: a tentative report becomes a confident species identification after being repeated by several colleagues. The contractor should receive the first-hand observation as well as any subsequent confirmed finding.
Capture the timing and the immediate response
Record the date and approximate time of the sighting, plus when it was entered in the log if those differ. A report made at opening may describe something noticed during the previous evening's close. That distinction can matter when comparing activity with deliveries, cleaning or doors left open. Do not force staff to invent an exact time they cannot remember.
Add what was happening nearby: a delivery was being unpacked, a roller door was open, or routine cleaning had just finished. These are context notes, not proof of a cause. Avoid blaming a supplier, staff member or neighbouring business based on timing alone. Patterns need investigation, and a single event rarely establishes how a pest entered.
Record the immediate action and the person notified. In a food business, use the existing food-safety procedure for potentially affected food or food-contact areas rather than waiting for a routine contractor visit. Food Standards Australia New Zealand's pest guidance explains the need to prevent pests and protect food. Ask the responsible food-safety person or regulator about your specific response; this log should support that process rather than replace it.
Keep observations separate from contractor findings
Create a follow-up area beside each sighting entry. This can record the contractor's visit, what they assessed, what action they took and what they recommended next. Do not rewrite the staff observation to match the final conclusion. Keeping both shows how the issue was investigated and prevents the record from losing its original context.
Link the entry to the relevant service report or photograph using a filename or reference. A folder full of service PDFs is difficult to search if the sighting log never identifies which report answered which concern. Likewise, the report should be recognisable by date and area. Ask the contractor to explain unclear device or location references before the record is archived.
A contractor may recommend a building repair, a storage change or further monitoring rather than treatment at every sighting. Record the action and who will arrange it. If a landlord or equipment contractor must be involved, the business manager needs a clear handoff. The rodent entry repair planning guide explains why an apparent opening requires a coordinated repair scope rather than indiscriminate sealing.
Use the log to identify operational patterns
Review entries by location and event type, not just total numbers. Repeated observations beside one delivery entrance may justify investigating that interface. Scattered entries across several rooms may suggest a different assessment scope. These are reasons to ask better questions, not reasons to diagnose the premises from a spreadsheet.
Changes in reporting can distort apparent trends. More entries may mean a new supervisor encouraged staff to report, while fewer entries may mean the night shift stopped using the log. Keep brief notes about changes in observation routines. A comparison only helps if you understand whether the same areas were being observed in a similar way.
Hypothetical example: a small shop records sightings near its rear door on delivery mornings. The manager adds a note about delivery handling and asks the contractor to inspect the doorway and adjacent storage. The contractor's findings lead to a specific repair request and a follow-up observation plan. The business does not conclude that the supplier caused the problem; it uses the timing and location to make the inspection more focused.
Close actions with evidence
An action should remain open until the nominated person has checked the agreed completion evidence. A message saying maintenance attended does not tell you whether a damaged door seal was replaced or merely inspected. Ask for a brief description of the completed repair and connect it to the original location in the log.
Closure can have more than one stage. A repair may be complete while the pest professional still needs to review activity afterward. Record these as separate steps so the administrative status does not imply the biological problem is resolved. If further observations occur, link them to the earlier entry and explain what changed rather than deleting the previous closure.
For a food business, documentation should sit within the wider food-safety system. FSANZ's pest management guidance describes useful records including inspections, treatments and remedial recommendations. A completed log by itself does not certify compliance or guarantee an audit outcome. Its practical value is that staff, management and the contractor can see what happened and whether the agreed response was carried through.
Prepare a concise contractor brief
Before requesting a visit, summarise the active questions from the log. Include the premises type, the affected areas, the observations, any relevant photographs and the current service arrangements. Tell the contractor which areas can be accessed during trading and which need a different arrangement. This is more useful than forwarding a large unfiltered message history.
Ask whether the visit is intended to identify a pest, investigate entry points, review a continuing program or assess a specific recurrence. Each question may require a different scope. Provide existing device maps and recent service reports where available, and explain any changes to the premises since they were prepared. Do not move or open installed pest devices to produce an inventory yourself.
Agree who receives the findings and who can authorise further work. A contractor speaking only with a staff member who cannot approve repairs may leave the important decisions unresolved. Use the commercial pest service page to start the conversation, then request a proposal based on the actual premises and recorded concern. The best log is the one that leads to a precise question, a responsible decision and a traceable follow-up.
Write a usable example entry
A hypothetical staff entry could read: opening shift, rear delivery doorway, one small dark insect moving on the inside floor beside the door; manager notified; photograph saved as rear-door-opening. If the witness cannot identify the insect, the record should say so. A later contractor entry can add the assessed identity, inspection findings and recommended action without erasing the original description.
The manager can then add a separate repair reference, the person responsible and the follow-up date agreed with the contractor. If no further observation is made, record the area actually checked rather than writing no pests anywhere. A brief observation of the delivery area says nothing about locked storage or the ceiling void. Keeping that scope visible makes the record more honest and more useful when the contractor compares several visits.
Avoid adding customer names, payment information or unrelated staff details to pest photographs and notes. Crop a sharing copy if private information is visible, while preserving the original evidence securely under your existing business records procedure. Send the contractor only the material needed to assess the pest concern.
Business log readiness check
Use this check to review your reporting process before briefing a contractor. It assesses whether the information is ready to discuss, not whether the premises are pest-free.
Checklist selections are not submitted.
Checklist progress appears here.