Colorado AI Act Replacement: What Companies Must Document
A plain guide to what the Colorado AI Act replacement, SB 26-189, requires companies to document for each AI tool that affects people.
Colorado replaced its 2024 AI Act with the Automated Decision-Making Technology Act (ADMTA). Senate Bill 26-189, signed May 14, 2026, takes effect January 1, 2027, according to the Orrick US AI Law Tracker. It covers automated tools whose output materially influences consequential decisions about people, such as hiring decisions.
An advisory deck cannot show how a hiring score affected one applicant. Your decision records must do that. Start with an inventory of the tools your company actually uses, then have counsel confirm which duties apply. The legal summary here reflects sources retrieved November 12, 2026; verify the enacted text before acting.
Does the Colorado AI Act apply to your company?
Start with how the tool affects a person. Orrick's tracker describes covered automated decision-making technology as technology that processes personal data and generates output used to inform a decision about an individual. That output must materially influence a consequential decision.
The statute's categories include employment, residential real estate, lending and health-care services, among others. A product's “AI-powered” label does not settle coverage. Give counsel the actual workflow and the decision it affects.
Where materiality decides it
A score a recruiter relies on before rejecting an applicant warrants review. A filter whose output nobody uses presents a different question. Trace what happens after the output appears: who sees it, what action follows, and whether it changes the outcome.
Do not assume a human's presence removes the tool from scope. Have counsel assess materiality and record the reasoning, including any conclusion that a tool falls outside the law.
Other Colorado duties to check
The Colorado Privacy Act, effective July 1, 2023, separately provides an opt-out right for certain solely automated decisions with legal or similarly significant effects. It also requires data protection assessments for certain processing activities.
Orrick's tracker also identifies HB 1263, effective January 1, 2027, as covering conversational AI services. Check these obligations separately rather than treating ADMTA compliance as compliance with every Colorado AI rule.
Which Colorado AI law are you actually reading?
A page describing SB 24-205 or its “high-risk AI system” framework may describe the replaced law. Governor Jared Polis signed its replacement, SB 26-189, on May 14, 2026. Check the statute a summary discusses before using its deadlines or requirements.
For Texas-based organizations, this is the multi-state counterpart to our Texas AI governance guidance. Keep one operational inventory and map each jurisdiction's requirements to the relevant tools. Separate state requirements do not require duplicate inventories.
Should the inventory come before reading the statute?
Start the inventory while counsel reviews the statute. You cannot assess a decision tool nobody has identified. Writing an acceptable-use policy first risks documenting controls for an incomplete list of systems.
Ask process owners which tools screen applicants or score customers. Include embedded vendor features, not just products purchased as AI. An IT asset list identifies software; it rarely explains every decision that software informs.
Ask vendors in writing whether their output informs decisions about consumers or employees. Request documentation of intended uses and known limitations. Ask how they communicate material updates. A compliance slide deck is an input, not evidence of how your company used the tool.
Assign a business owner and review date to each inventory entry. Keep the inventory inside the existing risk program so changes in purchasing or workflow reach the person responsible for it.
What fields should each inventory row carry?
Use one row for each tool-and-decision pair. The same product can support different decisions with different exposures. Prioritize decisions affecting jobs, money and housing; the fields below are operational recommendations, not a claim that the statute mandates this exact format.
| Field | What to record |
|---|---|
| Tool name and version | The product and release in use |
| Vendor | The provider and contact responsible for documentation |
| Business owner | The person accountable for the decision |
| Decision informed | The specific decision, such as applicant screening or loan approval |
| Population affected | The applicants, employees or customers affected, including relevant states |
| Human override | Who can change the outcome and how |
| Data inputs | The personal data the tool uses |
| Outputs and storage | What the tool produces, where it is kept and its retention period |
| Last material update | The date of the latest change that could alter results |
| Disclosure wording | The exact notice and where it appears |
| Materiality call | The dated conclusion and reasoning about the output's influence |
What must a deployer document for each tool?
For operational planning, focus on your role as the organization using the tool. Build records that reconstruct one person's decision, rather than a folder that merely proves you bought a product. Counsel should confirm which role you hold, deployer, developer or both, under the enacted definitions.
Disclosure before the tool runs
Orrick's tracker says deployers must disclose the use of covered ADMT before using it to materially influence a consequential decision. Place the notice before that use, not in an email sent after the decision.
Keep a dated copy of the wording and evidence of where it appeared. Test the actual application or portal workflow after changes; an approved notice sitting in a policy folder does not show that a consumer received it.
Adverse outcome notices
According to the tracker, an adverse outcome notice must describe the decision and the tool's role. It must explain how the person can obtain more information about the tool and its inputs, along with applicable rights concerning personal data and reconsideration.
Build the notice from the individual's decision record. A generic statement that “AI was used” does not explain what the output contributed. Have counsel approve the template and the process for responding to requests.
Human review you can prove
Name a reviewer who has authority to change the outcome. Give that person access to the relevant inputs and enough time to assess them. Log the review and its result.
A signature alone does not establish meaningful review. If nobody ever changes an outcome, inspect the process: the reviewer may be approving the score rather than testing it. A zero-override rate warrants investigation, not an automatic conclusion that every review failed.
Vendor material you still have to keep
The tracker says developers must provide information about intended uses, training data, limitations and appropriate monitoring, including meaningful human review, plus notice of material updates. Preserve that material with the tool's record.
Record when you received an update and whether it changed your use of the tool. The vendor's documentation cannot establish what your employees did with its output.
What belongs in an impact assessment?
Record the tool's purpose, the data it uses and produces, available performance results, and post-launch monitoring. Date the assessment. Revisit it after material updates or changes in use; an assessment of applicant screening does not automatically cover a later promotion-scoring workflow.
These are operational recommendations. Advocacy groups including EPIC urged Colorado lawmakers to retain impact-assessment provisions, but advocacy is not enacted law. Have counsel confirm the replacement law's requirements and separately assess any Colorado Privacy Act data protection assessment duty.
How do you confirm the enforcement date?
The sources retrieved November 12, 2026, report January 1, 2027, as the effective date, but the research for this article did not include the enacted text. Confirm it before you set a deadline. Start with SB 26-189 and the codified provisions at Co. Rev. Stat. § 6-1-1701 et seq., then check the Colorado Attorney General's site for any rules and guidance. Record who checked, the date and the version reviewed.
If a secondary summary and the enacted text disagree, the enacted text governs, and counsel should resolve the difference. Repeat the check before any policy approval or contract commitment that depends on these requirements.
When does a lawyer need to be involved?
Involve counsel when a tool affects a regulated decision, a person disputes an outcome, or your legal role is unclear. An inventory supports those decisions. It does not replace legal interpretation.
We provide AI inventories, acceptable-use policies, risk assessments and guardrails through our Fractional Chief AI Security Officer service. To scope that operational work, bring your current tool list to a 30-minute Risk Discussion, starting with systems that affect hiring or access to money and housing.
Frequently asked questions
What is the new AI law in Colorado?
SB 26-189 replaced the 2024 Colorado AI Act with the Automated Decision-Making Technology Act. Signed May 14, 2026, it takes effect January 1, 2027, according to Orrick's tracker as retrieved November 12, 2026. Confirm the current enacted text before relying on that deadline.
Does Colorado have a consumer protection law that covers automated decisions?
Yes. The Colorado Privacy Act has provided an opt-out right for certain solely automated decisions with legal or similarly significant effects since July 1, 2023. ADMTA separately addresses covered technology that materially influences consequential decisions; counsel should assess both against your workflow.
What laws just passed in Colorado?
The 2026 laws identified in the research include SB 26-189 and HB 1263, which addresses conversational AI services. Orrick's tracker reports a January 1, 2027, effective date for both. HB 1263 includes AI disclosure and user age-estimation requirements; verify the enacted provisions applicable to your service.
Does the law apply if our company is based outside Colorado?
An out-of-state headquarters is not a sufficient basis to dismiss Colorado obligations. If your tools affect Colorado residents, have counsel check the statute's reach and your role under it. Record the conclusion against each relevant tool and decision.
What penalties can apply?
Orrick's tracker, retrieved November 12, 2026, lists penalties of up to $20,000 per violation. It also identifies potential liability under state anti-discrimination laws for consequential decisions materially influenced by covered ADMT. Have counsel verify the enacted penalty provisions and how they apply to the conduct at issue.
Total 360 Security provides virtual Chief Security Officer, vCISO, and Enterprise Security Risk Management programs for mid-market organizations. They design, run, and report security programs covering all 13 risk domains rather than just offering advisory decks or point solutions. The firm is Texas DPS-licensed with CPP, CISSP, and CISM credentials.
Serving Texas, California, Nevada, New Mexico.
More from the blog
10 min read
Identity Access Management Software: What to Govern First
A practical order for identity access management software: define privileged access, name an owner, inventory raw exports and review each quarter before buying a tool.
Read article7 min read
SOC 2 Audit: What Type II Requires and Who Owns Each Control
A SOC 2 audit is an independent CPA examination of your controls against the AICPA criteria. Here is what a Type II report requires, who owns each control and what evidence to keep.
Read article7 min read
Compliance Monitoring: What to Check Monthly and Quarterly
Compliance monitoring is the ongoing check that your operations follow the rules that apply to you. This guide sets a monthly evidence set, a quarterly sampling routine and clear ownership for every exception.
Read article