A mock recall is only as valuable as the scenario you choose.

If the scenario is unrealistic, too simple, or poorly structured, you won’t properly test your system. On the other hand, if it’s too complex or poorly thought out, you may end up creating unnecessary work without gaining useful insights.

This article outlines the key principles for selecting an effective mock recall scenario, based on real-world practice.

Start With the Right Batch

The most important decision is selecting the batch.

A good mock recall batch should:

• Have a clearly recorded production quantity
• Be partially in stock
• Be partially distributed
• Include product that has reached the consumer

This creates a realistic recall situation where you must:

• Account for stock on hand
• Trace product in distribution
• Consider product already with consumers

If the product has not reached consumers, the situation is more likely to be a trade recall, not a consumer-level recall.

However, avoid batches that are too large or widely distributed. If a batch has gone to hundreds or thousands of customers, reconciliation becomes unnecessarily complex and time-consuming.

The goal is not to create chaos — it is to prove that you can account for 100% of the product.

Understand What “Good Reconciliation” Looks Like

A successful mock recall demonstrates that you know where all product is.

For example:

• 100 units produced
• 50 units in your warehouse
• 40 units with a distributor
• 10 units sold directly to customers

If you can trace and account for all 100 units, you are in control.

In many cases, this means no public recall is required. Regulators like MPI actively try to avoid unnecessary public recalls, as they:

• Create unnecessary workload
• Cause public confusion
• Reduce the impact of genuine recall notices

Online sales are particularly important here. If you sell directly to customers and have their contact details, you may be able to resolve the issue without a public recall.

Choose a Scenario That Could Actually Happen

The scenario should be:

• Realistic
• Relevant to your operation
• Credible

A good approach is to choose something that is slightly unusual, but still plausible.

Example: Allergen Contamination

A strong example is unintended allergen contamination.

For instance:

• A drink batch becomes contaminated with fish sauce
• Fish is not declared on the label
• A staff error leads to the contamination

While unusual, this is entirely plausible and creates a serious food safety issue.

Allergen scenarios are excellent because:

• They are common causes of real recalls
• They are high-risk
• They test communication and traceability systems

Consider Common Recall Categories

Looking at real recall data (e.g. MPI recall database), most recalls fall into a few categories:

1. Allergen Contamination

• Undeclared allergens
• Cross-contact during production

2. Foreign Matter

• Metal fragments
• Missing machine parts (e.g. screws)
• Packaging defects

Example:
If a machine screw goes missing and was positioned above product, you may reasonably assume it entered the batch.

3. Chemical Contamination

• Cleaning chemical residues
• Ingredient contamination
• Misformulation

4. Process Failure

• Incorrect cooking temperatures
• Equipment calibration errors

Example:
If your cooker was actually operating at 55°C instead of 75°C, all product since the last calibration may be unsafe.

This can trigger a multi-batch recall, which is significantly more complex.

Ingredient Supplier Issues

One of the most impactful scenarios involves supplier notifications.

For example:

• An ingredient is contaminated (e.g. allergen or heavy metal)
• You have used that ingredient across multiple batches
• Multiple products are affected

These scenarios can escalate quickly:

• Multiple products
• Multiple batches
• Multiple businesses

Real-world examples include:

• Lead contamination in sugar
• Gluten contamination in buckwheat
• Milk contamination in dark chocolate

These are large-scale recall situations and are useful for testing advanced systems — but may be too complex for smaller operators.

Match the Scenario to Your Business

The best mock recall scenario is one that reflects your actual risks.

You should consider:

• Your product type
• Your process steps
• Your ingredients
• Your equipment
• Your record-keeping system

Ask yourself:

• What could realistically go wrong here?
• Where are the weak points in our system?
• What would be hardest to trace?

The Role of Record Keeping

Your ability to manage a recall is heavily influenced by your records.

Under the Food Act, record-keeping requirements are relatively minimal. However, better records allow you to:

• Trace ingredients to batches
• Trace batches to products
• Isolate affected product quickly

If you don’t track ingredient usage properly, you may be forced into a full recall, even if only a small portion is affected.

Final Thoughts

Choosing the right mock recall scenario is critical.

You should aim for a scenario that:

• Tests your system properly
• Reflects real risks
• Allows full reconciliation
• Is manageable in scope

If you choose the wrong batch or scenario, you may complete the exercise without actually testing your recall capability.

A well-designed mock recall should give you confidence that, if a real issue occurs, you are fully in control.