What FDA Defect Action Levels Mean For A Food Plant

A defect action level is the point at which the US Food and Drug Administration will treat a food as adulterated because of a defect it considers unavoidable, such as insect fragments in flour or a rodent hair in corn meal. It is a limit on what ends up in the product. It is not an allowance for pests in the building.

That distinction gets lost in the retelling. A figure out of the handbook travels well, so "75 insect fragments per 50 grams of flour" turns into a belief that some amount of pest activity has been signed off on somewhere. The federal rule for food plants says the opposite in one sentence: pests must not be allowed in any area of a food plant. The levels describe a lot on a laboratory bench. The rules describe your building.

Where The Numbers Come From

From two places that work together. Title 21 of the Code of Federal Regulations, part 117, defines a defect action level as a level of a non-hazardous, naturally occurring, unavoidable defect at which FDA may regard a food product as adulterated, and points to the Defect Levels Handbook for the examples. The handbook holds the commodity figures, and FDA describes the levels it lists as presenting no inherent hazard to health while marking the limits at which the agency will regard a product adulterated and subject to enforcement under section 402(a)(3) of the Federal Food, Drug, and Cosmetic Act. FDA's Macroanalytical Procedures Manual puts the scale of the collection at roughly 200 action levels across about 110 food products.

What The Levels Actually Say

Four of FDA's compliance policy guides show the shape of it. Read the units closely, because they are not the same from one row to the next.

A few details about that table matter more than the figures in it. The levels are averages taken across subsamples rather than a reading off one scoop. They are written per commodity, which is why the wheat flour guide carves out durum. And where a product has no study of its own, FDA extrapolates: the macaroni levels were derived from the levels for soft wheat flour, because soft wheat flour is permitted in macaroni products.

The Pests That Have No Number At All

This is the part that gets skipped, and it is the part a plant manager needs. FDA's guidance on filth from insects, rodents and other pests sorts pests into categories: pests that are indicators of insanitation, opportunistic pests, adventive pests, obligatory storage pests, and incidental pests. It then says that the numerical defect action levels for incidental pests or insect fragments do not include the category I and category II pests unless the guidance specifically refers to them.

Read that in plain terms. A cockroach, or rodent evidence in product, is not weighed against a fragment count, because no count was written for it. There is no allowance to be inside of. The same guidance adds a line worth pinning up in a sanitation office: the use of chemical substances to control insects, rodents and other natural contaminants has little, if any, impact on natural and unavoidable defects in foods. Spraying more is not the lever. What moves a fragment count is exclusion and cleaning, plus knowing where the population actually lives, and that is the argument for treating rodent management as a structural job rather than a monthly bait check.

Why "We Were Under The Level" Is Not A Defense

Three separate rules close that door, and they close it from different directions.

• The handbook rejects the premise. FDA says it is incorrect to assume that because an action level exists for a commodity, a manufacturer need only stay just below it.
• Sanitation is a separate charge. Compliance with a defect action level does not excuse a violation of section 402(a)(4) of the act, which covers food prepared, packed or held under insanitary conditions.
• Blending is out. Part 117 states that mixing a lot containing defects above the action level with another lot is not permitted, and that the final food is adulterated regardless of the defect level of the finished blend.

Behind all three sits the plant rule itself. Part 117 requires effective measures to exclude pests from manufacturing, processing, packing and holding areas, and permits pesticide use only under precautions that protect food and food contact surfaces. An inspector who sees activity does not need a laboratory result to write it up.

What A High Filth Count Should Start

A number over the line is a lead, not a verdict. The useful response works backward from the lot to the room it ran through.

1. Hold the lot on its own. Part 117 has already answered the question of whether it can be blended down, so the decision left is where it goes, not what it is mixed with.
2. Separate what rode in from what grew inside. Compare the raw material against the finished product and pull the receiving record for that delivery. Our dock inspection guide covers what should have been caught at the door.
3. Walk the line that lot ran on. Stored product insects live in the residue a cleaning schedule misses: spillage under conveyors, dead spots in elevator legs, old product in equipment that is rarely opened. Our guide to stored product pests goes through where they breed.
4. Read the monitoring record as a trend line. One device with a jump in catch three weeks before a bad result is the most useful document in the building, and that is what audit documentation exists to produce.
5. Write down the correction and the date. An auditor reads what you did about the finding far more closely than the finding itself.

Who Inspects A Food Plant In Ohio

For most processors it is the Ohio Department of Agriculture, and the state rules point straight back at the federal ones. Ohio Revised Code section 3715.021 directs the Director of Agriculture to adopt standards and good manufacturing practices for food processing establishments that conform to, or are equivalent to, the FDA standards in Title 21 of the Code of Federal Regulations. Section 3715.041 puts an inspection behind the paperwork: the director inspects the establishment that has applied for initial registration, and a registration runs to the thirty-first day of January unless it is suspended or revoked. Meat processing sits with the department's Division of Meat Inspection instead, and restaurants and other retail food establishments are licensed under Chapter 3717 with local health districts doing the field work, which our restaurant inspection guide covers.

For a plant in Stark, Summit, Wayne, Portage or Tuscarawas County, the practical effect is that one pest program has to satisfy a state registration inspection, a customer audit and, for registered facilities, FDA. They ask for the same things in different words: exclusion that works, monitoring that produces a record, and corrections that are documented. That is what our food manufacturing pest control and warehouse and manufacturing programs are built around.

If you are looking at a filth result, a corrective action request, or an audit date on the calendar and want a straight read on the pest side of it, get a free estimate through our request form or call 330-494-6199.