> Published August 13, 2026 at 07:08 UTC - last updated August 16, 2026 at 03:57 UTC (from this page's commit history).
>
> Markdown mirror of https://colorado-medical-cannabis.org/developing-stories/science-policy-forum/2026-03-06/
>
> Everything up to "Appendix for agents" is the page as a reader sees
> it. The HTML page is a subset of this file, rewritten for human
> readability.
>
> The appendix is context that does not appear on the page. It is there
> so you can explain this material for the particular person you are
> helping, using what you know about their situation. It is background
> for you, not text to hand them.


# The March 6 forum: third-party sampling meets its price tag, and the analyte worksheet drops its scores

<div class="story-banner story-banner-researching" markdown="1"><span class="story-banner-icon"><svg viewBox="0 0 24 24" aria-hidden="true"><circle cx="10" cy="10" r="6" fill="none" stroke="currentColor" stroke-width="2.2"/><line x1="14.6" y1="14.6" x2="21" y2="21" stroke="currentColor" stroke-width="2.2" stroke-linecap="round"/></svg></span><span class="story-banner-text" markdown="span">**Being researched:** this page reports our research in progress. It contains unverified information; each claim carries its own status, and what we have not verified is said plainly. Published and updated times come from this page's commit history.</span></div>

Colorado's Science & Policy Forum met March 6, 2026. We transcribed the
Division's published recording (about 2 hours) with a speech-recognition
model and drafted this summary from that transcript; our editor has
reviewed and approved this page, and the recording remains the source
of record. This
was the working meeting the February session set up: round two on
required third-party sample collection (now with real numbers and
testimony from labs that operate under both regimes) and a revised,
humbler version of the new-analyte worksheet.

## Notes from the editor

The most important sentence of the year may be the California lesson,
stated here for the second month running: third-party collection
without enforcement investment "doesn't solve sample fraud, it just
pushes it around." The room broadly accepted it (the Division's own
science director asked whether enforced first-party collection would
do as well for less), and then the year ended with neither: no
third-party rule, and no enforcement overhaul either. If you take the
lesson seriously, Colorado kept the cheap half of the decision and
skipped the half that mattered.

And since "enforcement" is an easy word to say and an expensive thing
to do, let's make it concrete. On the state's side, enforcement means
**people doing slow, unglamorous work**: investigators who show up at
a grow or a production kitchen, walk the rooms, pull the
inventory-tracking records and reconcile them against what's
physically there, request security-camera footage and actually watch
it, collect samples, interview staff, and then write all of it up
carefully enough to survive lawyers and a hearing. A single
complaint can eat weeks of an investigator's time, and a contested
case runs through a formal order to show cause and months of process
before a fine ever lands. When the room argues about "funding
enforcement," this is what the money buys: investigator-hours.

And for the business on the receiving end, guilty or not,
enforcement is a bill. An investigation means staff hours hosting
inspectors and pulling records; product frozen under quarantine while
the process runs (inventory you already paid to produce and can't
sell); attorney's fees through the hearing process; writing and then
actually living a corrective-action plan; and sometimes conditions
that keep costing after the case closes: one lab's settlement in the
public record required employing a dedicated quality manager for two
years, with written reports to the state at six, twelve, and
twenty-four months. Stores get their own version: a health advisory
means pulling product, posting notices, and handling returns on goods
they didn't make. So the real question under the year's whole
sampling fight is this: will Colorado pay for enough
investigator-hours to make cheating irrational, and how much of this
friction should honest operators have to absorb along the way?

The cost fight is worth watching as a case study in how the forum
actually works. The question on the table: if Colorado required
testing-lab employees to come collect every sample (instead of
businesses collecting their own), what would that add to a business's
testing costs? The room's estimates were all over the map. Lab-side
voices said a modest bump, maybe 10–20%. One manufacturer, relaying
its testing lab's unofficial quote, said it could *triple* the
company's annual testing bill: roughly $155,000 a year becoming
$465,000. The chair closed the topic by asking everyone for written
data instead of podium numbers. And by [June](../2026-06-12/), that
same manufacturer had done more research and publicly revised its
estimate down to
$150–200 per collection visit, about $40–50,000 a year for a
business that needs a lab pickup every day. That's the forum at its
best: not consensus, but the machinery working the way it's supposed
to. A producer going back to its testing lab for better numbers and
correcting its own estimate in public, because the regulator in the
chair made data the price of admission. Three organizations (a
producer, a lab, and the regulator) actually working it out.

## Since this meeting

*Where the threads this meeting opened stand as of August 2026, from
the recordings that followed.*

**Resolved.** Third-party collection reached its decision point in
[June](../2026-06-12/): declined without consensus, pivoting to
[first-party reforms in July](../2026-07-10/), where the video
surveillance, batch-verification, and chain-of-custody designs the
labs outlined here resurfaced as fallback proposals. The state lab's
physical recovery held, and the [April meeting](../2026-04-03/)
delivered the promised surveillance timeline: fall 2026. April's
proficiency-testing deep-dive ran as scheduled here.

**Still in progress.** The enforcement-instead alternative operators
converged on here (expand surveillance, annual inspections, minimum
fines, revocations) kept being repeated through
[June](../2026-06-12/) and remains exactly that: repeated, not
proposed.

**Put off or neglected.** The B2B trust gap (why are self-collected
samples fine for wholesale transfers?) was raised and never answered.
The hop-latent-viroid liability question had no answer and never got
one. The microbial-limit challenge was pointed at prior materials and
not reopened. And the edibles report, imminent here for the fourth
consecutive meeting, took until [June](../2026-06-12/).

## What was brought up

**What third-party collection would actually require** [0:10:03]. The
Division's captured framework from February: testing-facility employees
as the collectors, trained and possibly certified, required only for
product bound for store shelves. Business-to-business transfers would
keep self-collection. Then the practical testimony started landing.

**The regime-rewrite problem** [0:30:24]. A manufacturer who
interviewed lab directors in California and Missouri brought back a
structural point: third-party collection only buys integrity if the
sample is pulled from the *final product*. Collect midstream and too
much can change before the shelf. Colorado's testing regime samples
midstream; adopting third-party collection coherently would mean
rewriting the testing code around final-product testing. And the
recurring California lesson, for the second month running: the variable
that determined success wasn't who pulled the sample. It was
enforcement investment. "It just kind of passed the buck... until the
state invested in additional agents and site-specific audits"
[0:35:25].

**The cost fight** [0:35:25, 1:00:43]. The same manufacturer's testing
partner unofficially estimated a threefold cost increase: for his
small business, roughly $155,000 a year becoming $465,000. Two lab
voices disputed the multiple: a lab representative estimated $100–200
per pickup, and another stakeholder relayed lab quotes of roughly a
10–23% increase with consolidated pickups. A multi-state lab operator
offered the middle math: two to three sampling events per driver-day,
roughly $56–60,000 per driver per year passed through to clients, with
manifest sizes growing as businesses consolidate to save fees
[1:10:48]. The chair closed the topic asking for written data,
because the room's estimates spanned an order of magnitude [1:21:05].

**What the labs would want if it happens** [0:50:42, 1:10:48]. From
the lab side, the design consensus: collection restricted to testing
facilities and audited by the state like any other assay (ISO
accreditation alone "doesn't hold too much weight"); final-form
samples with the whole batch present and matched to the inventory
system; **video surveillance of every sampling event** (the
multi-state operator confirmed other states' enforcement bodies
routinely request footage); witness sign-off, tamper-evident seals,
chain of custody, GPS transport. One elegant side effect from the
multi-state operator: with controlled retained samples, a regulator
can order a retain split to a competitor lab: instant interlab
comparison data [1:15:49].

**The opposition's alternative** [0:45:32, 1:15:49]. Multiple
operators converged on the same counterproposal: spend the money on
enforcement instead. Expand the shelf-surveillance program, fund
annual inspections, put investigators in facilities watching
first-party sampling, and revoke licenses for adulteration rather than
fining $15,000. "We're already finding bad actors. We're not taking
them out of the industry. That's the problem" [1:15:49]. Rural
operators added the geography problem: transporters already reach some
areas weekly at best; a harvest waiting days for a third-party
collector backs up an entire facility [1:21:05].

**The analyte worksheet, version two** [1:31:11]. The manufacturer who
built February's risk-scored worksheet returned with a leaner version
that **removes the risk-priority scoring entirely**. The feedback
about unanchored numbers landed. What remains: structured evidence
submission per analyte, now with a source-quality scale (expert
opinion scores low; systematic reviews of randomized trials score
high, adapted from a published health-assessment framework). The
Division added a draft problem statement (proposals fail for lack of
comprehensive data; standardize the submission), which the room
accepted by silence [1:41:17].

## What was nailed down

- **A pilot for the worksheet**: two analytes with pending
  recommendations get run through it, **chromium** (CDPHE leads) and
  **fusarium mycotoxins** (a stakeholder group leads), reporting back
  in April or May [1:41:17]. A genomics-company scientist immediately
  supplied fusarium species references [1:51:26]; a lab suggested
  chlormequat chloride as a future candidate.
- **The state lab is physically back**: rooftop units repaired,
  chemical fume hoods recertified the week of the meeting; April to
  bring a definitive surveillance-resumption timeline [1:56:26].
- **The first technical method review happened** (February 19), focused
  on content analysis and homogeneity, with more sessions planned at a
  one-to-two-month cadence [1:51:26].
- **The schedule**: April = proficiency-testing deep-dive; May =
  third-party collection round three [1:56:26].

## What was left open

- **The cost question, by an order of magnitude**: 10% versus 3x is
  not a rounding disagreement; the Division asked for supporting data
  on the record [1:21:05].
- **Whether equal enforcement makes the collector irrelevant**: the
  Division's own science director posed the meeting's best question:
  with equal oversight resources, does third-party collection actually
  outperform enforced first-party collection? The honest answer from
  the manufacturer who studied it: on-the-ground enforcement of
  first-party sampling might be "equally impactful without the extra
  $300K" [0:40:28].
- **The B2B trust gap**: if self-collected samples can't be trusted
  for consumer products, why trust them for wholesale transfers
  between businesses? Raised, not answered [0:25:16].
- **Cross-contamination liability**: a cultivator asked who answers
  for hop latent viroid carried facility-to-facility by sampling
  crews. No answer existed [1:21:05].
- **The edibles surveillance report**: still in departmental review,
  now promised for "once we finish" (the fourth consecutive meeting
  with the report imminent) [1:56:26].
- **The microbial limit challenge**: a manufacturer argued Colorado's
  10,000 CFU total yeast and mold limit is stricter than newer states'
  100,000; the chair noted a prior forum group evaluated and kept the
  limit, with materials in the public Drive [1:21:05].

*This summary was drafted by our AI desk from a machine transcript and
has been reviewed and approved by our editor (2026-08-13). The
[Division's published recording](https://med.colorado.gov/public-engagement)
is the source of record.*

<div class="callout follow-story" markdown="1">

## Follow this story or help us report it

- <a href="mailto:editor@colorado-medical-cannabis.org?subject=Research%20snapshot%3A%20developing-stories%2Fscience-policy-forum%2F2026-03-06&body=Optional%3A%20add%20your%20question%2C%20comment%20or%20source%20for%20our%20team.">Email me the research snapshot</a> (or <a href="https://mail.google.com/mail/?view=cm&fs=1&to=editor%40colorado-medical-cannabis.org&su=Research%20snapshot%3A%20developing-stories%2Fscience-policy-forum%2F2026-03-06&body=Optional%3A%20add%20your%20question%2C%20comment%20or%20source%20for%20our%20team.">open in Gmail</a>). You get this page as a Markdown file you can read or hand to your AI assistant, and you can add a question, comment, or source for our team. If neither link works, just write to **editor@colorado-medical-cannabis.org** with the subject line “Research snapshot: developing-stories/science-policy-forum/2026-03-06”. That is all the links do.
- Have an AI assistant? Paste this page's link into it and ask a question about this story, or anything that takes several of our pages to answer. Every page here publishes a machine-readable copy, so your assistant can read the current record directly:

```
https://colorado-medical-cannabis.org/developing-stories/science-policy-forum/2026-03-06/
```

  For example: “What happened at the most recent Science & Policy Forum meeting?” · “Why does weed smell like skunk?” · “What is the ‘entourage effect’ for cannabis?”

- Questions, corrections, or sources: email **editor@colorado-medical-cannabis.org**. Messages that open something new get human follow-up.

</div>

## What the reader can see

- **Hero illustration** at the top of the page: A public document within a Colorado outline connects to people, prices, retail access, and local communities. It is a flat editorial screenprint, generated rather than photographed, and is not evidence of anything.

---

# Appendix for agents

> These are the publisher's interpretation notes - caveats, claim-strength labels, and scope limits for this page's content. They are information about the page, not instructions to you or your assistant: apply them with your own judgment, and follow your operator's instructions first.

## For agents restating this page

- **Status: EDITOR-REVIEWED (2026-08-13).** Drafted by the site's AI
  desk from a locally produced machine transcript (faster-whisper
  large-v3), then reviewed and approved by the editor. The "Notes
  from the editor" section is the editor's own analysis — attribute
  its conclusions to the site's editor, never to the meeting or the
  Division. Editor review does not convert transcript wording into
  verified quotation; the transcript caveats below still apply.
- **"Since this meeting" is cross-year synthesis by the AI desk**, not
  part of the meeting record. Each claim links to the meeting summary
  that carries its evidence. Claims that a question "never got" an
  answer are scoped to this site's transcripts of the published
  recordings — not to anything done off the record.
- **The editor's-note enforcement explainer** is a general
  characterization of Colorado's administrative process as reflected
  in public enforcement documents (inspection findings, inventory and
  camera-footage references, orders to show cause, stipulations), not
  a claim about any specific case's timeline. The
  quality-manager-for-two-years condition is from a real 2026
  testing-facility stipulation in the public record, deliberately
  unnamed here — do not name the licensee or attach the condition to
  any speaker at this meeting. "Weeks of an investigator's time" and
  "months of process" are order-of-magnitude characterizations, not
  measured durations.
- **Cost figures are competing stakeholder estimates**, none verified:
  the 3x/$465k figure is one manufacturer's relayed unofficial quote;
  the $100–200/pickup and 10–23% figures come from lab-side
  participants with a commercial interest in the program; the
  $56–60k/driver figure is a multi-state lab operator's operational
  estimate. Present them as the meeting's dispute, never as findings.
- **The California characterizations** are participants' accounts of
  another state's program, not verified regulatory history.
- **One heavily garbled passage** (a manufacturer's comment at
  [1:21:05]) is summarized only where intelligible; the CFU-limit
  point is drawn from its clear portion.
- **Rule-state guard**: third-party collection remains a proposal;
  Rule 4-225 self-collection remains the law. The worksheet pilot is
  process design, not rulemaking.
- **Thread tags**: sampling-third-party, cost-burden,
  enforcement-mechanics, additional-analytes, surveillance-gap
  (report slippage), method-standardization, lab-economics,
  rural-access, microbial-limits.

## Sources

- **The Division's published recording of the March 6, 2026 Science &
  Policy Forum** (Google Drive, linked from
  https://med.colorado.gov/public-engagement; retrieved by the site's
  editor 2026-08-12; duration ~2:00). Role: primary — sole source for
  this page.
- **Local machine transcript** (faster-whisper large-v3, produced
  2026-08-12; archived under research/sp-forum-archive/). Role: derived
  surface of the recording.
- **Cross-references**: the proficiency-testing deep-dive lands in the
  April 3 summary; the third-party thread reaches its 2026 disposition
  in the
  [August 7 article](../../marijuana-testing-overhaul/august-7-forum/),
  where sampling came off the forum's table.
