Artificial Intelligence Policy Tracker
Legal requirement Impact assessment Colorado (United States) Repealed

Deployers must complete impact assessments for high-risk AI

Download: JSON · MarkdownUnder Colorado AI Act, C.R.S. 6-1-1703(3)

Pending review · linked to the official source, waiting for a reviewer to confirm it (a factual check against the official source, not a legal review or legal advice)
What this label means
Verified
— a named reviewer opened the official source and confirmed the record; the date and the reviewer are shown.
Pending review
— linked to the official source and in the queue for a reviewer to confirm.
Source-linked
— linked to the official source, not yet confirmed by a reviewer.
Verification policy and current standing · a factual check, not legal advice.
No longer in force: repealed · Signed 17 May 2024; its effective date was moved from 1 February 2026 to 30 June 2026 by SB 25B-004 (August 2025). Before that date arrived, SB 26-189, signed on 14 May 2026, repealed and re-enacted the framework as a narrower automated-decision-making-technology law that applies from 1 January 2027. This act therefore never took effect; see the SB 26-189 record. Recorded on 26 September 2026 from secondary reporting, pending review against the enrolled bill. · official source last checked
On this page 9 sections

In brief

Deployers must complete impact assessments for high-risk AI is a legal requirement under the Colorado AI Act in Colorado (United States) (C.R.S. 6-1-1703(3)). The record carries 1 evidence example and mappings to 2 frameworks. In practice: Build an impact-assessment template aligned with the statutory elements and calendar the annual refresh.

Instrument
Colorado AI Act
Nature
Legal requirement
Source reference
C.R.S. 6-1-1703(3)
Who it binds
Deployer / user organisation
Evidence examples
1
Framework mappings
ISO/IEC 42001:2023, NIST AI Risk Management Framework 1.0
Controls that meet it
2
Official source
Open official text
Verification
Pending review · source-linked

What does it require?

Deployers must complete an impact assessment before deployment, annually, and within 90 days of any intentional and substantial modification, covering purpose, risks of algorithmic discrimination and mitigation, data categories, performance metrics, transparency measures and post-deployment monitoring, and retain assessments for at least three years.

Practical action

Build an impact-assessment template aligned with the statutory elements and calendar the annual refresh.

Who does it apply to?

Deployers of high-risk AI systems.

Which controls meet this duty?

Satisfies: the control, operated properly, does the work the duty asks for. Supports: it contributes but the duty needs more. Each control page lists every other duty it serves, so work done once can be counted once.

  • satisfiesProcessAI system owner · once per ai system
    AI impact and fundamental-rights impact assessment

    Serves 11 recorded duties · evidence: AI impact assessment, Impact assessment approval, Impact assessment procedure and template

    Templated assessment aligned to the statutory elements, refreshed annually and on material change.

  • supportsTechnical measureAI system owner · continuous
    Post-deployment monitoring and drift detection

    Serves 10 recorded duties · evidence: Post-market monitoring plan, Monitoring dashboard or periodic monitoring report, Monitoring review decision

    Post-deployment monitoring described in the assessment.

Templates that cover this duty

Generated from the records. Free · no account · links emailed to your work address. This duty is cited in each file with its source reference and a link back here.

All 7 templates that cover it →

What evidence would a reviewer expect?

Evidence examples
EvidenceTypeNotes
Algorithmic impact assessmentreport

Framework mappings

Original editorial crosswalks. They cite clause numbers only and reproduce no standard text; confidence reflects how direct the mapping is.

See every Colorado (United States) duty mapped this way →

Framework mappings table
FrameworkReferenceNoteConfidence
ISO/IEC 42001:2023Clause 6.1.4 AI system impact assessmentOriginal editorial mapping.high
NIST AI RMF 1.0MAP 5.xOriginal editorial mapping.medium

Frequently asked questions

Is this a legal requirement?

Yes. It is a legal requirement under Colorado AI Act (C.R.S. 6-1-1703(3)).

Who must comply with this obligation?

Deployers of high-risk AI systems.

What evidence shows compliance?

A reviewer would expect: Algorithmic impact assessment.

Which frameworks map to this obligation?

It is mapped to ISO/IEC 42001:2023 Clause 6.1.4 AI system impact assessment, NIST AI Risk Management Framework 1.0 MAP 5.x. These are editorial crosswalks with a stated confidence, not official mappings.

Which controls satisfy this obligation?

AI impact and fundamental-rights impact assessment; Post-deployment monitoring and drift detection.

What should an organisation do in practice?

Build an impact-assessment template aligned with the statutory elements and calendar the annual refresh.

Cite this record

AIPolicyTracker (2026). “Deployers must complete impact assessments for high-risk AI (Colorado AI Act)” [AIPT-OBL-0085, not yet verified]. https://aipolicytracker.org/id/AIPT-OBL-0085 (accessed 27 October 2026). Data licensed CC BY 4.0.

Permanent id AIPT-OBL-0085: it never changes or gets reused, and its address keeps working if this page moves.

Cite the official text alongside it: SB24-205 Consumer Protections for Artificial Intelligence, Colorado General Assembly, https://leg.colorado.gov/bills/sb24-205.

BibTeX
@misc{aipolicytracker2026_deployersmustcompleteimp,
  author       = {{AIPolicyTracker}},
  title        = {{Deployers must complete impact assessments for high-risk AI (Colorado AI Act)}},
  year         = {2026},
  howpublished = {\url{https://aipolicytracker.org/obligations/us-colorado-deployer-impact-assessment}},
  url          = {https://aipolicytracker.org/obligations/us-colorado-deployer-impact-assessment},
  urldate      = {2026-10-27},
  note         = {Data licensed CC BY 4.0. Accessed 27 October 2026}
}

Change history

No change to this record's tracked fields has been recorded since 15 October 2026, when field-level history began.

Similar obligations in other instruments

Disclaimer: informational only, not legal advice. Verify every claim against the linked official sources and consult a qualified lawyer before acting.