The Rejection Email That Became Evidence

A recruiter wanted to let a candidate down gently. The role had come down to two people, and the candidate who missed out was in her late fifties, warm in the interviews, clearly capable. So the recruiter wrote the kind email: “We went with someone who felt like a better long-term fit, but please stay in touch.” Nine months later that sentence was an exhibit. The candidate had filed an age discrimination claim, her lawyer had requested the hiring file, and “better long-term fit” was sitting in a demand letter next to the ages of both finalists.

Nothing in that email was cruel. That is exactly why it was dangerous. In hiring litigation, the friendliest lines are often the ones that cost the most, because kindness reaches for shorthand, and shorthand is where protected traits hide.

Why a nice rejection turns into evidence

A discrimination finding almost never rests on the wording of one email. The reason behind the decision is what a regulator or a court cares about. The problem is that a phrase written to soften the news can become the visible proxy for that reason, and once it is in writing it is discoverable, quotable, and hard to explain away.

Three phrases do most of the damage, and they are all meant kindly:

• “A better long-term fit.” Read plainly it says nothing. Read next to two dates of birth it reads as a comment on how many years the candidate has left, which lines up directly with age.
• “Culture fit” or “not quite our culture.” Culture is real, but the phrase is a container. When the person rejected differs from the team by age, national origin, or disability, “culture fit” invites the reader to fill the container with the protected trait.
• “You seem overqualified.” Often true, often kind, and repeatedly treated by tribunals and the EEOC as a recognised euphemism for “too old” or “too expensive,” particularly for candidates over fifty.

The mechanism is not subtle. A claimant’s lawyer does not need to prove the recruiter was biased. They need a document where the stated reason maps onto a protected characteristic, and then the burden shifts to the employer to show the real reason was something else. A vague, warm phrase gives them the map and gives you nothing to stand on.

The scale of that exposure is not theoretical. In the United States a single company’s internal chat messages became the core of a USD 54 million civil-rights case. On the European side, disparaging shorthand carries its own price: a pharmaceutical company was fined EUR 25 million for telling doctors a rival generic “is not the same.” Different context, same lesson. An informal line written to be helpful becomes the record everyone reads back to you. (This is general information, not legal advice.)

The uncomfortable part for HR is that the careful candidates are the expensive ones. A brusque “you were not selected” creates almost no exposure. It is the thoughtful recruiter, the one who wants to give real feedback, who writes the sentence that gets quoted. The fix keeps the warmth and removes the shorthand, so the recruiter can stay human and still stay safe.

The one-question test before you hit send

You do not need a policy binder for this. Before any rejection leaves your outbox, run one question against every reason you give:

“Could this phrase be swapped for the candidate’s age, gender, race, disability, religion, or nationality and still make sense?”

If yes, the phrase is a proxy and it has to change. “Better long-term fit” survives the swap (“better younger fit”) and fails. “Overqualified” survives the swap and fails. “Chose a candidate with more direct experience in medical-device pricing” does not survive the swap, because you cannot substitute a protected trait for it. That is the signal you want: a reason so specific to the job that no protected characteristic can be read into it.

The taxonomy, at a glance

Soft phrase (drop it)	Why it is risky	Safer, still-kind line
“A better long-term fit”	Reads as age / tenure horizon	“The selected candidate more closely matched the specific requirements listed for this role”
“Culture fit”	Container for protected traits	“We moved forward with a candidate whose experience aligned more directly with the team’s current priorities”
“You seem overqualified”	Recognised age / cost euphemism	“We selected a candidate whose experience level matched the scope and seniority of this position”
“We were looking for someone more energetic / fresh / digital-native”	Direct age signal	“We prioritised specific, recent experience with the tools this role uses daily”

The boring-on-purpose template line

Keep one sentence on file and reuse it. It is deliberately plain, because plain is defensible:

“Thank you for the time you gave us. After a close comparison against the requirements for this specific role, we have decided to move forward with another candidate. We would genuinely welcome your application for future openings that match your experience.”

It is kind, it is human, and it says nothing a lawyer can convert into a protected trait. If you want to add real feedback, tie it to a named job requirement, and keep it to the requirement.

For the broader picture of how hiring language creates legal exposure, our note on discrimination risk in recruitment walks through the pattern in more depth.

Where a pre-send check actually fits

The honest limit first: no tool decides whether your hiring reason was lawful. That is the reason behind the decision, and it lives in the process, in the interview notes, in whether the shortlist was fair. Software does not fix a biased decision.

What a pre-send check does is narrower and useful. Most risky rejection emails are not written by bad actors. They are written by conscientious people at 6pm who reach for a warm phrase without noticing it has a second reading. VerbaPulse runs before the message is sent and flags that specific line, so a well-meaning recruiter sees the risk while they can still edit it. A real flag looks like this, phrase-level and short:

• Flagged: “you seem a little overqualified for where the team is right now”
• Suggestion: “your experience level was above the scope defined for this role”

That is the whole scope. It is a front-end shield for accidental risk, the careless line nobody meant to write. It is not an adversarial control, and it will not stop someone determined to put something damaging in writing. It complements your archiving and supervision stack (the Smarsh or Proofpoint layer that stores and reviews after the fact) by catching the avoidable issue before it ever reaches that queue, so fewer things land there in the first place.

The takeaway

Do one thing this week. Take your team’s rejection template and the last ten rejections your recruiters actually sent, and run every reason through the swap test: could this phrase be replaced with a protected trait and still read the same way? Delete every line that survives the swap, replace your soft phrases with a specific, job-anchored reason, and standardise on one boring template so warmth never has to improvise a risky sentence again. The goal is simple to state. Keep the kindness, and give a claimant’s lawyer nothing to quote.