Guide · Published November 14, 2026 · Reviewed November 14, 2026 · Ingenious AI team · Not legal advice
Starting ADMT Use After January 1, 2027: California's Comply-From-First-Use Rule
The short answer: California's timeline has two entries, and the second is the stricter one: businesses already using ADMT for a significant decision get the compliance phase beginning January 1, 2027, but a business that starts using ADMT after that date must comply from its first use — the risk assessment completed before the first decision, the pre-use notice live at the first interaction, the opt-out routes working from the first application, the record capturing the first case. There is no ramp. This guide sequences a new-use launch so that 'first use' is a state the business is already in, not a deadline it discovers in arrears.
Check your duties and dates — free Build your first notice — free
What is 'first use'? It is the first significant decision for which the new ADMT use runs on a real person — not the contract date, not the pilot with synthetic data, not the internal test. Everything the duties require must therefore be sequenced before that first real decision, which is the planning fact this guide organises. The duty set itself is the standard California four from California CCPA ADMT Requirements.
Why first-use compliance changes the project plan
A phase-in forgives sequencing errors: build the notices a month late and the exposure is a month of legacy cases. First-use compliance has no legacy: the first real decision either was preceded by its assessment and notice or it was not, permanently. The project plan must therefore be gated on readiness rather than on the calendar — the tool does not touch a real person until the four duties are demonstrably live, tested with dry runs on synthetic or internal cases.
This also reframes procurement: the vendor timeline (contract, integration, configuration) is no longer the critical path — the compliance artefacts are. Contracts should be signed with the documentation questions already answered (intended uses, data categories, limitations), because the risk assessment on the critical path consumes them. The twelve vendor questions move from a renewal nicety to a launch gate.
Gate one: the risk assessment, completed and filed
Before the first use, the assessment must exist in its four elements — purpose (written narrowly enough to test, per the assessment guide), data involved (categories and sources, including the derived fields that carry weight), risks (named for your population, accuracy and discrimination first), and safeguards (mapped one-to-one to risks, with owners and cadences). 'Completed' means dated, versioned, and filed with the record the new use will write into — an assessment in a slide deck is a draft.
Dry-run the assessment against three synthetic cases, including one adverse outcome and one correction, and confirm the safeguards operate as written: the reviewer route works, the correction path reaches a person, the sampling the assessment promises is actually scheduled. Safeguards that exist only inside the assessment document are the launch version of token review.
Worked example: Solstice Home Services
Example — fictional business, real duty structure. Solstice, the fictional California platform from the thresholds guide, launched a new work-assignment tool in March 2027 — after the phase-in date — under the first-use rule. Its gated launch:
- Gate one: risk assessment completed and filed 3 weeks before launch — purpose scoped to assignment drafting for 2 service lines, 8 data categories with sources, 5 named risks, safeguards mapped with owners; dry-run on 3 synthetic cases, including an adverse outcome and a correction.
- Gate two: pre-use notice live in the production flow and phone-tested; opt-out offered via two routes (in-flow and named contact), both tested end-to-end with test contractors — the exception route considered and not relied on, by recorded choice.
- Gate three: access, correction, and appeal workflows staffed (owner plus deputy each) and dry-run; reasons and data-summary capture switched on in the tool's configuration before the first real case.
- First real use: the tool's first production week processes 120 assignments — every one preceded by its notice and captured in the record; the first access request arrives on day 9 and is answered from the record in under a day.
- First quarter: monthly audits run weekly for month one, then monthly; the launch findings are re-tested at the first quarterly review against real volumes, with volumes 30% above estimate and the rota re-sized accordingly.
Gate two: notice and opt-out, live in the real flow
The pre-use notice must be in the production flow — at the point of interaction, per person, logged — before the first real applicant arrives, and the opt-out position decided and implemented: two easy routes live and tested, or an exception position filed with its conditions evidenced (appeal staffed to the qualified-reviewer standard, security-only scope mapped, or the evaluation file current). The applicant phone test is the acceptance evidence, run on the production flow with test cases, before launch.
First-use launches have one advantage legacy programmes lacked: no historical template versions. The first notice version is version one, the profile is built once with monitored contacts, and the record starts clean. Protect that advantage by versioning from day one, so the clean start remains provable rather than merely true.
Gate three: response workflows staffed before volume
Explanations' California analogue (access answers: logic, outcome, purpose), corrections with re-runs, and the review/appeal queue must be staffed and dry-run before the first decision, because the first adverse outcome can generate all three requests inside its first week. At launch volumes the rota can be small — what it cannot be is unassigned. Name the owners, the deputy, and the acknowledgement standards on the launch checklist itself.
Instrument from the first case: reasons and data summaries captured at decision time (the habit that cannot be retrofitted onto cases already decided), opt-out reconciliation running from the first month, and the findings file opened with the launch's own documented positions — coverage, listing, role, exceptions — each with its checker output attached.
Launch day and the first quarter
On launch day the compliance state should be boring: assessment filed, notice live and logging, opt-out tested, queue staffed, record capturing. The first quarter then runs the ordinary cadence at heightened attention — the monthly audits read weekly for the first month (clock-free California still has answer-quality and honoring to prove), the first access answer and first correction treated as template-setting events and reviewed as such, and the findings re-tested at the first quarterly review against real volumes rather than launch estimates.
If the launch slips, the rule to hold is the gate, not the date: a tool that waits a week for its assessment is a delayed launch; a tool that launches a week before it is a compliance defect with a permanent first case. Sequence vendors and integrations around that ordering from the first project plan, and first-use compliance becomes a property of the launch rather than an aspiration attached to it. Start the sequence with the free checker result for the new use, and generate the launch notices from the free generator's document shapes.
- Gate the launch on readiness, not the calendar: the tool touches no real person until the four duties are demonstrably live
- Complete and file the risk assessment first — four elements, dated and versioned — and dry-run its safeguards on synthetic cases
- Put the notice and the decided opt-out position live in the production flow, and pass the applicant phone test before launch
- Staff access, correction, and review/appeal workflows with owners and deputies, dry-run each, and switch on reasons capture at the source
- Run the first month at heightened attention, treat the first requests as template-setting events, and re-test the launch findings at the first quarterly review
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
- California CCPA ADMT Requirements: What Your Business Must Do by January 1, 2027
- Colorado AI Act Automated Decision Notices: What to Send
- Adverse-Outcome Explanations in Plain Language
- ADMT Deadline Tracker: Which State Duties Land When
See all ADMT guides for the full set.
Frequently asked questions
What does 'comply from first use' mean exactly?
A business that starts using ADMT for a significant decision after January 1, 2027 must meet the duties from its first use: the risk assessment completed before that use, the pre-use notice live, the opt-out position implemented, and the record capturing the first case. There is no phase-in for new use.
What counts as the first use?
The first significant decision where the ADMT runs on a real person. Contracts, integration, and synthetic-data pilots are not uses — which is why the compliance gates can and must be completed during them.
How does this differ from the January 1, 2027 compliance phase?
The phase is for businesses already using ADMT for a significant decision when the date arrives: their duties land on January 1, 2027. A later starter gets no equivalent runway — its runway is its own pre-launch period, gated on readiness.
Can we launch with the opt-out exception instead of routes?
If an exception's conditions genuinely hold — a qualified-reviewer appeal staffed to standard, a security-only scope, or an evaluated hiring/admission/work-assignment use with safeguards — the position can be filed and relied on. It must be evidenced before launch like every other gate.
What if the launch date slips?
Hold the gate, not the date: delay the tool's first real use until the assessment, notice, opt-out, and workflows are live. A late launch is a schedule event; an uncovered first use is a permanent defect on the record.