Skip to content

Session Expired

Your session has expired. Please sign in again to continue where you left off.

Sign In Again

CO SB189: Automated Decision-Making Technology

Enacted · set to take effect Jan 1, 2027 Colorado · 2026 session

Last verified Oct 2, 2026 · official bill text

SB189 · where it stands

4 of 5 steps complete
  1. Introduced Complete
  2. Passed first chamber Complete
  3. Passed both chambers Complete
  4. Enacted Complete
  5. Effective Jan 1, 2027
What do these statuses mean?
Introduced
Filed in the legislature; may be waiting for a committee hearing.
Passed a chamber
Approved by one or both chambers; awaiting further action.
Enacted
Signed into law, or became law without a signature or over a veto.
Effective date
The date the law says it takes effect. Once it has passed, the page shows "Effective" and the date. A court order can still block a law; if we know of one, the summary says so.
Dead / vetoed
Vetoed, failed, or the session ended without action.

In one paragraph

Colorado's SB 26-189 repeals and reenacts the 2024 AI Act as rules for automated decision-making technology (ADMT) that materially influences consequential decisions such as hiring, lending, housing and health care. Developers must document covered ADMT for deployers; deployers must give notice before use, explain adverse outcomes within 30 days and, on request, give correction steps and, where commercially reasonable, human review. Signed May 14, 2026 (Chapter 131); applies from January 1, 2027. A stipulated April 27, 2026 order in X. AI LLC v. Weiser bars AG enforcement of 2026 laws replacing SB 24-205 for violations through 14 days after a ruling on xAI's planned injunction motion.

Plain-English summary, written with AI assistance. The official text controls.

What it means for business

From January 1, 2027, developers must document ADMT for deployers, and deployers must give notices, adverse-outcome explanations and correction and review options; a stipulated order bars AG enforcement of 2026 laws replacing SB 24-205 for violations through 14 days after an injunction ruling.

Key provisions

  1. Covered ADMT: technology that processes personal data and computes outputs (predictions, scores, rankings, recommendations, classifications) used to make, guide or assist a decision about an individual, when the output is a non-de minimis factor that affects a consequential decision; excludes routine software, summarizing or drafting aids, chatbots barred from consequential decisions, and advertising, search, fraud-prevention, AML and cybersecurity uses (§ 6-1-1701)
  2. Developers: give each deployer the intended and known harmful uses, training-data categories, known limitations and risks, instructions for appropriate use, monitoring and meaningful human review, and information needed for consumer disclosures; notify deployers of material updates and changes within a reasonable time; keep records 3 years; applies to ADMT marketed, configured, contracted or licensed for consequential decisions (§ 6-1-1702)
  3. Deployers: clear and conspicuous notice before using covered ADMT in a consequential decision (a prominent public notice at points of interaction qualifies); after an adverse outcome, within 30 days, a plain-language description of the decision and the ADMT's role, a simple way to request the ADMT's name, version and developer and the personal data types and sources, and an explanation of rights; on request, instructions to correct inaccurate personal data and, to the extent commercially reasonable, meaningful human review and reconsideration; records kept 3 years; notices accessible to consumers with disabilities or limited English (§§ 6-1-1703 to 6-1-1705)
  4. A creditor's required ECOA (and, where applicable, FCRA) notice satisfies the notice duties for the same credit decision if it also meets them, and FERPA processes can satisfy the notice and rights duties for education decisions; insurers subject to § 10-3-1104.9 comply in the practice of insurance; HIPAA covered entities are exempt except for employment decisions but must give patients a general notice and financial-assistance disclosures; FDA-overseen medical devices exempt (§§ 6-1-1704, 6-1-1705, 6-1-1708)
  5. Attorney General enforcement only, under the Colorado Consumer Protection Act (a violation is a deceptive trade practice); notice and a 60-day cure before action if the AG deems a cure possible, except for knowing or repeated violations (cure rule repealed January 1, 2030); no new private right of action (§§ 6-1-1706, 6-1-1709)
  6. Under an April 27, 2026 minute order in X. AI LLC v. Weiser, No. 1:26-cv-01515 (D. Colo.), the Attorney General may not initiate enforcement, including investigations, for violations of SB 24-205 "or any legislation replacing or amending SB24-205 enacted during this legislative session" occurring through 14 days after the court rules on xAI's planned preliminary-injunction motion; the order does not name this act, which passed May 12, 2026 and repeals and reenacts SB 24-205's Part 17. xAI must file that motion within 28 days after final adoption of implementing rules. It is a stipulated stay; the court has not ruled on the merits
  7. Developers and deployers can be liable under state anti-discrimination law, including the Colorado Anti-Discrimination Act, for decisions materially influenced by covered ADMT, with fault allocated by relative fault; developers are liable only for uses they intended, documented, marketed or contracted for; contract clauses indemnifying a party for its own discriminatory acts are void (§ 6-1-1707)
  8. Signed May 14, 2026 (Chapter 131, Session Laws 2026). Under Section 5, the AG rulemaking duties (§§ 6-1-1704(4), 6-1-1705(3); rules to be adopted on or before January 1, 2027), the joinder clause (§ 6-1-1706(6)), the insurance commissioner's notice-rule power (§ 10-3-1104.9(3)(e)) and the $46,190 appropriation took effect on signing; the rest takes effect January 1, 2027 and applies to consequential decisions made on or after that date, so the 2024 act as amended by SB 25B-004 otherwise remains in Part 17 until then

Who must comply, and what it requires

Read from the official text by AI Laws by State and last checked Nov 11, 2026. Each entry links to the section it comes from. Information, not legal advice.

Who it covers

  • Developer. A person doing business in Colorado that develops, sells, licenses or otherwise makes commercially available a covered ADMT, develops a component designed for one, or intentionally and substantially modifies an ADMT into one. Research-only and internal-only developers are excluded. No size threshold in the text. C.R.S. 6-1-1701(8)
  • Deployer. A person doing business in Colorado that deploys a covered ADMT, meaning automated decision-making technology used to materially influence a consequential decision. No size threshold in the text. C.R.S. 6-1-1701(7), (5)
  • HIPAA covered entity. A HIPAA covered entity doing business in Colorado. It is exempt from most of the part but owes patients a general notice, and specific disclosures when a covered ADMT decides financial assistance eligibility. No size threshold in the text. C.R.S. 6-1-1708(3)(c), (d)

What it requires

  • Developer. Give each deployer documentation: intended and known harmful uses, categories of training data, known limitations, instructions for use, monitoring and human review, and information the deployer needs for its disclosures. A covered ADMT marketed, configured, contracted, sold or licensed to materially influence a consequential decision. The deployer must be told if information is withheld. C.R.S. 6-1-1702(1), (3), (5) Jan 1, 2027
  • Developer. Notify each deployer within a reasonable time of material updates, intentional and substantial modifications, and changes to intended use, limitations or risk mitigation. After such a change. Public release notes suffice if each deployer gets direct notice of the release. C.R.S. 6-1-1702(2) When triggered
  • Developer. Keep records needed to show compliance, including version identifiers, changelogs and update notices, for at least three years after each record is created. Records required or created under the developer section; longer if other law requires. C.R.S. 6-1-1702(4) Jan 1, 2027
  • Deployer. Before using a covered ADMT in a consequential decision, give the consumer clear and conspicuous notice of that use and instructions for getting more information. Any consequential decision materially influenced by a covered ADMT. A prominent public notice reasonably accessible at the point of interaction satisfies this. C.R.S. 6-1-1704(1), (2) Jan 1, 2027
  • Deployer. Within 30 days of an adverse decision, give a plain-language description of the decision and the ADMT's role, a process to request more information, and an explanation of consumer rights. When a covered ADMT materially influences a consequential decision with an adverse outcome for the consumer. C.R.S. 6-1-1704(3) When triggered
  • Deployer. On request after an adverse outcome, give instructions for requesting and correcting personal data, and an opportunity for meaningful human review and reconsideration to the extent commercially reasonable. When the consumer asks. Opinions, predictions, scores and protected evaluations need not be corrected. C.R.S. 6-1-1705(1) When triggered
  • Deployer. Keep records needed to show compliance for at least three years after the date of each consequential decision. Every consequential decision; longer if other law requires. C.R.S. 6-1-1703 Jan 1, 2027
  • Deployer or developer. Provide required notices and disclosures in a manner reasonably accessible to consumers with disabilities and consumers with limited English proficiency. All notices and disclosures under the part. C.R.S. 6-1-1704(8) Jan 1, 2027
  • HIPAA covered entity. Give patients a general notice of its use of advanced technologies, including covered ADMT; give specific disclosures when a covered ADMT decides eligibility for financial assistance. Financial-assistance disclosures may be given in advance or within 30 calendar days after an adverse outcome. C.R.S. 6-1-1708(3)(c)-(e) Jan 1, 2027
  • Developer or deployer. Contract terms that indemnify a developer or deployer for its own discriminatory use of ADMT are void; do not rely on them. Contracts between developers and deployers for ADMT used in consequential decisions; exception where the use was not intended by a compliant developer. C.R.S. 6-1-1707(7) Jan 1, 2027

Enforcement

Who enforces
Colorado Attorney General, exclusively for the disclosure duties and consumer rights; a violation is a deceptive trade practice under the Colorado Consumer Protection Act.
Time to fix a violation
60 days (repealed January 1, 2030; only where the attorney general deems a cure possible; not required for knowing or repeated violations)
C.R.S. 6-1-1706(3)

Agency rules and guidance

  • Colorado Attorney General. Required by January 1, 2027 for post-adverse-outcome disclosures and consumer rights; optional for the rest. The Attorney General filed proposed rules on August 11, 2026, released an interim draft on October 6 and held the rulemaking hearing on October 26, 2026. No final rules had been adopted as of the Department of Law's page dated October 27, 2026. C.R.S. 6-1-1704(4)(b); 6-1-1705(3); 6-1-1706(5); Colorado Department of Law rulemaking page

Exemptions and limits

  • Not ADMT: listed basic technologies (anti-malware, calculators, databases, spam filtering, spell-checking, non-ML spreadsheets, web hosting and similar), tools used only to summarize or organize information for human review, and consumer-facing chat technology not intended for consequential decisions and barred from that use by an acceptable use policy. C.R.S. 6-1-1701(2)(b)
  • Not consequential decisions: low-stakes or routine processes, advertising and marketing, search, content moderation, cybersecurity, fraud prevention, sanctions and anti-money-laundering controls, and routine academic administration. C.R.S. 6-1-1701(3)(b)
  • Insurers and affiliates subject to C.R.S. 10-3-1104.9 are in compliance for the practice of insurance, but not for their own employment decisions. C.R.S. 6-1-1708(1), (2)
  • HIPAA covered entities and their business associates are outside 6-1-1701 to 6-1-1706, except for employment decisions; for health-care providers this applies only when operating from a Colorado location. C.R.S. 6-1-1708(3)(a), (b)
  • FDA-overseen medical devices and FDA-overseen pharmaceutical or device research and development. C.R.S. 6-1-1708(4)
  • A creditor whose federal Equal Credit Opportunity Act and Fair Credit Reporting Act notice also satisfies this section need not send a separate notice. C.R.S. 6-1-1704(6)
  • A deployer subject to FERPA may use its existing FERPA notice, record access, amendment and appeal processes for education decisions. C.R.S. 6-1-1704(9); 6-1-1705(2)
  • No duty to disclose trade secrets or legally protected information (the consumer must be told information was withheld), or to disclose where federal law prohibits it or it would compromise security or fraud programs. C.R.S. 6-1-1704(5), (7)

Dates in the text

What the text leaves open (4)
  • The text sets no employee-count or revenue threshold; unlike the 2024 act it has no small-deployer exemption.
  • The act does not carry over the 2024 act's risk-management program, impact assessments, public statements or AI-interaction disclosure; those duties end when this reenactment takes effect.
  • How the 30-day disclosure interacts with sector notices is left to attorney general rules.
  • The penalty amounts were read from the 2024 edition of the Colorado Revised Statutes on the General Assembly's site, the newest edition posted there; any 2025 or 2026 amendment to C.R.S. 6-1-112 was not checked.

Citation: SB 26-189 (2026 Regular Session; Session Laws 2026, ch. 131), approved May 14, 2026; repeals and reenacts C.R.S. 6-1-1701 to 6-1-1709 (part 17 of article 1 of title 6) and adds 6-1-105(1)(uuuu). Official text. Spot an error? Tell us.

See every mapped duty in Colorado in one compliance plan, or build a plan across states.

Latest legislative action

May 14, 2026. Governor Signed

Sponsors (showing 5 of 45)

NameRoleDistrict
D Sponsor SD-021
D Sponsor HD-018
D Sponsor HD-053
R Sponsor HD-014
R Sponsor SD-023

Roll call votes (showing 3 of 12)

S Senate: House Amendments Concur May 12, 2026

34 yea1 nayPassed

S Senate: House Amendments Repass May 12, 2026

34 yea1 nayPassed

H House: Third Reading Bill May 9, 2026

57 yea6 nay2 otherPassed

Amendments (6)

  • Senate Business, Labor, & Technology Amendment L.001 Adopted 2026-05-05
  • Senate Business, Labor, & Technology Amendment L.002 Adopted 2026-05-05
  • Senate Appropriations Amendment J.001 Adopted 2026-05-06
  • Second Reading Amendment L.003 Adopted 2026-05-06
  • Second Reading Amendment L.004 Adopted 2026-05-06
  • House Judiciary Amendment L.006 Adopted 2026-05-08

Topics and industries

This page is general information, not legal advice. Summaries are AI-assisted and may contain errors; read the statute for the controlling text and talk to a lawyer about your situation. Full disclaimer · Report an error