Artificial Intelligence Policy Tracker

Notify consumers and explain adverse consequential decisions

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

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

Notify consumers and explain adverse consequential decisions is a legal requirement under the Colorado AI Act in Colorado (United States) (C.R.S. 6-1-1703(4)). Before a high-risk system makes a consequential decision, deployers must notify the consumer that AI is used, describe its purpose and nature, and provide contact and opt-out information where applicable.

Instrument
Colorado AI Act
Nature
Legal requirement
Source reference
C.R.S. 6-1-1703(4)
Who it binds
Deployer / user organisation
Evidence examples
1
Framework mappings
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?

Before a high-risk system makes a consequential decision, deployers must notify the consumer that AI is used, describe its purpose and nature, and provide contact and opt-out information where applicable. After an adverse decision they must state the principal reasons, the data used and its sources, and offer an opportunity to correct data and to appeal for human review where feasible.

Practical action

Add pre-decision AI notices and an adverse-decision explanation and appeal workflow.

Who does it apply to?

Deployers making consequential decisions with high-risk AI.

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.

  • satisfiesProcessProduct owner · at launch and on material change
    AI interaction and use disclosure notices

    Serves 18 recorded duties · evidence: AI interaction or use notice, Notice catalogue, Notice wording approval

    Pre-decision notice with purpose, nature and contact details.

  • satisfiesProcessCustomer operations lead · once per ai system
    Decision explanation, human review and appeal route

    Serves 12 recorded duties · evidence: Adverse-decision explanation template, AI decision challenge and human review procedure, Challenge and reversal log

    Adverse-decision reasons, data correction and appeal for human review.

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 8 templates that cover it →

What evidence would a reviewer expect?

Evidence examples
EvidenceTypeNotes
Consumer notice and adverse-action explanation templatesdocument

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
NIST AI RMF 1.0GOVERN 5.x, MANAGE 4.xRecourse and communication.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(4)).

Who must comply with this obligation?

Deployers making consequential decisions with high-risk AI.

What evidence shows compliance?

A reviewer would expect: Consumer notice and adverse-action explanation templates.

Which frameworks map to this obligation?

It is mapped to NIST AI Risk Management Framework 1.0 GOVERN 5.x, MANAGE 4.x. These are editorial crosswalks with a stated confidence, not official mappings.

Which controls satisfy this obligation?

AI interaction and use disclosure notices; Decision explanation, human review and appeal route.

What should an organisation do in practice?

Add pre-decision AI notices and an adverse-decision explanation and appeal workflow.

Cite this record

AIPolicyTracker (2026). “Notify consumers and explain adverse consequential decisions (Colorado AI Act)” [AIPT-OBL-0086, not yet verified]. https://aipolicytracker.org/id/AIPT-OBL-0086 (accessed 27 October 2026). Data licensed CC BY 4.0.

Permanent id AIPT-OBL-0086: 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_notifyconsumersandexplai,
  author       = {{AIPolicyTracker}},
  title        = {{Notify consumers and explain adverse consequential decisions (Colorado AI Act)}},
  year         = {2026},
  howpublished = {\url{https://aipolicytracker.org/obligations/us-colorado-consumer-notice-and-adverse-decision-explanation}},
  url          = {https://aipolicytracker.org/obligations/us-colorado-consumer-notice-and-adverse-decision-explanation},
  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.