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

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, 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: declined without consensus, pivoting to first-party reforms in July, 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 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 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.

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 is the source of record.