Guide · Published November 14, 2026 · Reviewed November 14, 2026 · Ingenious AI team · Not legal advice
Colorado's 30-Day Explanation Clock: How It Runs and How Not to Miss It
The short answer: Colorado's SB 26-189 gives a covered business 30 days from the decision to give the person a plain-language explanation after a consequential decision with an adverse outcome — a description of the tool's role in the decision and, per the kit's rules data, the principal reasons for the outcome. The clock is Colorado's alone: the kit's data states no fixed day count for California or Connecticut, and shows those decisions as 'no fixed clock'. The ADMT Notice Kit tracks the 30 days per decision, from the decision date stored in the record.
Check your duties and dates — free Build your first notice — free
What is the 30-day clock? It is the deadline attached to Colorado's adverse-outcome explanation duty, effective January 1, 2027: decision date plus 30 days. It runs per decision, not per batch, per month, or per complaint — a decision made on the 3rd is due its explanation by the 2nd of the following month, whether or not the person asks.
When the clock starts: the decision, not the discovery
The clock runs from the decision. That sounds simple until real workflows intrude: the tool scores on Monday, a reviewer confirms on Wednesday, the letter posts on Friday. Which date is 'the decision' in your record is a definition you must fix in advance and apply consistently — the kit stores one decision date per case, and the clock counts from it. A definition chosen after a deadline is questioned convinces no one.
Batch processing is the classic trap. If decisions are effectively made when the tool runs but only reviewed in a weekly batch, a decision can be six days old before a human sees it — a fifth of the clock gone. Align the recorded decision date with the moment the outcome becomes real for the person, and if your pipeline has a gap, shorten the pipeline rather than redefining the date.
What stops the clock: a sent explanation, not a drafted one
The duty is to give the person the explanation. A drafted, approved, or queued explanation has not been given. The kit's record therefore tracks the explanation's sent date against the decision date, and the deadline tracker view exists precisely so a case approaching day 30 is visible before it is late, not discovered after. Build the same visibility whatever tool you use: a list of open adverse decisions sorted by days remaining.
Contents matter to the clock's purpose: the explanation states the principal reasons and the tool's role, in plain language, with the correction and review paths. A one-line 'you did not meet our criteria' sent on day 29 meets the date and misses the duty. What the document should contain is walked through in How to Write an Adverse-Outcome Explanation and shown in Adverse-Outcome Explanations in Plain Language.
Worked example: Mile High Property Management
Example — fictional business, real duty structure. Mile High is a fictional Colorado property manager screening tenants. In its first month under the clock, March 2027, its tracker shows:
- Decisions made: 148 screening decisions, each with a single recorded decision date captured the day the outcome was set.
- Adverse outcomes: 39 decisions went against the applicant and entered the explanation queue automatically, each with its own day-30 date.
- Explanations sent: all 39 explanations sent — median day 9, slowest day 24 — drafted from the reasons and data summary stored at decision time.
- Near-miss caught: the queue view flagged 3 cases at day 21 unsent during a staff absence; the deputy approver cleared them the same day, which is what the rota exists for.
- Record kept: 148 decision dates, 39 explanation dates, and the day counts between them sit in one hash-chained record, held for three years.
The AG rules caveat, stated once and clearly
One uncertainty is built into Colorado's timeline, and the kit states it rather than hiding it: the Attorney General must adopt rules clarifying the post-decision disclosures by January 1, 2027, so the exact format of the explanation may still change. That is a reason to keep your explanation structure easy to adjust — reasons, data summary, next steps as separable blocks, as the kit's builder produces them — not a reason to wait. The clock itself is in the statute summary the kit is built from; the format clarification is what is pending.
Enforcement context from the checker data: the Attorney General enforces SB 26-189 under the Colorado Consumer Protection Act, there is no private right of action, and a 60-day cure period applies until January 1, 2030. None of that extends any individual explanation's 30 days — the cure period concerns enforcement, not the person's wait.
Running the clock across a real caseload
At volume, the clock is a queue-management problem. The workable pattern: every adverse decision enters the queue the day it is made, with its due date computed; explanations are drafted from the stored reasons and data summary (both captured at decision time, when they are known); a person sends them in daily or near-daily batches; the queue view shows anything inside seven days in a colour nobody can ignore.
The kit implements this as the deadline tracker over the hash-chained record: decision date in, day count out, explanation date logged against it. Whether you use the kit or a disciplined spreadsheet, the non-negotiables are the same three fields per case — decision date, explanation sent date, days between — auditable by anyone. The full deadline set across states is on the ADMT deadline tracker.
The mistakes that actually cause misses
Misses rarely come from defiance; they come from four ordinary failures. The decision date was never recorded, so no clock existed. The reasons were not captured at decision time, so drafting waited on reconstruction. The explanation waited for a weekly approver who was away. The sent date was not logged, so a sent explanation looked unsent and a duplicate (or a panic) followed.
Each failure is a missing field or a missing cadence, which is why the fix is structural rather than motivational. Capture reasons at decision time. Approve on a rota with a deputy. Log sending the day it happens. Run your position through the free duties checker to confirm the clock applies to your use, and let the free generator show you the explanation shape the clock is counting toward.
- Fix your definition of the decision date, write it down, and record it for every consequential decision
- Capture the principal reasons and data summary at decision time — drafting later from memory is where clocks die
- Track explanation sent dates against decision dates in one view, sorted by days remaining
- Set an internal alarm well before day 30 (day 21 works) with a named deputy approver
- Never borrow another state's numbers: California and Connecticut show 'no fixed clock' in the kit — Colorado's 30 days is Colorado's
Sources, as carried in the kit's own data: the duty summaries in app/rules.py and the checker data in app/checker_data.py, verified against primary or authoritative sources on October 28, 2026. Run the free duties checker for your jurisdiction, decision type, and the tool's role, and compare the kit's plans for the record, builder, and review queue. More from Ingenious AI is on the hub.
Related guides
- How to Write an Adverse-Outcome Explanation: Reasons, Data, and Next Steps
- Adverse-Outcome Explanations in Plain Language
- ADMT Deadline Tracker: Which State Duties Land When
- Colorado AI Act Automated Decision Notices: What to Send
See all ADMT guides for the full set.
Frequently asked questions
How long does a Colorado business have to explain an adverse outcome?
30 days from the decision, under SB 26-189, effective January 1, 2027: a plain-language description of the tool's role in the decision, with the principal reasons.
Does the 30-day clock start when the person complains?
No. It runs from the decision. The explanation is proactive — it is owed whether or not the person asks.
Do California and Connecticut have the same 30-day clock?
No. The kit's data states no fixed day count for California or Connecticut explanations, and the kit shows those decisions as 'no fixed clock' rather than inventing one.
Could the explanation format still change?
Yes. The Attorney General must adopt rules clarifying the post-decision disclosures by January 1, 2027, so the exact format may change. The kit keeps the explanation in separable blocks so it can adjust.
What enforces the Colorado clock?
The Attorney General enforces SB 26-189 under the Colorado Consumer Protection Act. There is no private right of action, and a 60-day cure period applies until January 1, 2030 — which concerns enforcement, not the 30 days a person waits.