A recall is a controlled response to product already beyond the manufacturer's direct control. Speed matters, but speed without correct scope creates two risks: failing to reach affected patients and removing unaffected product during a shortage.
Seal connects the initiating signal, health-hazard evaluation, product and defect, lots or serials, genealogy, distribution, consignees, inventory, recall strategy, regulatory communication, notifications, responses, effectiveness checks, returns, corrections, destruction, reconciliation, status reports, CAPA, and termination.
FDA's industry recall guidance hub brings together Part 7 guidance, notification, status, and effectiveness-check resources for drugs, devices, and other regulated products.
The initiating signal remains connected to the action
Complaint, adverse event, deviation, OOS, stability failure, supplier alert, data-integrity concern, inspection finding, counterfeit report, labeling error, device failure, or authority request can trigger assessment.
The original signal, evidence, detection date, awareness date, reporter, products, immediate containment, and preliminary scope remain permanent even as understanding changes.
Health-hazard evaluation frames urgency and depth
Defect, failure mode, exposure, severity, probability, detectability, vulnerable populations, clinical consequences, reversibility, existing controls, distributed quantity, uncertainty, and medical or technical assessment support risk classification.
The evaluation records evidence and dissent. Classification does not replace jurisdiction-
Scope begins broad enough to protect patients
Potentially affected product, lots, serials, batches, strengths, pack sizes, markets, date ranges, sites, lines, components, suppliers, equipment, software, labeling versions, and distribution channels form the initial population.
Scope expansion and narrowing retain evidence, rationale, approver, and time. A root cause discovered later does not rewrite the earlier containment decision.
Genealogy makes scope precise
Raw materials, components, bulk, intermediates, packaging orders, labels, serials, cases, pallets, samples, rework, returned product, and released inventory remain traversable forward and backward.
Many-to-one and one-to-many transformations preserve contribution and destination. The scope can distinguish units exposed before and after an equipment intervention or artwork change.
Distribution records identify who received what
Customer, distributor, wholesaler, pharmacy, clinic, site, country, shipment, delivery, lot, serial, quantity, date, address, contact, onward distribution where available, and current inventory form the consignee map.
Returned, transferred, resold, administered, implanted, consumed, quarantined, destroyed, and unknown product states remain separate.
The recall strategy is an executable plan
Action type, depth, classification, urgency, channels, notification content, public warning, consignee obligations, response mechanism, return or correction instructions, effectiveness-check design, status-report frequency, authority contacts, and termination criteria are approved together.
Different markets and product types can use coordinated strategies without collapsing legal differences.
Communications come from controlled facts
Product identity, affected lots or serials, defect, hazard, actions, recognition instructions, return or correction process, contact, response deadline, and regulatory statements resolve from approved strategy data.
Letters, emails, portal notices, phone scripts, public warnings, and field instructions retain version, recipient population, approval, send event, delivery, and acknowledgment.
Every consignee becomes a tracked obligation
Contact attempt, channel, delivery, acknowledgment, response, inventory on hand, distributed onward, used, returned, corrected, destroyed, unavailable, questions, follow-up, and closure state remain visible.
Escalation rules prioritize nonresponders based on risk, quantity, depth, and time—not alphabetic order.
Effectiveness checks test whether the action worked
The plan defines level, sample population, selection method, attempt count, questions, evidence, acceptance, failures, escalation, and completion. Checks remain independent of routine response chasing where required.
A delivered email is not proof that affected product was identified and controlled.
Physical product is reconciled continuously
Manufactured, released, distributed, in company control, consignee stock, used, administered, implanted, returned, corrected, destroyed, recovered, exported, expired, sampled, and unaccounted quantities form a live balance.
Units and quantity bases remain explicit. Serialized and nonserialized populations can coexist without false precision.
Corrections and removals retain unit-level work
Field correction, relabeling, software update, inspection, repair, replacement, advisory notice, stock recovery, and destruction use controlled instructions and qualified personnel. Actual unit or lot state, work performed, evidence, verification, and restored status remain traceable.
Failed or incomplete correction returns to the action queue and may change the strategy.
Authority communication stays synchronized with operations
Initial notification, classification discussion, strategy, public communication, periodic status, reportable correction or removal, distribution updates, health-hazard evidence, effectiveness results, proposed termination, and final correspondence retain jurisdiction, version, submission, questions, commitments, and response.
Regulatory statements are generated from current governed facts while preserving each frozen submission.
One defect can create recalls in several markets, a device correction, a drug recall, a clinical-site notification, and a supplier containment. Shared root evidence and genealogy remain connected while each action retains its authority, scope, strategy, clocks, and termination.
Global coordination does not erase local accountability.
CAPA and supply decisions see the same population
Root cause, correction, preventive action, supplier response, process or design change, enhanced monitoring, effectiveness, shortage risk, replacement supply, and restart criteria connect to the recall and affected products.
The business can evaluate patient protection and supply continuity from the same controlled facts without weakening the quality decision.
Mock recalls test real retrieval and response
Scenario, trigger, target population, start time, participants, genealogy retrieval, distribution retrieval, contact data, quantity reconciliation, simulated communications, response, gaps, timing, and actions are recorded.
The exercise tests difficult branches and stale master data—not only the easiest recent batch. Actions remain linked to later evidence of effectiveness.
Status reporting is generated from live state
Scope, quantities, notifications, responses, nonresponders, returns, corrections, destruction, effectiveness checks, adverse outcomes, root cause, CAPA, and open issues aggregate without manual recounting.
Each report freezes the underlying state and calculation. Later corrections remain traceable.
Termination requires evidence, not calendar time
The decision considers reasonable communication attempts, action depth, response and recovery, correction completion, effectiveness, quantity reconciliation, product disposition, authority commitments, ongoing complaints, CAPA, and residual risk.
Closed recall does not mean erased recall. Surviving monitoring, complaints, records, and CAPA continue against the historical population.
Source systems retain commercial and regulatory specialization
ERP, WMS, serialization repositories, distributor systems, complaint platforms, and authority submission portals can remain authoritative for their native records. Seal does not invent distribution events that partners cannot provide.
It owns the governed case, population logic, cross-system genealogy, strategy, obligations, evidence completeness, reconciliation, effectiveness, and accountable decisions.
Where Seal is strongest
Seal is strongest when the recall cannot be managed as a mailing list. Because manufacturing genealogy, packaging, serials, inventory, distribution, complaints, quality events, CAPA, and communications are related, scope and progress remain explainable.
A CRM can send notices; an ERP can list shipments. Seal's advantage is proving that the right affected population was identified, reached, controlled, reconciled, and evaluated through termination.
Prove one difficult recall end to end
The first implementation should start from a supplier defect affecting part of several lots, trace through packaging and mixed distribution, approve a multi-market strategy, notify direct and indirect consignees, manage nonresponders, returns and corrections, sample effectiveness, reconcile quantities, report status, and reach termination.
Include incomplete genealogy, stale contact, onward distribution, one administered unit, a serial mismatch, damaged return, failed field correction, recall expansion, public warning, shortage assessment, and late complaint. The model is ready when every unknown remains explicit and actionable.
