A pest control program is how a food plant keeps rodents, insects, birds, and other pests out of product using integrated pest management (IPM): exclusion and sanitation first, monitoring devices to catch what gets close, and pesticides only as a restricted last resort. FDA's rule at 21 CFR 117.35(c) states plainly that pests must not be allowed in any area of the plant.
Pests are unusual among contamination sources because they are visible, predictable, and preventable. A rodent does not appear from nowhere; it follows a food source through a gap someone left. This post covers what the FDA actually requires, what integrated pest management means in practice, how monitoring devices and trend mapping turn scattered catches into a signal, the hard limits on pesticide use, and the documentation an auditor will page through first.
What is a pest control program in a food plant?
A pest control program is the coordinated set of measures a facility uses to prevent, monitor, and control pests across the whole site, grounds, building envelope, and interior. It is built on integrated pest management, a strategy that ranks non-chemical controls ahead of chemical ones: make the plant unattractive and inaccessible to pests, watch for pressure, and treat only when monitoring shows you must, with the least-toxic effective method.
The reason IPM leads with exclusion rather than spraying is simple: a pesticide is itself a chemical hazard inside a food plant. Every application is a small risk you are choosing to accept, so the program's whole design is to need as few of them as possible. Most plants run this through a licensed pest management provider, but the plant, not the contractor, owns the program and its records.
What does the FDA require?
Two sections of the human-food CGMP rule carry pest control. 21 CFR 117.35(c) is the direct one: no pests are allowed in any area of a food plant, effective measures must be taken to exclude them and to protect food from contamination, and pesticides may be used only under precautions and restrictions that protect food, food-contact surfaces, and packaging. Guard, guide, or pest-detecting dogs may be allowed in some areas if they are unlikely to contaminate product, the rule's one narrow exception.
The second is 21 CFR 117.20 plant and grounds, which requires keeping grounds free of litter, waste, and standing water, and maintaining the building to prevent pests from harboring or entering. Together they set the standard: exclusion and sanitation are the primary controls, and chemical treatment is the tightly bounded exception. Neither section prescribes a specific device count or inspection frequency, which is why your program has to define those and defend them. That flexibility cuts both ways, it lets a plant right-size its program to its own layout and pest pressure, but it also means an inspector judges your program against what is reasonable for your facility, not against a fixed checklist. A written program that states its own device counts, inspection intervals, and action thresholds, and then follows them, is far easier to defend than one that improvises.
What is integrated pest management?
Integrated pest management is the operating method the whole program runs on. It has four working parts, and a real program can point to each one:
- Exclusion. Physically keep pests out: seal wall and utility penetrations, install and maintain door sweeps and air curtains, screen vents and windows, keep exterior doors closed, and manage drains and roof lines where pests travel. This is the highest-return work and the least glamorous.
- Sanitation and harborage removal. Take away food, water, and shelter. Clean spills, manage waste and dumpsters away from the building, remove standing water, control vegetation and clutter on the grounds, and rotate stock so nothing sits long enough to become a nest.
- Monitoring. Place and service monitoring devices on a defined schedule, inspect the structure, and record what you find, so pressure is detected early and trends become visible.
- Control, then verify. When monitoring shows action is needed, use the least-toxic effective method, mechanical traps and targeted treatment before broadcast chemicals, then verify it worked and feed the result back into exclusion and sanitation.
The order is the doctrine. Reaching for a sprayer before sealing the gap that let the pest in treats the symptom and guarantees a repeat. IPM makes exclusion and sanitation the load-bearing controls and treats chemical use as evidence that something upstream failed.
How do monitoring devices and trend mapping work?
Monitoring turns pest control from reaction into early warning. A plant lays out a device network keyed to a facility map: exterior rodent bait stations around the perimeter, interior mechanical rodent traps along walls, insect light traps at entries and in processing areas, and pheromone traps for stored-product insects. Each device is numbered and located on the map, and each service visit records the device, the date, and the catch.
The value is not any single catch, it is the trend. One fly in a light trap is noise; a rising count in the same trap over three weeks is a signal pointing at a door, a drain, or a sanitation gap nearby. Mapping catches back to their location turns the trap network into a heat map of where pressure is building, so you fix the source instead of emptying the same trap forever. That trend analysis is exactly what GFSI auditors expect to see, and it is the difference between a program that reacts and one that predicts.
What are the rules on pesticides?
Pesticides in a food plant are governed on two fronts. The FDA rule limits how they may be used, only under precautions and restrictions that protect food, food-contact surfaces, and packaging, and the EPA governs the products themselves, since every legal pesticide carries a label that is federal law. Using a product off-label, or in an area or concentration the label prohibits, is both a pesticide violation and a route to an adulterated food.
Practically, that means restricted-use products are applied by a licensed applicator, applications inside the plant favor targeted crack-and-crevice or bait over broadcast spraying near exposed product, food and packaging are removed or protected during treatment, and treated areas are cleaned before production resumes. Every application is logged, product, EPA registration number, target pest, location, rate, applicator, and date, and the label and safety data sheet are kept on file. The documentation is not paperwork for its own sake; it is how you prove a chemical hazard was controlled rather than introduced.
What documentation do auditors review?
Pest control is one of the most document-heavy prerequisite programs, and it is usually the first binder an auditor opens because it reveals so much about the plant's discipline. The core package: a current facility map with every device located and numbered, the service reports from each visit, catch data and trend analysis, a pesticide application log with labels and SDSs, the licenses and insurance of the pest management provider, corrective actions taken on findings, and a periodic program assessment. GFSI schemes and FDA inspectors alike expect the trend analysis and the corrective-action loop, not just a stack of service tickets.
| Document | What it proves | Who reviews it |
|---|---|---|
| Facility device map | Devices are placed by design and can be found and serviced | Auditor, inspector, provider |
| Service reports | Devices were inspected on schedule with findings recorded | Auditor, QA |
| Catch data & trend analysis | Pressure is tracked over time and acted on early | Auditor, QA |
| Pesticide application log | Chemicals used on-label, on-target, and documented | Auditor, inspector, regulator |
| Provider license & SDS file | Applications made legally by qualified people | Auditor, regulator |
| Corrective actions | Findings were closed and sources fixed, not just noted | Auditor, QA |
The numbers worth pinning
Pest control is anchored in rule and label law, so cite the primary sources:
- No pests are allowed in any area of a food plant effective measures must exclude them, and pesticides may be used only under protective precautions, 21 CFR 117.35(c).
- Grounds and buildings must be maintained to prevent pests from harboring or entering, including litter, waste, and standing-water control, 21 CFR 117.20.
- Every pesticide's label is enforceable federal law under FIFRA; the EPA registers products and sets use restrictions through the EPA pesticide registration program.
- FDA's plain-language CGMP overview covering sanitary operations and pest control is its What You Need to Know about CGMP guidance.
How does pest control fit the food safety plan?
Pest control is a prerequisite program, sitting under your HACCP-based food safety plan beside sanitation and personnel hygiene. It lowers the biological and physical contamination baseline so the hazard analysis has less to manage. Because it is a prerequisite, an auditor grades it almost entirely on the records above, and those records are exactly where paper systems leak, service tickets in a binder no one trends, corrective actions closed in someone's memory. Capturing device checks, catches, and corrective actions at the point of work makes the trend visible in real time and turns audit prep into a query, the same connected-records discipline behind GMP compliance and an environmental monitoring program. It is the digitize-the-paper move Harmony runs across production and quality logs (see how CLS did it), pointed at the pest binder. Pair it with disciplined personnel hygiene and clear SSOPs and the plant stops inviting pests in the first place.