Rejection emails people do not hate
You will reject far more people than you hire. It is most of what you produce.
If you hire thirty people this year you will reject somewhere north of two thousand. Rejection is not an edge case in your process. It is the primary output.
Speed matters more than wording
A same week no is kinder than a beautifully written no after five weeks. People are running parallel processes and making decisions. Holding them as a backup while you finish another loop is the thing that generates public complaints, not the rejection itself.
Set a rule: nobody sits past the decision by more than two working days. Automate the early stage ones so this is achievable.
Match the effort to what they invested
Someone who clicked apply gets a clear, short, human template. Someone who did four interviews and a take home gets a phone call from the recruiter. The middle ground gets a personal email that references the actual conversation.
The rule is simple. If they gave you hours, you give them minutes.
Be careful with feedback
Detailed feedback at late stages is a genuine gift and carries real legal exposure in several jurisdictions. Two guardrails. Talk about the role and the evidence, never about the person. And never say anything you would not be comfortable seeing in writing in a tribunal, because you might.
Useful: the panel wanted more depth on incident response, and the person we chose had run that for three years. Not useful: you seemed nervous.
Say what happens next, precisely
Whether they can reapply and when. Whether you will keep their details and for how long, which in Europe is a legal requirement and in North America is increasingly a state level one. Whether a different open role fits, and if so, link it in the same message.
The silent partner test
Read your rejection template and imagine the recipient is a candidate you will want in eighteen months, a customer, and someone who will screenshot it. All three are frequently true. Most templates fail that test on the first line.