Two deadlines. One law. No confirmed outcome.
Colorado’s AI Act, SB24-205, has its original effective date intact on paper: June 30, 2026. A court has ordered a stay of the Colorado Attorney General’s enforcement pending further regulatory and legislative developments, according to prior hub coverage of the judicial block. The enforcement stay holds. The deadline clock hasn’t stopped.
The law applies to developers and deployers of high-risk AI systems operating in Colorado. Its core requirements are a reasonable care standard to protect against algorithmic discrimination, mandatory impact assessments, and transparency obligations for consequential decision-making systems, hiring tools, credit scoring systems, healthcare algorithms, and similar applications. If you’re deploying any of those in Colorado, SB24-205’s scope reaches you.
Two paths are now in play. Path A: the enforcement stay ends, June 30 enforcement begins, and companies without completed impact assessments and documented reasonable care frameworks face exposure starting July 1. Path B: the Colorado legislature passes S.B. 26-189, which would reportedly move the effective date to January 1, 2027, and substantially restructure the compliance regime. Prior hub coverage from May 7 established that SB 26-189 isn’t a minor amendment, it’s a substantive revision. The specific January 1, 2027 replacement date is consistent with reporting but not yet confirmed in a primary legislative source.
Colorado AI Act: Two-Path Scenario
Don’t expect clarity to arrive 30 days before the deadline. Legislative calendars don’t move on compliance team timelines. The Colorado General Assembly’s session schedule determines when, or whether, SB 26-189 advances, and there’s no guarantee it passes before June 30.
The real question for compliance teams isn’t which path the legislature chooses. It’s whether your organization can demonstrate reasonable care and completed impact assessments by June 30 if Path A materializes. That documentation work takes weeks, not days. Starting it now keeps both paths manageable. Starting it in mid-June keeps only one of them manageable.
Context matters here. The federal preemption dynamic adds another layer of uncertainty: the White House has been pushing to block state AI laws, and prior hub coverage on federal preemption implications outlines what that fight means for state-law compliance planning. A federal preemption order wouldn’t automatically void Colorado’s enforcement posture overnight, but it would add a third variable to an already uncertain situation.
Colorado SB24-205 Compliance Actions, Act Now
- Identify all high-risk AI systems deployed in Colorado under SB24-205 scope
- Complete impact assessments for in-scope systems
- Document reasonable care framework for algorithmic discrimination protections
- Monitor Colorado General Assembly session schedule for SB 26-189 advancement
Watch for the Colorado General Assembly session schedule. If SB 26-189 doesn’t advance by late May, Path A becomes the working assumption. At that point, 30 days isn’t enough lead time to build the documentation infrastructure SB24-205 requires from scratch.
The catch is that “enforcement suspended” isn’t the same as “not applicable.” The stay blocks the AG’s enforcement mechanism. The law’s obligations, reasonable care, impact assessments, transparency notices, exist independently of whether the AG is actively pursuing cases. Companies that build their compliance posture on the assumption that the stay will persist indefinitely are taking a position their lawyers should probably review.