A mock recall form is the written record your facility fills out while simulating a product pullback, and completing it well means capturing every data point required by federal record-keeping rules while the exercise is actually happening. To complete a mock recall form, you build a template around the fields required by 21 CFR 117.305, pick a lot code at random, run a forward and backward trace against the clock, log each contact and quantity as data comes in, calculate an effectiveness percentage, and document any discrepancies with corrective actions before filing the record.
The form isn’t optional busywork. Facilities that handle food with a hazard requiring a preventive control must maintain a written recall plan under 21 CFR 117.139, covering consignee notification, public warnings when needed, effectiveness checks, and proper disposal of recalled product.1eCFR. 21 CFR 117.139 – Recall Plan The mock recall is how you prove that plan works, and the completed form is your evidence.
Required Fields on the Form
Federal record-keeping standards set the floor. Under 21 CFR 117.305, records must be accurate, indelible, and legible, created at the same time the documented activity takes place. Each record must identify the facility by name and location, include the date and time of the activity, carry the signature or initials of the person performing it, and note the product identity and lot code.2eCFR. 21 CFR 117.305 – General Requirements Applying to Records Reconstructing the form after the fact violates this rule. Fill it in as the exercise unfolds.
Build your template with these fields:
- Product identification: exact product name, lot or batch number, and any tracking codes such as GTIN or UPC used internally or by customers.
- Production details: date of manufacture, shift if the facility runs more than one, and the total quantity produced for that lot.
- Distribution records: a line for each recipient with company name, contact person, phone, physical address, quantity shipped, and shipping date.
- Recovery data: for each recipient, columns for quantity still in inventory, quantity in active production or on shelves, and quantity already consumed or sold through.
- Timing: exercise start time, end time, and total elapsed time.
- Effectiveness calculation: total quantity accounted for divided by total quantity shipped, as a percentage.
- Discrepancy notes: a field explaining any gap between what was shipped and what was located.
- Personnel: names and roles of everyone who participated, with signatures.
The USDA’s produce mock recall guidance follows this structure: it tracks amounts delivered, amounts found in inventory, amounts in food production, and amounts already served, then calculates recall effectiveness as (inventory + in production + served) divided by the amount delivered.3Food and Nutrition Service. Conducting a Mock Recall of Produce in a School Nutrition Operation The same math works for any food facility.
Filling the Form During the Exercise
Pick a lot code at random. Not the one you know has clean records — genuinely at random, because the point is to stress-test traceability under realistic conditions. Enter that lot number and product identification at the top of the form, then start a timer and log the start time.
The team’s first task is to pull every distribution record tied to that lot by matching it against shipping documents, bills of lading, and customer invoices. As each recipient is identified, add a row to the distribution section of the form. Then contact each recipient to determine how much product remains in their possession, how much has moved further down the chain, and how much has already been consumed or discarded. Fill in the recovery columns as responses come in, and note the time each contact was reached. Do not batch entries at the end; the regulation requires contemporaneous records.
Run the backward trace at the same time. Identify every raw material and ingredient lot that went into the finished product, and confirm you can trace those inputs back to their suppliers. This one-step-back, one-step-forward capability is what third-party auditors specifically look for.4SQF Institute. Edition 9 – Food Safety Code: Food Manufacturing
Stop the timer when every unit is accounted for or every lead is exhausted. Record the total elapsed time on the form. Four hours is a reasonable internal target for completing a full forward-and-backward trace; a real recall won’t wait for you to sort through filing cabinets.
Calculating and Recording Effectiveness
The effectiveness percentage is the single most important number on the form. Divide the total quantity you successfully located, in any status, by the total quantity originally shipped, then multiply by 100. Record the percentage prominently, along with a short narrative summary explaining the result.
An exercise that accounts for 100 percent is the goal, but anything below that tells you where tracking breaks down. If you hit 100 percent in under two hours, note what went right. If you stalled at 87 percent because one distributor had no record of receiving the shipment, that gap is the most valuable finding in the exercise. This is where most facilities discover their traceability problems, and discovering them here rather than during a real crisis is the point.
Documenting Discrepancies and Corrective Actions
Every unit you can’t account for needs an explanation on the form. Common root causes include incomplete shipping records, distributors who repackaged or relabeled product without updating lot information, customers who received the product but had already disposed of packaging with the tracking codes, and internal data-entry errors where the wrong lot number was assigned during production.
The FDA’s approach to root cause analysis fits here. Gather data from traceback records, production logs, standard operating procedures, and interviews with staff involved in that lot’s manufacture and shipment.5Food and Drug Administration. Strengthening Food Safety through Root Cause Analysis Document both the immediate corrective action, such as updating a customer’s contact information that was wrong in your system, and the long-term fix, such as adding a verification step to the shipping workflow so addresses are confirmed before dispatch.
Attach the corrective action plan directly to the completed form, or cross-reference it clearly. An auditor reviewing the record months later needs to see that you found the problem and closed the loop.
Noting the Recall Class
Add a field to the form for the assumed recall class, because that classification drives how aggressively you’d need to respond in a real situation. The FDA’s categories come from 21 CFR 7.3:6eCFR. 21 CFR 7.3 – Definitions
- Class I: a reasonable probability that using or being exposed to the product will cause serious health consequences or death.
- Class II: the product may cause temporary or reversible health consequences, or the probability of serious consequences is remote.
- Class III: exposure to the product is not likely to cause adverse health consequences.
A Class I scenario on the form should trigger public notification procedures and tighter timelines than a Class III drill. Noting the class up front lets your team practice the right level of urgency.
Reportable Food Registry Field
A mock recall tests internal traceability, but a real event involving a serious hazard adds an external reporting obligation. Under Section 417 of the Federal Food, Drug, and Cosmetic Act, a responsible party must submit a report to the FDA’s Reportable Food Registry within 24 hours of determining that a food product has a reasonable probability of causing serious health consequences or death.7Food and Drug Administration. Draft Guidance for Industry: Questions and Answers Regarding the Reportable Food Registry The 24-hour clock starts the moment you make the determination, not when you finish gathering data.
Add a checkbox and timestamp field to the form for “RFR submission required: yes/no.” That builds the decision into the workflow so it doesn’t get overlooked under real pressure.
A Note on FSMA Section 204
If your facility handles foods on the FDA’s Food Traceability List, the FSMA Food Traceability Rule will eventually require additional Key Data Elements tied to Critical Tracking Events. Congress directed the FDA not to enforce the rule before July 20, 2028, after moving the date back from January 20, 2026.8U.S. Food and Drug Administration. FSMA Final Rule on Requirements for Additional Traceability Records for Certain Foods Facilities that handle listed foods can add those data elements to the mock recall form now so future drills reflect the standard they’ll be held to.
Storing the Completed Form
Once filled in and signed, the form becomes a formal record. Under 21 USC 350g, records documenting preventive control monitoring, nonconformance, testing results, and corrective actions must be kept for at least two years.9Office of the Law Revision Counsel. 21 USC 350g – Hazard Analysis and Risk-Based Preventive Controls The implementing regulation at 21 CFR 117.315 sets the same two-year floor and adds that the food safety plan itself must stay onsite at all times, while other records can be stored offsite only if they can be retrieved and provided onsite within 24 hours of an official review request.10eCFR. 21 CFR 117.315 – Requirements for Record Retention
Electronic records count as onsite if they’re accessible from an onsite location, so a cloud-based quality system satisfies the rule as long as staff can pull the file during an inspection. Keep digital backups regardless of your primary format. Paper forms stored in one location are vulnerable to water damage, misfiling, and the general entropy of a busy production facility. Two years is the legal minimum; many facilities keep completed mock recall forms longer to show auditors a continuous history of improvement across multiple exercises.