Article 86 Right to Explanation: How Employees Can Challenge an Automated Decision
Article 86 turns an opaque score into an answerable decision. What the right covers, how it differs from GDPR Article 22, and the explanation pack to hold before the first request lands.
Workplace AI disputes rarely start with a regulator. They start with a person: a supervisor whose preferred shifts stopped appearing, a candidate rejected seconds after uploading a CV, a manager placed on a performance plan citing an “engagement trend” nobody can show her. The question is always the same: why?
Article 86 gives a statutory answer — the right to obtain from the deployer clear and meaningful explanations of the role of the AI system in the decision-making procedure and the main elements of the decision taken. For anyone deploying Annex III high-risk systems, that AI Act Article 86 right to explanation is where compliance stops being documentation and becomes a conversation you must hold.
What Article 86 actually gives an employee
Four elements must all be present:
- A decision taken by the deployer. Not the vendor. The employer using the system owns the duty.
- A decision taken on the output of an Annex III high-risk system, except point 2 — creditworthiness and essential services, where Union law already gives the right.
- Legal or similarly significant effects. Refusal of a role, shift reassignment, pay band change, disciplinary step, redundancy scoring.
- An adverse impact the person considers to affect health, safety or fundamental rights — a set including human dignity and protection of personal data. Harm need not be proved first.
Two features catch deployers out. The right is not limited to employees: applicants and rejected candidates are affected persons in Annex III point 4 decisions. And it does not require the decision to be solely automated — if the output was the basis, a human rubber-stamp does not remove it. Recital 171 calls this a decision “based mainly upon the output” of the system.
Article 86(2) disapplies the right where Union or national law provides exceptions, and Article 86(3) limits it to the extent the right is not already provided under Union law. That is why GDPR supplies much of the practical answer today, and why the two run together rather than in sequence.
GDPR Article 22 and AI Act Article 86: two rights, one inbox
GDPR Article 22 restricts decisions based solely on automated processing that produce legal or similarly significant effects, unless an Article 22(2) exception applies; Article 22(3) then requires human intervention, a point of view and the right to contest. Recital 71 adds “an explanation of the decision reached”, naming e-recruiting without human intervention as the paradigm case. “Meaningful information about the logic involved” comes from Articles 13(2)(f), 14(2)(g) and 15(1)(h).
| GDPR Article 22 | AI Act Article 86 | |
|---|---|---|
| Trigger | Decision based solely on automated processing with legal or similar effects, unless an Article 22(2) exception applies | Deployer decision based on an Annex III high-risk output (point 2 excluded) with effects the person considers adverse |
| Scope | Personal data only, and only where no meaningful human was in the loop | Any Annex III high-risk output, including where a human was formally involved but the output was the basis |
| Response | Human intervention, point of view, contest, meaningful information about the logic involved | Clear, meaningful explanation of the system’s role in the decision-making procedure and the main elements of the decision |
| Deadline | One month under Article 12(3), extendable by two, notice in the first month | No numbered deadline — align to the same clock rather than invent a slower one |
| Remedy | Complaint to a supervisory authority, court action, compensation (Arts. 77, 79, 82) | Complaint to the market surveillance authority under Article 85, with every GDPR route still open |
One request, two duties, one response: state what the system did, what the human decided, and why.
Where the right bites in a mid-market workplace
Annex III point 4 covers recruitment and selection, decisions on terms of work-related relationships, and monitoring and evaluating performance and behaviour. Most HR technology sits in those three sentences.
- A 600-person logistics operator runs a task-allocation engine proposing shift patterns. A supervisor’s open shifts are reallocated until her weekends disappear. She asks why.
- A retail group screens applicants with a ranked shortlist. A rejected candidate asks what the ranking used — she is inside Article 86 whether or not she signed a contract.
- A consultancy feeds productivity analytics into performance conversations. A consultant is put on an improvement plan citing “low collaboration signals”. The measurement is the decision’s foundation, so the explanation duty attaches.
Article 26(11) reinforces this: deployers of Annex III systems that make, or assist in making, decisions about natural persons shall inform those persons that they are subject to the system’s use. Silence at deployment guarantees confusion at contest.
The explanation pack: prepare before the first request
Reconstructing a decision the week after it is disputed is how mistakes are made. Hold one pack per system, refreshed on every model or rule change:
- System identity. Name, version, provider, intended purpose, Annex III classification and reasoning, instructions of use.
- The role the system played. What the output actually was — score, rank, flag, recommendation — and whether it was decisive. Name the human holding Article 26(2) oversight: competence, training, authority.
- The main elements of the decision. The decision, date, decision-maker, the factors that carried weight, and what would have to change for a different outcome.
- The logic in plain language. The main factors, the direction each pushes the outcome, the input data used or ignored. Article 78 protects trade secrets, including source code, in regulators’ hands — not a licence to withhold an explanation. Explain the reasoning, not the weights.
- The evidence trail. Input snapshot, issued output, logs. Article 26(6) sets a six-month floor, shorter than most dispute cycles, so retain decision evidence for the life of the decision plus its appeal window.
- An owner and a template. One named reviewer, one fixed structure, one sign-off path that does not depend on a vendor answering email.
How requests arrive, and how long you have
Requests rarely announce themselves as Article 86 requests. They arrive as a data subject access request quoting GDPR Article 15, an HR grievance, a works council enquiry for a member, an appeal against a disciplinary outcome, or a terse email from an interview. They also arrive indirectly: a complaint to a data protection authority or to the market surveillance authority under Article 85, reaching you later as a request for information you did not know was coming.
Triage on three questions — which system, which decision, which person. Log the date received, route jointly to HR, privacy and the system owner, and answer every right in play at once. A request framed as access is usually also an explanation request and a contest under Article 22(3).
Article 86 sets no day count, and that is not a gap to exploit. Where personal data is involved the GDPR clock runs from receipt: one month, extendable by two, with notice inside the first month. Acknowledge within three to five working days, fix the response date at acknowledgement, and hold the evidence by day twenty. The clock starts when the request reaches any part of the organisation.
Works councils, DPIAs and the standing evidence base
Article 26(7) requires employers to inform workers’ representatives and affected workers before a high-risk system is put into service or used at the workplace. In Germany, co-determination over technical monitoring of behaviour or performance makes this a negotiation rather than a notice; other member states add consultation rights on their own timetable. Those agreements often say how decisions will be explained — write that clause deliberately, because it becomes your standing procedure.
The DPIA is the second pillar. Systematic monitoring and large-scale profiling normally trigger GDPR Article 35, and the explanation protocol belongs inside it as a documented mitigation: what is produced, by whom, within what period, from which records. A fundamental rights impact assessment under Article 27 is not triggered by a private-sector HR use case, so the DPIA carries the weight.
What happens when a decision is contested and you refuse
- Article 85 complaint. Any person with grounds to consider an infringement may complain to the market surveillance authority, without prejudice to other administrative or judicial remedies; a worker’s report under Article 87 is separately protected.
- GDPR enforcement. Infringement of data subject rights carries fines up to €20 million or 4% of worldwide turnover, plus compensation for material and non-material damage.
- AI Act penalties. Breach of deployer obligations under Article 26 sits in Article 99(4) at up to €15 million or 3%; misleading information to an authority is €7.5 million or 1%; SMEs pay the lower of the two measures.
- The honest nuance. Article 86 does not appear by number in the Article 99 tiers. Refusals rarely arrive alone: they follow a failure to inform the worker, to exercise oversight or to keep logs — each finable once the Annex III regime applies on 2 December 2027. Today the sharper edge is GDPR, which applies now.
A refusal that is really a failure of preparation is the most expensive kind: no argument to make, only a record of not having one.
How to check your own position
- List every Annex III system touching terms, shifts, pay, progression or monitoring, with the classification reasoning written down.
- Confirm a named human oversight owner per system, with written authority to suspend it.
- Check that the Article 26(11) notice went out before use, not after the first complaint.
- Pull a decision file from six months ago and rebuild the explanation from your records. If you cannot, the retention window is wrong.
- Send a test request marked “AI decision” to your HR inbox and count the days until one named owner replies.
- Draft the explanation template now, review it with the works council where one exists, and record the response clock in procedure.
- Re-run after every model, rule or vendor change; an explanation written against last year’s version is a wrong explanation.
Frequently asked questions
Can an employee demand the source code or the model weights?
No. Article 86 requires the system’s role in the decision-making procedure and the main elements of the decision, not the internals; Article 78 protects trade secrets, including source code, in regulators’ hands. You do owe the plain-language logic, the factors that moved the outcome, and the personal data behind it where GDPR Article 15 access applies.
Does Article 86 apply to rejected applicants as well as employees?
Yes. It runs to any affected person subject to a decision based on an Annex III high-risk output, and Annex III point 4 covers recruitment. Contract status is irrelevant: an applicant rejected by a ranked shortlist has the same right as a worker passed over for promotion.
What if a human made the final decision?
Article 86 still applies where the decision was taken on the system’s output. Nominal human review does not extinguish the right, and GDPR Article 22 bites where processing is effectively automated. Your explanation must say what the system produced and what the person decided on top of it.
How long do we have to answer?
Article 86 sets no period of its own. Where personal data is involved, GDPR Article 12(3) gives one month from receipt, extendable by two, with notice inside the first month. Treat that as the operative deadline and answer both rights together.
Does Article 86 apply now or only from December 2027?
Article 86 has applied since 2 August 2026, while Article 26 deployer duties apply from 2 December 2027. Because Article 86(3) defers to rights already provided under Union law, GDPR answers in the meantime — so the process has to work now.
What is the fastest way to appeal an AI decision?
Put it in writing to HR or the grievance channel, name the decision and the system if you know it, and ask both for an explanation under Article 86 and to contest under GDPR Article 22(3). Escalate to your works council or union, then to the data protection authority or market surveillance authority if no answer comes.
Put this guide to work on your own estate.
Run the free exposure scan to see which of these articles actually apply to your company — 12 questions, four minutes, no card. Confirm your email and the full report unlocks.
- Free forever plan
- No credit card
- EU-hosted · GDPR-native
Build a live AI register in minutes — upgrade only when you need the audit pack.