Run a recall drill from a lot to its recipients

A team locates every unit of an affected lot still in its warehouse and reports a successful recall drill. The same lot was also supplied to several distributors, partially returned and repacked under another reference. Those quantities never appeared in the warehouse query.

Recall traceability needs a broader question: can the organisation reconstruct the affected population, identify its relevant recipients and account for subsequent movements? A stock report is one input. A drill should also test the decision process, record access and communication readiness defined by the approved recall procedure.

WHO's distribution guidance addresses recall records, recipient information and reconciliation. WHO TRS 1025 Annex 7, section 10. The applicable recall procedure and responsible authorities determine real-event actions and communications.

Define the simulated scope before querying

Specify the product, lot or other affected identity used in the drill and the assumed reason for the exercise. Establish which sites, business entities and time period are included. Make the simulation status unmistakable so test records or messages cannot be mistaken for a live recall instruction.

The exercise should follow the authorised drill plan. Decide whether external parties participate and obtain the appropriate arrangements before sending any simulated communication. A contact-readiness check can often use approved internal verification without contacting a customer during the exercise.

Select a scope with meaningful complexity. A lot that never left one bin may demonstrate basic retrieval but will not test inter-depot transfers, repacking or distribution handovers. Choose the scenario for the capability being assessed, not simply for the easiest successful result.

Reconcile the 10,000-pack population

Consider an illustrative population of 10,000 packs at a stated cutoff. The records initially show 6,000 shipped, 3,500 still held internally and 500 supported by sample or destruction records.

The arithmetic closes, but that alone does not prove the categories are correct. Inspect whether a returned shipment was counted both as shipped and on hand, whether the 500 packs have actual supporting records and whether an inter-depot movement was mistaken for an external shipment.

If 200 packs have returned from a recipient by the cutoff, the model must represent their current location without counting them twice. One approach is to retain gross shipment history and separately reconcile returns to current external and internal balances. State the chosen convention so reviewers can reproduce the result.

The exercise must also distinguish accounted quantity from recovered quantity. A delivery record showing where 6,000 packs went does not establish that any of those packs have been recovered or that each recipient has confirmed its current position.

Trace transformations without losing the source

Repacking, relabelling and other authorised transformations can change the identifiers used downstream. Preserve the relationship between input identity, operation, output identity and relevant quantities. A search by the original lot should reach the resulting population where it falls within the affected scope.

Check unit conversions explicitly. A case, carton and saleable pack are not interchangeable quantities. Use the controlled conversion applicable to the actual presentation and preserve evidence of partial containers.

The batch genealogy guide develops manufacturing relationships. The serialization guide addresses a different level of identity and event exchange. Neither a lot reference nor a serial number alone supplies a complete history when the joins between records are missing.

When historical data cannot support an exact relationship, make the gap visible to the responsible recall team. Do not narrow the affected scope through an unsupported assumption simply to make the drill balance.

Verify the recipient record at the operating level

A customer master may identify a billing entity while the goods went to a particular receiving site. The recall workflow needs the relevant recipient and contact information for the approved process, not only the invoice address.

Link dispatch references to destination, contact record, supplied identity and quantity. Distinguish the direct customer from any downstream distribution information available through the agreed arrangements. Record where information stops and who must obtain the next part.

Inspect inactive customers, renamed businesses and historical addresses. A current master-data screen may have overwritten the details that applied at dispatch. Preserve sufficient transaction context to reconstruct the original recipient while obtaining current contact information for an actual communication.

Assign a custodian for contact readiness. A successful database join does not prove that the named person is reachable or that the backup route is current.

Track different outcomes separately

Use separate drill measures for scope identification, internal location confirmation, recipient identification, communication readiness and reconciliation. Where the approved exercise includes acknowledgements or simulated recovery, keep those stages distinct too.

An “all complete” field can conceal important differences. A recipient can be identified but not contacted; contacted but not acknowledged; acknowledged but still reconciling stock. A quantity can be physically received back while its final disposition remains unresolved.

The workflow should preserve the owner and evidence for each stage. It should also expose contradictory information, such as a customer reporting more packs than the recorded shipment or a return reference that belongs to another lot.

Make missing data an actionable result

Classify gaps by the decision they prevent. Examples include a missing lot on a dispatch line, an unlinked repacking output, an obsolete recipient contact and an unexplained quantity adjustment. Assign each to the process owner who can correct the source or operating arrangement.

Avoid repairing only the drill spreadsheet. If the application cannot preserve the required relationship, fix the originating record or integration and verify that the improvement survives another exercise.

The distribution software guide helps evaluate the systems involved. A specialised recall view can be useful, but it should expose source records and unresolved links rather than presenting a polished result that hides them.

Repeat the difficult part after remediation

Agree acceptance conditions before evaluating the drill. These should reflect the approved procedure and operating scope, including how completeness, response and unresolved differences are assessed. Do not invent a universal completion time for every product and distribution network.

After remediation, repeat the scenario that exposed the gap. If a returned quantity caused double counting, verify that the new model reconciles gross shipments, returns and current location correctly. If a renamed customer broke the contact link, test the historical and current identities together.

Measure improvement against comparable exercises and retain the scope differences. A faster drill using a simpler lot is not evidence that the difficult handover improved. Keep findings, actions and follow-up evidence connected so the exercise supports learning rather than only a completion certificate.

NextEdge Labs can help map the identity joins and build a drill view that distinguishes known facts from missing evidence. The first engineering deliverable should be a reproducible reconciliation for a representative population.

Summary and next actions

A recall drill should account for the affected population beyond the warehouse and test the handovers needed to reach relevant recipients. Located, contacted and recovered quantities are separate outcomes.

• Choose an authorised simulation scope with a meaningful distribution or transformation history.
• Reconcile its quantities using explicit units, cutoff and non-overlapping categories.
• Check recipient identity and contact readiness alongside stock and movement records.
• Assign each gap to its source-process owner and repeat the failed scenario after remediation.