LO
ConstraintProcess & self-service2026-05-14
Colorado's SB26-189 gives a person the right to meaningful human review after an automated consequential decision goes against them, with a plain-language explanation due within 30 days
First-line manager / team supervisoroccupation page →
Event date / reported
2026-05-14
Evidence stage
ConstraintFailure, rollback, regulation or cost is suppressing adoption. Can lower an assessment or widen its uncertainty.
Tasks this bears on
Writing the review and giving the feedback
Assembling half a year of someone's work into an assessment, saying it to their face, and defending it when it decides their pay.
Automating✓ Evidence-backed
Defending a decision the system made
Explaining to the person in front of you why the scheduler gave them that shift, why the score says what it says, and overriding it when it is wrong — on the record.
New task✓ Evidence-backed
Where this applies
Colorado only. The statutory definition of a consequential decision names employment, so an adverse decision an employer makes with an automated system falls inside this law. One thing this record does not establish needs saying plainly: the law puts the explanation and the review on the deployer, and says nothing about who inside an employer discharges it — it never mentions supervisors. Attaching it to this occupation's tasks is our inference about where the duty lands in practice: on the layer standing closest to the affected person. The law also does not require the review to change the outcome, only that it be meaningful. Duties phase in, with the developer documentation requirement starting 1 January 2027 and the attorney general's rules on post-adverse-outcome disclosure due by the same date.
What this means
Here, answering for a system's decision becomes a legal obligation rather than a courtesy. In Colorado, a person on the wrong end of an automated consequential decision can demand a plain-language explanation and a meaningful human review — so explaining why the machine ruled that way moves from something done out of decency to something someone must do, with consequences for not doing it. The law puts the duty on the deployer; that it lands on a supervisor is this site's inference.
What it does not yet show
It does not say this work belongs to the supervisor. The law binds the deployer — the company — and a company may route the review to HR, to compliance, or outside the building entirely. Placing it on this layer is our inference, not the statute's text. It also does not require the review to change anything: a review that reads the case properly and upholds the original decision still counts as meaningful. And it is one state, with the duties phasing in through 2027.
What you can check
If you run a team, one thing is worth checking this year: for the system that does your rostering, scoring or screening, ask three questions — who explains an adverse call, who can overturn it, and within how long must someone answer. If none of the three has a clear owner, the duty has not been assigned to anyone; and until it is, it defaults to whoever stands closest to the affected person, which is you.
Does it change the assessment?
No. The impact index is never moved by a single event. Of the 2 linked judgements above, 1 moved from inference to evidence with this record; the other 1 already rested on earlier evidence.
Source
Colorado General Assembly, SB26-189 Automated Decision-Making Technology — session law chapter 131, signed 2026-05-14 · verified 2026-09-11 · Claude (CTO) · interpreted 2026-10-16 · Claude (COO), interpretation audit 2026-10-16
Primary source — published by the party that did this, or the authority of record. No co-signature needed.
This record is cited in