CertifiedData.io

Colorado · ADMT in consequential decisions · effective January 1, 2027

Colorado SB 26-189: ADMT obligations and evidence crosswalk

Colorado SB 26-189 (C.R.S. 6-1-1701 to 6-1-1709) regulates covered automated decision-making technology (ADMT) that materially influences consequential decisions about consumers in education, employment, housing, financial or lending services, insurance, health care, and essential government services. It applies to consequential decisions made on or after January 1, 2027, and places documentation duties on developers and notice, record-keeping, correction, and human-review duties on deployers. The Attorney General enforces it; it creates no new private right of action.

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.

Key dates

  • May 14, 2026SB 26-189 approved (S.L. 2026, ch. 131); repeals and reenacts C.R.S. title 6, article 1, part 17.
  • August 11, 2026Department of Law filed proposed rules (4 CCR 904-6) with the Secretary of State, eDocket tracking no. 2026-00360.
  • October 6, 2026AG interim draft of the proposed rules released (proposed; subject to change).
  • October 21, 2026AG Regulatory Analysis published.
  • October 26, 2026Formal public rulemaking hearing; written comments considered if received by 11:59 PM MST that day.
  • January 1, 2027Act takes effect and applies to consequential decisions made on or after this date. Statute directs the AG to adopt rules on post-adverse-outcome disclosures and consumer rights on or before this date; the draft proposes the same effective date.

Details and current status: AG rulemaking timeline.

Obligations overview

Developers (C.R.S. 6-1-1702)

Make documentation available to each deployer of a covered ADMT (intended and known harmful uses, training data categories, limitations, instructions for use, monitoring and meaningful human review, and information the deployer needs for its 6-1-1704 notices), give notice of material updates, and retain related records for not less than three years.

Deployers (C.R.S. 6-1-1703 to 6-1-1705)

Retain records for not less than three years after each consequential decision; give a clear and conspicuous notice before using a covered ADMT to materially influence a consequential decision (a prominent public notice at points of interaction can satisfy this); after an adverse outcome, send the disclosure within thirty days; notify the consumer when information is withheld as a trade secret; and, on request after an adverse outcome, provide correction instructions and an opportunity for meaningful human review and reconsideration to the extent commercially reasonable.

What SB 26-189 does not require

The enacted text contains no impact-assessment or risk-management-program duty. Those were in SB 24-205, which SB 26-189 repealed and reenacted. Read the article.

Obligation-to-evidence crosswalk

Each row is labeled supports evidence for: CertifiedData helps you produce records; it does not perform or certify the obligation. AG rule references are proposed (interim draft, October 6, 2026).

ObligationCiteCertifiedData featureSupports evidence for…
Developer documentation to each deployer: intended and known harmful uses, training data categories, known limitations, instructions for use/monitoring/human review, information needed for 6-1-1704 (and notice if withheld)C.R.S. 6-1-1702(1)Certificates and audit bundle export can hold version-pinned documentation artifacts with a verifiable fingerprint and signature; public verifier lets a deployer check them.Supports evidence for what documentation existed, in which version, and when. The content of the documentation is the developer's.
Developer notice of material updates, intentional and substantial modifications, and changes to intended use/limitations/risk mitigation; 3-year retention of version identifiers, changelogs, and noticesC.R.S. 6-1-1702(2), (4)Decision Ledger records carry model/version identifiers; ledger and certificates give timestamped, tamper-evident changelog and notice records; Colorado evidence pack records ADMT version and developer.Helps you produce records for version history and notices. Deciding what is a material update is the developer's.
Deployer record keeping: at least 3 years after the date of each consequential decision (longer if other law requires); may include ADMT version identifiers, changelogs, mitigation changesC.R.S. 6-1-1703Decision Ledger (signed, hash-chained records); Colorado ADMT evidence pack computes retain-until = decision date + 3 years and includes hash-chain/signature verification material; audit bundle export.Supports evidence for integrity and completeness of records. Retention settings and storage remain the deployer's responsibility to confirm.
Pre-use notice that a covered ADMT is or will be used in a consequential decision, with instructions for obtaining more information; may be met by a prominent public notice at points of interactionC.R.S. 6-1-1704(1), (2)Evidence pack records the notice URL, version, and time shown; ledger signing makes the reference tamper-evident.Supports evidence for which notice was shown and when. Notice wording and placement are the deployer's.
Post-adverse-outcome disclosure within 30 days: plain-language description of the decision and ADMT role; how to request information (ADMT name, version, developer, types/categories/sources of personal data); explanation of 6-1-1705 rightsC.R.S. 6-1-1704(3); proposed AG Rule 7 (interim draft, Oct 6, 2026)Evidence pack records disclosure send time and checks it against decision time + 30 days; records data categories/sources and the ADMT role.Helps you produce records for what was sent and when. It does not judge whether the content was adequate or whether an outcome was adverse.
Creditor path: an ECOA/Regulation B (and, when applicable, FCRA) notice that also satisfies this section can satisfy the related notice requirementsC.R.S. 6-1-1704(6)Evidence pack disclosure records can be marked with the creditor_ecoa_fcra path and a notice reference.Supports evidence for which notice the creditor relied on. Whether it satisfies both regimes is a legal question for counsel.
Trade-secret withholding: no duty to disclose trade secrets or legally protected information, but the consumer must be notified when information is withheldC.R.S. 6-1-1704(5); developers: 6-1-1702(1)(e)Evidence pack records a withheld flag and the notice time, and surfaces withheld-without-notice-recorded cases.Supports evidence that a withholding notice was recorded. It does not determine what qualifies as a trade secret.
Consumer rights after an adverse outcome: instructions to request personal data and correct factually incorrect or materially inaccurate data; opportunity for meaningful human review and reconsideration to the extent commercially reasonableC.R.S. 6-1-1705(1); 6-1-1701(15); proposed AG Rule 8 (interim draft, Oct 6, 2026)Decision Ledger follow-up records capture each correction/human-review request, reviewer, outcome, and timestamps; ledger records human_override on the decision.Helps you produce records for requests and reviews. Whether a review met the 'meaningful human review' definition is a deployer/legal judgment.
Impact assessments and risk-management programsNot required by SB 26-189Optional voluntary governance: ledger and certificates can document your own assessments and monitoring; see the NIST AI RMF mapping.These duties were in SB 24-205, which SB 26-189 repealed and reenacted; they do not appear in the enacted text. CertifiedData does not present them as required here.
Attorney General enforcement: exclusive AG enforcement through the Colorado Consumer Protection Act; notice of violation and 60-day cure where the AG deems cure possible; no private right of action createdC.R.S. 6-1-1706(1)-(4), 6-1-1709Context only: records above are the kind of material a deployer may want available if asked.Context. No tool changes enforcement exposure; this is not a prediction of how the AG will act.

Features referenced: the Decision Ledger, audit bundle export, signed certificates, the public verifier, and the Colorado ADMT evidence pack.

Frequently asked questions

When does Colorado SB 26-189 take effect?

January 1, 2027. Section 5 of the act applies it to consequential decisions made on or after that date. A few provisions, including the AG rulemaking directions in 6-1-1704(4) and 6-1-1705(3), took effect upon passage.

Does SB 26-189 require impact assessments or a risk management program?

No. The enacted text of SB 26-189 contains no impact-assessment or risk-management-program duty. Those were part of SB 24-205, the 2024 act that SB 26-189 repealed and reenacted. Voluntary governance may still be sensible; see the dedicated article.

How long must records be kept?

Deployers must retain records reasonably necessary to demonstrate compliance for not less than three years after the date of the consequential decision, or longer if other law requires (C.R.S. 6-1-1703). Developers have a parallel three-year duty measured from creation of the record (6-1-1702(4)).

What must a deployer send after an adverse outcome?

Within thirty days after making the decision: a plain-language description of the decision and the ADMT's role, instructions for requesting more information (including the ADMT name, version, developer, and types, categories, and sources of personal data, to the extent the deployer receives it from the developer), and an explanation of the 6-1-1705 consumer rights (C.R.S. 6-1-1704(3)).

Are the Attorney General's rules final?

Not as of November 13, 2026. The AG released an interim draft of proposed rules on October 6, 2026 and held a public hearing on October 26, 2026. No adopted final rule was shown on the AG's rulemaking page as of November 13, 2026, so rule content is proposed and subject to change.

Does CertifiedData make my organization compliant?

No. CertifiedData helps you produce signed, tamper-evident records that support evidence for record keeping and disclosures. It does not determine whether you are a developer or deployer, whether a decision is consequential, or whether a notice was adequate.

Start producing the records

The Colorado ADMT evidence pack packages the fields the statute makes relevant, with the signature and hash material a third party needs to verify integrity. It supports evidence for record keeping and disclosures; it does not decide coverage or compliance.

Colorado SB 26-189 (ADMT Act): obligations & evidence crosswalk | CertifiedData