Emergency Preparedness, Recall, and Traceability
When normal control fails
Emergency planning means deciding in advance what to do when the power fails, water is lost or contaminated, a fire or flood occurs, or sewage backs up. The first question is always whether safe operations are possible; if not, stop food handling, close, notify the regulator, and document. Interrupted temperature control triggers an evaluation of the product: how long, at what temperature, and what the food is. A common rule of thumb is that product above 41°F for more than four hours is discarded, and a full walk-in that stays closed holds temperature for a limited time only.
Recall readiness is a Food Code and FSMA theme. Manufacturers of covered foods need a written recall plan; all operations should be able to trace product one step back and one step forward and to conduct a mock recall within a defined time. Traceability relies on lot codes, batch records, bills of lading, and receiving logs, and increasingly on critical tracking events and key data elements for high-risk foods.
Know the recall classes by severity, not by size: Class I involves a reasonable probability of serious adverse health consequences or death; Class II involves a remote probability of temporary or medically reversible harm; Class III is unlikely to cause harm. The firm proposes the recall, the regulator assigns the class, and effectiveness checks verify that consignees received the notice and removed product. Depth of recall (consumer, retail, or wholesale) depends on where the product went.
Traps: confusing class with volume, forgetting the effectiveness check, and assuming a mock recall is optional.
Worked example: a supplier reports Listeria in a shipped lot. Class I, consumer-level depth, immediate notification, quarantine of remaining stock, and documented effectiveness checks for each consignee.