What are the 3 classes of FDA recalls?

Class I: reasonable probability that the product will cause serious adverse health consequences or death (pathogens, undeclared major allergens). Class II: may cause temporary or medically reversible harm, remote chance of serious harm. Class III: not likely to cause harm but the product violates regulations. The class drives recall depth, publicity, and effectiveness-check intensity.

Is a recall plan required by law?

Yes, for most FDA-registered food facilities. Under FSMA's preventive controls rule, 21 CFR 117.139 requires a written recall plan for any food with a hazard requiring a preventive control. The plan must assign responsibility for notifying direct consignees, notifying the public when appropriate, conducting effectiveness checks, and disposing of recalled food.

What is the difference between a recall and a market withdrawal?

A recall removes product that violates regulations and could face agency action, it is classified and monitored by FDA. A market withdrawal removes product for a minor issue that involves no violation (or one that wouldn't trigger legal action). A stock recovery pulls product that never left your direct control. Defining all three in your plan prevents mislabeling an event.

Who should be on a food recall team?

Seven named roles with backups: a recall coordinator, a traceability lead, an operations lead, a customer notification lead, a communications lead, a regulatory/legal lead, and a scribe who timestamps every decision into one event log. Small plants combine roles, but every function needs a name and a phone number in the written plan.

How fast do you have to report a food safety problem to FDA?

For foods with a reasonable probability of causing serious adverse health consequences, registered facilities must submit a Reportable Food Registry report within 24 hours of determining the food is reportable. The recall itself is typically voluntary and company-run, with FDA reviewing the strategy and monitoring effectiveness.

How often should you do a mock recall?

At least annually, that is the working expectation under GFSI-benchmarked certification schemes, and many customers require it contractually. Better practice is twice a year: one records-only trace exercise and one fuller simulation with notification calls, each graded on trace time and mass balance, feeding revisions to the plan.

What is an effectiveness check in a recall?

Verification that consignees actually received the recall notice and acted on it, confirmed receipt, quantities returned or destroyed, and follow-up on non-responders. FDA reviews effectiveness checks during recalls; your plan should define who performs them, by what method (call, email, visit), and what response rate triggers escalation.

Food Recall Plan: Build It Before You Need It

The classes, the regulation, the team, and the first-week clock, decided calmly, in advance.

A food recall plan is a written plan that assigns responsibility and spells out procedures for pulling unsafe product from the market: notifying customers who received it, notifying the public when needed, checking the recall worked, and disposing of what comes back. Under FSMA, FDA requires one in writing for any food with a hazard requiring a preventive control (21 CFR 117.139).

Recalls are decided in hours by people who are tired and scared. The plan exists so those hours run on decisions you made calmly, in advance. This guide covers the FDA recall classes, exactly what 21 CFR 117.139 requires, the recall team roles, the decision tree, the communication fan-out, and the timeline your plan should be built to hit, plus the practice regime that keeps it real.

What are FDA recall Classes I, II, and III?

FDA assigns every recall a classification based on the health hazard the product presents (defined in 21 CFR 7.3 and used in FDA's enforcement reports):

Class	Definition	Food examples
Class I	Reasonable probability that use or exposure will cause serious adverse health consequences or death	Pathogen contamination (Listeria, Salmonella), undeclared major allergens, hazardous foreign material
Class II	Use or exposure may cause temporary or medically reversible adverse health consequences; remote probability of serious harm	Some quality-related contamination, certain labeling violations with limited health impact
Class III	Use or exposure not likely to cause adverse health consequences, but the product violates regulations	Minor labeling defects, quality standard violations

Classification matters because it drives depth (how far down the chain you recall, wholesale, retail, or consumer level), publicity (Class I usually means a public press release), and effectiveness-check intensity. Note the related but different actions: a market withdrawal removes product for a minor issue that isn't a violation, and a stock recovery pulls product that never left your control. Your plan should define all three, because calling an event the wrong thing has regulatory consequences.

Meat, poultry, and egg products run through USDA FSIS rather than FDA, with an equivalent class system and its own recall process dual-jurisdiction companies need both paths in the plan.

What does FSMA actually require? 21 CFR 117.139

For any food whose hazard analysis identifies a hazard requiring a preventive control, 21 CFR 117.139 requires a written recall plan that includes procedures, with assigned responsibility for each, to:

Directly notify direct consignees of the recalled food, including how to return or dispose of it;
Notify the public about hazards in the food, when appropriate to protect health;
Conduct effectiveness checks to verify the recall is carried out; and
Appropriately dispose of recalled food reprocess, rework, divert to a safe use, or destroy.

Two more legal gears sit next to that rule. The Reportable Food Registry requires registered facilities to report to FDA within 24 hours when there is a reasonable probability that a food will cause serious adverse health consequences. And FSMA gave FDA mandatory recall authority, if a company refuses to recall voluntarily, FDA can order it. In practice nearly all recalls are voluntary, run by the company, with FDA reviewing strategy and monitoring effectiveness. FDA's draft guidance chapter on recall plans is the best free blueprint for writing yours.

Who is on the recall team? Seven roles

Names and backups, not departments. Put phone numbers in the plan and keep a printed copy, the recall that starts at 6 p.m. Friday does not wait for the org chart.

Recall coordinator. Owns the event end to end: convenes the team, makes the recall/withdrawal call with QA and legal input, talks to FDA. Usually the quality or food safety leader. Needs a named deputy.
Traceability lead. Produces the affected-lot picture: what was made, from which inputs, shipped where, how much remains. The clock on the whole event runs on this person's records, see traceability in manufacturing.
Operations lead. Holds remaining inventory, stops further production and shipment, quarantines returns, manages reconditioning or destruction.
Customer notification lead. Owns the direct-consignee calls and written notices: who received affected lots, confirmation of receipt, return/disposal instructions, response tracking.
Communications lead. Public notice, press release, website statement, consumer hotline, coordinated with FDA when public notification is warranted.
Regulatory/legal lead. RFR submission, FDA/FSIS liaison, records preservation, insurer notification.
Scribe. Underrated and essential: timestamps every decision, call, and quantity into one event log. That log is your defense in the after-action review and any regulatory follow-up.

How is the recall decision actually made?

Every trigger, a customer complaint, a positive environmental or product test, a supplier notification, an internal discovery at a changeover, should route into the same evaluation. The tree keeps 2 a.m. decisions consistent:

One tree for every trigger. The left exits (withdrawal, stock recovery) are why definitions belong in the plan, calling a recall a withdrawal, or vice versa, creates its own problem.

Who gets told, in what order?

A recall is mostly a communication event. The plan pre-writes the fan-out: templates, contact lists, and owners for every arrow.

The fan-out from the recall room. Consignee notification and regulator contact carry the hard deadlines; internal notification is the one plants forget until the hotline rings the front desk.

What does the first week look like?

Build the plan against a clock. Hours are targets to design for, not regulatory promises, but if your plan cannot hit them on paper, it will not hit them under stress:

The traceability window sets the pace of everything after it. If assembling the lot picture takes two days, every regulatory and customer clock starts two days late.

Notice what gates the timeline: records. The 4-hour trace assumes you can join production lots, ingredient lots, and shipments quickly. That is precisely the muscle mock recalls exercise, the capability FSMA 204 will demand within 24 hours for listed foods, and the reason plants pull production and shipping records out of paper and into live systems, plant-wide, searchable operational data is the core of what Harmony builds (see the platform).

The numbers that justify the binder

Recall class definitions are set in 21 CFR 7.3; Class I means serious harm or death is reasonably probable.
A written recall plan is mandatory for foods with hazards requiring preventive controls under 21 CFR 117.139 covering consignee notification, public notification, effectiveness checks, and disposition.
Undeclared allergens and pathogen contamination lead recall causes: USDA's Economic Research Service found pathogens (41%) and undeclared allergens (27%) drove most US recalls in 2004–2013, with allergen recalls nearly doubling over the period (USDA ERS), and undeclared allergens have led FDA recall counts in recent years, which is why allergen management is the recall-prevention program.
24 hours is the Reportable Food Registry deadline for foods reasonably likely to cause serious harm.

How do you keep the plan alive?

A recall plan written once and filed is a compliance artifact, not a capability. Keep it real with a standing regime: run a mock recall at least annually (GFSI-benchmarked schemes expect a documented traceability/recall test at that frequency, and most plants that take it seriously run two, one paper trace, one full simulation with calls); update the contact lists quarterly, because phone numbers rot faster than procedures; re-verify the plan after every change to products, customers, co-packers, or systems; and grade every exercise against the clock, trace time, notification time, mass-balance percentage, so the next revision has targets. Your HACCP system decides how unlikely the recall is; the plan decides how bad it gets when unlikely happens anyway.