Consent and compliance

GDPR Article 22 in recruitment (2026): when automated hiring decisions are allowed, the safeguards and the case law

On this page
  1. What does Article 22 say, and which other articles go with it?
  2. When does an automated hiring step fall under Article 22?
  3. What did the Court of Justice decide, and why does it matter for vendor scores?
  4. Which exception can an employer use?
  5. What safeguards must be in place when an exception applies?
  6. How is the UK different since February 5, 2026?
  7. How does Article 22 sit with the EU AI Act and other regimes?
  8. Checklist for recruiters and staffing agencies
  9. Questions people ask

Under GDPR Article 22(1), a candidate has "the right not to be subject to a decision based solely on automated processing, including profiling," that produces legal or similarly significant effects, and Recital 71 names "e-recruiting practices without any human intervention" as an example. The EDPB-endorsed guidelines read this as a general prohibition. An automated rejection or shortlist is allowed only if it is necessary for entering into a contract, authorised by EU or member state law, or based on explicit consent, and then the employer must offer at least human intervention, a chance for the candidate to give their view, and a way to contest. The Court of Justice has held that a score can itself be a decision when the recipient gives it a determining role (SCHUFA, C-634/21, 2023) and that the explanation must describe the "procedure and principles actually applied" (Dun & Bradstreet Austria, C-203/22, 2025). In the UK, Articles 22A to 22D have replaced Article 22 since February 5, 2026. All of this is as of November 2026.

The full GDPR duty list for recruiters is on the GDPR checklist for recruiters, and the lawful basis for screening is on legitimate interest in recruitment. This page covers only automated decisions: when Article 22 applies, the exceptions, the safeguards and what the courts have said.

Not legal advice. This summarizes Regulation (EU) 2016/679 as adopted, the Article 29 Working Party's guidelines WP251rev.01 (endorsed by the EDPB on May 25, 2018), the EDPB's Guidelines 05/2020 on consent, Court of Justice press releases, and section 80 of the UK Data (Use and Access) Act 2025, as checked on November 17, 2026. National employment rules under Article 88 can add requirements; ask counsel in each country.

What does Article 22 say, and which other articles go with it?

ProvisionWhat it saysWhat it means in hiring
Art. 22(1)Right not to be subject to a decision based solely on automated processing, including profiling, with legal or similarly significant effectsNo fully automated reject, advance or shortlist decision unless an exception applies
Art. 22(2)Exceptions: (a) necessary for entering into or performing a contract; (b) authorised by EU or member state law with suitable safeguards; (c) explicit consentUsually (a) for high-volume shortlisting; (c) is weak in hiring
Art. 22(3)For (a) and (c): suitable measures, "at least the right to obtain human intervention on the part of the controller, to express his or her point of view and to contest the decision"A real review route for rejected candidates
Art. 22(4)No decisions based on special category data unless Art. 9(2)(a) explicit consent or 9(2)(g) substantial public interest applies, with safeguardsKeep health, ethnicity, religion and similar data out of automated decisions
Arts. 13(2)(f), 14(2)(g), 15(1)(h)Tell people about automated decision-making and give "meaningful information about the logic involved, as well as the significance and the envisaged consequences"Say it in the candidate notice and in access request answers
Art. 35(3)(a)A DPIA is required for systematic and extensive evaluation based on automated processing on which decisions with legal or similarly significant effects are basedDo a DPIA before deploying automated screening
Art. 88(1)Member states may set more specific rules for employee data, "in particular for the purposes of the recruitment"Check national law and works council rules

Recital 71 adds that safeguards "should include specific information to the data subject and the right to obtain human intervention, to express his or her point of view, to obtain an explanation of the decision reached after such assessment and to challenge the decision," and that controllers should use "appropriate mathematical or statistical procedures," correct inaccuracies and prevent "discriminatory effects."

When does an automated hiring step fall under Article 22?

Three conditions must all be met.

  1. There is a decision. Rejecting, shortlisting or advancing a candidate is one. Since SCHUFA, a score produced by someone else can count as the decision if the recipient relies on it decisively (see below).
  2. It is based solely on automated processing. The guidelines say a controller "cannot avoid the Article 22 provisions by fabricating human involvement." Oversight must be "meaningful, rather than just a token gesture," by "someone who has the authority and competence to change the decision," who should "consider all the relevant data."
  3. It has legal or similarly significant effects. The guidelines list "decisions that deny someone an employment opportunity or put them at a serious disadvantage" among decisions that can meet the threshold.
SetupSolely automated with significant effects?Why
Knockout answers or a match score below a cutoff reject applicants; nobody looksYesRecital 71's e-recruiting example
Recruiter bulk-approves the tool's rejections without opening profilesLikely yesA token gesture is not human involvement
Vendor score decides who gets an interview, and the employer never departs from itLikely yesThe SCHUFA reasoning on a score given a determining role
Tool ranks; a recruiter with authority reads each profile and the other information, then decidesNoMeaningful human involvement
Interview transcription and summaries read by the interviewer before scoringNoA person decides; other GDPR duties still apply

What did the Court of Justice decide, and why does it matter for vendor scores?

SCHUFA Holding (Scoring), C-634/21, December 7, 2023. According to the Court's press release, a credit agency's score "must be regarded as an 'automated individual decision' prohibited in principle by the GDPR, in so far as SCHUFA's clients, such as banks, attribute to it a determining role in the granting of credit." The case is about credit, but the structure fits recruiting: a vendor scores candidates, and the employer acts on the score. If the score effectively decides, the employer cannot assume Article 22 is out of reach because a person signs off at the end.

Dun & Bradstreet Austria, C-203/22, February 27, 2025. The Court's press release says the controller "must describe the procedure and principles actually applied" so the person can understand which of their data were used and how. It may help to explain "the extent to which a variation in the personal data taken into account would have led to a different result," while "the mere communication of an algorithm does not constitute a sufficiently concise and intelligible explanation." Where the controller claims trade secrets, it must give the information to the supervisory authority or court, which balances the interests. For recruiters, that means your vendor must be able to explain an individual rejection in plain terms, not just hand over a model card.

Which exception can an employer use?

  • Necessary for entering into a contract (22(2)(a)). The guidelines' own example is a business that "receives tens of thousands of applications" and may find it "not practically possible to identify fitting candidates without first using fully automated means to sift out irrelevant applications"; automated decision-making "may be necessary in order to make a short list." The controller must show necessity: "If other effective and less intrusive means to achieve the same goal exist, then it would not be 'necessary'." A role with 40 applicants will struggle to meet that test.
  • Authorised by law (22(2)(b)). Only where EU or member state law authorises the decision and lays down safeguards. General employment law rarely does this for private-sector screening; check national rules made under Article 88.
  • Explicit consent (22(2)(c)). The EDPB's Guidelines 05/2020 on consent say it is "problematic for employers to process personal data of current or future employees on the basis of consent as it is unlikely to be freely given." Candidates who fear rejection if they refuse are not giving free consent.

What safeguards must be in place when an exception applies?

  1. Human intervention on request by a reviewer who can change the outcome (Art. 22(3)).
  2. A way for the candidate to give their view and contest the decision, for example a reply address in the rejection message that reaches that reviewer.
  3. Information before the decision: the notice at collection states that automated decision-making is used, the logic involved and its consequences (Arts. 13(2)(f), 14(2)(g)). The guidelines say this means "the rationale behind, or the criteria relied on," not "a complex explanation of the algorithms."
  4. An individual explanation on access requests (Art. 15(1)(h)), to the standard set in Dun & Bradstreet. See candidate data access requests.
  5. Bias and accuracy controls: Recital 71's statistical procedures, error correction and prevention of discriminatory effects, documented in a DPIA under Art. 35(3)(a).
  6. No special category data in the decision, unless Art. 22(4) is met.
Example notice wording (adapt with your DPO)

We use [tool type] to [compare applications with the requirements in
the job posting]. If your application does not meet [the required
licence / minimum experience], it is declined automatically, without a
person reviewing it. We rely on [Article 22(2)(a): this step is
necessary to shortlist the volume of applications we receive].
You can ask for a person on our recruiting team to review the
decision, tell us your point of view, and contest it: [contact].
You can also ask us how the decision was reached for you.

Wording for wider AI notices is in our GDPR candidate privacy notice template.

How is the UK different since February 5, 2026?

Section 80 of the Data (Use and Access) Act 2025, in force for these purposes from February 5, 2026 under S.I. 2026/82, replaced Article 22 of the UK GDPR with Articles 22A to 22D. A decision is "based solely on automated processing if there is no meaningful human involvement," and a significant decision is one with a legal or similarly significant effect. Instead of a general prohibition, Article 22B limits solely automated significant decisions in two cases: decisions based on special category data (allowed only with explicit consent, or where contract or law and Article 9(2)(g) apply), and decisions where the processing relies on the "recognised legitimate interest" basis in Article 6(1)(ea), which are not allowed. Whenever such a decision is taken, Article 22C requires safeguards that give the person information about the decision and let them make representations, obtain human intervention and contest it. UK recording and notice duties are on recording interviews under UK GDPR.

How does Article 22 sit with the EU AI Act and other regimes?

Recruitment and selection systems are listed as high-risk in Annex III of the EU AI Act, which adds provider and deployer duties but does not replace Article 22; both can apply to the same tool. Dates and duties are on our EU AI Act recruiting guide. Outside Europe, Quebec has a narrower rule that requires notice and review rather than forbidding the decision: see Quebec Law 25 and automated decisions. For US rules, start with AI hiring laws by state.

Checklist for recruiters and staffing agencies

  1. List every step where software rejects, advances, shortlists or scores candidates.
  2. For each, test the human involvement: does a person with authority look at the profile and other information, and do they ever overrule the tool? Keep evidence.
  3. Where a step is solely automated, document the exception. For 22(2)(a), record the application volumes and why less intrusive means would not work.
  4. Add the human review, point-of-view and contest route to every automated rejection message.
  5. Update the candidate notice with the logic and consequences, and prepare an individual explanation for access requests with the vendor's help.
  6. Run a DPIA before deployment and keep bias and accuracy test results.
  7. Agencies: agree with each client who is controller for the screening step, who answers review and access requests, and whose reviewer can change the outcome.
  8. Check national employment rules and works council duties under Article 88 in each country you hire in.

Questions people ask

Does GDPR Article 22 ban automated rejection of job applicants?

As a rule, yes. Article 22(1) gives a person the right not to be subject to a decision based solely on automated processing that produces legal or similarly significant effects, Recital 71 names e-recruiting practices without any human intervention as an example, and the EDPB-endorsed guidelines read it as a general prohibition. It is lifted only if the decision is necessary for entering into a contract, authorised by EU or member state law with safeguards, or based on explicit consent, and then safeguards including human intervention and the right to contest apply.

Is a recruiter clicking approve enough to avoid Article 22?

Not if the click is a formality. The EDPB-endorsed guidelines say a controller cannot avoid Article 22 by fabricating human involvement: oversight must be meaningful rather than a token gesture, carried out by someone with the authority and competence to change the decision, who considers all the relevant data.

Can an employer rely on candidate consent for automated screening under the GDPR?

Explicit consent is one of the three exceptions in Article 22(2), but it is hard to use in hiring. The EDPB's consent guidelines say it is problematic for employers to process the personal data of current or future employees on the basis of consent, because consent is unlikely to be freely given in an employment relationship.

What did the CJEU decide in SCHUFA about automated decisions?

In Case C-634/21, decided December 7, 2023, the Court of Justice held that a credit agency's score must be regarded as an automated individual decision, prohibited in principle by the GDPR, in so far as its clients attribute to it a determining role in granting credit. The same reasoning is a risk for vendor candidate scores that employers treat as decisive.

What changed for automated decisions under UK GDPR in 2026?

Section 80 of the Data (Use and Access) Act 2025, in force since February 5, 2026, replaced Article 22 in the UK GDPR with Articles 22A to 22D. Significant decisions based solely on automated processing are allowed with safeguards: information about the decision, the ability to make representations, human intervention and a way to contest it. Stricter limits apply to special category data.