Most rejection letters are never written. The role gets filled, the successful candidate is onboarded, and the other forty applications sit in a folder that nobody opens again. The intention was there. The letter was going to be written on Friday, and then Friday had its own problems.
The reason it keeps happening is not callousness. It is that sending forty individual messages is a real task with no deadline attached, and tasks with no deadline lose to tasks with one. Solving it is partly a writing problem and mostly a process problem, so this covers both: what the letter should say, and how to make sending it take five minutes rather than an afternoon.
What the silence actually costs
The case for writing the letter is usually made in terms of employer brand, which is true and abstract. Three concrete costs are easier to act on.
The applicant keeps chasing. Somebody who has heard nothing after three weeks emails to ask. That email goes to a shared inbox and someone has to answer it individually, which is more work than the original letter would have been, and it arrives at an unpredictable time rather than in a batch.
The pipeline stops being readable. If rejected applicants are never marked as rejected, the list of applications is a list of everyone who ever applied. Six weeks later, when the next role opens, nobody can tell who was already considered and passed over, so the same people are read again from scratch.
Reapplication becomes awkward. A strong candidate who was second choice is worth contacting when the next opening appears. That conversation is straightforward if they were told clearly the first time and impossible if they were ghosted, because the first thing they will remember is the silence.
None of these is about kindness. They are about the recruiting process still working next quarter.
The four parts of a rejection that lands well
A rejection letter has one job: to end the uncertainty cleanly. Everything that does not serve that is padding, and padding is what makes these letters read as insincere.
A decision, stated early. The outcome belongs in the first two sentences. A letter that opens with two paragraphs of appreciation before reaching the point forces the reader to hunt for the answer while already suspecting it. That is a worse experience than a blunt first line.
The specific role and the date. Applicants apply to several places. A letter that does not name the position and roughly when they applied is confusing, and if it also does not name the company it can read as a phishing attempt.
A reason, kept general. "A candidate whose experience was a closer match for this role" is true, non specific and unarguable. It tells the applicant the decision was comparative rather than a judgement on them, which is the thing most people actually want to know.
A clear statement about what happens to the application. Either it is being kept for future openings or it is not. Both are acceptable. What is not acceptable is implying the first while doing the second, because an applicant who believes their details are on file will not reapply when the right role appears.
Notably absent from that list: detailed feedback. It is covered further down, because whether to offer it is a policy decision rather than a writing one.
Length follows from those four parts. An application stage rejection that runs to three short paragraphs is doing everything it needs to do. Anything longer is usually the writer trying to soften the message, and softening tends to obscure it. The test is whether somebody reading the first two lines on a phone, between other things, comes away knowing the answer.
Three templates
The differences between these are driven by how far the person got, because effort invested should be matched by specificity.
For applicants rejected on the application itself, before any conversation:
Subject: Your application for [Role] at [Company]
Dear [Name],
Thank you for applying for the [Role] position. We have completed our
review of applications and will not be taking yours forward on this
occasion.
We had a strong field for this role and have moved ahead with candidates
whose experience matched the requirements more closely. This is not a
reflection of your wider experience.
[We will keep your application on file for six months and will contact
you if a suitable role opens. / We do not retain applications after a
hiring round closes, so please do apply again if you see another role
that suits you.]
Thank you for the time you spent on your application, and best of luck
with your search.
[Sender name]
[Company]
For applicants rejected after a first interview:
Subject: Your interview for [Role] at [Company]
Dear [Name],
Thank you for meeting with us on [date] about the [Role] position.
After discussing all of the candidates we interviewed, we have decided
not to progress your application.
The decision came down to [depth of experience in a specific area /
overlap with the immediate priorities of the team], and it was a close
one. Your [specific thing that was genuinely good] stood out.
[Retention sentence as above.]
Thank you for the time you gave us, and for the questions you asked.
[Sender name]
[Company]
For finalists:
Subject: [Role] at [Company]
Dear [Name],
Thank you for the time you have given us over the past [period]. After
a difficult decision, we have offered the [Role] position to another
candidate.
You reached the final stage of a strong process and the decision was
close. [One specific, honest sentence about what tipped it.]
We would welcome an application from you in future and will contact you
directly if a suitable role opens.
If it would be useful, we are happy to talk through the decision on a
short call. Reply to this message and we will arrange it.
[Sender name]
[Company]
The call offer in the third template is deliberately absent from the first two. Offering it to forty people creates an obligation that cannot be met, and an unanswered offer of feedback is worse than no offer.
What to leave out
Feedback nobody asked for. Unsolicited criticism in a rejection email is read as justification rather than help, and it is frequently argued with. Offering feedback on request, to candidates who reached an interview, keeps the volume manageable and means the person receiving it wanted it.
Overstated praise. "An exceptionally strong application" followed by a rejection reads as untrue and slightly insulting. Warmth is fine. Inflation is not.
Vagueness about the outcome. Phrases such as "not progressing at this time" leave a door ajar that is not really open. If the answer is no, the letter should be readable as no by somebody skimming it on a phone.
Anything that sounds like a legal judgement. Reasons touching on age, health, family circumstances, nationality or anything a candidate could reasonably read as a protected characteristic do not belong in writing, even when the actual decision had nothing to do with them. Comparative language about experience and fit to the role is safer and also more accurate.
When to send
Two timings work, and both are better than the third option, which is whenever somebody remembers.
Rejecting on the application itself is best done within a week of the closing date, in one batch. There is nothing to wait for, and the applicant can direct their attention elsewhere.
Rejecting after an interview should wait until the offer is accepted, not until the offer is made. Offers fall through, and a second choice candidate who has already been told no is much harder to go back to. The gap is usually a few days, and it is worth telling interviewed candidates when to expect a decision so the wait is bounded.
The one pattern to avoid is rejecting some people and not others. Partial coverage is how the pipeline becomes unreadable, because the absence of a rejection stops meaning anything.
Who the letter comes from
The sender address matters more than the signature. A letter sent from a no reply address tells the applicant that the conversation is closed before they have decided whether they want to ask anything, and anyone who replies to it gets a bounce. An address that a person reads is the minimum, even when the expected volume of replies is near zero, because the small number who do reply are usually the ones worth answering.
The name on the letter is a separate choice. A named recruiter or hiring manager reads better than a department, and it also means that when a strong candidate applies again in six months there is a person for them to address. The cost of naming somebody is that the replies land on that person, which is an argument for sending from a shared address under an individual's name rather than from a personal mailbox.
Keeping second choice candidates reachable
Every hiring round produces people who were close. In a market where roles reopen, those candidates are the cheapest source of a future hire, and the rejection letter is the last chance to keep that door usable.
Two things preserve it. The letter has to be honest that the decision was close, without promising anything, and the record has to be findable later. Honesty in the letter costs nothing. Findability is the part that usually fails, because six months later nobody remembers which of forty applicants were the near misses.
The fix is a note on the record at the time the decision is made, while the reasoning is fresh. A tag such as reconsider, or a short internal note saying what the person was strong at, turns a closed application into something searchable. It takes fifteen seconds per candidate during the round and saves a full sourcing cycle later.
This is also the argument against deleting applications the moment a role closes. A rejected application with a note attached is an asset. A deleted one is a candidate who will be found again through an agency fee.
Sending them without losing the afternoon
This is the part that determines whether any of the above happens.
If applications arrive as emails in a shared inbox, sending forty rejections means forty individual replies, and the record of which ones were sent is the sent folder, which nobody checks. That is the process that reliably fails.
The workable shape has three properties. Each application carries a status, so rejected is a state of the record rather than a memory. Rejections can be sent to a filtered group in one action, with the applicant's name and the role dropped in from their own answers. And the send is recorded against each application, so the question "did this person get a letter" has an answer that does not require searching an inbox.
A tool that keeps applications and replies on the same screen gives all three without a mail merge. The recruitment use case covers the flow from application through to the reply, and the features page sets out what the response screen holds. The saved wording matters as much as the sending: a template stored alongside the applications means the letter is written once and improved over time, rather than rewritten from memory by whoever has the afternoon free.
Keeping the record afterwards
Applications are personnel records, and they have a retention life after the rejection is sent.
In the United States, the EEOC states that employers covered by federal anti discrimination laws must keep all personnel or employment records for one year, and that this applies whether or not a charge has been filed. If a charge is filed, relevant records must be kept until the final disposition of the charge or any resulting lawsuit. Retention rules differ by country, so local advice governs, but the shape is consistent: applications cannot simply be deleted the moment a decision is made.
That has a practical consequence for where applications live. A folder of email attachments is a poor system of record, because it cannot answer who applied, what was decided, when, and what was sent to them. A list where each application holds its own status, decision and correspondence answers all four in one place, which is also what makes the retention period painless when it ends.
What to change first
Pick the last role that closed and count how many applicants never received an answer. That number is the size of the problem, and it will be larger than expected. Then write the three templates above once, store them where the applications are, and send the outstanding letters as a batch this week. Halict keeps each application with its own status and a record of what was sent, which is what turns the letter from a Friday task into a click.
Q1. Should every applicant get a rejection letter, or only those who interviewed?
Every applicant, with the letter's length matched to how far they got. Applicants rejected on the application itself need three short paragraphs sent as a batch. Interviewed candidates need something specific to the conversation.
Q2. Is it necessary to give a reason for the rejection?
A general comparative reason is enough, such as another candidate matching the requirements more closely. Detailed feedback is better offered on request to people who reached an interview, because unsolicited criticism in a rejection email is usually read as justification rather than help.
Q3. When should rejections be sent after an interview?
After the chosen candidate has accepted, not when the offer is made. Offers fall through, and going back to a second choice candidate who has already been told no is considerably harder.
Q4. How long should rejected applications be kept?
In the United States, the EEOC requires employers covered by federal anti discrimination laws to keep personnel and employment records for one year, and longer if a charge has been filed. Other countries have their own rules, so local advice applies, but applications should not be deleted at the moment of the decision.
Q5. What should the letter say about keeping the application on file?
Whatever is actually true. If applications are retained, state the period and say that contact will be made if a suitable role opens. If they are not, say so and invite the person to apply again. Implying retention that does not happen stops good candidates from reapplying.