Why "we’ll only contact you if shortlisted" costs your employer brand

We build software with a one-click close-out email in it. In our own database, it has been used zero times. Of 78 real candidates, 56 gave us an email address, and nine of them ever received anything — all interview invitations. Forty-seven people applied, were read, were scored, and heard nothing. That is not a criticism of a client. That workspace is ours.

What the phrase actually says

"We'll only contact you if you're shortlisted" reads, from the other side, as: we are not going to tell you when this is over. The applicant is left to work it out from silence, and silence has no timestamp. A week is normal. Three weeks is probably a no. Or the role is slow. Or the email went to spam. There is no way to tell, so the question stays open.

Nobody writes that sentence meaning to be unkind. It is written because replying to everyone sounds expensive and the sentence makes it optional in advance.

Our own numbers, which do not flatter us

Two honest limits on that table. It is one small workspace over one month, so it is not a survey of anything. And we can only see what went through our own product — if someone replied to candidates from their own inbox, we have no way of knowing. What we can say precisely is that the path we built for this has never once been taken.

Why it happens

• It is never urgent. Everything else in hiring has a person waiting on the other end who can chase you. The people you are not hiring cannot.
• It arrives at the worst moment. The natural time to close people out is when you have just made an offer — the one moment everybody is relieved and moving on.
• It feels like it needs writing. If a rejection is a document you compose, it will not happen 47 times. It should be four lines you approve, not an essay you draft.
• The list is invisible. If nobody can see who is still waiting, nobody is waiting. Held candidates need to be as visible as shortlisted ones, or they stop existing.

What the silence actually costs

We cannot put a number on this and will not pretend to — we have no data on how applicants feel or what they do afterwards, and neither does anyone quoting a statistic at you. What can be said without any research at all:

• They are not a stranger. In a market where one company hires from a handful of universities and job boards, the person you did not answer will apply again, or will be asked about you by someone who is applying.
• The good ones are still looking. Someone with options who hears nothing for three weeks is not waiting; they have accepted something else. Your silence is what made that decision easy.
• It compounds quietly. Forty-seven people in one month, from one posting, at one small company. Do that for a year and the number is not small any more.

The scale objection, priced

"We get 500 applications, we can't reply to all of them." You can, and the objection is about composing rather than sending.

Sending 500 emails is instant and effectively free. What takes the time is deciding what to say, and that is a one-time cost: write it once, approve it per round, send it to everyone below the line. The processing side of 500 applications is about half an hour — a bulk close-out adds minutes to that, not hours.

The honest version of the objection is "we haven't set it up", which is fixable, rather than "it's too expensive", which is not true.

What to do instead of the sentence

1. Put a date in the posting. "You will hear from us by the 30th, either way." A date converts silence from ambiguous to overdue, which is the entire point.
2. Close out in batches, at a fixed moment. When the shortlist is set, not when the offer is signed. The people who did not make the shortlist already know less than you do.
3. Keep held and rejected separate. Someone you might come back to should not receive a final answer, and should not be left in silence either — "not for this role, and here is what happens next" is a real third option.
4. Never let the system do it alone. A batch close-out should name everyone in it before it sends, and a person should press the button. Automatic silence and automatic rejection are the same failure with different wrapping.

Why we are publishing our own zero

Because the lesson is more useful than the embarrassment is costly. We assumed that making a thing one click would make it happen. It did not, and no amount of product design substitutes for someone deciding that closing people out is part of finishing a hire rather than an optional courtesy afterwards.

The number in this article is one we intend to change, and we will publish it again when it does. If it has not moved, that will be worth knowing too — and it will also tell you something about which parts of hiring actually get cheaper when the software gets better, and which parts never will, because they were always about someone choosing to do them.