← Back

Guide · Published November 14, 2026 · Reviewed November 14, 2026 · Ingenious AI team · Not legal advice

← All guides

ADMT Compliance Checklist for January 1, 2027: Colorado and California Go Live Together

The short answer: On January 1, 2027, two regimes start together: Colorado's SB 26-189 duties take effect (pre-use notice, 30-day explanation, correction, human review, 3-year records), and California's CCPA ADMT compliance phase begins for businesses already using ADMT for a significant decision (risk assessment, pre-use notice, opt-out, access). Connecticut's notice duties follow on October 1, 2027, and its discrimination rule is already live. Readiness is a dependency chain — inventory before assessments, assessments before notices, notices before queues, records underneath everything — and this checklist follows that order.

Check your duties and dates — free Build your first notice — free

What is this checklist for? It is the readiness sequence for the January 1, 2027 start, built only from duties in the kit's data. It is not a legal opinion about any business — run your own facts through the free duties checker per state, decision type, and tool role, and treat its output as your duty set. The master date list lives on the ADMT deadline tracker.

Phase one: know what you run (inventory and scope)

Nothing else can start until the tool list exists. Run the five-pass inventory (procurement, workflows, data flows, shadow tools, register) from How to Inventory Automated Decision Tools, then apply the role test per tool per state from How to Tell If a Tool Is ADMT. Deliverable: a register where every row has a duty set or a documented negative finding.

Do this first because every later phase inherits its errors. An assessment written for the wrong tool list, or notices built for three of five in-scope systems, must be redone when the missing systems surface — and they surface at the worst time, usually in response to a person's question the file cannot answer.

Phase two: assessments before use (California risk, Connecticut data-protection)

California's risk assessment (purpose, data involved, risks, safeguards) must be complete before use — for existing use, that means before the compliance date. Connecticut's data-protection assessment precedes heightened-risk profiling and is likely already owed. Deliverable: one assessment per covered use, dated, versioned, and filed with the record, per the assessment guide.

Assessments come before notices in the sequence because the notice's role sentence and the opt-out design both depend on the assessment's findings. Writing notices first produces documents that describe the workflow as imagined; writing them after the assessment produces documents that describe it as found.

Worked example: Redwood Coast Services Group

Example — fictional business, real duty structure. Redwood Coast is a fictional services group with Colorado and California operations that ran the five phases across the autumn before the deadline. Its readiness state on December 15, 2026:

Phase three: notices, opt-outs, and placement

Build the per-state notice set: Colorado's pre-use notice at the point of interaction; California's pre-use notice naming opt-out and access rights, with two easy opt-out routes or a documented exception position; Connecticut's notice pair diarised for October 1, 2027 deployments, with the data fields (trade name, categories, sources) collected from vendors now. Deliverable: approved texts, placed in the real flows, generated per person, and logged — per the placement guide.

Test the full path as an applicant on a phone before the date: notice encountered pre-use, opt-out completable, contacts working. A notice system that has never been walked end-to-end is a plan, not a control.

Phase four: the response machinery (explanations, corrections, reviews, access)

Stand up the four response workflows with owners and rotas: Colorado explanations drafted from reasons captured at decision time and sent inside 30 days; corrections logged, verified, acted on, and re-run; human review by named people with authority, per the meaningful standard; California access answers assembled from the record (logic, outcome, purpose). Deliverable: each workflow run at least once on a test case before January 1.

Dry runs matter because January's first real cases will not wait for the workflow to be designed. The cheapest time to discover that the explanation approver is a single person with no deputy is in a dry run, on a test case, not on a live clock.

Phase five: the record, the exports, and the calendar

Underneath everything, the record: one chain per decision carrying notice, decision, reasons and data summary, explanation, requests, and responses — retained for three years, exportable, integrity-checked. Deliverable: the one-hour test passed on a recent case, an export read cold by someone outside the team, per the records guide.

Finally, the calendar beyond January: Connecticut notices on October 1, 2027; EU Annex III deployer duties on December 2, 2027 for the listed areas; Colorado's Attorney General rules on post-decision disclosures due by January 1, 2027, which may adjust explanation formats. Readiness is a state you maintain, not a date you survive — the register, the assessments, and the record reviews all carry quarterly dates from here.

  1. Inventory every decision tool and record a duty set or a documented negative per tool, per state
  2. Complete California risk assessments (and any Connecticut data-protection assessments) before the compliance date
  3. Place per-state notices in the real flows, per person, logged — with two tested California opt-out routes or a documented exception
  4. Dry-run explanations, corrections, reviews, and access answers on test cases before January 1, 2027
  5. Pass the one-hour record test, verify the chain, test an export — then diarise October 1, 2027 and December 2, 2027

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.

Build your first notice — free

Related guides

See all ADMT guides for the full set.

Frequently asked questions

What starts on January 1, 2027?

Colorado's SB 26-189 duties take effect, and California's CCPA ADMT compliance phase begins for businesses already using ADMT for a significant decision. A business starting ADMT use after that date must comply from its first use.

What is already in force before January 2027?

Connecticut's profiling opt-out (since July 1, 2023, expanded July 1, 2026), its discrimination no-defence rule (since October 1, 2026), California's ADMT regulations themselves (in effect since January 1, 2026), and the EU's Article 50 transparency duties (since August 2, 2026).

In what order should readiness work happen?

Inventory and scope first; assessments second; notices and opt-outs third; response workflows fourth; the record and calendar underneath and last. Each phase inherits the previous phase's accuracy.

What follows January 2027 on the calendar?

Connecticut's AEDT notice duties for tools deployed on or after October 1, 2027, and the EU's Annex III high-risk deployer duties on December 2, 2027 for employment, education, creditworthiness, and essential-services systems.

How do we know we are ready?

Test, don't attest: the applicant phone test for notices, a dry run per response workflow, the one-hour record test, and an export read cold. Each produces evidence, not reassurance.

Build your first notice — free