Back to blog

September 21, 202610 min

AGG and AI shortlisting: what German HR needs to check

This article is not legal advice and does not replace a review by privacy, employment counsel, or the works council. It turns the overlap of Germany’s General Equal Treatment Act, GDPR Art. 22, and human oversight under the AI Act into a checklist recruiting and HR ops can run before an algorithmic shortlist goes live.

  • AGG
  • AI recruiting
  • Compliance
  • Fair hiring
  • Germany

Why the AGG does not disappear behind GDPR when you add AI

Vendor checklists often stop at the DPA, EU hosting, and deletion deadlines. The AGG bites earlier: the advertisement and every criterion you use to sort applications. Algorithmic shortlisting does not rewrite the prohibitions — it scales them. A biased criterion in a spreadsheet hits one person; the same criterion in a model hits the whole funnel.

  • AGG § 1 protects against discrimination on grounds including ethnic origin, sex, religion, disability, age, and sexual identity
  • § 3 distinguishes direct and indirect discrimination — proxies (postcode, CV gaps, “culture fit”) can have the same effect
  • § 7 covers access to employment, so recruiting is in scope
  • § 11 covers job advertisements: they must not breach § 7
  • GDPR (Art. 22, transparency) and the AI Act (Art. 14, Annex III point 4) add duties — they do not replace the AGG

Where AI specifically raises the AGG risk

The model rarely stores the protected characteristic as a column. It stores correlates. That is why “we do not save gender” is not a defence on its own.

  • Training on historical hires reproduces whom you have hired — including the gaps
  • Keywords such as elite universities, sports clubs, or particular employers can proxy origin and age
  • Unstructured “culture fit” scoring is legally and diagnostically weak — and hard to explain when someone asks
  • Video or voice analysis is outside what most DACH teams can justify; leave it out
  • A rejection the score has already made, with the recruiter only confirming, is the Art. 22 pattern the CJEU described in the SCHUFA line: a decisive score, a human as a formality

Checklist before the shortlist goes live

Run this with legal or the DPO. “The vendor is GDPR-ready” is not a row on this list.

CheckWhyWhat “done” looks like
Job-related requirements profileAGG and assessment practice require criteria the role actually needs — not stereotypesMust-haves are written down, must-nots deleted, ad language checked against § 11
No knock-outs on protected characteristicsAge, sex, origin, mother-tongue language, mandatory photoThe form and parser do not filter on them; photo is optional or absent
Explainable matchingWithout a rationale nobody can object — then human-in-the-loop is theatreThe score hangs on 4–8 role criteria; the recruiter sees evidence and can override
No solely automated rejectionGDPR Art. 22; AGG files need a human decisionStatus changes only after a recruiter action; AI proposes, it does not decide
Inform applicantsGDPR Art. 13, AI Act transparencyThe application notice says AI ranks against role criteria and a human decides
Decision historyAGG claim window, supervisors, works councilRecommendation, override, and rejection live on the record — not only in Slack
Works council / co-determinationTechnical systems for monitoring conduct or performance, often plus AI expertiseThe rollout is agreed or you have a recorded reason why co-determination does not apply — not silent go-live

Fix the job ad first — before anything scores

The funnel is already skewed if qualified people never apply. Phrases such as “young team”, “digital native”, “German as a mother tongue” without a demonstrable requirement, or unnecessary physical must-haves, are the classic § 11 issue. A language check before publish is cheaper than explaining a homogeneous shortlist later.

  • Derive requirements from the role profile, not from the last person who held the job
  • State language as a CEFR level when the role needs it — not as a proxy for origin
  • Replace “team fit” with observable collaboration, or delete it
  • Use the same ad internally and externally; document side doors (“we already know them”) or you create an unchecked second track

Screening: structure it, justify it, allow dissent

Skills-first matching against a written profile is the antidote to gut feel — if a human reads the rationale. A rank without “why” forces recruiters to trust the model. That is the opposite of AI Act Art. 14.

  • Same core interview questions and the same rating scale — structured screening does not rescue an unstructured conversation
  • Blind early screening (name, photo, age later) reduces a known anchor; it does not anonymise later rounds
  • Overrides are a feature, not a bug: if nobody disagrees, oversight is dead
  • Rejections short and factual, without a fake rationale that opens a new AGG surface — keep the file internally

What software can carry — and what it does not certify

An ATS can enforce form fields, language flags, explainable scores, override logs, and deletion deadlines. It cannot find that your process complies with the AGG. Compliance stays with you: configuration, training, works-council agreement, a real last decision.

  • Job-ad checks and structured criteria reduce typical breaks — they are not an anti-discrimination certificate
  • EU hosting and a DPA answer privacy questions, not what the model sorts on
  • “Bias-free AI” as a vendor claim is a warning; serious vendors describe limits and human oversight
  • Counsel, the works council, and equal-treatment officers remain part of the rollout — not a footer link
See the job-ad check and fair first-screen workflow

Bottom line

AGG and AI shortlisting are the same question in two languages: what are we sorting on, and could we explain it to a supervisor, a court, and the person we rejected? Document the ad, the criteria, the rationale, and the human decision, and you cut risk and time-to-hire together. Buy only a score, and you buy speed — and the record that comes with it.

See the fair hiring approach

Frequently asked questions

Does the AGG apply if the AI never stores sex or age?

Yes. Indirect discrimination does not require the protected characteristic as a field. Correlates in the CV, language, or history can be enough. And § 11 already applies to the job ad, before you collect data.

Is a human who confirms the AI suggestion enough?

Only if that person can examine, challenge, and discard the recommendation — with a visible rationale. Clicking “accept” on an unexplained score is not effective oversight in practice (GDPR Art. 22, AI Act Art. 14).

Do we have to tell applicants that AI is used in screening?

You must inform them about the processing (GDPR Art. 13), clearly and at the form — not only in the website privacy policy. Say that AI ranks against role criteria and that recruiters decide. Detail belongs in the notice, the DPA, and internal documentation.

Does a job-ad language check make us AGG-compliant?

No. A check flags typical exclusionary wording. Whether your requirement is job-related, whether scoring proxy-discriminates, and whether rejections are documented remains your review — plus counsel. No product certifies AGG compliance.

Sources

  1. [1]Allgemeines Gleichbehandlungsgesetz (AGG), in particular §§ 1, 3, 7, 11, 15.
  2. [2]Regulation (EU) 2016/679 (GDPR), Art. 13 and Art. 22.
  3. [3]Regulation (EU) 2024/1689 (AI Act), Art. 14 and Annex III point 4 (employment and workers’ management).
  4. [4]CJEU, 7 December 2023, C-634/21 (SCHUFA) — automated decisions where a score is decisive.

Cookies and analytics consent

We use Google Analytics to understand usage and improve the product. You can accept or reject analytics tracking.