Overview
This case study outlines a situation where a food business was advised to initiate a voluntary recall despite having test results indicating that the product was safe.
The case highlights a common but poorly understood dynamic:
- Regulatory authorities may recommend a recall without fully disclosing their reasoning
- Businesses may rely on testing data that does not reflect the true risk
- Critical information may sit outside the business’s visibility, particularly when contract manufacturers are involved
Initial Situation
The business was contacted by the regulator with serious concerns about product safety and a recommendation to carry out a voluntary recall.
At the time:
- The product had been manufactured by a contract manufacturer
- Each batch had undergone extensive laboratory testing
- All available test results indicated the product was within specification
- The business had no clear understanding of the issue
Despite this, the recommendation to recall remained.
The Core Problem
The business was effectively being asked to:
- Recall product
- Accept reputational and financial damage
- Without being given a clear, evidence-based explanation
This created a high level of distress and uncertainty.
From a technical standpoint, there was no obvious justification for recall based on the information available to the business.
Understanding “Voluntary Recall”
A key concept in this case was the nature of a “voluntary” recall.
While technically voluntary:
- A refusal may trigger escalation
- Authorities can ultimately mandate a recall
- The decision often becomes procedural rather than optional
This creates a situation where:
👉 The business appears to have a choice — but in practice, does not.
Initial Decision
Based on available evidence:
- The consultant
- The contract manufacturer
- Other advisors
…all agreed that there was no strong case for recall.
The decision was made to decline the recall recommendation initially, with the understanding that the decision could be revisited if new information emerged.
Escalation and New Information
Following the decision to decline, the regulator made further contact and disclosed additional information that had not previously been shared.
This included:
Contract Manufacturer Performance Issues
- The manufacturer was under heightened regulatory scrutiny
- There were concerns about overall operational performance
- This information had not been disclosed earlier due to confidentiality constraints
Scope Misalignment
- The product being manufactured was not fully aligned with the manufacturer’s approved scope
- This introduced additional compliance and process risks
Microbiological Risk (Post-Process Contamination)
- There were concerns regarding post-processing contamination risk
- Environmental monitoring (such as swabbing) was more relevant than finished product testing
👉 The business had invested heavily in finished product testing, but the real risk sat in the processing environment, not the final product.
A Key Technical Insight
The product was positioned in a category where:
- It could rely on a consumer cooking step as a control measure
- But only if properly validated
This requires:
- Clear cooking instructions
- Validated conditions
- Consistent achievement of a safe temperature
In this case:
- Cooking instructions were not validated
- There was no assurance of a consistent kill step
This meant the product could not reliably rely on this control measure.
Final Decision
With access to the full context, the situation changed significantly.
While the risk was not immediately obvious from test results:
- There were systemic concerns
- There was uncertainty in process control
- There was potential for consumer risk
The decision was made to proceed with the recall.
Key Learnings
Testing Is Not Always the Answer
Extensive finished product testing:
- Can provide reassurance
- But may fail to detect the real risk
You May Not Have the Full Picture
When using contract manufacturers:
- Critical information may not be visible
- Risks may sit outside your direct control
“Voluntary” Is Often a Formality
A voluntary recall:
- Is usually the preferred regulatory pathway
- But may effectively be required
Validation Matters
Control measures such as cooking instructions:
- Must be validated
- Must be reliable in real-world use
Communication Gaps Are Real
In this case:
- The regulator had valid concerns
- But was initially unable to communicate them fully
Practical Takeaway
Not all recall decisions are based on clear, visible evidence.
Sometimes the most important factors are:
- Hidden risks
- System-level issues
- Information gaps between stakeholders
A structured and informed approach is essential to:
- Understand when to push back
- Recognise when risk is real
- And make the right decision under pressure