ReviewDesk
← Back

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

What must a Colorado pre-use notice for an automated decision tool say?

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

The short answer. Before you use an automated decision-making tool on a Colorado consumer, you must tell them — in plain language, before the tool runs — that it will be used, what kind of decision it informs, and how they can later ask for an explanation and a human review. ReviewDesk publishes that notice as a hosted page for each workflow, linked wherever you collect applications, and files every step in a timestamped audit trail.

What is a Colorado pre-use notice?

A Colorado pre-use notice is the disclosure a business gives a person before automated decision-making technology is used to make, or materially help make, a consequential decision about them — for example in hiring, credit, housing or insurance. Under Colorado SB 26-189, effective 1 January 2027, the notice comes before use, not after a decision, and it is written for the person affected, not for a regulator.

When is the Colorado notice due — before use, not after?

The timing is the whole point of the rule. A notice delivered with a rejection letter is not a pre-use notice; it is an apology. Colorado's framework separates two moments: first, before the tool processes the person's information, they learn that a tool will be used and what it will be used for; second, after an adverse outcome, they receive an explanation and the chance to ask a person to look again. Teams that bundle both moments into one end-of-process letter miss the first duty entirely, and no later document can cure it, because the person never had the chance to understand — or correct their information — before the tool ran.

In practice, the notice belongs at the point of collection: the application form, the screening consent screen, the intake page. A hosted notice page makes that placement trivial, because the same public link can sit on every intake surface you run. ReviewDesk generates the page from your workflow — the jurisdiction, the decision area, the tool description you enter — and the free tier covers one workflow in one jurisdiction, which is exactly the shape of a first Colorado deployment. The generator also runs with no account at all, so you can draft the wording before you commit to a workflow.

What does the notice actually have to cover?

A useful Colorado notice answers five questions in ordinary words. What tool is being used, in general terms a non-specialist can grasp. What decision it helps with — screening job applicants is a different disclosure from pricing an insurance renewal. What categories of information it draws on, so the person can spot an error that matters. What role the tool plays — whether it recommends, ranks, scores or decides. And what happens next for the person: how an adverse outcome will be explained, and how to request human review. Vague lines such as 'we may use technology in our process' answer none of those questions and age badly the first time an applicant quotes them back.

The notice also needs a correction path. Colorado's adverse-outcome duties include letting the person correct incorrect personal data where that is feasible, and a notice that never mentions correction leaves that duty to improvisation later. The guide to correcting data after an adverse decision walks through how that path works in practice. Write the correction route into the notice itself: a named contact, the review form, and a sentence promising that a person — not the tool — will conduct the review.

Who counts as covered by the Colorado duties?

The duties attach to consequential decisions: the kinds of decisions that change someone's access to work, money, housing, insurance, healthcare or education. A recommendation engine choosing which banner a visitor sees is not in that territory; a screening tool ranking who gets an interview is squarely in it. The hard cases sit between those poles, which is why ReviewDesk's evidence engine includes a scope-test worksheet: for each decision type you record your own determination of whether the system materially influences or substantially replaces human judgement, timestamped and stored with the record. The determination is yours — the tool records and evidences it, it does not make legal determinations for you.

Deployers and developers both appear in the Colorado picture. If you buy screening software, your vendor's marketing page is not your notice; the duty to tell the applicant sits with the business making the decision about them. Vendor contracts should therefore ask what notice support, factor information and review tooling the product provides — the questions are set out in the vendor questions guide. If the vendor cannot describe the principal factors its tool uses, you cannot write an honest adverse-outcome letter later.

How does a hosted notice page hold the duty over time?

A notice is not a one-off document; it is a standing page that must still be accurate when the tool, the vendor or the decision changes. That is where scattered PDFs fail: three versions circulate, nobody knows which one an applicant saw in March, and the audit trail cannot answer the simplest question — what did we tell this person, and when? A hosted page has one current version at one address, and ReviewDesk logs the workflow's events with timestamps, so the notice, the decision and the review request can be lined up on a single timeline months later.

Version discipline still matters. When you change the tool or the factors it uses, update the notice before the change goes live, not in the next quarterly tidy-up, and keep the earlier wording in your records. The three-year record horizon discussed in the audit-trail guide applies to the notice history as much as to decisions: an explanation letter that quotes a notice version you can no longer produce is a weak exhibit.

What are the most common Colorado notice mistakes?

The first is burying the notice inside a general privacy policy. A privacy policy describes data practices across a whole business; a pre-use notice describes one tool, one decision and one person's rights, and it must be findable at the moment of application. The second is describing the tool in vendor slogans — 'our AI finds the best candidates' — instead of functions: what it scores, what it ignores, who sees the output. The third is omitting the human. A notice that explains the software in detail but never says a person can review the outcome teaches applicants that appeal is pointless, which is the opposite of what the framework intends.

The fourth mistake is treating the notice as a legal department artefact that operations never reads. The people running the inbox need to know exactly what the notice promised, because every review request will be measured against that promise. ReviewDesk keeps the notice, the human-review inbox and the letter generator in one desk for precisely that reason: the promise and the fulfilment live in the same place, and the audit trail shows both.

How does the Colorado notice connect to the 30-day explanation?

The notice is the first half of a two-part conversation. The second half arrives when a decision goes against someone: Colorado expects an explanation of the adverse outcome within 30 days, covering the principal reasons and the data behind them, plus the review offer. If the notice was specific — tool, factors, role — the letter can be specific in the same vocabulary, and the applicant can follow the thread from warning to outcome. If the notice was generic, the letter inherits the vagueness and reads as evasion, even when the underlying decision was sound.

That continuity is a design choice, not an accident. In ReviewDesk the letter generator assembles each letter from the workflow's own record — the applicant, the decision and the principal reasons you enter — and adds the jurisdiction note for Colorado. The full mechanics are covered in the Colorado 30-day explanation guide. Start with the notice, and the letter mostly writes itself; start with the letter, and you will be reconstructing the notice under deadline pressure.

Your five actions for a Colorado pre-use notice

  1. Publish the notice before the tool first runs on a person's information — linked at every intake point, not filed inside the privacy policy.
  2. Name the decision, the tool's role and the categories of information it uses, in words an applicant can repeat back.
  3. State the correction path and the human-review path in the notice itself, with a named contact route.
  4. Record your scope determination for the decision type, and update the notice before any tool or factor change goes live.
  5. Generate your first draft free with the notice builder, then save it as a hosted workflow page so the audit trail starts.

Worked example: a furniture retailer screens warehouse applicants in Colorado

Consider a fictional retailer — call it Mesa Home Goods — with a distribution centre that hires pickers in waves. In October it shortlisted 214 applicants by hand; in January it plans to use a screening tool that scores applications against attendance history, shift availability and prior warehouse experience, then ranks them for interview. Before the first scored application is processed, Mesa publishes its pre-use notice: the tool is named by function, the three factor groups are listed, the notice states that a hiring manager sees the ranking and makes the interview call, and it gives the review form link and a correction route for wrong availability data.

When the first wave closes, 63 applicants are not interviewed. Because the notice already described the factors, each adverse-outcome letter can be equally concrete: the decision, the principal reasons drawn from those same factor groups, and the review offer, sent inside the 30-day window. Nine applicants ask for review; two surface genuine data errors — an availability record transposed from another applicant — and are re-scored. The notice did not just satisfy a disclosure duty; it made the explanations, the corrections and the reviews administratively possible.

Frequently asked questions

What is a Colorado pre-use notice?

It is the plain-language disclosure given before an automated decision tool is used on a person in a consequential decision — hiring, credit, housing, insurance and similar areas — under Colorado SB 26-189, effective 1 January 2027. It explains the tool, the decision, the information used and the person's explanation, correction and human-review rights.

When must the notice be given?

Before the tool is used on the person's information. A disclosure that first appears in a rejection letter is not a pre-use notice, because the person had no chance to understand or correct their information before the decision process ran.

Does the free ReviewDesk tier cover a Colorado notice?

Yes. Free covers one decision workflow in one jurisdiction — Colorado, California or Illinois — including the hosted public pre-use notice page, the adverse-outcome letter generator, the human-review inbox and the timestamped audit trail. The notice builder also runs free with no account.

What happens after an adverse decision in Colorado?

The person is entitled to an explanation of the adverse outcome within 30 days — the decision, the principal reasons and the relevant data — together with a chance to correct incorrect data where feasible and to request meaningful human review. ReviewDesk generates that letter from the workflow's record.

Is this guide legal advice?

No. ReviewDesk is templates and workflow tooling, not legal advice. Duties are summarised from Colorado SB 26-189 as reported in our research; consult counsel for your situation.

Keep reading: What must a California ADMT pre-use notice include? · What does Illinois HB 3773 require when AI is used in employment decisions? · What is automated decision-making technology (ADMT)? · How do you explain an adverse automated decision within Colorado's 30 days? · What makes a human review of an automated decision 'meaningful'? · 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.