← Back to Blog
October 15, 2026 · 7 min read · By Rezumz Team

How to Write a Rejection Email That Keeps Good Candidates

A good rejection email is sent promptly, says no in the first two sentences, thanks the person for something specific, gives a short honest reason or says you cannot give one, and, where it is true, invites them to apply again. Candidates forgive a no. They do not forgive silence, a vague message that hides the answer, or a promise to keep in touch that nobody means.

Why the rejection email matters more than it seems

Most people you reject today are people you may want tomorrow: a strong runner-up, a person who was right for a different team, or someone who will be a customer or a referrer. They also talk. A decent rejection costs you a few minutes. A poor one can turn a near miss into someone who tells friends not to apply. The email is also the last thing the candidate experiences of your hiring process, which colours how they remember all of it.

Send it quickly and lead with the answer

Send it quickly. Tell people as soon as the decision is made. Do not wait until the new hire has signed. If you have said you will reply by a date, keep to it. Where a decision depends on other candidates, say honestly that you are still deciding and give a date for the next update. People who have given time to interviews deserve an answer sooner than people who only applied, and your message should reflect that. Lead with the answer. Do not bury the decision under three paragraphs of thanks. State it early and kindly: "We have decided not to move forward with your application for this role." Then thank them for something real, such as the time they spent preparing a task or the way they described a project. A general "we were impressed by your background" sounds like a template, because it is one. Treat the timing as part of the message. A rejection that arrives weeks after the last interview feels like an afterthought however kind the words are. If your process is slow, say so in advance and share the expected dates, so that a late answer is not a surprise. Apply the same care to every stage. A person who applied online and heard nothing for a month deserves a brief message, even an automated one, written in plain language. People remember the tone of a rejection long after they forget the role.

Give a reason you can stand behind

A short reason is the most useful thing you can give, and the most risky if it is careless. Stick to job-related, factual points, such as "we chose a candidate with more experience managing a team of this size." Do not guess at personality, and never mention anything that touches protected characteristics. If your company policy or your lawyers advise against giving reasons after interviews, say that you are not able to give detailed feedback, and be polite about it. Some employers will give reasons only to people who ask. Check what your policy and local rules allow.

Match the detail to the stage, and leave the door open only if you mean it

Tailor the level of detail to the stage. Someone rejected at application stage needs a brief, respectful note. Someone who has done two interviews and a take-home task deserves more: a call or a more personal email, and where you can, one or two sentences of useful feedback. The more effort the candidate gave, the more you owe in return. Leave the door open only if you mean it. If the person was a strong runner-up, say so and ask whether you may contact them about future roles. Then actually do it, with their permission recorded. Do not write "we will keep your CV on file" unless you will. Keeping personal data has legal limits in many countries, including a requirement in some to have a reason and a time limit, so tell the candidate how long you will keep it. For runners-up, a short phone call before the email is worth the extra five minutes. It lets you be warm, explain the closeness of the decision, and hear whether they would like to stay in touch. Keep a list of people you promised to contact, with the roles that might suit them, and check it when a new job opens. If you say you will keep someone in mind, put a reminder somewhere you will see it.

A simple structure to adapt

1. The decision in one sentence. 2. A specific thank-you. 3. A short, job-related reason, or a polite note that you cannot give feedback. 4. If true, an invitation to apply again or a request to stay in touch. 5. A kind close with a named sender. Keep it under 150 words. Write it as you would want to receive it.

Rules differ by country

Rules on how long you may keep candidate data, whether you must give reasons, and what feedback may reveal differ between countries and even regions. Check the rules where you hire before you settle on a template.

Common mistakes to avoid

Several habits turn a neutral no into a bad experience. Sending nothing is the most common, and the most remembered. Sending the message from a no-reply address with no way to ask a question makes the company feel closed. Praising the candidate heavily and then rejecting them can sound insincere unless you explain what tipped the decision. Giving feedback on personality or fit, instead of on evidence from the process, is hard to defend and hard to act on. Promising a future role you have no plan to fill raises hopes for nothing. Finally, avoid copying the wrong name or the wrong role into a template. Read each message once before it goes. A small error in a rejection is more noticeable than in almost any other email you send.

In Rezumz

In Rezumz you can choose Email this candidate from their record, start from a template or write your own, and tick the option to mark them as rejected in the same step. The email comes from Rezumz, replies go to you, and every email is logged under the candidate. Recording a reason when you reject also shows later where candidates drop out. Rezumz does not reject anyone on its own: a person makes each decision and chooses the wording.

Frequently asked questions

How soon after the interview should I send a rejection?

As soon as the decision is made. If you promised a date, keep it, and if you are still deciding, say so and give a new date.

Should I always give feedback?

Give brief, job-related feedback where your policy and local rules allow it, especially to people who invested time in interviews. Where you cannot, say so politely.

Is it fine to use a template?

Yes, if you personalise the thank-you and the reason. A template with the person's name and nothing else reads as careless.

See it on a real hire

Open a private demo with fictional candidates and walk a hire from job description to offer. No sign-up needed.

Try the live demo →