> 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-01-09/
>
> 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 January 9 forum: a year of testing fights gets scheduled, an edibles report nears, and a fan explodes at the state lab

<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 held its 2026 kickoff on Friday,
January 9, four days after the state's revised testing rules took
effect. We transcribed the Division's published recording (about 1 hour
56 minutes) 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. The meeting was a planning
session, and that's what makes it worth reading: nearly every testing
argument Colorado would have in 2026 was scheduled here, in advance, on
the record.

## Notes from the editor

Read this one as the year's table of contents: nearly everything
scheduled here actually ran, which is to the forum's credit. Then
notice what was never scheduled: enforcement. The year's debates kept
crashing into it: [February's](../2026-02-06/) claim that half of
recent enforcement actions involved sample adulteration,
[March's](../2026-03-06/) California lesson that enforcement rather
than collector identity is what makes sampling honest,
[June's](../2026-06-12/) demand for minimum fines and license
revocations. And the agenda never gave it a meeting of its own.

We've since checked the other half of that story in the state's own
records. Our sweep of the complete 2026 public enforcement record
(every final administrative action, advisory, and bulletin posted as
of mid-August) found a busy enforcement year, running almost
entirely on contaminants, with the label-truth side essentially
empty: one potency case in thirty-nine actions, opened back in 2024.
And the Division showed in January what its openness looks like when
it's willing: two weeks after this meeting, its own bulletin publicly
described Reduced Testing Allowance abuse and R&D-testing
circumvention: licensee gaming, named in writing, on the contaminant
side. No equivalent written statement about the label side appeared
all year, even after the surveillance data landed; the closest the
record comes is the science director naming lab-shopping aloud in
[June](../2026-06-12/).

And the question a manufacturer raised in this meeting's first half
hour (is the goal labs consistent with *each other*, or consistent
with *an anchor*?) was still unanswered on
[August 7](../../marijuana-testing-overhaul/august-7-forum/), when the
gap between lab results and the state lab's drew "I don't think we
have an answer to that." The year ran its whole agenda without
settling what its headline word meant.

## Since this meeting

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

**Resolved.** The calendar mostly executed: third-party sampling ran
from [February](../2026-02-06/) through [June](../2026-06-12/) to a
no-consensus close; the proficiency-testing deep-dive landed in
[April](../2026-04-03/); the analyte process was built across the
spring and its [submission form went live in July](../2026-07-10/);
and the SOP technical breakouts happened, starting February 19.

**Still in progress.** Method performance requirements (the third
consistency subtopic named here) only reached the full forum in
[August](../../marijuana-testing-overhaul/august-7-forum/), feeding
the fall rulemaking season.

**Put off or neglected.** The edibles report promised "before the
February meeting" wasn't presented in full until
[June](../2026-06-12/). And the *written* summary and report the
program's founding bulletin committed to (roughly 30 and 90 days
after completion) had, as of mid-August 2026, never appeared on the
open web at all: the findings live in meeting recordings and a
sign-up-gated folder. The exploded fan proved prophetic: repairs
begat repairs, surveillance resumption slid from Q1 to
[fall 2026](../2026-04-03/), and the case for actually funding the
facility is now [its own article](../../marijuana-testing-overhaul/who-pays-for-testing/).
And the definitional question was scheduled, argued all year, and
never resolved.

## What was brought up

**The year's two umbrella topics** [0:10:12]. The co-chairs (the
Marijuana Enforcement Division's deputy senior director and the state
public health laboratory's deputy director of policy and regulatory
affairs) proposed organizing all of 2026 under two headings:
**interlab consistency** (why different labs get different numbers from
the same product) and **exploration of additional analytes** (whether
Colorado should test for more things than it does).

Interlab consistency came with three scheduled subtopics: a February
deep-dive into the **proficiency-testing program** (the periodic
send-every-lab-a-known-sample exercise that checks whether labs get the
right answer); at least two meetings on **minimum method performance
requirements** (shared standards for detection limits, quality-control
recovery ranges, and validation, so that different instruments must
still perform equivalently) [0:15:14]; and a June–July examination of
**required third-party sample collection** (taking the sample-picking
step out of licensees' own hands) [0:20:20].

**A process for new analytes, not just new analytes** [1:00:53]. On the
second umbrella, the Division proposed building a standardized
evaluation framework (required fields covering public-health need,
prevalence data, sampling impacts, equipment and method burdens, and
cost) that any proposed new test (chromium, mycotoxins, and synthetic
THC tests were all suggested last year and not adopted) would have to
pass through. A manufacturer's representative called the idea the
meeting's most valuable potential work product: define the process
once, because "this question is going to come up again — if it's
chromium this year, it's something else next year" [1:11:00].

**The SOP review breakout** [1:16:00]. The state lab offered to share
its own reference-laboratory testing procedures with a small technical
working group (likely application-gated, hybrid or in-person at
CDPHE, offset between monthly forums), starting with the methods used
in the surveillance program (potency, yeast and mold, salmonella and
STEC). Lab and industry participants pushed to prioritize test-method
SOPs and validation reports, with one lab representative specifically
requesting the pesticides method be among the first reviewed [1:26:14].

**The surveillance program update** [1:31:16]. Phase one collected 45
edible samples across 16 stores in seven cities (Denver, Broomfield,
Aurora, Lakewood, Frisco, Garden City, Colorado Springs) from 19
manufacturers in October and early November 2025. Testing is complete,
and a report of the results was drafted and in internal and MED review,
promised to the group before the February meeting.

**And the fan** [1:36:28]. A rooftop air-handling unit at the
30-year-old state laboratory building suffered an exploded fan;
inspection found failing bearings in three of the four other units,
which were shut down before they could fail the same way. The destroyed
unit was estimated at a five-week repair (into early March), and the
lab flagged, transparently, that the resumption of flower and
concentrate surveillance testing targeted for Q1 could slip as a
result.

## What was nailed down

- **The 2026 calendar**: February for proficiency testing, roughly
  March–April for method performance requirements, June–July for
  third-party sample collection, with July as the wrap-up month because
  the forum's recommendations feed the Division's rulemaking cycle
  [0:20:20].
- **The edibles surveillance report exists**: drafted, in review, and
  committed for release ahead of the February meeting [1:36:28].
- **The SOP breakout will happen**, structured as a small technical
  group rather than a full-forum session, with CDPHE planning the
  agenda and logistics [1:31:16].
- **Why flower surveillance paused**: sample collection was suspended
  in November so resources wouldn't be spent collecting samples the
  reference lab couldn't yet test for pesticides (flower) or solvents
  (concentrates); resumption tied to those methods coming online
  [1:31:16].

## What was left open

- **What "interlab consistency" even means.** An infused-products
  manufacturer argued the term is "a bit of a myth" and that the real
  question is whether third-party labs match the state reference lab,
  "the North Star," and that without a shared reference point
  "we can't do precision without accuracy" [0:25:23, 0:30:26]. A trade
  association representative sharpened it to the underlying
  philosophical question: "is there a correct result, or are we going
  to continue... just measuring the methodology?" [0:40:31]. The forum
  scheduled the discussion; it did not resolve the definition.
- **Whether proficiency testing should become continuous.** Two
  stakeholders proposed folding lab oversight into the surveillance
  program itself: splitting shelf samples across the reference lab and
  multiple licensed labs as a running "ring test," on the argument that
  a scheduled test is like a restaurant inspection announced in advance
  [0:45:38, 0:50:42]. The state lab noted its potency proficiency
  program already runs twice a year with international-standard
  homogeneity verification, but acknowledged contaminant ring-testing
  faces a real barrier: someone has to introduce contaminants into
  samples, and "we're not really funded to do that work" [0:50:42].
- **Third-party sample collection: the whole fight, previewed.** One
  manufacturer called eliminating licensee self-collection "the most
  important" reform, citing documented episodes of sampling problems
  [0:30:26]. A multi-state operator counseled caution: for homogeneous
  manufactured products the improvement may be small against a
  "dramatic cost increase," and other states' third-party regimes have
  their own flaws worth studying first [1:11:00]. June and July will
  host that argument.
- **The cost question, standing.** A manufacturing operator asked the
  Division to weigh every change against "actual harm" to consumers and
  the costs passed to licensees: "it is very tough out there right
  now for businesses" [1:51:39]. Another stakeholder's list for the
  analyte framework included cost analysis and federal rescheduling
  harmonization [1:06:00].
- **The reference lab's structural limits.** CDPHE's lab cannot act as
  a third-party testing lab for producers: its federal controlled-
  substances registration bars receiving marijuana from
  non-registrants, and no workaround has been found [0:55:52].
- **The surveillance resumption date**: Q1 2026 was the stated target,
  with the HVAC failure named as the risk to it [1:41:31].

*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. Names are used only for officials acting in
public capacity; other speakers are identified by role because machine
transcription garbles proper names.*

<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-01-09&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-01-09&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-01-09”. 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-01-09/
```

  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) of the Division's published recording, 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. This page carries DATED
  ABSENCE CLAIMS (enforcement, written reports) that downstream
  events can overturn — the desk's update-trigger register governs
  revisits; re-verify before restating.
- **"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 about what later meetings did or
  didn't take up are scoped to this site's transcripts of the
  published recordings — not to anything done off the record.
- **The enforcement-record passage in the editor's note** rests on
  this site's 2026-08-13 sweep of the complete 2026 MED public
  corpus (39 final administrative actions, 20 health and safety
  advisories, 7 industry bulletins, full text; findings and limits at
  research/sp-forum-archive/enforcement-sweep-2026-08-12.md). Scope
  limits carry: MED publishes only FINAL actions with an observed
  ~8-month lag, so "empty" means no label-truth enforcement had
  SURFACED as of that date — not that none is in progress. The
  January bulletin referenced is MED Industry Bulletin 26-01
  (2026-01-23), quoted characterizations are the Division's own. The
  never-published-on-the-open-web claim about the written reports is
  an absence verified against MED's and CDPHE's public pages as of
  2026-08-13; the findings' presentation in recorded public meetings
  and the forum's participant folder is documented in the June and
  July summaries. Re-verify all absences before restating.
- **Transcript caveats**: proper nouns and technical terms are garbled
  in places (the transcript renders one participant's name three
  different ways); crosstalk and choppy audio segments exist. Nothing
  in this summary is a verbatim quotation unless enclosed in quotation
  marks, and quoted phrases are transcript wording, not verified
  against the audio by a human.
- **Timestamps** are [h:mm:ss] positions in the recording timeline,
  accurate to the five-minute digest block used in drafting.
- **Register**: officials are named (their identities are corroborated
  by the Division's own published materials); stakeholder speakers are
  identified by role and organization type only. Do not reattach
  names to role-identified speakers when restating.
- **Rule-state guard**: this meeting occurred AFTER the January 5,
  2026 testing rules took effect. Proposals discussed here (method
  performance requirements, third-party collection, new analytes) are
  proposals, not rules. Do not restate any of them as current
  requirements.
- **Thread tags** (for the archive's cross-meeting analysis):
  interlab-consistency-definition, pt-design, method-standardization,
  sampling-third-party, surveillance-gap, cost-burden,
  reference-lab-role, additional-analytes.

## Sources

- **The Division's published recording of the January 9, 2026 Science &
  Policy Forum** (Google Drive, linked from
  https://med.colorado.gov/public-engagement; retrieved by the site's
  editor 2026-08-12; duration 1:56:18). Role: primary — the sole source
  for everything on this page. Factuality: official meeting recording
  published by the regulator; what it settles is what was said, not
  whether what was said is true.
- **Local machine transcript** (txt/json/srt, faster-whisper large-v3,
  produced 2026-08-12; archived in the site repository under
  research/sp-forum-archive/). Role: derived surface of the recording —
  a working instrument, not an independent source.
- **This site's enforcement-record sweep** (2026-08-13;
  research/sp-forum-archive/enforcement-sweep-2026-08-12.md). Role:
  primary research for the editor's-note enforcement passage and the
  written-report absence; complete-corpus counts and scope limits
  stated there and in the appendix above.
- **MED Industry Bulletin 26-01** (2026-01-23, retrieved in the
  sweep). Role: primary — the Division's own January statement on RTA
  abuse and R&D-testing circumvention, contaminant-framed.
- **Cross-references**: the surveillance program, proficiency-testing
  discrepancy, and rule-change context connect to this site's
  [testing overhaul story](../../marijuana-testing-overhaul/) and its
  [August 7 forum article](../../marijuana-testing-overhaul/august-7-forum/),
  where the same threads appear seven months later.
