How to write a rejection email people don’t resent

Most rejection emails are bad in one of two ways: so vague they say nothing, or so padded with false warmth that the person has to read three paragraphs to find the answer. A good one is four lines, arrives when you said it would, and does not pretend. Here is the template we ship, and the reasoning behind each line.

What it has to do

Four things, in this order of importance:

1. Give the answer, early. The reader is scanning for one piece of information. Make it findable in the first two lines.
2. Close the loop. They should finish knowing this is over, not wondering whether to follow up.
3. Not insult them. No fake praise, no invented reasons, nothing they can tell is a template pretending not to be.
4. Not create obligations you won't keep. "We'll keep you on file" is a promise. If you will not look at that file, do not make it.

The template

Four placeholders, all of which the sender fills automatically. There is no score in it and no personalised reasoning, and both of those absences are deliberate.

Line by line

"Thank you for applying… and for the time you put into it"

One sentence of acknowledgement, not three. It names the specific role, so the reader knows immediately which of their applications this is — a real problem for someone applying to fifteen places.

"After reviewing every application"

Only write this if it is true. If you stopped reading at sixty, say "after reviewing applications". The claim that everyone was read is one candidates care about, and in a manual process it is also the claim most likely to be false.

"…other candidates whose background more closely matches"

The answer, stated plainly, in the second paragraph. Not "we have decided to pursue other avenues at this time". Not a sentence that could be read as maybe.

"…not a reflection of your ability"

This one is worth its space because it is true and the reader does not know it. Most rejections are about fit against one specific set of requirements, not about the person's worth, and saying so costs nothing.

What is not in it

No score. No breakdown. No "you scored 41 out of 100 on skills match". A score is an internal working note, taken against one posting, with known blind spots — it cannot see anything the CV did not say — and handing it to a candidate as a verdict is indefensible. Our product will not put one in a candidate email at all.

What to cut

• "Unfortunately" in the first line. Not wrong, just a delay. The sentence works without it.
• "We had an overwhelming number of high-quality applicants." Every rejection says this. It has stopped meaning anything and now reads as filler.
• "We'll keep your CV on file for future opportunities" — unless you have a file, look at it, and can name a time you hired from it. Otherwise it is a small lie that costs you nothing and costs them a month of waiting.
• Feedback you are not going to give. "Happy to give feedback if useful" generates replies you will not answer, which is worse than not offering.
• Anything implying a decision was close when it was not. Kindness that is not true is legible, and it reads as management rather than respect.

Timing, which matters more than wording

A plain email in week one beats a beautiful one in week five. Two rules:

Put a date in the job posting — "you will hear from us by the 30th, either way" — and then keep it. That single line converts your silence from ambiguous into a commitment with a deadline, which is the only thing that reliably makes the close-out happen.

Send when the shortlist is set, not when the offer is signed. Waiting until the role is closed means everyone else waits weeks for information you already had. The people who did not make the shortlist are not affected by what happens next.

Held is not rejected

There is a third state and it deserves its own message. Someone strong who lost to a stronger candidate is not a "no" — they are a "not for this role". If you might come back to them, say exactly that, and say what happens next: "we are keeping your application for the Analyst role opening in November, and will write to you then either way."

In our own system, candidates below the cut-off sit in a held state, not a rejected one, and nothing expires them into a rejection. No software should close someone out on its own, and a bulk close-out should name every person in it before it sends.

When to write something personal

Rarely, and for a specific reason. If someone reached a final interview, or spent hours on a work sample, a template is the wrong instrument — three specific sentences from the person who interviewed them is worth more than any amount of polish in a bulk send.

For everyone else, the template is not a lesser thing. It is an honest thing that arrives on time, and almost nobody sends anything at all — including us, which we have written about with our own numbers.

If your process runs in Bangla

Send it in the language they applied in. A candidate who applied and interviewed in Bangla receiving a formal English close-out is being told, in a small way, which language the real conversation happened in. The same care that applies to the interview applies here, and it is cheaper to get right.