How to Conduct a Successful Mock Recall

The Fundamentals of Mock Recalls

A successful mock recall is a simulated emergency exercise that verifies a food manufacturer’s ability to locate and retrieve potentially unsafe products from the supply chain within a predefined timeframe. To be effective, the exercise must test both the traceability system (the data) and the recall procedure (the people and communication) under realistic, time-sensitive conditions. In South Africa, these exercises are not merely best practice but are foundational requirements for both legal compliance and international certification.

Understanding the "why" behind these exercises is critical. Beyond compliance, a mock recall protects the business from the astronomical food recall cost, which includes logistics, disposal, legal fees, and brand rehabilitation. By identifying a failure in your food traceability system during a simulation, you prevent that same failure from occurring during a high-stakes public health incident.

Key Takeaways

• Legal vs. Voluntary: Understand that R.638 requires a traceability system, while GFSI standards mandate at least one annual mock recall.
• Time is Critical: Most standards expect a 100% reconciliation of product within 2 to 4 hours.
• Test Every Direction: A robust exercise includes both forward traceability (to customers) and backward traceability (to raw materials).
• Document Everything: An audit finding is often caused by missing logs, not just slow retrieval.
• Continuous Improvement: The primary goal is to identify gaps in your system, not to achieve a 'perfect' result through cheating the clock.

The Regulatory and Certification Landscape in South Africa

Before initiating an exercise, it is vital to distinguish between what the South African government requires and what your certification body demands. Grounding your procedure in the correct framework ensures you are prepared for both the Environmental Health Practitioner (EHP) and the third-party auditor.

Statutory Requirements: R.638 and Act 54

Under the Foodstuffs, Cosmetics and Disinfectants Act 54 of 1972 and its associated Regulation R.638 (Regulations Governing General Hygiene Requirements for Food Premises, the Transport of Food and Related Matters), every food premises must have a traceability system in place. While R.638 does not explicitly use the term 'mock recall', it mandates that a person in charge must be able to trace any foodstuff to its source. Failure to produce these records for an EHP can lead to the withdrawal of your Certificate of Acceptability. Note that the COA requirements checklist specifically emphasizes the ability to demonstrate hygiene control through documentation, of which traceability is a core pillar.

Certification Standards: FSSC 22000, BRCGS, and ISO 22000

If your facility is pursuing or maintaining a GFSI-benchmarked standard, the requirements become more prescriptive. FSSC 22000 requirements and BRCGS Global Standard for Food Safety Issue 9 both require a documented food recall procedure that is tested at least annually. These standards typically look for:

• Reconciliation of mass balance (input vs. output).
• Speed of response (usually a 4-hour window for full reconciliation).
• Inclusion of primary packaging and raw materials.
• Verification of contact details for the recall team and emergency services, including the National Consumer Commission (NCC).
• Evaluation of the food recall risk assessment to ensure the mock scenario was appropriate for the product type.

Step-by-Step Guide to Conducting the Exercise

1. Select a Challenging Scenario

Do not pick your easiest, most frequent production run. To truly test the system, choose a scenario that involves a raw material used in multiple finished goods or a batch that has been partially shipped to different types of customers (e.g., retail, wholesale, and export). Potential triggers include a simulated positive Listeria result, an undeclared allergen due to a supplier labelling error, or a physical contaminant reported by a consumer. Reviewing food recall examples in South Africa can help you design a scenario that is locally relevant, such as a spice blend containing an unlisted preservative or a dairy product with a fermentation failure.

2. Convene the Recall Team

A mock recall is not a one-person job for the QA Manager. Active participation is required from Production (for yield data), Logistics (for shipping records), and Procurement (for supplier information). Start the clock the moment the 'incident' is announced. Ensure your recall team roles are clearly defined and that alternates are identified in case of leave or absence. This cross-functional approach is a hallmark of a strong food safety culture, as it demonstrates that every department understands its role in consumer protection.

3. Execute the Traceability Component

The core of the exercise is the traceability challenge. You must be able to identify:

• Which raw material lots went into the affected batch.
• The total quantity produced (verified against production logs).
• The quantity currently in your warehouse (verified by physical count).
• The quantity already dispatched and exactly which customers received it (verified by delivery notes).

Use our traceability exercise checklist to ensure no steps are missed during this high-pressure phase. In an audit, you will likely be asked to perform a batch traceability exercise on the spot, so practicing this monthly—even outside of the full annual mock recall—is recommended.

4. Perform the Mass Balance Calculation

This is where many South African manufacturers fail their audits. You must account for 100% of the product. The formula is: Total Produced = (Stock on Hand + Total Dispatched + Samples + Waste/Rework). If you can only account for 98% of the product, you have a 2% 'variance' that must be explained. Auditors will scrutinise these discrepancies to see if your mass balance accounts for floor sweepings, moisture loss (where applicable), and lab samples. A common failure mode is forgetting to subtract "retention samples" or "lab samples" from the total produced, leading to an over-calculation of available stock.

Documentation and Evidence Checklist

When the audit comes, the auditor will not see the exercise; they will only see the paper trail. Ensure the following documents are filed together:

Deep Dive: Forward vs. Backward Traceability

A comprehensive mock recall must test the system in both directions to be valid for standards like BRCGS or FSSC 22000.

Forward Traceability (Product to Customer)

This starts with a finished product batch number. You must prove you can identify every customer who received that specific batch. In the South African retail landscape, this often involves coordinating with third-party logistics (3PL) providers. A common gap is failing to account for "stock in transit"—product that has left your gate but hasn't yet been scanned into the customer's DC.

Backward Traceability (Product to Supplier)

This starts with the finished product and works back to the raw materials and primary packaging. You must be able to produce the supplier approval records and the specific Certificates of Analysis (COA) for the ingredients used. If your exercise reveals that you used an ingredient from an unapproved supplier, this triggers a separate supplier nonconformities investigation.

Common Pitfalls and How to Fix Them

Over-reliance on Digital Systems

While digital food traceability significantly speeds up the process, ensure your team knows how to access data if the server is down or the specialist operator is unavailable. A mock recall should occasionally be conducted when the 'power is out'—a very real scenario in South African manufacturing—to test manual backup systems. If your ERP system fails, do you have printed daily stock sheets to fall back on?

Neglecting Packaging and Processing Aids

Many manufacturers focus solely on the ingredients. However, if the recall is due to a printing error on a sleeve (e.g., missing allergen warning) or a chemical contaminant in a processing aid (like conveyor lubricant), you must be able to trace those lot numbers. Ensure your system includes every component listed in your HACCP plan that could pose a risk.

'Perfect' Timings and Dry-Labbing

If your mock recall takes exactly 59 minutes every year, auditors may become suspicious of 'dry-labbing' (faking data). Real exercises uncover missing signatures, illegible pallet labels, or slow communication from a third-party warehouse. These 'failures' are actually successes because they allow for root cause analysis and system improvement before a real crisis occurs. If a gap is found, utilize a fishbone diagram explained in our guides to determine if the failure was due to methods, machinery, or manpower.

Communication Breakdowns

Often, the "trace" is successful (the data is found), but the "recall" (the communication) fails. Does your recall communication plan include out-of-hours numbers for key customers? During the mock exercise, you should actually call a sample of customers (clearly stating "THIS IS A MOCK EXERCISE") to verify that the contact details on file are still valid. Personnel turnover at retail buying offices is high; an outdated contact list can delay a recall by hours.

The Post-Exercise Review: Closing the Loop

Once the exercise is complete, the team must meet for a 'post-mortem'. This is not just a formality; it is a requirement for internal audits and management review. Use the following questions to guide the session:

1. Was 100% of the product located? If not, why?
2. Did the exercise take longer than the 4-hour target?
3. Were all traceability records legible and easily accessible?
4. Did the recall team members know their responsibilities without referring to the manual?
5. Was the mass balance variance within the acceptable 1-2% range?

If the reconciliation took 5 hours instead of 4, or if a pallet was "lost" in the system, you must issue a CAPA (Corrective and Preventive Action). Follow the CAPA process to ensure the root cause is addressed. This demonstrates a mature food safety culture where the business prioritises consumer safety over simply 'ticking the box'.

Relationship to Other Food Safety Programs

A mock recall does not exist in a vacuum. It is the final verification of several other prerequisite programs:

• Supplier Management: If you cannot trace back to the supplier, your supplier management program has failed.
• Training: If staff cannot find records, it indicates a need for further training and education.
• Food Defence: A recall scenario might involve intentional adulteration, requiring coordination with your food defence plan.
• Food Fraud: If the mass balance shows more product sold than ingredients bought, you may have uncovered a food fraud issue.

Conclusion

A mock recall is the ultimate stress test for your facility's resilience. By following a structured approach that satisfies both South African R.638 hygiene requirements and international GFSI standards, you protect your brand from catastrophic financial and reputational damage. Remember, the goal is not to prove you are perfect, but to prove you are prepared. Regular testing ensures that when a real crisis hits, your team acts with precision rather than panic.

If you need assistance in refining your recall procedures or implementing a more robust traceability system, Shilux offers expert food safety consulting to help you navigate these complexities. Our QMSURE paperless system can also automate your traceability logs, reducing recall time from hours to minutes. Contact us today to ensure your facility is truly crisis-ready and compliant with all South African food safety regulations.