Guide · Published November 14, 2026 · Reviewed November 14, 2026 · Ingenious AI team · Not legal advice
How to Write an ADMT Pre-Use Notice People Actually Understand
The short answer: A good pre-use notice does five things in order: it names the business and the tool, states the kind of decision at stake, describes the tool's role honestly, states the person's rights in that state (correction everywhere in the kit's data; opt-out and access in California; the equivalent paths elsewhere), and prints named contacts for correction and review. It is given before the tool is used on the person, at the point of interaction. Everything else — length, format, tone — serves those five jobs. The kit's builder generates exactly this structure; this guide explains the drafting choices inside it.
Check your duties and dates — free Build your first notice — free
What is a pre-use notice, as a writing task? It is the short document that must work for a reader who did not ask to receive it, in the middle of a process they care about, possibly on a phone. The legal content comes from your state's duty set (start with the free checker); the writing task is to make each required fact findable in one pass. The Colorado template is dissected line by line in Colorado ADMT Pre-Use Notice Template.
Step one: the opening sentence carries three facts
Draft the first sentence until it contains the business, the tool, and the decision: '[Business] uses [tool] to help make a [hiring / housing / lending] decision that may affect you.' Test every draft against substitution: if a competitor could paste their name in and change nothing else of substance, the sentence is describing a category, not your use. The tool's real name goes in — the kit's rules data for Colorado says the notice names the tool, and Connecticut's written notice requires its trade name expressly.
Resist the urge to open with reassurance ('we value fairness') or with the law ('pursuant to…'). The reader's first question is 'what is happening to me?' — answer it first. Legal framing can appear later, in the rights section, where the kit's template names the law the notice is given under.
Step two: describe the tool's role as it actually is
The role sentence is where notices go to be vague: 'technology assists our team'. Write instead what the tool does and what a person does with its output: it scores, ranks, screens, recommends; a named role reviews the output and can decide otherwise — or, if in truth the output is usually decisive, the sentence should reflect the weight it really carries. California's human-decision test cuts the same way from the other side: token review does not make decision-making human.
A practical test: read the role sentence to the person who runs the workflow. If they say 'well, sort of', rewrite until they say 'yes, that's what happens'. That person's confirmation is worth more than any drafting polish. The honesty standard is explored further in Meaningful Human Review.
Worked example: Willow Creek Home Care
Example — fictional business, real duty structure. Willow Creek is a fictional home-care agency hiring care workers in Colorado. It rewrites its pre-use notice using the five-part structure, and the before/after shows in its next hiring round:
- Before: one paragraph on the careers page saying the agency 'uses innovative technology to support fair hiring' — no tool named, no decision named, no contacts.
- After: a per-applicant notice naming the agency, the screening tool, and the hiring decision, with the tool's role described as the operations manager confirmed it actually works.
- Notices produced: 88 notices in the round, each generated and logged per applicant before screening.
- Reader behaviour: 4 applicants use the correction contact before decisions (two correct a certification date, two an address), and 3 later request review using the contact printed on their notice — the paths work because they were printed.
- Record kept: the approved notice text version, the 88 per-person generations, and the follow-on contacts sit in one chain, held for three years.
Step three: rights in the reader's verbs, contacts in real names
Write the rights section in the reader's verbs: 'You can ask what data about you the tool used. You can ask us to correct data that is wrong. If the decision goes against you, you can ask for an explanation and for review by a person.' Then attach a contact to each verb — a name or a role and an email that is monitored. A right phrased as a noun ('correction rights are available under applicable law') with no contact is the single most common drafting failure the kit's template is designed to prevent.
Match the rights to the state. California's notice names the opt-out and access rights; Colorado's centres on correction, explanation, and review; Connecticut's written notice has its own specified contents. Drafting one blended 'US notice' produces a document that overpromises in one state and underdelivers in another.
Step four: placement and timing are part of the writing
A notice is not finished when the text is approved; it is finished when it reaches the person before the tool runs, at the point of interaction, in a form they can keep. Write for the actual surface: the application flow, the portal step, the letter that precedes the assessment. If the surface truncates text, the five working parts must survive the truncation — which argues for putting them early and keeping the notice self-contained rather than linked.
Check the mobile rendering. Most applicants meet the notice on a phone, mid-flow, with limited patience. Short paragraphs, the contacts visible without scrolling through legal text, and a copy the person can save or that is emailed to them — these are compliance properties, not design preferences. Placement failure modes are catalogued in Notice Placement.
The pre-send check: five questions before any notice goes out
Run the finished draft against five questions. One: could the reader name the tool, the business, and the decision after one read? Two: does the role sentence match the workflow as the operator describes it? Three: does every right named have a working contact beside it? Four: does the notice match this state's duty set — no borrowed deadlines, no missing rights? Five: will this exact text be logged with the date it was given, per person?
If any answer is no, the notice is a draft. The kit's generator exists so most of these checks are structural — profile-driven contacts, state-driven rights, per-person generation with logging — but the role sentence and the plain-language pass remain yours. Generate a test notice in the free generator, read it as the applicant, and then decide what to change.
- Rewrite the opening sentence until it names your business, your tool, and the kind of decision — all three
- Confirm the role sentence with the person who runs the workflow; rewrite until they say it is accurate
- Phrase every right as something the reader can do, and put a monitored, named contact beside each one
- Match the rights and contents to the state — no borrowed deadlines, no blended US notice
- Check placement, timing, and mobile rendering, then log the exact text given to each person with its date
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
- Colorado ADMT Pre-Use Notice Template: What the Notice Must Say, Line by Line
- Meaningful Human Review: What 'Meaningful' Requires in Practice
- Notice Placement: Clear, Conspicuous, and at the Point of Interaction
- Colorado AI Act Automated Decision Notices: What to Send
See all ADMT guides for the full set.
Frequently asked questions
How long should a pre-use notice be?
As long as the five working parts need and no longer: business and tool, decision kind, the tool's role, the person's rights in that state, and named contacts. The kit's template fits on one screen or one page side.
Must the notice name the actual tool?
Yes. Colorado's kit data says the notice tells the person the tool name, and Connecticut's written notice requires the tool's trade name expressly.
Can one notice serve all states?
No. The rights differ: California names opt-out and access rights; Colorado centres on correction, the 30-day explanation, and review; Connecticut's written notice has specified contents including data categories and sources.
When is the notice given?
Before the tool is used on the person, at the point where they interact with it — not with the outcome and not after the decision.
What is the most common drafting failure?
Rights without contacts: a notice that mentions correction or review in the abstract but prints no name or monitored address the person can actually use.