How to read a cannabis COA
A cannabis certificate of analysis (COA) should help you reduce uncertainty, not create false confidence. Many teams skim a COA for one or two values, then assume the product is low risk. A stronger approach is to read the COA as a structured record: identify the lot, confirm sample relevance, review panel scope, evaluate measurement context, and capture any unanswered questions before procurement approval.
Step 1: Confirm identity and traceability
Start with basic alignment checks. If the tested lot, production date, or product category does not match what is being sold, every downstream value is less useful. COAs should map cleanly to the specific inventory under review.
- Lot/batch ID should match invoice and packaging records.
- Sample collection and report dates should fit production timelines.
- Laboratory name and report identifiers should be auditable.
Step 2: Check panel coverage, not just outcomes
Passing values only matter if the right analytes were tested. Different product forms carry different contaminant and process risks. A complete review asks whether panel scope is appropriate for the product format and market context, then documents any out-of-scope areas before approval.
Step 3: Read results with measurement context
Values near an action limit deserve more scrutiny than comfortably separated values, even if both are technically passing. Also watch for reporting quirks: non-detect notation without clear limits, unusual unit presentation, or missing method details on critical analytes. These issues do not always invalidate a COA, but they do affect confidence.
Step 4: Evaluate data consistency over time
A single COA is a snapshot. Procurement decisions improve when you compare multiple lots and look for stability. Repeated volatility, frequent corrections, or inconsistent panel availability can indicate process control problems even when no single report looks alarming in isolation.
Step 5: Capture unresolved issues in writing
Approval meetings move quickly. If unresolved questions are not logged, teams can accidentally treat assumptions as facts. Maintain a short COA review memo for each supplier that records exceptions, follow-up requests, and approval conditions. This improves accountability and makes future requalification easier.
Common COA review errors
- Approving based only on potency or one headline metric.
- Ignoring mismatch between tested matrix and marketed product.
- Treating “third-party tested” as a substitute for panel details.
- Failing to save the exact report version used for approval.
Practical review template
Use a fixed sequence for every COA: identity, scope, values, variance history, unresolved issues, and decision. Repeatability matters more than complexity. The objective is not perfect scientific interpretation; it is defensible procurement control with a clear evidence trail.
Field implementation worksheet
Teams usually fail not because they lack information, but because they review information differently each time. Convert this guide into a one-page worksheet your reviewers must complete before approval. Keep the worksheet short enough to be used under deadline pressure, but strict enough that a missing answer is visible. If a section cannot be completed, the default state should be conditional approval or deferral, not silent assumption.
For multi-person teams, require a short reviewer note with three lines: what was verified, what remains unresolved, and what action is required next. This turns individual judgment into a repeatable process and makes future audits easier. When suppliers challenge decisions, a structured worksheet is more defensible than memory-based explanation.
Supplier call questions that improve clarity
- What documentation can you provide within one business day without escalation?
- Which quality or compliance issues in the last 12 months required corrective action?
- How do you version-control updated testing or compliance records?
- What triggers internal hold, recall, or restricted distribution decisions?
- Who owns final sign-off when evidence and sales urgency conflict?
- How are unresolved exceptions communicated to downstream buyers?
- What would cause you to pause shipments to a key account?
Minimum documentation package
If you want consistency across suppliers, ask for the same minimum package from every counterparty. You can always request more detail later, but starting from a fixed baseline prevents bias toward better-marketed suppliers.
- Lot-linked testing records tied to current inventory.
- Clear point of contact for quality/compliance escalations.
- Incident response summary with recent examples if available.
- Disclosure of known constraints, data gaps, or pending updates.
- Written acknowledgment of approval conditions and review cadence.
Quarterly governance loop
Schedule quarterly revalidation even for approved suppliers. Use a fixed agenda: documentation completeness, variance trends, unresolved exceptions, and trigger events since last review. This keeps your controls current without requiring constant ad hoc rework. Strong governance is mostly rhythm, not complexity.