← Back

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

← All guides

Notice Placement: Clear, Conspicuous, and at the Point of Interaction

The short answer: Colorado's duty is stated with its placement built in: a clear and conspicuous notice, at the point where the person interacts with the tool, that an automated decision-making tool is being used. Connecticut's first employment notice uses the same logic — owed when a person will directly interact with the tool. A notice with perfect text placed in a footer, a policy page, or post-decision paperwork fails the placement half of the duty. This guide is about the geography of notices: the surfaces where people meet tools, the placements that fail, and how to test yours.

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

What is the point of interaction? It is the surface and moment where the person meets the tool: the application flow that starts a screening, the assessment's first screen, the portal step that triggers an eligibility check. The kit's notice generation is per-person and pre-decision precisely because placement is temporal as well as spatial — the notice must arrive before the tool is used on that person, in the flow they are actually in.

The surfaces where people actually meet tools

Walk each decision workflow and mark the first moment the person's data enters the tool, or the person meets the tool directly. In hiring: the application submission or the assessment start. In screening: the application form that triggers the check. In lending: the application flow before the scoring step. In services: the enrolment or eligibility step in the portal. The notice belongs at or immediately before that mark — in the same flow, not in a different document the person may have seen weeks earlier.

Multiple tools at multiple points mean multiple placement points. A hiring flow that later introduces an interview-scoring tool has a second interaction, and Connecticut's interaction notice follows it. The inventory register should record, per tool, its interaction point — placement is a register field, not a web team's guess.

Placements that fail, however good the text

Four placements fail predictably. The footer link: present on the site, encountered by nobody in the flow. The general privacy notice: the right words diluted in a document about everything, read at a different time for a different purpose. The post-decision letter: a pre-use notice delivered with the outcome is not pre-use. The one-time account notice: shown at account creation, months before the tool is used on the person for a specific decision, when it cannot inform anything about that decision.

Each failure shares a structure: the business can prove the notice existed but not that it reached the person in time to matter. The duty's wording — clear, conspicuous, at the point of interaction — is written against exactly that structure. If your evidence for a notice is a URL, you have placement work to do; if it is a per-person generation log at the interaction point, you are describing compliance.

Worked example: Summit Peak Staffing

Example — fictional business, real duty structure. Summit Peak is a fictional Colorado staffing firm that audited notice placement across its three hiring tools with the phone test. The audit found:

Clear and conspicuous: the readability half of placement

Placement is also typography and timing. Conspicuous means findable without hunting: presented as its own step or block, in the flow's reading order, not as a collapsed disclosure or a line of small print among forty. Clear means the short-answer quality the kit's templates aim for: the reader learns the tool is being used, for what decision, and what they can do — in one pass, in plain language.

Mobile is the default test surface, because it is where most interactions happen. A notice that is conspicuous on a desktop monitor and a scroll-past footnote on a phone fails on the surface most people use. Test on a phone, mid-flow, with the impatience of a real applicant: that is the conspicuousness standard in practice. The drafting half is in How to Write an ADMT Pre-Use Notice.

Per-person generation: making placement provable

The kit's design answer is to generate the notice for the named person at the interaction point, and log the generation with its date as part of the decision record. Placement then stops being an assertion about a web page and becomes a fact in the file: this person, this notice text, this date, before this decision. When placement is questioned — by the person, in a review, in an audit — the record answers it directly.

Adopt the same standard in any stack: the event you can evidence is 'notice N was presented to person P at time T in flow F'. Generation records and flow logs can carry it; a screenshot of the current web page cannot, because it shows today's page, not the day the decision was made. Version the notice text so the log points at the wording actually shown.

Testing placement: the five-minute applicant test

Test placement the way the person experiences it. Take a phone, start the real application or assessment as a test applicant, and note: when do I first learn a tool will be used? Is it before my data goes to the tool? Can I say what decision is at stake and what my options are? Can I keep a copy? Every 'no' is a placement defect with a location and a fix.

Repeat the test after any flow redesign, vendor portal update, or notice text change — placements regress silently when a vendor ships a new flow. Add the test to the register's quarterly review, alongside the tool inventory, and file the dated result. Placement verified in the free generator's flow shows the intended order: notice first, per person, logged — then the decision workflow proceeds.

  1. Mark, per tool, the first moment a person meets it or their data enters it — that point goes in the register
  2. Move the notice into that flow, before the tool runs — never footer-only, policy-only, or with the outcome
  3. Check conspicuousness on a phone mid-flow: its own block, plain language, no hunting, copy keepable
  4. Log placement per person — notice, text version, date, flow — as part of the decision record
  5. Re-run the applicant phone test after every flow or vendor change, and file the dated result

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

Where must the Colorado pre-use notice appear?

At the point where the person interacts with the tool — clear and conspicuous, before the tool is used on them, per the kit's checker data for SB 26-189.

Is a privacy-policy paragraph enough?

No. A general policy is a different document read at a different time; the duty specifies the point of interaction. The notice must reach the person in the flow, before the tool runs.

What if a workflow has two tools at two points?

Each interaction point is a placement point. Connecticut's interaction notice follows the same logic — it is owed when the person will directly interact with the tool.

How do we prove placement later?

Log it per person: the notice text version, the date, and the flow, as part of the decision record. The kit generates the notice per person and logs the generation, which makes placement a fact in the file.

Does placement include mobile rendering?

In practice, yes. Conspicuousness is judged where the person actually is — most applicants meet the notice on a phone. Test placement on a phone, mid-flow.

Build your first notice — free