Checklist · Cannabis · Recall Response

Cannabis Recall Response Playbook

Contain the affected product, define the recall universe, preserve traceability, control communications, reconcile returns, and close with documented corrective action.

By Lincoln Square Law · 7-minute read

🖨 Print this checklist

• Triggering evidence is preserved in its original form with date, source, product identifier, and recipient.
• A written hold order identifies the affected product and prevents further manufacture, transfer, delivery, or sale while scope is assessed.

Define the recall universe from traceability data

The scope should be evidence-driven. Use batch, lot, package, test-sample, production, ingredient, transfer, and sale records to identify every potentially affected unit. Do not assume the named batch is the entire universe if shared ingredients, equipment, packaging, or process conditions could affect adjacent batches. Record both the initial scope and every later expansion or narrowing, with the basis for the change.

• Affected batch, lot, package, SKU, production date, test sample, and ingredient identifiers are mapped.
• State tracking data identifies current on-hand inventory, transfers, receiving facilities, and disposition status.
• Point-of-sale or distribution records are used to determine whether affected product reached consumers and in what quantities.

Quarantine first, then investigate without destroying evidence

Physically segregate affected product, block it electronically where the system permits, and control access. Quarantine records should show quantity, identifiers, location, date, and responsible employee. Do not destroy, remediate, relabel, or return product until the applicable regulator or rule allows the disposition. Preserve representative samples and supporting records when appropriate because the investigation may need to determine root cause, testing integrity, or the extent of contamination.

• All affected on-site product is physically segregated and clearly marked against unauthorized release.
• State-system status and internal ERP/POS status prevent accidental sale or transfer.
• No destruction, remediation, repackaging, or relabeling occurs until authority and documentation requirements are confirmed.

Make regulator and business notifications fact-specific

Notification duties depend on the event and jurisdiction. Prepare a verified factual chronology before communicating.

Identify product, risk, scope, distribution, immediate containment, and next steps. Avoid speculation about cause or safety conclusions that have not been established. If downstream licensees hold affected inventory, provide clear instructions for quarantine and confirmation. Maintain a log of every communication, recipient, method, time, and response.

• Applicable regulator-notification requirements and deadlines are identified for the actual trigger.
• Downstream facilities receive a product-specific hold or recall notice with identifiers and handling instructions.
• Consumer-facing communication, if needed, is reviewed for accuracy, clarity, and consistency with regulator instructions.

Reconcile effectiveness, returns, and final disposition

A recall is not complete when notices are sent. Measure how much product was distributed, how much was located, how much was returned or quarantined, and what remains unaccounted for. Follow up on nonresponsive recipients.

Record regulator-approved destruction, remediation, or other final disposition in the state system and internal records.

The closeout file should show an arithmetic reconciliation of the recall universe.

• Distributed quantity, on-hand quantity, returned quantity, destroyed/remediated quantity, and unresolved quantity reconcile.
• Nonresponsive downstream recipients are escalated and follow-up attempts are logged.
• Final disposition is authorized, witnessed or documented as required, and reflected in state tracking.

Close with root cause and CAPA

After containment, determine why the problem occurred and which control failed to detect it earlier. Corrective and preventive action should identify an owner, deadline, verification method, and follow-up test. Update SOPs and training only when the investigation supports the change. Then run a mock trace on a different batch to confirm the revised control can locate product and supporting records quickly.

Classify the hazard before choosing the message

Not every recall trigger presents the same risk. A pesticide failure, microbiological contamination, undeclared allergen, potency misstatement, package defect, foreign material, labeling error, or traceability failure may require different containment and communication. Build a written risk assessment that identifies the known facts, uncertainty, potential exposure, affected population, severity, and whether product remains in commerce. That assessment should drive the urgency and breadth of the response without overstating facts that are still under investigation.

• Risk assessment separates confirmed facts from hypotheses and open questions.
• Team documents why the initial recall scope is sufficient or why it is expanded.
• Communications use consistent product, lot, and risk identifiers across approved versions.

Preserve privilege and factual integrity during the investigation

A fast-moving recall can generate inconsistent emails, draft theories, and duplicate spreadsheets. Establish one factual chronology and one controlled repository. Identify when counsel is directing legal analysis versus when ordinary business records are being created. Employees should preserve records and avoid deleting, editing, or backfilling source data. Interviews should distinguish what the witness observed from what the witness inferred after the event.

The final root-cause record should cite the evidence supporting the conclusion.

• Original records, messages, COAs, system history, and relevant photographs are preserved without overwriting.
• A controlled chronology identifies the source for each material fact.
• Root-cause conclusions cite evidence rather than relying only on memory or team consensus.

Run a post-recall effectiveness review

Thirty to sixty days after closeout, test whether corrective actions actually changed the process. Sample the revised SOP, training records, production or receiving records, and a new batch trace. Confirm that employees are using the new control and that the control would have detected the original problem earlier. If the fix exists only in a revised document, the recall has not produced a reliable preventive control.

Prepare the recall system before a real event

Run a mock recall at least periodically using a live but unaffected batch. Give the team a product identifier and require it to determine source inputs, testing record, quantities produced, current inventory, transfers, receiving facilities, and consumer-sale data where available. Time the exercise and record missing records, duplicate identifiers, stale contacts, or unclear decision authority. A mock recall tests the system without the pressure of an actual health or compliance event.

• Mock recall uses a real batch and measures time needed to locate product and records.
• Contact lists for regulators, receiving facilities, laboratory, insurer, and leadership are tested.
• Each mock-recall gap generates a corrective action with owner and deadline.

Coordinate insurance and contractual notice

Product contamination, recall, commercial general liability, property, cyber, or other coverage may contain prompt-notice requirements. Supply and distribution contracts may also require notice, cooperation, indemnity, or preservation of evidence. The response team should identify those obligations early without allowing insurance or contract questions to delay containment. Preserve cost records from the first day so the company can later quantify destruction, testing, freight, communications, replacement, business interruption, and professional expenses.

The closeout package should state what happened, what product was affected, how much was recovered, what remained outstanding, what the regulator required, what corrective actions were completed, and which risks remain.

That record becomes the starting point for the next inspection, insurer question, transaction diligence request, or similar incident.

Evidence-retention check: preserve the exact versions of notices, call scripts, regulator submissions, distribution lists, photographs, inventory extracts, and destruction or remediation records used during the event. Do not rely on an email inbox as the recall archive. A controlled closeout folder should allow a later reviewer to reconstruct who knew what, when decisions were made, how the recall universe changed, and why the final disposition was selected.