What is a mock recall?
A mock recall is a controlled exercise that tests recall readiness. The business selects a lot or scenario and traces the product through records as if a real withdrawal or recall were needed.
Use this checklist with the Recall Plan Template, Traceability Plan Template, CAPA Template, and templates hub.
Who this is for
This checklist is for small food manufacturers, bakeries, co-packers, QA coordinators, warehouse teams, and owners who need to prove that traceability and recall records work before a customer, certifier, regulator, or buyer asks for evidence.
It is also useful after a software change, new distributor, new co-packer, new product line, supplier transition, or traceability problem.
How often to run a mock recall
Frequency can depend on customer requirements, certification programs, product risk, regulatory expectations, and internal policy. Many audit programs expect periodic testing. A small business should define the frequency in its procedure and meet it.
Run additional exercises after major changes such as new software, new co-packer, new product category, new distributor, or a traceability failure.
What records to test
Test records that would be used in a real event:
- Supplier lot records.
- Receiving logs.
- Batch or production records.
- Rework records.
- Packaging and label records.
- Finished product release records.
- Inventory records.
- Shipping records.
- Customer contact lists.
- Product hold and disposition records.
One-step-forward and one-step-back traceability
One-step-back means identifying where the ingredient or product came from. One-step-forward means identifying where finished product went. A strong system can do both without relying on memory.
Mass balance
Mass balance compares quantities. For example, a business may compare ingredient received, ingredient used, waste, finished product produced, samples, product on hand, and product shipped.
The goal is not always perfect arithmetic, especially for processes with normal loss. The goal is a documented explanation that makes sense.
Distribution list review
The distribution list should identify customers, locations, dates, quantities, and lots. For distributors, the business should understand how downstream customer communication would happen.
Time target
Set a time target for the exercise. Customers and certification programs may specify expectations. Even without an external target, QA should record how long it took and whether records were easy to retrieve.
Corrective actions after the exercise
If records are missing, late, unclear, or inconsistent, open CAPA. Corrective actions may include form changes, software access updates, label procedure changes, training, supplier data requirements, or shipping record cleanup.
Mock recall report structure
A practical report can include:
- Date and scenario.
- Product and lot selected.
- Team members.
- Records reviewed.
- One-step-back results.
- One-step-forward results.
- Mass balance.
- Time to complete.
- Gaps found.
- CAPA number or action plan.
- QA approval.
Example: one lot traced backward and forward
Select one finished lot of packaged product. Trace backward to the production record, ingredient lots, packaging lots, receiving records, and supplier documents. Then trace forward to every shipment, customer, distributor, sample, hold quantity, destroyed quantity, and remaining inventory. Compare the quantities in a mass balance and document any difference that needs explanation.
What to include
A mock recall checklist should include the selected product and lot, scenario, start time, team members, one-step-back records, one-step-forward records, mass balance, customer contact review, product on-hand check, time to complete, gaps found, CAPA assignment, and QA approval.
Records to keep
Keep the mock recall report, production records, receiving records, ingredient lot records, packaging records, rework records if used, inventory records, shipping records, customer contact list, mass balance calculation, product hold evidence where applicable, CAPA records, and final QA approval.
Practical checklist
- Select a product and lot.
- Define the scenario.
- Start the timer.
- Pull supplier and receiving records.
- Pull production and finished lot records.
- Pull shipping and customer records.
- Calculate mass balance.
- Confirm product on hand or disposition.
- Prepare a mock customer notification list.
- Record time and gaps.
- Assign CAPA and verify completion.
Common audit or customer request
Auditors and customers commonly ask for the most recent mock recall report, the time to complete the exercise, mass balance results, one-step-forward and one-step-back evidence, corrective actions for gaps, and proof that CAPA was verified.
They may also ask whether the exercise used a meaningful lot or only an easy sample.
Common mistakes
Common mistakes include selecting an easy lot every time, skipping mass balance, ignoring customer contact accuracy, failing to include rework, and not opening CAPA for missing records.
Another issue is testing only QA records. Warehouse, shipping, production, purchasing, customer service, and management records may all be needed.
QA perspective
From a QA perspective, a mock recall should create confidence or expose weak points. Either outcome is useful. A failed mock recall is better than discovering the same gap during an actual event.
The most useful exercises test the handoffs: receiving to production, production to inventory, inventory to shipping, and shipping to customer contact. If the records depend on one person remembering where the file is, the traceability system needs stronger document control.
Make the exercise real enough to test the system, but controlled enough to avoid confusing customers or employees.
Source notes
For recall and traceability context, verify:
- FDA Industry Guidance For Recalls.
- FDA Initiation of Voluntary Recalls Under 21 CFR Part 7, Subpart C.
- eCFR 21 CFR Part 7 Subpart C.
- FDA Tracking and Tracing of Food.
- USDA FSIS Understanding FSIS Food Recalls for FSIS-regulated products.
FAQ
What is the purpose of a mock recall?
The purpose is to test whether traceability and recall records work before an actual recall, complaint, or regulatory event.
Should a mock recall include mass balance?
Yes. Mass balance helps compare quantity received or produced against quantity shipped, held, destroyed, sampled, or remaining in inventory.
What happens after a failed mock recall?
Document the gaps, assign corrective actions, verify effectiveness, and update procedures or training where needed.