Back

The Shortlist Sitting in the Hiring Manager's Inbox

Once AI screening makes the recruiter stage fast, the delay in hiring moves to the hiring manager. Why shortlists go unreviewed, why few teams measure it, and what changes the behavior.

Hiring Effectiveness5 min read
The Shortlist Sitting in the Hiring Manager's Inbox

When you speed up one step of a process, the waiting usually doesn't go away. It moves to the next step. The work isn't done any sooner; the pile just sits somewhere else.

Recruiting is going through this right now. For about three years, most of the new hiring software has been aimed at the recruiter's half of the pipeline: AI screening, automated scoring, voice calls for first contact. The assumption behind all of it was that recruiter throughput is where the delay lives. That used to be true. But when screening that took three days takes a few hours, the delay moves downstream, and in many companies it has landed with the hiring manager. Very few teams' metrics show it.

Here's what that looks like for a candidate. They apply on Monday and get screened on Wednesday. On Thursday they're on a shortlist. The interview invitation arrives the following Wednesday. For nine days they've been in other companies' processes, and some of those companies were quicker. Your screening was fast, but the candidate never saw your screening speed. What they saw was the total time between applying and hearing that you wanted to talk.

The reason is not mysterious. Hiring managers have other jobs. A VP of Engineering in the middle of a sprint, reviewing design decisions and handling escalations from product, is not sitting at inbox zero waiting for recruiting to send over candidates. Everyone knows this, and yet most hiring processes are designed as if it weren't so.

The shortlist nobody opens

Picture the shortlist landing in the manager's inbox before they've reached their desk. By mid-morning there are thirty other things competing for their attention, and by Thursday the email has scrolled out of view. Nothing in any dashboard records that this happened.

I don't think it's a discipline problem. Most ATS platforms were built for recruiters, with status pipelines, communication logs, and disposition workflows. The handoff to the hiring manager is usually an email or a Slack message with a list attached. That's a task with no deadline, living outside the tools the manager uses every day, with nothing pushing them to act by a particular time. A reminder nudge doesn't change much, because the problem isn't that they forgot.

What does change it, I think, is how much effort the shortlist looks like. Reading a stack of unstructured resumes is real work, and people put off real work when something more urgent is in front of them. If the shortlist arrives already summarized and structured, so the manager can get through it in the gap between two meetings, and if there's an agreed turnaround time attached to it, a lot of the deferral goes away. People postpone tasks roughly in proportion to how big they look.

What doesn't get measured

Most recruiting teams track time-to-fill, time-to-hire, applications per role, and recruiter-to-req ratio. Very few track how long the hiring manager takes: the hours from shortlist delivery to first review, from interview to feedback, from panel alignment to offer approval. Those intervals don't show up on recruiter dashboards because they aren't recruiter actions. They sit in the gap between recruiting and the rest of the business.

My guess is that a large share of pipeline failures start in that gap. Losing candidates to faster employers, rising offer declines, people dropping out between interview and offer: these tend to get blamed on the market when the cause was internal. If you're rethinking which numbers tell you how healthy a pipeline is, there's a case for tracking hiring manager velocity as a KPI, as part of a wider argument that metrics designed before AI now point at the wrong problems.

I care about this partly because of what we make. With Asendia, an applicant's phone rings soon after they apply, and they talk the role through with an AI interviewer that follows up on what they actually say. By the logic above, making that first conversation happen sooner just moves the queue unless what comes out the other end is easy for a busy manager to act on. So instead of a resume score, what the manager finds in the ATS is a structured summary of each candidate: what they said about their experience, excerpts from the conversation in their own words, and how they measure up against the criteria set for that specific role. Reading one takes a minute or two rather than the quarter hour a resume can take, and I think that's what makes same-day review realistic. The recruiters then pass on a documented shortlist rather than a pile of applications. If the cost of manager lag is already showing up in your offer data, this analysis of why candidates are declining offers looks at where process delay, rather than pay, is causing the losses.

To see whether this is happening to you, pick one open role and measure two things: how long screening took, and how long the shortlist sat before the hiring manager first looked at it. When the second number is bigger, you've been making the wrong stage faster.

Ready to transform your hiring strategy? Schedule a Demo with our founders today!

Badis Zormati

Co-Founder, Asendia AI

Ready to transform your hiring strategy?

Schedule a Demo

Keep reading