New Zealand MPI guidance on doing a food recall
Government source used for recall process, notification, product identification and effectiveness principles.
Recall readiness
Bottled Water Recall and Mock Recall Plan
A mock recall should test whether the business can make and execute a product-protection decision under time pressure, not merely demonstrate that one shipment record can be found.
Direct answer
What should a bottled water recall and mock recall plan include?
The plan should define the recall team and decision authority, regulatory and customer notification paths, product and lot identification, forward and backward traceability, distribution and inventory records, quantity reconciliation, external communication approval, retrieval or control instructions, effectiveness checks, returned-product status and final disposition. A mock recall selects a realistic scenario and tests people, systems, after-hours contacts and external custody points without creating false public communication. Record elapsed decision points, data gaps, unreconciled quantities and failed contacts, then assign corrective actions and retest the weak controls.
System focus 01
Define recall authority, roles and escalation before an event
Name primary and alternate roles for incident leadership, quality assessment, regulatory liaison, legal review, communications, customer service, warehouse control, logistics and record retrieval. Define who can initiate a hold, recommend a recall, approve public messaging and close the action. Contact details should work outside normal office hours and cover contractors or third-party warehouses that hold product. The team should understand the applicable legal reporting route in each destination market. A decision log captures facts, uncertainty, options and approvals so the organization can act quickly without losing accountability.
- Maintain named primary and alternate contacts with tested after-hours communication routes.
- Separate technical risk assessment, legal notification and message approval while preserving one incident leader.
- Predefine triggers for escalation from internal hold to market action when distributed product may be affected.
- Keep current regulator, customer, distributor, laboratory and disposal-service contact references under document control.
System focus 02
Build the affected lot from ingredient, process and packaging genealogy
Start with the initiating hazard or defect and identify the material, source, treatment, filler, packaging and time relationships that could carry it. Trace one step backward to relevant supplied inputs and one step forward through every finished product, warehouse and consignee, while applying any broader local obligations. Include work in process, retained samples, rework where permitted, part pallets, returns and stock under third-party control. If code or timing evidence is incomplete, expand the boundary conservatively. Record why adjacent lots are included or excluded so the scope can be challenged and reproduced.
- Link product codes to production times, source and treatment records, filler, caps, labels and pallet identities.
- Identify every internal and external custody location, including transfers not yet reflected in final invoices.
- Protect wider plausible production when the last known good or first known affected boundary is uncertain.
- Preserve the query, report version and extraction time used to build the distribution list.
System focus 03
Reconcile quantities rather than reporting trace speed alone
A rapid customer list can still omit product. Calculate the total relevant production and reconcile units in plant, sampled, destroyed, corrected where permitted, shipped, returned and otherwise accounted for. Use consistent units and document conversion assumptions between bottles, cases, layers and pallets. Investigate duplicates, canceled shipments, inventory adjustments, code changes and transfers. Reconciliation should reveal both a percentage and the actual unresolved quantity, because a high percentage can hide a meaningful number of unlocated units. The approver decides whether remaining uncertainty requires a wider action.
- Start from a controlled production total and preserve the original units before converting quantities.
- Separate located, physically controlled, customer-confirmed, consumed, returned and unexplained quantities.
- Resolve duplicate shipment references and mixed pallets rather than assuming the system total is correct.
- Record reconciliation gaps with an owner, investigation step and consequence for recall scope.
System focus 04
Control communications, retrieval and effectiveness checks
Messages should identify the product and codes, hazard or reason at the approved level of detail, required recipient action, stock handling and response channel. Use current legal and regulatory guidance for notification content and timing. Distributors need instructions to cascade the action through their own customers. Track delivery, acknowledgment, stock located and action completed; sending an email is not an effectiveness check. Select risk-based verification methods for different recipient groups and escalate nonresponse. Returned or recovered goods remain identified, segregated and protected from accidental resale until controlled disposition.
- Approve one source message and manage translations or market versions without changing the technical meaning.
- Track each consignee, communication channel, acknowledgment, quantity held and follow-up status.
- Define effectiveness checks that verify action, not merely message transmission.
- Maintain secure custody, counts and status for returned, recovered or destroyed product.
System focus 05
Design a mock recall that tests weak interfaces and drives correction
Choose a plausible scenario that forces the team to use real records across production, packaging, warehouse and distribution. Vary the starting point: a cap lot, treatment deviation, source issue, coding failure or customer report creates different trace paths. Clearly mark the exercise and control all simulated external messages. Measure time to assemble the team, define scope, retrieve evidence, reconcile quantity and reach selected custody points, but do not reduce success to one stopwatch target. Debrief facts promptly, assign actions for every material gap and verify completion through targeted retesting.
- Rotate scenarios, shifts, products and starting records so the exercise does not become a rehearsed database query.
- Include at least one external or third-party custody interface under controlled simulation where feasible.
- Capture wrong assumptions, access failures, stale contacts and manual workarounds as test findings.
- Retest corrected controls and update the recall plan, training and data ownership after the exercise.
Mock recall scorecard
Test decisions and custody, not only database retrieval
A useful exercise shows whether the team can protect real material through imperfect interfaces.
| Capability | Exercise evidence | Failure signal | Corrective direction |
|---|---|---|---|
| Scope definition | Documented inclusion and exclusion logic | Boundary based on guesswork | Improve event and genealogy records |
| Quantity control | Complete unit reconciliation | Unexplained stock or duplicate totals | Repair transaction and conversion controls |
| Contact execution | Acknowledged action by custody point | Stale contact or no confirmation | Test alternates and escalation |
| Decision governance | Timed log with evidence and authority | Approval or legal route unclear | Clarify roles and train alternates |
Run exercises under a controlled simulation label and follow current market-specific recall law for any real event.
Editable buyer worksheet
Download the mock-recall exercise record
Test the scenario, contacts, backward and forward trace, quantity reconciliation, timing, gaps and corrective-action closure.
Technical reading
Authoritative references behind the planning framework.
Confirm the standards, guidance and legal requirements that apply to the project location and product before final design.
FDA guidance on initiation of voluntary recalls
Primary regulator guidance used for recall readiness and prompt initiation context in the United States.
FDA key elements of being recall ready
Regulatory preparedness source supporting trained roles, records and effective execution; jurisdiction-specific requirements remain controlling.
Buyer questions
Frequently asked questions
Use these answers as a project-planning starting point. Final equipment and performance remain subject to the confirmed brief.
How fast must a bottled water mock recall be completed?
Use any applicable legal, customer or certified-system requirement and the site risk assessment; do not rely on a universal internet target. Record separate decision and retrieval milestones, but judge completeness, accuracy, quantity reconciliation and contact effectiveness as well as speed.
Can a mock recall use only internal warehouse stock?
That can test containment but not the full external recall interface. A mature exercise should periodically test distributor or third-party custody records and controlled communication, while clearly preventing the simulation from being mistaken for a real public action.
What quantity must be reconciled during a bottled water recall?
Begin with all product inside the credible affected boundary and reconcile production, samples, waste, stock, shipments, returns and other dispositions in consistent units. Report unresolved physical quantity as well as any percentage, then decide whether uncertainty requires a wider scope.
When does an internal product hold become a recall?
Escalate when potentially affected product has left controlled custody and the applicable risk and legal assessment indicates market action. The recall team should use current jurisdiction-specific rules and notify authorities as required; it should not delay protection while waiting for perfect information.
Project-specific confirmation
Capacities, process routes, layouts, utilities and equipment shown on this site are decision frameworks and reference examples. They are not a final specification, performance guarantee or offer. Confirmed scope and performance are defined in the signed technical and commercial agreement.
Allot Tech project desk
Turn your requirements into a comparable line brief.
Share the source water, bottle, target output, pack format, factory status and destination. We will use them as the basis for a project-specific configuration discussion.
- CompanyAllot Tech (Suzhou) Co., Ltd.
- Emailsales@allottech.com
- China+86 186 6213 1120
- United States+1 818 262 0958
- Corporate websiteallottech.com