ReviewDesk
← Back

ReviewDesk guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

How do you run ADMT workflows across Colorado, California and Illinois at once?

Generate a free adverse-outcome letter — no sign-up Build a free pre-use notice See pricing

The short answer. Keep one internal source for the tool description and factor list, and let each jurisdiction's workflow draw from it — while notices, letters, clocks and routes stay jurisdiction-specific: Illinois notice now, Colorado's 30-day explanation machinery, California's opt-out or appeal handling. ReviewDesk's paid plans hold multiple workflows with the CO/CA/IL rule packs in one workspace, so the estate is operated as a system rather than as three side projects.

What is multi-jurisdiction ADMT operations?

Multi-jurisdiction ADMT operation is the running of automated-decision workflows under more than one regime at once — in ReviewDesk's world, Colorado SB 26-189, the California CPPA ADMT regulations and Illinois HB 3773. Its organising principle is shared facts, local duties: the underlying decision and factors are common; the notices, explanations, clocks and consumer routes are configured per jurisdiction.

What is shared and what must never be shared?

Shared: the tool itself, its factor structure, the criteria, the decision data, the reviewer standards, the record architecture. Local: the notice text and its rights routes, the letter's jurisdiction note, the clocks that apply, the consumer-facing vocabulary of the regimes ('consequential' in Colorado's mouth, 'significant' in California's, employment notice in Illinois'). The failure mode is confusing the columns — one global notice pasted into three states, which discharges none of them properly because each is missing its own machinery: California without its opt-out route, Colorado without its explanation clock, Illinois a year late.

The second failure mode is the opposite: three fully separate programmes, three factor lists drifting apart, three inboxes staffed by three habits. Divergence is the cost of total separation; the shared-source model exists to avoid paying it. ReviewDesk's workflow structure is the compromise made concrete — workflows share the workspace, the team and the record discipline, while each carries its own jurisdiction configuration and rule pack.

How do the three timelines interleave in one calendar?

Illinois is live now for employment. California's regulations took effect 1 January 2026 with compliance duties from 1 January 2027. Colorado's SB 26-189 takes effect 1 January 2027. California's first annual risk-assessment pack lands 1 April 2028. Sequenced honestly, the work orders itself: Illinois notices and review routes first where you hire there; Colorado and California workflows built through the run-up to 2027, generating records from day one; the assessment assembled from those records in early 2028. The full picture is in the deadlines calendar.

One calendar, one owner. The regimes reward a single programme lead who sees the whole estate, because the resource conflicts are real — the same HR team, the same vendor, the same inbox bench serves all three — and a per-state ownership model discovers those conflicts as missed clocks. The Monday view should be the estate's view: open cases by jurisdiction, clocks by urgency, changes pending by workflow.

How do letters stay jurisdiction-correct automatically?

By generation from the workflow, not by drafting discipline. A letter generated inside the Colorado workflow carries the Colorado note — the 30-day explanation frame, the correction path, the review offer as Colorado frames it. The same facts inside the California workflow produce the California letter with its opt-out or appeal position stated. The Illinois workflow produces the employment-notice regime's correspondence. The reviewer writes the decision and the reasons once, in the case; the jurisdiction machinery is inherited from the workflow the case belongs to. Human memory is never the jurisdiction control.

This is the strongest practical argument for running the estate in one desk. In a document-based estate, jurisdiction correctness is a proofreading property — true on the day someone checked. In a workflow estate it is a structural property — the letter cannot easily leave with the wrong state's note, because the note is not typed. Structure beats vigilance at volume, every quarter, forever.

How are people routed to the right workflow?

By the decision's own facts: the person's state, the decision type, the entity deciding. The notice page is per workflow, so collection points must link the right page — a detail that sounds clerical and is actually jurisdictional. A California applicant who lands on the Colorado notice has been told the wrong rights, and the error is the organisation's, however it happened. Placement audits, per the hosted-notice guide, must verify not just that a notice is linked at each door, but that it is the door's own jurisdiction's notice.

Edge cases deserve a rule written in advance: the remote worker living in one state, employed by an entity in another, screened for a role in a third. Decide the routing principle with counsel — the person's location is the usual centre of gravity in these frameworks — encode it in the intake logic, and record which workflow handled each case so a misroute, when found, is a findable set rather than a suspicion.

How does staffing work across jurisdictions?

One bench, jurisdiction-aware. Reviewers need the decision competence first and the jurisdiction note second — and since the note is generated, the second is mostly awareness: this case's clock is Colorado's thirty days; this case carries a California opt-out already exercised. Assignment, per the assignment guide, routes by decision type and deadline, with the jurisdiction visible on the case. The inbox owner's board aggregates across the estate, because a surge in California corrections and a Colorado clock crunch are one staffing problem wearing two flags.

Knowledge, though, should specialise lightly: one person as the California-route expert, one as the Colorado-clock watcher, cross-trained as deputies. Regimes evolve — guidance lands, forms change — and the estate needs named humans who notice. Light specialisation inside one bench gives both resilience and attention; three separate benches give neither at small scale.

When does an organisation outgrow one workspace?

Later than it fears. Multiple workflows, three jurisdictions, several decision types and a real review bench all fit the one-desk model, because the model's unit — the workflow — multiplies cleanly. Separation becomes arguable when legal entities genuinely diverge: a subsidiary with its own decisions, its own applicants and its own counsel may warrant its own workspace and its own vault, so that records, access and exports follow the entity boundary. The test is the decision's ownership, not the estate's size.

Until that test bites, keep the estate together. The consolidated view is worth more than tidiness: one coverage number, one corrections log, one vendor conversation, one risk picture. The programmes that fragment early spend their maturity re-aggregating for the annual assessment what a single workspace would have held natively. Build in ReviewDesk the way the regimes are built — one programme, local duties — and the structure will still be right when the fourth jurisdiction arrives.

Your five actions for multi-jurisdiction ADMT operations

  1. Keep one shared source for the tool description and factors; let each jurisdiction's workflow carry its own notice, note and clocks.
  2. Sequence by live duty: Illinois now, Colorado and California workflows generating records ahead of 1 January 2027.
  3. Generate letters from the workflow so jurisdiction correctness is structural, never a proofreading outcome.
  4. Audit notice placement per door for the right jurisdiction, and write the routing rule for cross-state people in advance.
  5. Run one bench with light jurisdiction specialisation, on one board, under one programme owner.

Worked example: one screening tool, three states, one Monday board

A fictional employer — Northgate Health Services — screens support staff in Illinois, Colorado and California with the same tool. Its estate is three workflows on one desk: Illinois live first (employment notice, inbox, letters), Colorado and California built in the following quarter with their own notices — Colorado's carrying the explanation promise, California's the opt-out route — all three drawing factors from one shared description owned by the programme lead.

The Monday board shows the estate at a glance: 61 open cases across the three, two Colorado cases inside their final third, a California correction cluster pointing at one clinic's intake form, Illinois steady. One vendor conversation covers the factor change the vendor proposes, assessed once against all three notices. Northgate's counsel reviews one programme with three configurations — not three programmes — and the annual assessment, when it comes, will be an assembly exercise. The estate behaves like a system because it was built as one.

Frequently asked questions

Can one workflow cover three states?

No — the duties differ in machinery, so each jurisdiction gets its own workflow with its own notice, letter note, clocks and routes. What is shared is the source: the tool description, factors, criteria, team and record discipline, inside one workspace on paid plans.

Which jurisdiction should be built first?

The one whose duty is already live for you — Illinois employment, if you hire there. Then Colorado and California ahead of their 1 January 2027 compliance start, early enough that records accumulate before the first annual assessment.

How do letters avoid carrying the wrong state's note?

By being generated inside the workflow the case belongs to. The reviewer writes the decision and reasons; the jurisdiction note, clocks and routes are inherited from the workflow's configuration rather than typed from memory.

What about applicants who live in a different state from the job?

Decide the routing principle with counsel in advance — the person's location is the usual centre of gravity — encode it in intake, and record which workflow handled each case so any misroute is findable.

Is this guide legal advice?

No. ReviewDesk is templates and workflow tooling, not legal advice. The operating model is ReviewDesk's; consult counsel for your multi-state position.

Keep reading: How can an agency run ADMT desks for multiple client businesses? · How can HR-tech resellers offer ADMT notice and review tooling to their clients? · How can a small business meet ADMT notice and review duties without a compliance department? · What should a startup build first when its product or hiring uses AI screening? · A landlord's step-by-step plan for compliant automated tenant screening · All ReviewDesk guides · ReviewDesk home · Try the free desk · Free letter generator · Free notice builder · Pricing

ReviewDesk is built by Ingenious AI. Templates and workflow tools — not legal advice.