Food service
The Food Code names four means of controlling pests. Three of them are not pesticide application — which means an operator whose entire pest file is service tickets has evidence for one quarter of the requirement.
What this page establishes
- FDA Food Code 6-501.111 names four means of pest control. Three of them are not pesticide application.
- The requirement is a program, not a treatment.
- Exclusion is a code requirement, not best practice.
- Pest control is a prerequisite program, not a critical control point.
The requirement is a program, not a treatment
Section 6-501.111 opens with an absolute: the premises must be maintained free of insects, rodents, and other pests. It then specifies how that is to be achieved, and the specification is the part operators miss. Pest presence is to be controlled by routinely inspecting incoming shipments of food and supplies; by routinely inspecting the premises for evidence of pests; by using trapping devices or other approved methods when pests are found; and by eliminating harborage conditions.
Receiving inspection, premises inspection, control methods, harborage elimination. Only the third is what most operators think of as pest control, and it is the only one the vendor's invoice evidences.
An inspector working this section can ask an operator to demonstrate a receiving inspection practice. Most cannot, because nobody told them that checking incoming product for pests is a pest control requirement rather than a quality preference. It is written into the code as one of the four named means.
Exclusion is a code requirement, not best practice
Outer openings must be protected against the entry of insects and rodents: gaps along floors, walls, and ceilings filled or closed; windows closed and tight-fitting; doors solid, self-closing, and tight-fitting; and screening, where screening is used, of at least 16 mesh to 25.4 mm.
This converts a large share of pest findings into building work. A propped back door during a delivery, a worn door sweep, an unsealed utility penetration behind a dishmachine — each is a code deficiency in its own right, independent of whether any pest has been seen. It also means the person who can actually close the finding is often maintenance or the landlord, not the pest vendor, which is a problem to solve before an inspection rather than during one.
Device placement is decided once, at installation
Insect control devices that electrocute or stun flying insects must be designed and installed so that dead insects and fragments are retained within the device, and must not be installed over a food preparation area or anywhere they could contaminate food, equipment, utensils, linens, or single-service articles.
Placement is the failure mode inspectors actually find, and because it is set at installation it tends to persist for years. A unit mounted above a prep table is a standing deficiency that no amount of service frequency corrects.
Removal has a cadence requirement
Dead or trapped birds, insects, rodents, and other pests must be removed from control devices and from the premises at a frequency that prevents accumulation, decomposition, or the attraction of other pests. A quarterly service interval does not satisfy a requirement expressed as "at a frequency that prevents accumulation" if accumulation is occurring — the code sets the outcome, and the contract interval has to be built backwards from it.
Pest control is a prerequisite program, not a critical control point
For any operation running HACCP, the classification matters more than it sounds. Under the NACMCF 1997 guidelines, pest control is a prerequisite program. It is expected to be documented, verified, and stable before the HACCP plan is written, and its failure is a finding against the foundation of the plan rather than a deviation at a critical control point.
That is why a pest finding in an audited operation escalates the way it does. A CCP deviation is a bounded event with a defined corrective action. A prerequisite program failure calls the validity of the plan built on top of it into question, and auditors treat it accordingly.
How the Food Code reaches an operator
The Food Code is a model code. It is not directly binding anywhere; it becomes law when a state — and sometimes a county or city — adopts an edition of it, with amendments, on its own schedule. Two consequences follow, and both matter to a multi-site operator:
- Two jurisdictions may be enforcing different editions in the same year, so section numbering and requirements can differ across a footprint.
- Local amendments can add requirements the model code does not contain. The governing text is always the adopted state or local code, never the FDA publication on its own.
Establishing which edition, as amended, actually governs each site is the first step of a compliance program review for a multi-jurisdiction operator, and it is where the exercise usually produces its first surprise.
The same sections govern institutional kitchens that sit inside another regulated facility — a school cafeteria, a hospital kitchen, a correctional food service operation — which means those facilities are inspected under two regimes at once, with different evidence expectations for the same physical space.
The citations this page rests on
Every entry states how far it has been verified: whether the primary source was read into this repository and on what date, or whether it is corroborated from secondary sources with the primary text still unread.
-
FDA Food Code 6-501.111
FDA Food Code 2022 (January 18, 2023 version), as amended by the Supplement to the 2022 Food Code (November 2024), §6-501.111 — Controlling Pests
What it requiresThe premises must be maintained free of insects, rodents, and other pests. Their presence must be controlled by four named means: routinely inspecting incoming shipments of food and supplies; routinely inspecting the premises for evidence of pests; using trapping devices or other approved methods of control when pests are found; and eliminating harborage conditions. Three of the four are inspection and exclusion work, not pesticide application — the standard is written as a program, and a facility that can only produce service tickets has evidence for one quarter of it.
Verified against the primary source on . Primary sourceEdition: FDA Food Code 2022 (January 18, 2023 version) as amended by the Supplement to the 2022 Food Code (issued November 2024; December 2024 version; https://www.fda.gov/media/183271/download). The Supplement revises the 2022 text effective upon issuance and does not alter this section.
-
FDA Food Code 6-501.112
FDA Food Code 2022 (January 18, 2023 version), as amended by the Supplement to the 2022 Food Code (November 2024), §6-501.112 — Removing Dead or Trapped Birds, Insects, Rodents, and Other Pests
What it requiresDead or trapped birds, insects, rodents, and other pests must be removed from control devices and from the premises at a frequency that prevents their accumulation, decomposition, or the attraction of other pests. This is a housekeeping cadence requirement, and it is the one most often left implicit in a pest vendor contract that specifies only a service interval.
Verified against the primary source on . Primary sourceOperator verification, performed independently of this build environment. The entry was checked and needed no change. Edition: FDA Food Code 2022 (January 18, 2023 version) as amended by the Supplement to the 2022 Food Code (issued November 2024; December 2024 version; https://www.fda.gov/media/183271/download). The Supplement revises the 2022 text effective upon issuance and does not alter this section.
-
FDA Food Code 6-202.15
FDA Food Code 2022 (January 18, 2023 version), as amended by the Supplement to the 2022 Food Code (November 2024), §6-202.15 — Outer Openings, Protected
What it requiresOuter openings of a food establishment must be protected against the entry of insects and rodents — by filling or closing holes and other gaps along floors, walls, and ceilings; by closed, tight-fitting windows and solid, self-closing, tight-fitting doors; and, where screening is used, by screening of at least 16 mesh to 25.4 mm (16 mesh to one inch). This is the exclusion standard that converts a pest finding into a building-envelope work order rather than a treatment order.
Verified against the primary source on . Primary sourceOperator verification, performed independently of this build environment. The 16 mesh to 25.4 mm figure was withheld from the first build rather than guessed; it is now supplied from that verification. Edition: FDA Food Code 2022 (January 18, 2023 version) as amended by the Supplement to the 2022 Food Code (issued November 2024; December 2024 version; https://www.fda.gov/media/183271/download). The Supplement revises the 2022 text effective upon issuance and does not alter this section.
-
FDA Food Code 6-202.13
FDA Food Code 2022 (January 18, 2023 version), as amended by the Supplement to the 2022 Food Code (November 2024), §6-202.13 — Insect Control Devices, Design and Installation
What it requiresInsect control devices that electrocute or stun flying insects must be designed and installed so that dead insects and insect fragments are retained within the device, and the device is not installed over a food preparation area or where it could contaminate food, equipment, utensils, linens, or single-service articles. Device placement is the failure mode inspectors find, and it is a design decision made once at installation.
Verified against the primary source on . Primary sourceEdition: FDA Food Code 2022 (January 18, 2023 version) as amended by the Supplement to the 2022 Food Code (issued November 2024; December 2024 version; https://www.fda.gov/media/183271/download). The Supplement revises the 2022 text effective upon issuance and does not alter this section.
-
NACMCF 1997, Appendix A
National Advisory Committee on Microbiological Criteria for Foods, Hazard Analysis and Critical Control Point Principles and Application Guidelines, August 14, 1997, Appendix A — Examples of Common Prerequisite Programs
What it requiresPest control is a prerequisite program, not a critical control point. The distinction decides where pest evidence belongs in a food safety plan and how it is audited: a prerequisite program is expected to be documented, verified, and stable before the HACCP plan is written, and its failure is a finding against the foundation of the plan rather than a deviation at a CCP.
Verified against the primary source on . Primary source
Cite this page
Suggested citation
Frazer, Trenton S. “Food service.” Frazer Applied Entomology. https://frazerappliedentomology.com/industries/food-service/. Accessed [access date].
Every citation on this page should be verified against the primary source before any litigation-grade use. Each citation block states whether this site has read the primary source or corroborated it from secondary sources.
The engagements this page points to
The engagements are the same across sectors; what changes is which one a facility needs first.
- EngagementSurvey readiness A review of the program and the paperwork before an accreditation survey, state inspection, or audit — while there is still time to fix what it finds. Survey readiness
- EngagementCompliance program review An assessment of the pest management program you already have, measured against the rules that actually govern your building, delivered as a written finding. Compliance program review
- EngagementDeficiency response After a citation: what the finding actually requires, what a plan of correction has to address, and what evidence will satisfy a revisit. Deficiency response
Would your program survive the inspection you are due?
Send the operation, the authority that inspects it, and the date — a scheduled audit, a routine inspection, or a finding already written.
If the program is built around a treatment schedule rather than around receiving inspection, premises inspection, control methods, and harborage elimination, the gap is structural.