Nobody sits down and decides to ghost a candidate. There is no meeting where a team agrees that the 40 people who interviewed last month should hear nothing at all. It happens anyway, in organised companies, run by people who would be embarrassed to describe it out loud.
That is worth sitting with, because it tells you what kind of problem this is. Ghosting in hiring is not a character failure. It is what a process produces when the last step has no owner.
What ghosting in hiring actually looks like
Ghosting in hiring has two directions, and the version that matters for employers is simple. Someone applies, gets screened, comes in for an interview, and then hears nothing. The posting eventually disappears. They are left to work out for themselves that they did not get it.
Most teams do not think of this as ghosting. They think of it as the role being closed. From the candidate’s side those are the same event, and it is their version that gets talked about.
The other direction, where the candidate disappears on you, is a real problem too. It is a different one, with different causes, and it shows up most clearly in candidates who never show up to a scheduled interview. This post is about the side you control.
Why ghosting in hiring happens in well run teams
Three things explain almost all of it, and none of them are indifference.
The last step belongs to nobody
Every other stage of hiring has an owner and a trigger. Sourcing starts when the req opens. Screening starts when applications arrive. Interviews get scheduled by someone whose job it is to schedule them.
Telling the people who did not get it has neither. No system prompts it, no meeting reviews it, and no metric goes red when it does not happen. It sits outside the workflow, so it depends entirely on someone remembering after the part they were measured on is finished.
The message feels harder to write than it is
Managers delay rejections because they imagine having to justify the decision. They picture a difficult reply, a request for feedback, an argument.
In practice, almost none of that happens. A candidate wants to know the outcome so they can stop waiting. Telling them the role has been filled takes 1 line and answers the only question they actually have.
The volume hides the problem
At 3 hires a quarter, everyone gets a reply, because 12 people are easy to hold in your head. At 40 hires a month with 5 interviews each, that is 160 people, most of whom will not get an offer.
Nothing about the process changed. The arithmetic did. This is the same pattern you see when hiring volume outgrows the team: the steps that depend on someone remembering are the first to fail, and they fail quietly.
What it costs, in things you can count
The case against ghosting in hiring is usually made on manners. That argument is true and it has never changed anyone’s process, so here is the operational version.
You lose the runner up. The second best candidate for a role you filled in March is often the best candidate for the role you open in June. If they were ghosted the first time, they are not in your pool anymore. At volume, that pool is the cheapest source of hires you have.
You lose the reapplication. Front line hiring depends on people applying again, sometimes to a different location. Someone who heard nothing has no reason to.
You lose referrals. Candidates talk to other candidates in the same labour pool, particularly in retail, hospitality and field roles where everyone knows someone at 3 nearby employers.
Your reputation compounds at volume. One ghosted candidate is an anecdote. 160 a month is a pattern that shows up in reviews, and it raises the cost of every future posting.
And in Ontario, it is now a legal obligation. Employers with 25 or more employees have to tell interviewed applicants whether a decision has been made within 45 days. That is no longer a matter of courtesy in Ontario, and other jurisdictions are moving in the same direction.
The fix is structural, not motivational
Telling managers to be better about rejections does not work. It has been tried in every company that has this problem. What works is removing the need for anyone to remember.
Make notification part of closing the role. A req is not done when the offer is accepted. It is done when everyone interviewed has been told. Put that in the definition, and the step stops being optional.
Write the message once and reuse it. One short template, no feedback, no explanation. The hesitation disappears when there is nothing to compose.
Give it a deadline shorter than the legal one. If Ontario allows 45 days, run an internal standard of 5. A rule that only binds at the last minute gets treated as optional until the last minute.
Send from one place. When 12 managers each handle their own candidates, you have 12 different standards and no visibility. Preventing ghosting in hiring is mostly a matter of consolidating who sends what.
How Workwolf® handles this
Workwolf® runs the hiring process on your behalf, so candidate communication does not sit with your hiring managers. Everyone who reaches an interview is tracked through to an outcome, and the notification goes out when the role closes.
That matters because the failure mode is always the same. It is not that a manager decided to skip it. It is that the month got hard, the location was short staffed, and the step that nobody was measured on went first. Moving it outside your team means a difficult month does not change whether it happens.
It also produces the record you need. In Ontario that record is a requirement. Everywhere else it is just how you find out whether the standard is real.
Where to start
Take your last closed role and count. How many people were interviewed, how many were told, and how long it took. Most teams find the first number and the second one do not match, and that nobody knew.
Then ask who would have to do it differently for that gap to close. If the answer is a hiring manager already carrying a full month of interviews, the problem is capacity rather than attitude, and no amount of reminding will fix it.
If that sounds like your situation, it is worth a conversation. Book a call with our team and we will walk through where candidates are currently falling out of your process without an answer.
