CertifiedData.io

Colorado SB 26-189 · ADMT in consequential decisions

Impact assessments and risk management: are they required by SB 26-189?

No. The enacted text of Colorado SB 26-189 (C.R.S. 6-1-1701 to 6-1-1709) contains no impact-assessment duty and no risk-management-program duty. Those obligations were part of SB 24-205, the 2024 Colorado AI Act, which SB 26-189 repealed and reenacted as part 17 of article 1 of title 6. Other law, including the Colorado Anti-Discrimination Act, still applies.

Last reviewed: November 13, 2026 · Published

Not legal advice. This page is general information about Colorado SB 26-189 for engineering, product, and governance teams. It is not legal advice and does not create an attorney-client relationship. CertifiedData supports evidence for record keeping and disclosures; it does not determine whether a system is covered by the law and does not make any organization compliant. Confirm your obligations with qualified Colorado counsel.

Attorney General rule text referenced on this page is a proposed interim draft (released October 6, 2026) for 4 CCR 904-6 and is subject to change. As of November 13, 2026 no adopted final rule was shown on the Attorney General's rulemaking page.

What the enacted text does and does not contain

Section 1 of SB 26-189 repeals and reenacts part 17 of article 1 of title 6, which SB 24-205 had created. We reviewed the enacted session law (S.L. 2026, ch. 131) and the reenacted sections impose these duties: developer documentation and update notices (6-1-1702), record keeping (6-1-1703), consumer notices and post-adverse-outcome disclosures (6-1-1704), and correction and human-review rights (6-1-1705). None of them requires a deployer or developer to conduct an impact assessment or to maintain a risk-management program.

The duties that were in SB 24-205 are not in the enacted SB 26-189 text. We do not summarize SB 24-205's provisions here. For that history, read the bill page at https://leg.colorado.gov/bills/sb24-205.

If a vendor questionnaire, contract template, or internal policy still cites impact assessments or risk-management programs as Colorado requirements, check it against the enacted SB 26-189 text and with counsel.

Where the enacted law touches limitations and monitoring

Without a standalone assessment duty, the statute still pushes some of the same information along the supply chain. Under 6-1-1702(1)(c), developers must make available the known limitations of the covered ADMT, including known risks and circumstances in which it should not be used. Under 6-1-1702(1)(d), they must provide instructions for the deployer's appropriate use, monitoring, and meaningful human review, where applicable. Section 6-1-1702(2) requires notice of material updates and changes to intended use, limitations, or risk mitigation.

Meaningful human review is defined in 6-1-1701(15): review by an individual designated by the deployer with authority to approve, modify, or override the decision, who considers relevant primary evidence, is trained to conduct the review, does not default to the system output, and has enough information to understand the output's intended use, material limitations, categories of inputs, and the principal factors used to generate the output, without requiring disclosure of proprietary source code, model weights, or other trade secrets. A deployer that offers human review under 6-1-1705(1)(a)(II) therefore needs the developer information described above to make it real.

Other law still applies

  • Section 6-1-1706(4): nothing in part 17 limits or reduces existing rights or remedies under state or federal law, including the Colorado Anti-Discrimination Act (parts 3 to 8 of article 34 of title 24), the Colorado Consumer Protection Act, and product liability law.
  • Section 6-1-1707: a developer or deployer may be held liable under state anti-discrimination law for a consequential decision materially influenced by a covered ADMT, and use of an ADMT does not excuse or provide a defense to obligations under state or federal law (6-1-1707(9)).
  • Sections 6-1-1707(8) and 6-1-1709(2): compliance with part 17 is not a defense to, and does not excuse noncompliance with, any applicable law.
  • Insurers: insurers subject to C.R.S. 10-3-1104.9 are deemed in compliance with part 17 in the practice of insurance (6-1-1708(1)(a)), and the Commissioner of Insurance may adopt or update rules on notices and disclosures from insurers to consumers (10-3-1104.9(3)(e)). Insurers have separate Division of Insurance rules under that section.

In practice, this means that even without a statutory assessment requirement, a team whose ADMT materially influences hiring, lending, housing, or similar decisions has its own reasons to document how the system is used and tested.

What still makes sense to do voluntarily

These are practices, not statutory requirements of SB 26-189:

  • Document the intended use of each ADMT and each decision it influences, so you can answer coverage questions and write accurate disclosures.
  • Record known limitations and the circumstances in which the system should not be used, using the developer documentation under 6-1-1702(1)(c).
  • Monitor outputs and material updates, and log version changes, because the 6-1-1704(3)(b) disclosure can include the ADMT version number and 6-1-1703 contemplates version identifiers and changelogs in records.
  • Define who performs human review, what they can see, and their authority to override, aligned with 6-1-1701(15).
  • Align the program to a recognized framework. See the NIST AI RMF mapping at /compliance/nist-ai-rmf. Using NIST AI RMF is voluntary; the enacted text of SB 26-189 does not mention it or provide a safe harbor for following it.
  • Review contracts for the void-indemnity rule in 6-1-1707(7)(a).

How CertifiedData supports evidence

CertifiedData helps you produce records for the governance practices above. Decision Ledger records are canonicalized with RFC 8785 JCS, SHA-256 hashed, Ed25519 signed, and hash-chained, so modification is detectable. Audit bundle export packages a certificate, transparency log entry, public key, and verification instructions in a ZIP, and records can be checked at /verify.

The Colorado ADMT evidence pack (/compliance/colorado-sb-26-189/evidence-pack) packages ADMT name, version, and developer, covered domain, data categories, and human-review requests that you supply, with verification material. It does not perform an impact assessment, and it does not decide whether your documentation is sufficient.

Frequently asked questions

Does Colorado SB 26-189 require an impact assessment?

The enacted text contains no impact-assessment requirement. Those duties were in SB 24-205, which SB 26-189 repealed and reenacted.

Does SB 26-189 require a risk management program?

No risk-management-program duty appears in C.R.S. 6-1-1701 to 6-1-1709 as enacted. A voluntary framework such as NIST AI RMF can still be useful, but the enacted text does not mention it or provide a safe harbor for following it.

Does complying with SB 26-189 protect me from discrimination claims?

No. C.R.S. 6-1-1707(8) and 6-1-1709(2) state that compliance with part 17 is not a defense to, and does not excuse noncompliance with, other applicable law, and 6-1-1706(4) preserves existing rights and remedies.

Where can I read about what SB 24-205 required?

Start with the Colorado General Assembly bill page at https://leg.colorado.gov/bills/sb24-205 and confirm specifics with counsel.

Impact Assessments Under Colorado SB 26-189? | CertifiedData