There’s a number most hiring teams track religiously: time-to-hire. It shows up in quarterly reviews. It gets discussed in leadership standups. It becomes the thing everyone wants to shorten.
And it’s the wrong number to obsess over.
The metric that’s actually bleeding candidates from your pipeline is one most teams don’t even measure: time-to-first-response — the gap between someone hitting “apply” and receiving any sign of life from your company. Not an offer. Not a rejection. Just… acknowledgement that a human being on the other end noticed they exist.
I’ve watched this play out dozens of times. A strong candidate applies on Tuesday. By Friday, they’ve heard nothing. By the following Monday, they’ve accepted a phone screen somewhere else. When our team finally reaches out on day nine, the reply is some version of “Thanks, but I’ve already moved forward with another company.” We didn’t lose that person because our hiring process was too long. We lost them because our silence spoke louder than our job posting ever did.
The 10-Day Window Nobody Talks About
Here’s the math that should keep hiring managers up at night. According to data widely cited by LinkedIn and Officevibe, top candidates — the ones with in-demand skills and multiple options — are off the market within 10 days of starting their search. Ten. Meanwhile, Robert Half’s 2025 survey of over 2,200 U.S. hiring managers found that 93% say the hiring process takes longer now than it did two years ago, with over half saying it takes more time just to evaluate applications.
So the best people are gone in a week and a half, and most companies are still reviewing resumes.
A Greenhouse survey found that 58% of candidates expect to hear back within one week of applying. Not “get an offer” — just hear something. A status update. A timeline. Anything that signals the application didn’t vanish into a digital void. And Talent Board’s 2022 benchmark research revealed that 34% of candidates were still waiting one to two months — or longer — to hear about next steps after submitting an application. That figure was 48% worse than the previous year.
Two months. For a first response.
That’s not a slow pipeline. That’s a broken front door.
What Happens in the Silence
The damage from a delayed first response isn’t theoretical. It unfolds in a very specific, very predictable sequence.
Within the first 48 hours, a candidate is still engaged. They’re checking their email, maybe refreshing their application portal, feeling cautiously optimistic. By day four or five, doubt creeps in. Did the application go through? Was I immediately disqualified? Is this company even real? By the end of the first week, most people have reframed their expectation. They mentally file your company under “probably not happening” and shift their energy to whoever did respond.
And that’s the part hiring managers rarely see. No one sends you a note saying “I lost interest because you took eight days to acknowledge me.” They just quietly disappear. Your ATS marks them as “unresponsive” when you finally reach out, and you assume they weren’t that interested to begin with.
I’ve been on both sides of this. The candidate side, where silence from a company I was excited about slowly turned into resentment. And the hiring side, where I didn’t realize my “we’ll get back to everyone next week” actually meant some people waited twelve days for a form email. The intent was never to ghost anyone. But the effect was identical.
There’s also a brand cost. Talent Board’s research has consistently shown that candidates who have negative experiences are far less likely to apply again, refer others, or even buy the company’s products. A LinkedIn survey found that 52% of candidates say the most frustrating part of job searching is not hearing back from employers. That frustration doesn’t just evaporate — it turns into Glassdoor reviews, into Reddit threads, into warnings passed along to friends.
Why This Metric Stays Invisible
If time-to-respond matters so much, why don’t more teams track it?
Partly because most applicant tracking systems aren’t built to surface it. They’ll tell you time-to-hire. They’ll show you time-to-fill. Some will even break down stage-by-stage durations. But the specific gap between “application received” and “first outbound communication to candidate” is rarely a default dashboard metric. You’d have to configure it yourself, and most teams don’t know they should.
The other reason is more human. Hiring managers don’t feel the delay the way candidates do. When you’re juggling a full workload plus an open role, a week goes by in a blink. You barely notice it. But for the person who just put themselves out there — who tailored a cover letter, recorded a video, or spent forty minutes on an application — that same week feels like a month. The asymmetry of attention is enormous, and it makes the problem self-reinforcing. The people causing the delay don’t experience the consequences of it.
Four Things You Can Do This Week
You don’t need a new ATS or a bigger recruiting team. You need a few deliberate changes to how the first 72 hours of your process work.
Set up an auto-acknowledgment that actually says something. Not “We received your application.” That’s table stakes and everyone ignores it. Instead, tell the candidate what happens next and when. “We review applications in batches every Monday and Thursday. You’ll hear from us within five business days either way.” That one sentence does more for candidate experience than most employer branding campaigns.
Create an internal SLA for the first human touchpoint. Pick a number — 48 hours, 72 hours, whatever you can actually sustain — and hold each other to it. Write it on a sticky note. Put it in Slack. The goal isn’t perfection; it’s making response time something your team is conscious of instead of something that just drifts.
Block dedicated screening time on the calendar. One of the biggest reasons first responses lag is that screening gets squeezed between other priorities. Hiring managers do it in leftover pockets of time, which means it happens inconsistently. Even two 30-minute blocks per week — Tuesday and Thursday mornings, say — can cut your average response time dramatically. Treat it like a meeting, not a to-do.
Replace early-stage phone screens with async video. The scheduling dance of phone screens is one of the sneakiest time sinks in hiring. You email the candidate to find a time. They reply a day later. You go back and forth. By the time you actually talk, a week has passed and the conversation starts cold. Video interview software — like VideoApply, for example — let candidates record responses on their own schedule, and let you review them in batches whenever it’s convenient. No calendar coordination. No phone tag. An on demand video interview step cuts response time dramatically — even without any additional tooling layered on top.
The Point Isn’t to Hire Faster
I want to be clear: this isn’t an argument for rushing your hiring decisions. Take the time you need to evaluate fit, check references, involve the right stakeholders. A thoughtful process is a good process.
But there’s a difference between a thoughtful process and a silent one. You can take four weeks to make a decision and still respond to every applicant within 48 hours. You can have five interview rounds and still send a status update between each one. Whether you’re using ai candidate screening or reviewing applications manually, speed of decision and speed of communication are different things — and conflating them is how most companies end up losing people they never even got to evaluate.
So the next time someone in your org brings up time-to-hire, ask a different question: how long does it take us to say anything to the people who apply? If nobody knows the answer, that’s the problem worth solving first.