Nobody sits down and decides to ghost a candidate. There’s no meeting where a team agrees that the 40 people who interviewed last month should hear nothing at all. It happens anyway, in organized companies, run by people who’d be embarrassed to describe it out loud.
That’s worth sitting with, because it tells you what kind of problem this is. Ghosting in hiring isn’t a character failure. It’s 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, passes a screen, comes in for an interview and then hears nothing. The posting eventually disappears. They’re left to work out for themselves that they didn’t get it.
Most teams don’t think of this as ghosting. They think of it as closing the role. From the candidate’s side those are the same event, and it’s their version people talk about.
The other direction, where the candidate disappears on you, is a real problem too. It’s 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 most 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. Someone whose job it is to schedule interviews books them.
Telling the people who didn’t get it has neither. No system prompts it, no meeting reviews it and no metric goes red when it doesn’t happen. It sits outside the workflow, so it depends entirely on someone remembering after they finish the part that counts toward their metrics.
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, that rarely happens. A candidate wants to know the outcome so they can stop waiting. Telling them you filled the role takes one line and answers the only question they actually have.
The volume hides the problem
Say you make three hires a quarter and interview four people for each. That’s 12 people, and they’re easy to hold in your head, so everyone gets a reply. Now say you make 40 hires a month and interview five people for each. That’s 200 people interviewed and 160 who won’t 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
People usually make the case against ghosting in hiring on manners. That argument is true, but it rarely changes anyone’s process, so here’s 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 you ghosted them the first time, they’re not in your pool anymore. At volume, that pool is one of the cheapest sources of hires you have. Keeping it warm is the idea behind an evergreen job requisition for recurring roles.
You lose the reapplication. Frontline hiring depends on people applying again, sometimes to a different location. Someone who heard nothing has no reason to.
Referrals dry up. Candidates talk to other candidates in the same labor pool, particularly in retail, call center and field roles where everyone knows someone at three nearby employers.
Your reputation compounds at volume. One ghosted candidate is an anecdote. Ghosting 160 people a month is a pattern that can show up in reviews, and it raises the cost of every future posting.
And in Ontario, it’s now a legal obligation. Under Ontario’s Employment Standards Act, employers with 25 or more employees have to tell interviewed applicants whether they’ve made a hiring decision within 45 days of the last interview, for interviews on or after January 1, 2026. Employers also have to keep a copy of what they told each applicant for three years. That’s no longer a matter of courtesy in Ontario.
The fix is structural, not motivational
Telling managers to be better about rejections rarely works on its own. What works is removing the need for anyone to remember.
Make notification part of closing the role. A req isn’t done when the candidate accepts the offer. It’s done when you’ve told everyone you interviewed. 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’s nothing to compose.
Give it a deadline shorter than the legal one. If Ontario allows 45 days, run an internal standard of five. Teams treat a rule that only binds at the last minute 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
Ghosting grows when the people running interviews are also carrying the rest of hiring. Workwolf® sources candidates, filters them with AI, phone screens them with its recruiters and books the best fits into your calendar, so you only meet the finalists and make the hire. Candidates who don’t move forward after the phone screen hear back from Workwolf®, so nobody is left waiting. Clients get transparency into how candidates were sourced and scored. That’s the practical difference between managed recruiting and recruiting software: the work moves outside your team, not just the tracking.
That matters because the failure mode is always the same. It’s not that a manager decided to skip it. It’s that the month got hard, the location was short staffed and the step nobody measured went first. When your managers only meet finalists, the list of people they need to close the loop with gets much shorter.
Where to start
Take your last closed role and count. How many people did you interview, how many did you tell, and how long did it take? Many teams find that the first number and the second one don’t 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. Before you sign with outside help, start with these questions to ask an agency.
If that sounds like your situation, it’s worth a conversation. Book a call with our team and we’ll walk through where candidates are falling out of your process without an answer, or run your numbers in our hiring ROI calculator.
