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.

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.

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, ahospital kitchen, acorrectional food service operation — which means those facilities are inspected under two regimes at once, with different evidence expectations for the same physical space.

Working with the practice in this sector

The engagements are the same across sectors: acompliance program review to establish what this facility is accountable for and where the program does not meet it, survey readiness run against a date,deficiency response after a citation, anEntomologist of Record engagement to hold the program between surveys, andexpert witness work when the matter is in litigation. Contact the practice with the facility and the regime that governs it.