In a food manufacturing audit, pest control is rarely assessed on whether pests were present. It is assessed on whether you can demonstrate a system: a documented assessment of the risk at this site, a monitoring plan that covers the facility rather than the obvious corners, evidence that it was inspected on schedule by someone qualified to interpret what they found, and a record that shows what has been happening over time rather than on the day.
That is the reason a site can pass with evidence of activity and fail with none. An auditor who sees a sighting log, a trend, an action taken and a verification is looking at a system that works. An auditor who sees a clean site and a thin file is looking at a site that might simply have been lucky since the last visit.
Nightshift has been protecting food manufacturing facilities for over 45 years, and the programme below is built to be read by somebody else: your technical manager, your customer's auditor, and whoever arrives unannounced.
The programme
Site-specific risk assessment
Written for your facility rather than adapted from a template. What is manufactured, where the raw intake and waste streams run, which structural features and neighbouring land drive the pressure, and where a failure would reach product. This is the document the rest of the programme is derived from, and an auditor will ask to see the link between the two.
Mapped monitoring plan with facility-wide coverage
Every device numbered, positioned and mapped, covering the whole facility including the areas nobody walks past: voids, roof spaces, service runs, external perimeter and the intake and dispatch faces. A plan that covers production and stops at the plant room door is the most common finding we see on sites that thought they were covered.
Routine technician visits every 4 to 8 weeks
Frequency set from the risk assessment rather than from a standard contract, within a 4 to 8 week interval according to what the site actually is. High-risk open-product areas are not visited on the same cycle as an ambient warehouse, and the assessment is what justifies the difference if anybody asks.
Field biologist inspections at least twice a year
Nightshift's qualified field biologists inspect at least twice yearly, independently of the routine visits. This is the layer auditors look for and many programmes lack: an experienced specialist reviewing the whole system, challenging the device layout, reading the trend rather than the last visit, and recommending change before a pattern becomes a finding.
Fully compliant products and processes
Integrated pest management throughout: exclusion, proofing and monitoring first, with treatment targeted rather than routine. Rodenticide use follows CRRU stewardship, and non-toxic monitoring is used in open-product areas wherever it will do the job. Every product used is appropriate to a food environment and evidenced as such.
Complete sighting logs and trend analysis
Your own staff sightings and our findings in one record, so the log tells a single story rather than two. Trend analysis across visits is the part most files are missing: three catches in the same zone over three months is a pattern and needs an action, while three catches in three different zones is background. An auditor is testing whether anybody noticed the difference.
BPCA-qualified staff with food industry experience
BPCA membership, CEPA certification, and technicians who have worked food manufacturing sites rather than learning them on yours. The practical difference shows in what somebody does not do: where they walk, what they open, what they will not place near open product, and how they behave in a high-care area.
Audit-ready documentation from day one
The file is built for an auditor from the first visit rather than assembled when one is booked. Reports issued the same day, RAMS and COSHH on request, device maps current, actions tracked to closure, and everything maintained and accessible rather than archived somewhere only we can reach.
What a pest control non-conformance actually costs
Pest management is examined in every food safety audit that matters, and it is a recurring source of findings because it is one of the few areas where the evidence is cumulative. You cannot produce six months of trend data in the week before an audit.
A minor finding is a corrective action and an irritation. A major or critical finding against pest control is a different matter: it can move a grade, trigger an unannounced re-audit, and in the worst case suspend a certification that a customer contract depends on. The cost is almost never the treatment. It is the contract that required the certificate.
That is why the argument for a documented programme is not really about pests. Failure in pest control invalidates the HACCP plan built on top of it, because that plan assumes the prerequisite is working. The systematic, documented version is what protects the certification.
Common questions
Is pest control a CCP or a prerequisite programme under HACCP?
In almost all food manufacturing HACCP plans, pest control is a prerequisite programme rather than a critical control point. That is precisely why a failure matters so much: the plan does not monitor it as a CCP because it assumes the prerequisite is already controlling the hazard. When the prerequisite fails, the assumption underneath the plan fails with it, and the plan itself no longer demonstrates control.
Will your documentation satisfy a BRCGS or SALSA audit?
It is written for that purpose rather than for our own records. You get a site-specific risk assessment, a current mapped device plan, dated reports from every visit, combined sighting logs, trend analysis across visits, field biologist reports at least twice a year, and actions tracked to closure. To be clear about what we are and are not: those standards certify your business, not your pest contractor. What we provide is the pest control evidence your audit requires.
How often should a food manufacturing site be visited?
Between every 4 and 8 weeks, set by the site-specific risk assessment rather than by a standard contract. What justifies the interval matters as much as the interval itself: an auditor asking why a high-care area is on the same cycle as an ambient store wants to see the assessment that decided it, not a schedule that was never revisited.
What does a field biologist add over a routine technician visit?
A different job. The routine visit services the system; the biologist inspection reviews whether the system is still right. That means challenging the device layout, reading the trend across months rather than the state on the day, assessing structural and proofing issues, and recommending change before a pattern becomes an audit finding. Nightshift includes at least two a year as standard, and it is one of the clearest differences between a programme and a service call.
We are preparing for an unannounced audit. Can you help at short notice?
We can review your current file, tell you plainly where the gaps are and close what can be closed, but it is worth being honest about the limit: nobody can retrospectively create six months of trend data. If you are early, a review now is genuinely valuable. If the audit is imminent, expect an accurate picture of your exposure rather than a fix for all of it.
Do you work outside production hours?
Yes, and on a manufacturing site it is usually the only sensible way. Technicians work nights as their standard shift rather than being called out, so monitoring, treatment and proofing happen during cleandown or downtime rather than around a running line, and out-of-hours attendance is not charged as a premium.
Related: bakeries and food production, warehousing and distribution, farms and grain stores, and how pests affect a food hygiene rating. For a whole estate on one agreement, see commercial pest control contracts.
Bring us your current pest control file
Surveys, quotations and advice are free and without obligation. The most useful thing we can do before you change anything is read what you already have and tell you where an auditor would press, including where the answer is that your existing programme is sound.
Arrange a survey