Do we really have to reject everyone, even unqualified applicants?

No direct legal duty, but an indirect one: silence in AGG context can be inference reversing burden of proof. A 30-second standard rejection is cheaper than the risk. Plus: reputation protection - candidates remember ghosting five years later.

How concrete must the reason be?

Concrete enough to show factual assessment happened. '5+ years Python needed; you have 2' is concrete. 'There are more qualified applications' isn't enough. But caution: no detail statements you can't defend ('your answer to question 3 was too short' opens debate risk).

What about the timeframe for rejection?

Standard: within 14 days from application receipt or from final hire (whichever first). For very large funnels (300+) a receipt saying 'You'll hear from us in 21 days' can extend, but not indefinitely. Beyond 35 days of silence is risk zone.

Should we share the KI score reasoning with applicants?

On request yes, proactively no. The KI reasoning can express what we'd say, but it can also say wrong things ('person has 8 years of experience' for a 3-year CV) - you don't want that in a rejection. Recommendation: HR writes the rejection reason; KI score stays internal.

KI BMS

Pricing

Guides

Fair, legally safe rejection mail in recruiting - templates + anti-patterns

A rejection isn't just politeness, it's risk management. Here are three templates for three situations plus the five wordings that are AGG-risky.

Rejection

AGG

Guide

Julia YukovichCo-Founder + CEO

·March 24, 2026·

4 min read

Key takeaways

Concrete rejection > vague rejection. '5+ years backend needed, you have 2' is legally safer than 'unfortunately doesn't fit'.

Rejection within 14 days is standard; over 30 days of ghosting is AGG-risky because an inference effect arises.

Never reference sensitive attributes (age, gender, origin, religion, disability) - not even implicitly.

Talent-pool offer is friendly, BUT only with explicit consent to retention.

Step by step

1. Create three templates for three situations

Knockout (prereq missing - e.g. no EU work permit): in 24h, brief, friendly. Structurally qualified but not fit (skills mismatch): in 14 days, with concrete reason. Top candidate, role filled (fit, but someone else hired): in 7 days, with talent-pool offer.

2. Concrete reason instead of vague politeness

Instead of 'unfortunately doesn't fit' write 'for this role we need 5+ years Python backend; your focus is frontend'. Concrete + factual + safe. If you can't be concrete, you probably didn't honestly review the application.

3. Activate auto-send on stage change

In KI BMS: create template, set auto-send on 'rejected' stage. Each rejection auto-sends when HR changes stage - no 'oh, I forgot to send'. Variables like {candidate_first_name}, {job_title}, {rejection_reason} substitute.

4. Talent-pool offer with explicit consent

On top-candidate rejection offer: 'Want to stay in our talent pool? We'd contact you for matching roles in the next 12 months.' With click link confirming retention. KI BMS stores the extension with date + source.

5. AI Act notice for KI-pre-sorted rejections

If rejection involves KI score (never exclusively, but as ordering factor), include one sentence: 'Your application was pre-assessed with KI support; the final decision was made by humans. On request we'll explain the logic.' KI BMS adds the line automatically in any auto-mail.

Why most rejection mails are bad

Three patterns. One - vague. 'Unfortunately we chose other applications' is factually empty; it doesn't inform, just discharges duty. Candidate learns nothing and (often rightly) suspects discrimination. Two - too late. 21 days silence + standard rejection signals 'we forgot you', doubling the reputational damage. Three - opens risk via detail statements that don't hold ('looking for someone with more energy' is an AGG alarm).

The five wordings you can't use

One - 'we're looking for someone younger / older'. Direct AGG violation (age). Two - 'the role fits a man / woman better'. Direct AGG violation (gender). Three - 'native German speaker' as requirement. Indirect AGG violation (ethnic origin); replace with 'business-fluent German C1'. Four - 'someone who fits the team'. Vague + 'team fit' is often shell for sensitive attributes; risk. Five - 'you seem overqualified'. Often code for age discrimination; hard to defend in court.

The honest answer to 'can I ghost?'

Legally: silence isn't directly forbidden but is risky. If an application stays unanswered 30+ days and the candidate later files an AGG claim, silence can be treated as inference of discrimination - reversing the burden of proof. Not an accusation, just the consequence of silence.

Practically: a standard rejection within 14 days is cheaper than a later AGG claim. KI BMS has an auto-send template 'receipt with timeframe'; after 21 days a 'we're reviewing' mail goes automatically; after 35 days the standard rejection if no one changed stage. Three mails, three legal protective layers.

FAQ

Frequently asked

Share this article

Try KI BMS

Free plan, no credit card. We host in Germany. You can export and delete everything self-serve.

Written by

Julia Yukovich

Co-Founder + CEO

Julia is one of the Co-Founders. She handles design, product direction, and most of the support replies that arrive in the morning.

julia.yukovich at aicuflow dot comLinkedIn