Notice of automated action before effect
A notice the state's agent must issue before an adverse automated action takes effect, stating in plain language that automation acted and what it relied on. It gives the affected person, and their own agent, a chance to see and respond to a decision before it takes hold, instead of learning about it only after the fact.
The impact of agents
As government deploys agents that initiate adverse action, raising a debt, issuing a penalty, triggering enforcement, the first a person hears of it will be a demand with a due date. When a person's agent acts on the state, a review checkpoint can stand between draft and submission; when the direction reverses, the state's agent will act first and the person will discover the consequence afterward. The scale is already on record from before agents: a single automated letter template was used 82,217 times in the twelve months to October 2018, and the state was not bound by what its own letter said.
The disclosure duties now arriving stop at the entity level: a privacy policy or a departmental website tells the population that automation exists somewhere in the service. Nothing tells the person, on the decision that names them, that automation acted on them, why, and on what data, while there is still time to answer back. As initiating fleets scale, that gap becomes the default experience of adverse government action.
What must be verified
Government needs to be able to show, for every adverse state-initiated agent action, that the affected person received a proposed-action notice before the action took effect. The notice has to include four things: an explicit statement on the decision itself that an automated process produced it, plain-language reasons naming the data relied on, the date the action will take effect, and a machine-readable copy of the record that the person's own agent can check. The agency operating the initiating agent owes the duty to issue the notice, to hold evidence of its delivery, and to keep the stated basis consistent with the record it discloses.
Protecting access
The notice model fails the people who are hardest to notify: those without a stable address or a monitored digital inbox, those who do not read the service language, and those in crisis for whom a legalistic letter with a deadline is unreadable. For them, notice-before-effect degrades into effect-without-notice, the exact outcome the pattern exists to prevent, and a machine-readable record chiefly serves whoever already has an agent to parse it.
Keeping the path open
- Make the human-readable, plain-language notice the primary artifact, with the machine-readable record as its attachment rather than its substitute.
- Deliver through every channel in use: mail, phone, in person, assisted digital.
- Start the response window from confirmed delivery rather than dispatch.
- Route the unreachable to a human officer before effect, instead of converting an unanswered notice automatically into enforcement.
- Write the notice to read at a general literacy level, in community languages, and work with assistive technology, so a person can understand and answer it without any agent at all.
Response surface
Nothing takes effect before the person has been told, so the agency issues a proposed-action notice carrying the reasons and the date the action lands if unanswered.
Proposed action
PA-2026-0341An automated data-matching process produced this proposed assessment. No officer has reviewed it.
A rebate overpayment of $486.00 for March to May 2026.
- Reported income for March to May — $9,140, from employer payroll reporting.
- Rebate payments made over the same period — $1,212, from the rebate payment record.
- Income ceiling for this rebate — $8,400 a quarter; income above it reduces the rebate.
Nothing happens before 16 Jul. If you do not respond by then, the adjustment takes effect and a repayment notice follows.
The notice is the artifact that starts the clock: the response window runs from confirmed delivery, not from dispatch. An unanswered notice routes to a human officer before the effect date; it never converts on its own into enforcement.
Maturity
- Established
For the decision-level automation mention, operating in France since 2016 (CRPA article L311-3-1) and in Canada's Directive on Automated Decision-Making, which requires plain-language notice at every impact level.
- Emerging
For statutory notice duties with commencement dates: EU AI Act Article 26(11), deferred to 2 December 2027, and Australia's entity-level Australian Privacy Principles (APP) 1.7-1.9 disclosure from 10 December 2026, with Australia's post-Royal Commission automated decision-making (ADM) framework still in policy development.
- Frontier Headline
As a pre-effect gate, pairing the mention with a machine-readable record and making notice the condition of the action taking effect, which no surveyed jurisdiction requires.
Precedents
Robodebt Royal Commission recommendations 17.1 and 17.2. The final report set the baseline for automated government action: a clear path to review for those affected, departmental advice that automated decision-making is in use with a plain-language explanation of how it works, business rules and algorithms open to independent expert scrutiny, and a dedicated body to monitor and audit them. The Government response accepted, or accepted in principle, all 56 recommendations it addressed. The implementing framework remains in policy development.
France, CRPA article L311-3-1, the mention on the decision itself. The article requires an individual decision taken on the basis of algorithmic processing to carry an explicit mention informing the person, with the rules defining the processing and the principal characteristics of its implementation communicated on request. The Conseil constitutionnel treats these as live obligations that other provisions must affirmatively satisfy. It is a mandatory line on the adverse decision itself.
Canada's Directive on Automated Decision-Making, notice scaled to impact. The Directive requires plain-language notice at every impact level, through all service delivery channels in use, and from Level II up a detailed plain-language explanation accompanies any decision that denies a benefit or service or involves a regulatory action. Notice is proportioned to consequence on a published scale.
EU AI Act Articles 26(11) and 86. Article 26(11) requires deployers of Annex III high-risk systems that make or assist decisions about natural persons to inform those persons, and Article 86 grants a right to explanation for decisions based on such a system's output. Article 6(3) makes an Annex III system always high-risk where it profiles natural persons, which places data-matching debt recovery inside the classification. Neither duty is in force yet.
Australia, APP 1.7-1.9, the entity-level contrast. The Privacy and Other Legislation Amendment Act 2024 requires privacy policies to disclose the kinds of decisions made or substantially assisted by computer programs. It tells the population that automation exists, and never tells the person that automation acted on them.
What carries over to agent use
The mention itself transfers directly: France has operated it on individual decisions since 2016, and Canada's Directive shows how to scale the notice and explanation burden to the consequence of the decision, the same proportionate posture the library asks of every pattern. The Royal Commission recommendations translate the duty into the exact vocabulary of an initiating government agent: say that automation is used, explain it plainly, and keep a review path open.
What breaks in transit is timing. Every surveyed precedent attaches the notice to the decision as issued or after it: the French mention rides on a decision already taken, Canada's explanation accompanies the decision, and the AI Act duties inform a person already subject to the system. None makes notice a precondition of the action taking effect, and none contemplates a machine-readable record addressed to the person's own agent. The pre-effect gate, delivery verification at fleet speed, and the record format a user's agent can check against its own receipts remain undesigned.
Where things go wrong
Without the notice, the person discovers the action as its consequence: a garnisheed payment, a blocked service, a demand with interest already running. The pattern's own signal can also be gamed by the issuing side. An agency can bury the automation mention in boilerplate so it informs no one. It can also issue notices at machine speed with response windows no human can meet. That turns notice-before-effect into a compliance stamp on effect-first operation, with the notice itself invoked as a liability shield ('we told you'). At fleet scale the stakes compound: one faulty rule can put thousands of proposed debts with due dates into circulation before the first contest lands, and the record already shows a single automated template, used tens of thousands of times in a year, that the state declined to stand behind.
Sources
9 references
The instrument, the operating deployment, or the official record itself.
- Royal Commission into the Robodebt Scheme — Report (recommendations 17.1 and 17.2)
- Australian Government response to the Robodebt Royal Commission (PM&C)
- Légifrance — Code des relations entre le public et l'administration, article L311-3-1
-
Conseil constitutionnel — Decision no. 2020-834 QPC (Parcoursup algorithms)
Treats the CRPA L311-3-1 obligations as duties a Parcoursup admissions-secrecy provision had to satisfy, upholding that provision only subject to a stated condition. Cited for the existence of the obligation, not for the content of the reservation.
- Treasury Board of Canada — Directive on Automated Decision-Making, Appendix C (notice and explanation rows)
-
EUR-Lex — Regulation (EU) 2024/1689 (AI Act), Articles 6, 26(11) and 86
Dates as amended by the Digital Omnibus on AI: Article 26(11) is deferred to 2 December 2027, that date only. Article 86 was not deferred, yet its right attaches only to decisions based on an Annex III high-risk system's output, and that classification applies from the same date. Neither duty applies before then.
- Privacy and Other Legislation Amendment Act 2024 (Cth), as passed — APP 1.7-1.9
- ATO — View of Decision, Pintarich v Deputy Commissioner of Taxation [2018] FCAFC 79
Writing about the subject rather than the framework itself, including vendor commentary.