Working With a Pest Control Contractor

A pest control contractor is only as useful as the paperwork and follow-up around them. To satisfy the Food Standards Code and your auditor, you need a written service agreement, dated monitoring reports after every visit, evidence you acted on recommendations, and a tidy records file. This guide explains what a good agreement covers, how to read monitoring reports, how to close out recommendations, and what to keep for audits. Key takeaways: The Food Standards Code makes YOU responsible for a pest-free premises, even when a contractor does the treatments.. A written service agreement should define scope, frequency, bait/device maps, chemicals used and reporting.. Every visit should produce a dated, signed monitoring report you keep on file.. Auditors look for evidence you acted on recommendations, not just that a contractor attended.. Keep reports, the agreement, a site plan, SDS and licences together in one pest control file.. Who is responsible: you or the contractor? Under Standard 3.2.2 of the Food Standards Code, a food business must take all practicable measures to prevent pests entering the premises and to eradicate and prevent harbourage of pests on the premises. Engaging a licensed pest control contractor is one of the most practical of those measures, but it does not transfer the legal responsibility. If an auditor or authorised officer finds evidence of pest activity, it is your business that is answerable, regardless of who holds the service contract. Treat the contractor as a specialist partner who provides monitoring, treatment and expert advice, while your team retains ownership of day-to-day prevention: sealing gaps, managing waste, cleaning, stock rotation and reporting sightings promptly. The best outcomes come from that shared model rather than assuming a monthly visit alone keeps pests out. Choosing a licensed contractor Pest management technicians who apply pesticides are licensed at the state or territory level, and the licensing scheme and business registration requirements differ between jurisdictions. Before you sign, confirm the technician and the business hold current licences and insurance, and ask how they approach integrated pest management (IPM) rather than relying solely on chemicals. A contractor experienced with food premises should understand the Food Standards Code, know which products are safe to use around open food, and be comfortable working around your production hours. Confirm licensing and any local registration requirements with your state or territory regulator and local council. Current pest management licence for the technician and business. Public liability and professional indemnity insurance. Experience specifically with food premises and audit expectations. An integrated pest management approach, not chemicals by default. Willingness to provide written reports and safety data sheets. What a service agreement should cover A verbal arrangement is not enough for an audit. Ask for a written service agreement that clearly sets out the scope and standard of service so both sides know what is expected. It should name the premises and areas covered, the frequency of routine visits, the target pests, and the response time for call-outs when you report activity between visits. It should describe the devices installed and where they are located, the products that may be applied and their safety data sheets, and exactly what documentation you will receive after each visit. A clear agreement also protects you when a new auditor or officer asks to see the basis of your pest program. Premises and specific areas covered (kitchen, store, bins, external). Routine visit frequency and emergency call-out response times. Target pests: rodents, cockroaches, flies, stored-product pests, birds. A device/bait station map with numbered locations. Chemicals that may be used, with current safety data sheets (SDS). Reporting: what you receive after each visit and how quickly. Understanding monitoring reports Every visit should generate a monitoring report, sometimes called a service report or service docket. This is the single most useful document in your pest control file because it is the dated evidence that monitoring is actually happening. A good report records the date and time, the technician's name and licence, the stations or areas inspected, any activity or catches found, any products applied with quantities and locations, and recommendations for you to action. Read each report when you receive it rather than filing it unread; the recommendations are where your obligations sit. If a report is vague or simply says 'no activity' every visit with no detail, ask the contractor to provide the level of detail an auditor expects. Date, time and technician name and licence number. Stations, traps or areas inspected on this visit. Activity, catches or evidence found, and where. Products applied, quantities and treatment locations. Recommendations and any conducive conditions noted. Acting on recommendations Auditors consistently look for a closed loop: the contractor identifies a problem or a conducive condition, and your business does something about it. Recommendations often sit outside the contractor's scope, such as sealing a gap under a delivery door, fixing a dripping tap that attracts pests, removing cardboard harbourage from a store, or improving bin hygiene. When you receive a recommendation, decide who owns it, act within a reasonable timeframe, and record what you did and when. A recommendation that appears on three consecutive reports with no action is exactly the kind of finding that turns into a non-conformance. Where a recommendation cannot be actioned immediately, note the interim control and the planned completion date so your intent is documented. Keeping records for audits Keep everything related to pest management together so you can produce it quickly during an audit or inspection. Your pest control file should hold the service agreement, a current site plan showing device locations, every monitoring report in date order, the safety data sheets for any products used, and evidence of the contractor's licences and insurance. Alongside the contractor's paperwork, keep your own internal pest sighting log so staff can record activity between visits, and your evidence of actioned recommendations. Check your state or territory and industry requirements for how long to retain records, and confirm any specific retention period with your regulator; as a practical rule, retaining at least the current and previous audit cycles is sensible. Signed service agreement and scope. Current site plan / device location map. All monitoring reports in date order. Safety data sheets (SDS) for products used. Contractor licences and insurance certificates. Internal pest sighting log and evidence of actioned recommendations. Managing the relationship day to day The contractor visits periodically, but pest prevention is continuous, so keep the partnership active between visits. Brief your team to report sightings immediately into the internal log rather than waiting for the next service, and pass those observations to the contractor so they can adjust their approach. Give the technician safe, unobstructed access to stations at each visit, and never move or discard bait stations or devices without telling them. Review the reports as a trend over time, not one at a time: repeated activity in the same area points to a structural or hygiene issue your team needs to fix. A short conversation at each visit about what the technician saw is often more valuable than the docket alone. Checklist: Written service agreement on file with defined scope and frequency. Contractor and technician licences and insurance verified and current. Current site plan showing all bait stations and devices. A monitoring report received, read and filed after every visit. Safety data sheets held for every product applied. Recommendations assigned an owner and actioned with a date recorded. Internal pest sighting log in place for staff to use between visits. All pest records stored together and retrievable for audit. Common mistakes: Assuming the contract transfers your legal responsibility for a pest-free premises. Filing monitoring reports unread and never acting on recommendations. Letting the same recommendation recur on report after report with no action. No written agreement, so scope and frequency are unclear at audit. Moving or discarding bait stations without telling the contractor. No safety data sheets on file for chemicals used on site. Relying only on the contractor and neglecting daily prevention and hygiene.