Colorado’s AI Act Is 72 Days Away. Most Enterprise Deployers Aren’t Ready.

Colorado SB 24-205 — the Colorado AI Act — takes effect June 30, 2026. That is 72 days from today. The law is not aspirational guidance or a policy framework. It is enforceable state law requiring specific, documented compliance actions from any enterprise deploying AI systems that make consequential decisions about Colorado consumers.

Most large enterprises have not completed those actions. The countdown is real, and the White House framework recommending federal preemption of state AI laws has not changed it. Multinational teams face a similar obligation set in Europe, covered in EU AI Act high-risk systems compliance.

Whether federal action changes the timeline is the open question in federal AI preemption and state laws. Enterprises deploying high-risk AI in Colorado should document impact assessments before the Colorado AI Act deadline. The Colorado AI Act creates duties for both developers and deployers, so vendor contracts need to reflect them.

Legal teams are mapping which HR, lending and insurance tools fall under the Colorado AI Act. Consumer notice requirements in the Colorado AI Act will affect customer-facing chatbots as well as scoring models. Companies that already run NIST-style risk programs will find the Colorado AI Act easier to satisfy. Enforcement under the Colorado AI Act will be led by the state attorney general, so documentation matters from day one.

The Act’s requirements divide cleanly across two roles: developers (companies that build or train AI systems) and deployers (companies that use those systems to make decisions). If your company uses a vendor’s AI model to screen job applications, approve loans, assess insurance risk, or triage healthcare decisions for Colorado residents, you are a deployer under the Act — regardless of where your company is headquartered. The geographic trigger is where the consumer is located, not where the enterprise operates.

Colorado AI Act: What the Law Requires

Colorado AI Act compliance review

Colorado AI Act obligations for deployers look familiar to any team that has already mapped its EU exposure. The high-risk classification logic overlaps closely with the approach described in EU AI Act high-risk systems compliance, so one inventory of consequential decisions can serve both regimes. Teams that document impact assessments once, in a form both regulators would accept, avoid rebuilding the same evidence twice. The Colorado AI Act is one of the clearest US state tests of that overlap.

The Act targets “high-risk AI systems” — defined as systems that make or substantially influence consequential decisions in employment, education, financial services, healthcare, housing, insurance, or legal services. If an AI system in any of those categories processes decisions about Colorado residents, it is in scope.

Developer obligations under Colorado SB 24-205 include: disclosing system capabilities, known limitations, and discrimination potential to deployers; providing documentation on training data, intended use, and performance evaluations; and reporting discovered algorithmic discrimination to the Colorado Attorney General within 90 days of discovery.

Deployer obligations are more extensive: conduct a pre-deployment impact assessment for each high-risk AI system; maintain an annual algorithmic discrimination review process; provide consumer-facing disclosures explaining AI use in consequential decisions; establish complaint mechanisms that allow consumers to contest AI-driven decisions; and report discovered algorithmic discrimination to the AG within 90 days. The full scope of both sets of obligations is detailed in Brownstein’s analysis and the Glacis compliance guide.

The 90-day AG reporting obligation deserves particular attention. It is not triggered by a breach or a lawsuit — it is triggered by discovery. If after June 30 your AI system produces discriminatory outcomes — even inadvertently — and your internal processes identify it, you have 90 days to report to the Attorney General. Without a pre-deployment impact assessment and annual review process already in place, your organisation has no systematic mechanism for early discovery and no audit trail demonstrating good-faith compliance effort.

The Three Compliance Gaps Most Enterprises Have

Based on analysis from ComplianceHub’s June 30 deadline assessment and the ALM Corp compliance guide, the pattern of non-readiness across enterprise deployers concentrates in three areas.

Pre-deployment impact assessments. The assessment process requires documenting the AI system’s purpose, the population it affects, known bias risks in training data, the protected characteristics at risk (race, color, age, disability, religion, sex, veteran status, and other Colorado/federal protected classifications), and the mitigation measures in place. This is a multi-week process requiring coordination between legal, data science, and product teams. Most enterprises have not started it for their AI-assisted decision workflows.

Annual discrimination review processes. Even companies that have conducted one-time bias audits for regulatory purposes do not typically have a standing annual review process with documented ownership, defined methodology, and executive sign-off. The Act requires this as an ongoing obligation, not a one-time certification. Building this process — including defining what metrics trigger remediation — requires compliance infrastructure that does not exist at most enterprises.

AG reporting mechanisms. The 90-day reporting obligation to the Colorado AG requires that an enterprise has: a process for identifying when algorithmic discrimination has been discovered; a defined internal escalation chain for that discovery; and a prepared reporting template and designated legal contact for AG notification. The Colorado AG’s office is running active rulemaking that will specify reporting formats and procedures — but enterprises cannot wait for rulemaking completion before building the internal process.

The Federal Preemption Misconception

The most common reason enterprise compliance teams are deferring action is the White House framework issued March 20, 2026, which recommends federal preemption of state AI laws. The reasoning is understandable: if federal law preempts the Colorado AI Act, compliance effort is wasted.

The problem with this reasoning is that the White House framework is a policy recommendation, not law. Congress has not passed federal AI legislation. The current legislative calendar does not contain an AI preemption bill with a credible path to enactment before June 30. The Colorado Act stands as enforceable state law until Congress passes something different — and the probability of that happening in the next 72 days is effectively zero.

This is not analogous to a regulatory grace period or a temporary moratorium. The Seyfarth analysis notes that Colorado’s Act is operating alongside Illinois AI disclosure requirements and California employment discrimination AI regulations — a multi-state compliance environment that is deepening, not contracting, regardless of federal preemption intent.

For context, the EU AI Act provides a useful comparison: it is broader in scope and applies internationally to EU market participants, but its compliance timeline is measured in years. Colorado’s Act is narrower in geographic scope but is taking effect in 72 days with no further delay mechanism available.

The preemption debate is the other variable that could change the Colorado AI Act picture. A federal framework that displaces state rules would alter compliance scope, but deployers should not plan around that outcome until it becomes law. The current federal position, outlined in federal AI preemption and state laws, is a signal to watch rather than a safe harbor. Until a preemption statute passes, state obligations remain the operative baseline.

What to Watch

Colorado AG rulemaking output. The AG’s office at coag.gov/ai is developing specific compliance standards. Any rulemaking published before June 30 will clarify the impact assessment methodology, the AG reporting format, and potentially the enforcement posture for the first 90 days post-effectiveness. Monitor this actively — the rulemaking output is the single most actionable signal for compliance teams.

Enforcement posture in Q3 2026. How the Colorado AG approaches enforcement against enterprises that have made good-faith compliance efforts but are not fully compliant by June 30 will set the practical standard. An AG that pursues documentation of effort rather than perfection changes the risk calculus; an AG that enforces strictly from July 1 changes it differently.

Multi-state AI regulatory convergence. Illinois, California, and now Colorado represent a growing state-level regulatory layer that exists independent of federal action. If Texas or New York introduce comparable legislation in H2 2026, the compliance cost of managing state-by-state AI regulation will begin to approach EU AI Act complexity — creating real pressure on Congress to act on preemption or harmonisation. See our US AI regulation gap analysis for the broader federal context.

Vendor documentation availability. The developer obligations in the Act require AI system vendors to provide documentation on training data, performance evaluations, and discrimination risks to deployers. Enterprises using third-party AI systems should be requesting this documentation from vendors now — both to complete their own impact assessments and to establish that they requested it, creating an audit trail if documentation is incomplete or delayed.

The June 30 deadline will not shift again. The compliance actions required — impact assessments, annual review processes, AG reporting mechanisms, consumer disclosures — are not overnight tasks. Enterprises that begin the triage process now can complete minimum viable compliance before June 30. Enterprises waiting for federal preemption are making a bet that has a near-zero probability of paying off in 72 days.

This article was produced with AI assistance and reviewed by the editorial team.

Marcus Webb

Marcus Webb

Marcus Webb covers technology policy, regulation, and geopolitics for Next Waves Insight, tracking how governments in the US, EU, and Asia are responding to AI and emerging tech. His reporting focuses on what regulatory frameworks actually require in practice — translating legislative text and enforcement actions into their real operational impact for companies building and deploying new technology.

4 thoughts on “Colorado’s AI Act Is 72 Days Away. Most Enterprise Deployers Aren’t Ready.”

Leave a Comment