How to write fair rejections without spending hours on them

The rejection is the only mail that, 100% of the time, takes something away from someone. Even an invite is a promise that can still be kept; a rejection is a door closing. That's why rejections take many HR people longer than invites.

Second layer: poorly written rejections often do more employer-brand damage than the rest of the careers page repairs. A small investment in the rejection template pays back several times over per quarter.

The template is short and has exactly three parts: name salutation, one sentence reason, a closing offer (talent pool / 'glad to hear from you in 6 months'). Variables like {candidate_first_name} and {job_title} resolve at send.

Plain text: 'Hi {candidate_first_name}, thank you for applying for {job_title}. We chose another candidate because their profile was closer to [specific requirement]. Your background is strong - with your consent we'll keep you in the talent pool and reach out for the next matching role. Best, {recruiter_name}.'

First: a specific reason sentence. Not 'unfortunately it didn't work out', but 'we're looking specifically for 5+ years backend in Python; your focus is on frontend development.' That reads as honest, not defensive.

Second: a real closing offer. Talent pool only if you actually use it. Otherwise drop it - an empty promise is worse than none.

Anti-pattern 1: 'It wasn't you, it was the market.' Sounds kind, reads as a lie, candidates notice. Anti-pattern 2: 'We can't share reasons for legal reasons.' Wrong - GDPR fully allows specific feedback, German AGG explicitly accommodates a sober, specific justification. Anti-pattern 3: four paragraphs about your company + a final paragraph that holds the actual rejection. Nobody reads that far.