← Back

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

← All guides

California ADMT Access Requests: Explaining the Logic, the Outcome, and the Purpose

The short answer: A California access request asks how automated decision-making technology was used in that person's decision. The answer the regulation requires covers the logic, the outcome, and the purpose (section 7222). It is an explanation duty triggered by request — distinct from Colorado's automatic 30-day adverse-outcome explanation — and the kit's data states no fixed day count for it. The practical challenge is assembly: the answer must be built from the decision record for one person, not written from memory about the tool in general.

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

What is an ADMT access request? It is a consumer's request, under the CCPA ADMT regulations, for an explanation of how ADMT was used in their significant decision. The kit's rules data states it as: a person can ask how the technology was used in their decision, including the logic applied and the outcome. The pre-use notice is what tells people this right exists — see California CCPA ADMT Requirements.

The three required contents: logic, outcome, purpose

Each element answers a different question. Purpose: what the tool was used for in this decision. Logic: how the technology works on inputs like this person's — the method in plain terms, not source code and not marketing. Outcome: what the decision in their case actually was. An answer covering two of the three — a common draft explains the tool's general logic and the outcome but never states the purpose — is an incomplete answer under the regulation's own list.

Plain language is the standard the pre-use notice already sets (section 7220 describes the notice as plain-language), and it is the only standard that makes an access answer useful. 'The model weighted multiple factors' is not logic; 'the tool scored your application on income stability, rental history length, and current debt load, in that order of weight' is the beginning of logic a person can question.

Individual, not generic: the answer is about one person's decision

The request is about their decision, so a template describing the tool in general does not answer it. The person-specific content — which data of theirs fed the decision, what the outcome was, which reasons were principal — lives in the decision record, or nowhere. This is why the kit stores a per-person record: notice, data summary, reasons, outcome, and dates in one chain per decision.

If your current process cannot produce the data summary for a named past applicant, that gap — not the drafting — is the compliance problem, and it is better discovered by an internal test request than by a real one. Run a test: pick a decision from last month and try to assemble the three elements. The exercise takes an afternoon and tells you exactly what to fix. The correction workflow that depends on the same record is covered in How to Handle ADMT Data Correction Requests.

Worked example: Bay City Auto Finance

Example — fictional business, real duty structure. Bay City Auto Finance is a fictional California lender. In its first quarter under the access duty, its request log shows:

How access differs from Colorado's explanation — and why the kit keeps both straight

Colorado's explanation is proactive: after an adverse outcome, the business sends a plain-language statement of the principal reasons within 30 days, whether or not anyone asks. California's access answer is reactive: it is owed on request, covers logic, outcome, and purpose, and carries no fixed day count in the kit's data. A business operating in both states needs both workflows, and confusing them produces two errors: waiting to be asked in Colorado (missing the 30-day clock), and promising Californians a 30-day deadline the regulation does not state.

The kit's interface keeps the distinction visible: Colorado decisions show the 30-day clock; California decisions show 'no fixed clock'. What a proactive explanation reads like is shown in Adverse-Outcome Explanations in Plain Language, and the proactive clock itself in Colorado's 30-Day Explanation Clock.

Receiving the request: intake is part of the duty

An access right people cannot exercise does not function. The pre-use notice names the access right; intake must then accept requests through a route a person can actually use, log each request with its date and the requester's decision reference, and route it to whoever assembles answers from the record. Misrouted requests — sitting in a general inbox while the person waits — are a process failure the record will show plainly.

Identity handling deserves one honest sentence: you need enough confidence the answer goes to the person it describes, and the request log should show what was checked. The kit takes no position on your verification method; it records that the request arrived, what was answered, and when — the facts any later review will ask for first.

Answering well: what good looks like

A good access answer is short, specific, and complete: purpose in a sentence, logic in a short paragraph naming the main inputs and their order of weight, the outcome in a sentence, and the person's next options — correction and, where it applies, the human-review appeal — with contacts. It does not argue with the requester, does not characterise the decision as fair (the kit never judges fairness), and does not disclose other people's data or the vendor's trade secrets beyond the logic the regulation asks for.

File the answer with the request in the record. Over a year, those filed answers become your best drafting asset: real questions, answered in plain language, ready to adapt. Start by confirming the duty applies to you in the free duties checker, and generate the underlying notices in the free notice generator so the record exists before the first request arrives.

  1. Confirm the access duty applies to your use with the free checker, and name the right in your pre-use notice
  2. Test-assemble one answer for a real past decision: purpose, logic, outcome — and fix whatever the test shows is missing
  3. Build intake that logs each request with its date and decision reference, routed to whoever answers from the record
  4. Check every draft against the three elements before it sends, in plain language a non-lawyer can act on
  5. File each answer with its request, and name the correction and review routes with contacts in every answer

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

What must a California ADMT access answer include?

How ADMT was used in the person's decision, including the logic, the outcome, and the purpose (regulation section 7222).

Is there a deadline for answering a California ADMT access request?

The kit's data states no fixed day count for California explanations. The 30-day explanation clock is Colorado's. This kit does not invent a California deadline.

How is an access request different from Colorado's explanation duty?

Colorado's is proactive — sent after an adverse outcome within 30 days whether or not anyone asks. California's is reactive — owed on request, covering logic, outcome, and purpose.

Can the answer describe the tool in general terms?

Not fully. The request concerns the person's own decision, so the answer needs their outcome and how the technology was used in their case, drawn from the decision record.

Who can make an ADMT access request?

A person who was subject to a significant decision involving ADMT — the pre-use notice tells them about the right to access information, per section 7220.

Build your first notice — free