---
title: "How to Tell a Candidate They Didn't Get the Job (Free Templates)"
description: "Prompt, definite, and matched to the stage: the formula for a good rejection, plus ready-to-use templates and the lines that never belong in one."
url: https://zjcv.com/journal/how-to-reject-a-candidate/
canonical: https://zjcv.com/journal/how-to-reject-a-candidate/
author: "Zen Job CV Team"
published: 2026-06-24
updated: 2026-06-24
category: "Playbooks"
tags: ["candidate experience", "rejection", "recruitment templates", "hiring compliance", "candidate communication"]
lang: en
---

# How to Tell a Candidate They Didn't Get the Job (Free Templates)

> **TL;DR** To tell a candidate they did not get the job, send a short, prompt, definite message: thank them, state plainly you are moving forward with others, and give one specific factual reason if they interviewed. Match effort to the stage, a quick written note for the not-shortlisted, a call for final-stage candidates. Speed matters more than wording, because ghosting, which around 80 percent of hiring managers admit to, does the real damage. Use templates so sending is easy, personalise where the candidate invested time, and never give a reason you did not evaluate or promise retention you do not operate.

To tell a candidate they did not get the job, send a short, clear, prompt message that thanks them for their time, states plainly that you are moving forward with other candidates, and, if they reached an interview, gives one specific and factual reason. That is the whole formula, and the templates below fill it in. The hard part of rejection is almost never the wording; it is sending it at all, and sending it in time. A plain message that arrives promptly beats a beautifully written one that arrives late, or never.

That "or never" is not rare. Ghosting has become the default in hiring: [about 80 percent of hiring managers admit to having ghosted a candidate](https://www.hrdive.com/news/hiring-managers-responsive-applicants/716173/), and the [candidate side of the same research](https://www.greenhouse.com/blog/greenhouse-2024-state-of-job-hunting-report) shows how routine going silent has become. Every template here is built to be quick enough that sending it is easier than not.

## The three principles behind every good rejection

Before the templates, three rules make any rejection land better, and they hold at every stage.

Be prompt: send within a week of the decision, and within two working days for anyone you interviewed. Speed matters more than wording, because the damage in a rejection comes from silence and delay far more than from the word no. Be definite: "we have decided not to take your application further" beats "we have decided to move forward with other candidates at this time," which hedges and leaves people re-reading for hope that is not there. And match the effort to the investment: someone who did four interviews is owed a call and a specific reason; someone who applied and was not shortlisted is owed a prompt, clear note, not silence. The deeper operational side of getting this right at volume is covered in [how to reject candidates well](/journal/how-to-reject-candidates-well/); what follows is the language.

## Which message fits which stage

The right message scales with how far the candidate travelled, so match the template to the stage rather than sending everyone the same line.

| Stage reached | Format | Timing | Reason to give |
|---|---|---|---|
| Applied, not shortlisted | Short written note | Within a week of the decision | A brief category, or none |
| Phone screen | Written, personal | Two working days | One factual reason |
| Interview | Written or a call | Two working days | One specific, evaluated reason |
| Final stage | A call, then written | Within 24 hours | Specific, plus an honest future signal |

The pattern is that the further someone travelled, the more of your time they are owed, and the more specific and personal the message becomes. Nobody expects a phone call after a one-click application; everybody who did four interviews deserves more than an automated line.

## Ready-to-use templates

Fill in the brackets. Keep them short; a long rejection reads as defensive.

**Applied, not shortlisted (prompt, high volume):**

> Hi [name], thank you for applying for the [role] position. We had a lot of strong applications and have decided not to take yours further this time. We are grateful for the time you spent applying, and we wish you the best with your search. [Optional: your data will be deleted within four weeks unless you would like us to keep it on file for future roles, which you can choose here.]

**After a phone screen:**

> Hi [name], thank you for taking the time to speak with me about the [role] position. After our conversation we have decided not to move you forward to the next stage, as we are prioritising candidates with [specific factual reason, e.g. direct experience in X]. I appreciated the conversation and wish you well.

**After an interview:**

> Hi [name], thank you for interviewing for the [role] position and for the thought you put into it. We have decided not to make you an offer. It came down to [one specific, evaluated reason, e.g. depth of experience with X], where another candidate was further along. Everything else about your application was strong, and I would be glad to keep in touch about future roles if that is welcome.

**Final stage, by call then written:**

> [On the call, lead with the decision, give one specific reason, and be human. Then confirm in writing:] Hi [name], following up on our call, thank you again for the time you invested in this process. As I mentioned, we are not moving forward, and it genuinely came down to [specific reason]. If a suitable role opens here in the next year, I would like to reach out to you first.

None of these are warm in a performed way. They are specific, they close the loop, and, crucially, they can all be sent the same week.

## When to personalise, and when a template is fine

A template is not a lesser option; it is what makes prompt rejection possible at volume, and a prompt template beats a personal message that never gets written. The judgement is where to spend personalisation.

| Situation | Template or personal | Why |
|---|---|---|
| High-volume, not shortlisted | Template, always sent | Speed and coverage matter most |
| Phone screen | Template with one personal line | A factual reason, quickly |
| Interviewed | Personalised | They invested real time |
| Final-stage near miss | Personal call | Proportionate to the investment |

The rule underneath: automate the coverage so nobody is ghosted, and spend your personal attention where the candidate spent theirs. A team that tries to hand-write every rejection ends up sending none, which is how ghosting happens.

## What never belongs in a rejection

A few things turn a routine rejection into a legal or reputational problem, and they are easy to avoid.

Do not give a reason you did not actually evaluate, or one you did not apply to everyone, because an inconsistent or invented reason is where a rejected candidate starts looking for a discriminatory explanation. Do not comment on protected characteristics, age, health, family situation, or anything adjacent, even kindly. Do not offer detailed unsolicited coaching to high-volume candidates; it is not your job and rarely lands well. And do not promise to "keep the CV on file" unless that is a real, consented, time-bounded thing you operate, because in the EU that is a retention claim with rules attached: the Dutch supervisory authority treats [deletion within four weeks of a procedure ending](https://www.autoriteitpersoonsgegevens.nl/en/themes/employment-and-benefits/job-applications/personal-data-of-applicants) as the norm, extending to a year with the candidate's consent, and the [wider rules on handling candidate data](/journal/gdpr-rules-for-cv-screening/) apply to the rejection stage as much as to screening.

## Sending them without ghosting anyone

Templates only help if they are actually sent, and the failure mode is always the same: the not-shortlisted majority get forgotten while attention goes to the shortlist. Two disciplines fix it. Send the not-shortlisted rejection as part of closing the role, not as a separate task you mean to get to, and keep a record that each candidate was contacted, which is also good practice for showing a fair, consistent process. A screening tool that keeps every candidate visible with their status makes "did everyone hear back?" a question you can answer, rather than one you hope the answer to. The point is not automation for its own sake; it is that a closed loop is what separates a humane process from a ghosting one.

## A worked example

A five-person team fills a marketing role and, by the end, has 160 applicants: 150 not shortlisted, 8 phone-screened, 3 interviewed, and 1 hired. The instinct is to focus the rejection effort on the people they met, and that is exactly how the 150 get ghosted, because hand-writing 150 notes is a task nobody finds time for.

The proportionate approach takes an afternoon, not a week. The 150 not-shortlisted get the high-volume template, sent as part of closing the role, with the optional consented line offering a place on a talent list; most take seconds each and nobody is left in silence. The 8 phone-screened get the phone-screen template with one factual reason filled in. The 3 interviewed get a short personal message, and the two who reached the final stage get a call first. Total personal effort is concentrated on 11 people, the 150 are handled by a template that still closes the loop, and not one applicant is ghosted.

Contrast the common alternative: the team writes thoughtful notes to the 3 interviewed, means to get to the rest, and never does. Six months later two of those 150 are customers who remember applying and hearing nothing, and one leaves a public review about it. The templated approach cost an afternoon; the ghosting cost more, later, and invisibly. That asymmetry, small effort now against diffuse reputational cost later, is the whole reason to systematise rejection rather than leave it to goodwill and spare time.

## How to tell a candidate they did not get the job

Send promptly, be definite, and match the effort to how far the candidate travelled: a clear written note for the not-shortlisted within a week, one factual reason for anyone you spoke to, and a call plus a specific reason for final-stage candidates within a day. Use the templates so sending is easy, personalise where the candidate invested real time, and never give a reason you did not evaluate or promise open-ended retention you do not operate. Above all, send something: the worst rejection is the one that never arrives.

## Quick answers

**How do you tell a candidate they didn't get the job?** Send a short, prompt, definite message that thanks them, states plainly you are moving forward with others, and, if they interviewed, gives one specific factual reason. Match the effort to the stage: a quick written note for the not-shortlisted, a call and a specific reason for final-stage candidates. Speed matters more than wording, so send within a week of the decision.

**What should you write in a rejection email?** Keep it to four things: thanks for their time, a clear statement that you are not moving forward, one factual reason if they reached an interview, and a warm close. Keep it short, because long rejections read as defensive, and be definite rather than hedging. Optionally offer a consented, time-limited place on a talent list, but only if you genuinely operate one.

**When should a rejection be personalised rather than a template?** Personalise in proportion to how much the candidate invested. A template sent promptly is the right call for high-volume, not-shortlisted candidates, because coverage and speed matter most and a template is what makes sending possible. Anyone who interviewed deserves a personalised message with a specific reason, and a final-stage near-miss deserves a call.

**What should you never say in a rejection?** A reason you did not actually evaluate or apply to everyone, anything touching a protected characteristic such as age, health or family situation, and any promise to keep a CV on file that you do not genuinely operate as a consented, time-limited list. Inconsistent or invented reasons are where a rejected candidate starts looking for a discriminatory explanation, so stick to evaluated, job-relevant facts.

**How do you avoid ghosting candidates?** Send the not-shortlisted rejection as part of closing the role rather than a separate task, and keep a record that every candidate was contacted so "did everyone hear back?" is a question you can answer. Automate the coverage so nobody is forgotten and spend personal attention where the candidate invested theirs. Ghosting is common, with around 80 percent of hiring managers admitting to it, and a closed loop is what avoids it.

---

Source: https://zjcv.com/journal/how-to-reject-a-candidate/
Author: Zen Job CV Team