Guide · Published November 14, 2026 · Reviewed November 14, 2026 · Ingenious AI team · Not legal advice
Colorado's Pending AG Rules on Post-Decision Disclosures: What Is Settled and What May Change
The short answer: One element of Colorado's SB 26-189 package is expressly unfinished, and the kit's data says so in two places: the Attorney General must adopt rules clarifying the post-decision disclosures by January 1, 2027, so the exact format of the explanation may still change. What is settled: the duties themselves and their dates — pre-use notice, the 30-day plain-language explanation of the tool's role, correction, human review, 3-year records, all from January 1, 2027. What is pending: the clarified format of the post-decision disclosure. The correct posture is to build the full workflow now, on a document structure designed to adjust — reasons, data summary, and next steps as separable blocks — and to diary the rules as a change trigger.
Check your duties and dates — free Build your first notice — free
What are the pending rules? They are the Attorney General rulemaking that SB 26-189 itself schedules: rules clarifying the post-decision disclosures, due by the same date the duties take effect. The kit's rules data records the position as it stood when the kit was built — rules due January 1, 2027 and still pending; duty wording follows the statute summary; formats may change when the rules publish. This guide adds no speculation about what the rules will say.
What is settled, stated as a build list
Build these without waiting: the pre-use notice at the point of interaction; the explanation workflow that produces a plain-language statement of the principal reasons and the tool's role within 30 days; the correction path with named contacts; meaningful human review with real authority; and the 3-year record capturing all of it per decision. None of these is described as pending in the kit's data — each is a duty in the statute summary, effective January 1, 2027.
Also settled, and worth building around: the explanation's content core as the checker states it — a plain-language description of the tool's role in the decision. Format clarification operates on presentation and particulars; it does not unsettle the content core or the clock. A business that builds the core and the clock has built the load-bearing structure whatever the rules add.
What may change, and what 'may' honestly covers
The pending item is the exact format of the explanation (the post-decision disclosure). Honest uncertainty covers a range: prescribed fields or ordering, wording requirements, delivery particulars. This guide does not rank those possibilities, because the kit's data does not — inventing a forecast would violate the discipline the whole series runs on. What can be said structurally: format changes are absorbed by systems whose documents are generated from blocks, and they punish systems whose documents are frozen artefacts.
That asymmetry is the actionable content of the uncertainty. It argues for generated documents (the kit's model: builder functions composing profile, case facts, reasons, and data summary into the notice and explanation) over exported PDFs and printed stock, and for keeping reasons and data summaries as structured case data rather than as prose baked into letters — structured inputs can be re-rendered into a clarified format; baked prose must be rewritten case by case, including, potentially, for the record.
Worked example: Mile High Property Management
Example — fictional business, real duty structure. Mile High, the fictional Colorado property manager from the clock and plain-language guides, built its explanation workflow under the pending-rules caveat. Its design choices:
- Blocks, not letters: the explanation is composed from 4 blocks (what happened, reasons, data summary, next steps); a simulated format change in testing — reordering blocks and adding a field — is absorbed in one template revision, with zero workflow changes.
- Structured inputs: reasons and data summaries are captured as case data at decision time, so any clarified format can re-render from the same facts; the quarter's 39 explanations all trace to structured inputs.
- Versioning live: the template carries a version identifier recorded per explanation; the record can already answer 'which format did March use?' — currently version 1, with the transition procedure written before it is needed.
- Trigger owned: the AG-rules watch sits on the compliance calendar with a named owner and a publication diff procedure; the pending status is filed in the risk register in the kit's own wording.
- No waiting: the full workflow — clock, queue, capture — runs from January 1, 2027 readiness onward; the caveat changed the document architecture, not the programme's dates.
The build-now design: separable blocks, versioned templates
Concretely: hold the explanation as blocks — what happened (with the tool's role), principal reasons, data summary, next steps with contacts — each independently editable at the template level; version the template so the record can show which format each explanation used; and keep the workflow's clocks, queues, and capture points independent of the template, so a format change touches one layer. The kit's builder already composes documents this way, which is precisely why its data notes the pending rules without treating them as a blocker.
Template versioning deserves its sentence: when the rules publish and the format adjusts, explanations sent before the change keep the version they were sent under, and the record shows the transition date. A programme that can display its own format history answers the only hard question a format change creates — 'which of our explanations used which format?' — from the file, in minutes.
The diary discipline: a named trigger, an owner, a watch
Put the rulemaking on the compliance calendar as a dated trigger with an owner: the AG rules are due by January 1, 2027; the owner's job, on publication, is a diff — rules versus current template — a template revision through the change process (including the plain-language tests), and a version note in the register. Until publication, the watch is periodic and cheap: the duty is to notice, not to predict.
File the pending status itself in the programme's risk register, in the kit's words — formats may change when the rules publish — so the uncertainty is a managed item with a trigger rather than institutional knowledge held by whoever read the checker notes most carefully. The deadline tracker carries the AG-rules date alongside the duty dates for the same reason: it is a date on which something you depend on may change.
What not to do with a pending rule
Three postures fail. Waiting: deferring the explanation workflow until the format settles forfeits the certain duties (the clock, the capture of reasons) to an uncertainty about presentation — and January's decisions will not wait with you. Over-building to a guessed format: implementing a speculated specification wastes the same effort in the opposite direction and can bake the guess into stock that must be discarded. Silent non-adjustment: publishing-day comes and goes without a diff, and the programme runs a stale format on autopilot — the failure the diary discipline exists to prevent.
The kit's own posture is the model: its data states the pending status openly, its documents are generated from blocks, and its guides repeat the caveat wherever Colorado explanations are described. Adopt the same posture and the rulemaking becomes a template event in a running system — which is all, on the evidence available, that it can responsibly be planned as.
- Build the settled duties now — notice, 30-day explanation workflow, correction, review, 3-year record — without waiting for the format rules
- Compose explanations from separable blocks (what happened, reasons, data summary, next steps) generated from structured case data
- Version the explanation template and record the version per explanation, so format history is answerable from the file
- Diary the AG rules as an owned trigger: on publication, diff against the template, revise through the change process, note the version transition
- File the pending status in the risk register in plain words — formats may change when the rules publish — and refuse both waiting and guessing
Sources, as carried in the kit's own data: the duty summaries in app/rules.py and the checker data in app/checker_data.py, verified against primary or authoritative sources on October 28, 2026. Run the free duties checker for your jurisdiction, decision type, and the tool's role, and compare the kit's plans for the record, builder, and review queue. More from Ingenious AI is on the hub.
Related guides
- Colorado AI Act Automated Decision Notices: What to Send
- Adverse-Outcome Explanations in Plain Language
- ADMT Deadline Tracker: Which State Duties Land When
- California CCPA ADMT Requirements: What Your Business Must Do by January 1, 2027
See all ADMT guides for the full set.
Frequently asked questions
What exactly is pending in Colorado?
The Attorney General must adopt rules clarifying the post-decision disclosures by January 1, 2027, so the exact format of the adverse-outcome explanation may still change, per the kit's data.
Should we wait for the rules before building the explanation workflow?
No. The duties and the 30-day clock are settled and effective January 1, 2027; only the explanation's exact format may be clarified. Build the workflow now, on a block-structured, generated document that can absorb a format change.
What content is settled for the explanation?
A plain-language description of the tool's role in the decision (the checker's statement), with the principal reasons in the kit's rules data — plus the correction and review paths. Format clarification operates on presentation and particulars.
How do we prepare for a format change concretely?
Generate documents from separable blocks and structured case data, version the template, record the version per explanation, and diary the rulemaking with a named owner and a publication-diff procedure.
Where does the kit state the pending status?
In its Colorado data in two places: the rules data (AG rules due January 1, 2027, still pending when the kit was built) and the checker notes (the AG must adopt rules clarifying the post-decision disclosures by January 1, 2027, so the exact format may still change).