Pest control records: why inspectors ask for them first
General information for UK hospitality operators, not legal advice. If something here is wrong or out of date, the editorial policy explains how to report it.
Pest control is a legal duty, but pest control records are what inspectors actually check, not just the contractor's invoice.
The Food Safety and Hygiene (England) Regulations 2013 require every food business to have adequate procedures in place to control pests, a duty that has applied unchanged since the regulations came into force. In practice this means an environmental health officer arriving on any given day expects to see two things: evidence that the premises actively prevents pests, and pest control records that show any problem found was dealt with. An inspector who finds live evidence of an infestation, droppings, gnawing or nesting material, can close a kitchen on the spot, and that outcome is rare in premises with a working contract. The far more common failing is quieter: a contractor visits on schedule, writes a perfectly competent report, and that report is then lost, filed inconsistently, or never followed up, so the business cannot show the control it is actually achieving. Pest control records are what turn a contract into proof, and getting them right is a matter of routine rather than expense.
What the regulations actually require
The wording in the Food Safety and Hygiene (England) Regulations 2013 does not specify a named contractor, a set visit frequency or a particular type of bait station. It asks for a system that keeps pests from contaminating food, so far as is reasonably practicable, and it expects the business to be able to demonstrate that the system exists and is actually followed day to day. A signed contract with a pest control company proves that a service has been engaged; it does not, on its own, prove that pests are being kept out or that problems are caught early. Inspectors know the difference, and they will usually ask to see the visit reports themselves rather than take the existence of a contract as sufficient evidence of control.
Prevention is the standard, not reaction
Environmental health officers expect proactive control rather than a reaction once pests are already established. That means proofing gaps around pipework, doors and cladding, keeping drains clear and covered, storing deliveries off the floor and away from walls, and making sure bins are not left overflowing or uncollected for long periods. Waste that sits out overnight, particularly food waste, is one of the most reliable ways to attract rodents, flies and gulls to a back door, and getting bin storage right removes a large part of the risk before a pest control contractor ever needs to be involved. How premises are expected to separate and store food waste is covered in our guide to commercial food waste separation, and the same principles apply whether the concern is recycling compliance or pest prevention.
Most sites also hold a contract with a professional pest control provider who visits on a fixed schedule, usually monthly or bi-monthly depending on risk, to inspect bait points, check for signs of activity and report findings. That visit is only the first half of the job. The second half is acting on whatever the contractor recommends, whether that is a proofing job, a change to bin storage, or closer monitoring of a specific area, and recording that the action was completed.
Why pest control records matter more than the contract
Pest control records are what turn a contractor's visit into evidence of control rather than simply evidence of spend. A single report showing no activity found is useful on its own, but the record that actually protects a business is the trail across several visits: what was recommended, on what date, and who signed off that the recommendation was carried out. If a contractor flags a gap under a fire door and recommends proofing, and that same recommendation appears unactioned on the next two reports, the record itself has stopped being a defence and started being evidence of a known risk that was ignored.
Inspectors tend to read pest control records the way they read the rest of a due diligence file: as proof that the business responds to what it is told, not merely that it pays someone to look. That principle runs through every part of a food safety system, from cleaning schedules to temperature logs, and it applies to pest control as directly as anywhere else. Our guide to the due diligence defence sets out why records, rather than good intentions, are what actually stand up when a business needs to show it took reasonable precautions.
What a complete pest control record should contain
A usable pest control record is more than a filed PDF from the contractor. It should capture the date and time of each visit, what was found including any evidence of activity rather than just a trap count, the recommendation made if any, the date that recommendation was actioned, and who was responsible for closing it out. Where a recommendation involves building work, such as proofing a wall or replacing a door seal, the record should link through to a maintenance job and its completion date rather than sit as an isolated note that nobody circles back to. The Food Standards Agency's Safer food, better business (SFBB) pack is where many independent operators are expected to log checks of this kind, and pest control fits alongside cleaning and temperature diaries in that system rather than sitting apart from it.
- Date, time and outcome of every contracted visit.
- Any recommendation made, with a clear owner and a target date.
- Confirmation and date that the recommendation was completed.
- Repeat findings in the same area, flagged for escalation rather than repeated as routine notes.
Common failures in multi-site pest control record keeping
The most frequent problem is not an active infestation, since most contracted providers do a competent job of monitoring for one. It is that the evidence of that monitoring never makes it into a coherent, retrievable file. Reports arrive by email to whichever manager was on shift that day, get printed and left in a folder in a back office, or simply do not survive a change of site manager months later. In a group running several sites this fragmentation multiplies quickly: head office cannot see which sites have outstanding proofing work, which are overdue a visit, or which venue has had repeat activity in the same corner of the kitchen for months running. An area manager who cannot answer those questions as fast as an inspector can ask them is relying on the contractor's competence alone, rather than on a system the business actually controls.
Linking pest control evidence to the rest of your food safety system
Pest control does not sit apart from the rest of a food safety system; it is one input into the same file that already covers cleaning, temperature control, allergen checks and supplier approval. Keeping visit reports, recommendations and sign-offs alongside those other records, rather than in a separate folder or a contractor's own portal, means an inspector reviewing any part of the system can see the whole picture without a manager going to find a different document. It also means an outstanding pest control action is visible next to an outstanding cleaning task or a missed temperature check, so it is not forgotten simply because it happens to belong to a different supplier. This kind of consolidated approach is also what supports a strong food hygiene rating score, since inspectors mark the whole management system rather than any one record in isolation. Digital food safety software that holds pest control evidence alongside HACCP monitoring, cleaning schedules and supplier checks removes the fragmentation that causes most of the lost marks in this area, because every site logs the same information in the same place.
Next step
See how food safety software keeps pest control visits, recommendations and completed actions together for every site.
Frequently asked questions
How often should a pest control contractor visit?
There is no fixed legal frequency. Most premises are visited monthly or bi-monthly depending on a risk assessment covering location, waste storage and previous activity. What matters to an inspector is not the exact interval but whether visits are happening on schedule and whether the records show any findings were followed up rather than left open.
What should a pest control record include as a minimum?
Each entry should show the date and time of the visit, what was found including any evidence of activity, any recommendation made, the date it was actioned, and who signed it off. Repeat findings in the same area across visits should be flagged clearly rather than logged as routine, separate notes.
Can a single pest sighting close a kitchen?
Evidence of an active infestation, such as droppings, gnawing or nesting material, can lead an inspector to restrict or close operations on the spot. This outcome is rare where a contract and consistent records already exist; it is far more common where control was actually adequate but nobody could prove it on the day.
Who should be responsible for pest control records across multiple sites?
The site manager typically receives and files the contractor's report, but an area or group manager should have visibility of every site's status without asking each manager individually. Leaving pest control evidence with one person per site creates a single point of failure that shows up the moment that person is away or moves on.
How long should pest control records be kept?
There is no single statutory retention period set specifically for pest control reports. Keeping at least twelve months of visit history alongside other food safety due diligence records gives an inspector a track record to review and gives the business its own evidence that recommendations were consistently acted on over time.