
A · Human-ranked hiring
How to Shortlist Candidates Fast: Hours, Not Weeks
How to shortlist candidates fast: rank every applicant on evidence of fit in one pass and build a shortlist you can defend in hours.
- To shortlist candidates fast, rank every applicant against the role's requirements in a single pass instead of reading resumes one by one. Score each person on evidence of fit, sort by that score, and take the top five to ten. A shortlist you can defend then takes hours, because the slow part was always the manual triage.
Why shortlisting takes weeks
- SHRM's 2025 benchmarking report puts the median time to fill a role at about a month and a half, for executive and nonexecutive positions alike ([SHRM 2025 Talent Acquisition Benchmarking Report](https://www.shrm.org/content/dam/en/shrm/research/2025-recruiting-benchmarking-report.pdf)). Time to hire is a different measure: the stretch from a candidate applying to accepting an offer ([Workable](https://resources.workable.com/tutorial/faq-time-to-fill-hire)).
- Interviews take some of that time. A lot of it goes to the pile of resumes nobody has ranked yet, and that reading isn't careful. Recruiters give each resume about 11 seconds on the first scan ([InterviewPal](https://www.interviewpal.com/blog/how-long-recruiters-actually-spend-reading-your-resume-data-study)), which is enough to spot a keyword and too little to judge a person.
- So the slow part of hiring is also the sloppy part. Qualified people drop out because their resume phrased a skill differently, and the ones who "sound right" rise whether or not they can do the work. The fix for the delay is the same as the fix for the mistakes.
Rank people on evidence
- Traditional screening asks one question of each resume: does it contain the words I searched for? That is why your [ATS rejects qualified candidates](/spaces/why-ats-rejects-qualified-candidates) every day. It matches strings.
- Fast shortlisting asks a different question. You rank everyone against what the role demands, such as shipped work, measurable outcomes, relevant scope and demonstrated skills. Every applicant is scored on the same evidence, so nobody drops off the list over vocabulary. That is the difference between [keyword matching and skills ranking](/spaces/keyword-matching-vs-skills-ranking).
- When you rank on evidence, the top of the list is your interview queue, and the cutoff is a score you can point to instead of a gut call you have to justify later.
Shortlist in hours, step by step
- The process is the same whether you run it by hand or use a platform to do the scoring.
- Define the evidence before you read anything. Before the first resume arrives, write down what "qualified" looks like. "5 years of React" becomes "has shipped and maintained a production frontend at scale." Most teams skip this step, which is why their shortlists are noise.
- Score every applicant on the same criteria. Read to rank, and give each candidate a fit score against the requirements you just wrote, using one rubric in one pass. Nobody is filtered out before they are ranked.
- Sort by fit and cut at a line you can defend. Rank the whole pool by score and draw the line at five to ten names, where the drop in fit becomes obvious. You can explain that cutoff to any hiring manager who asks.
- Check the top and the borderline. Spend real attention on the top of the list and the few just under the line, where you catch the cases a score can't see. With a small pool, that takes minutes.
- Send the ranked shortlist to the hiring manager. Hand over five to ten names, each with the evidence behind its rank, and the manager interviews the strongest first. Nobody has to reargue the whole applicant pool, because the reasoning is on the page.
- The slow version stretches this across weeks because a person reads every resume in turn. The fast version scores the whole pool at once and saves human judgment for the places where it changes the result.
Fast and slow shortlisting, side by side
| Step | Manual keyword screening | Ranking on evidence |
|---|---|---|
| Reading the pool | Resume by resume | Scored in one pass |
| Basis for cuts | Keyword presence | Evidence of fit |
| Time to first shortlist | Days to weeks | Hours |
| Qualified people lost | Many, through vocabulary mismatch | Few, because everyone is ranked |
| Defending the cutoff | Gut feel | A score you can show |
| Where people spend time | Skimming everyone | Judging the top few |
What speed buys you
- Faster shortlisting moves the effort to where it matters. Turn days of screening into an afternoon and you get that time back for interviews, references and the team fit conversations that people should have. The judgment stays with you, and you have more time for it.
- It also wins candidates. The strongest people leave the market first, so if your shortlist takes weeks, your best candidate may have accepted another offer. If it takes hours, yours can be the first offer they get.
- It also guards against the plausible resume. When you rank on evidence, the person who did the work outranks the person who wrote about it well. That is what [hiring on proof of fit](/spaces/hiring-on-proof-of-fit) means in practice.
How Unframed does it
- Unframed ranks every applicant on evidence of fit and turns a full applicant pool into a ranked shortlist you can defend, in hours. Each candidate is scored against the role's real requirements, so nobody qualified is dropped on a technicality and you can explain every cut.
- You keep the judgment, and we take on the screening that stands between you and it. If you want to interview your strongest candidate tomorrow, [see how it works for hiring teams](/companies).
Frequently asked questions
- How fast can you actually build a shortlist?
- In hours. The slow part was always manual keyword triage. Rank every applicant against the role's requirements in one pass and a top ten you can defend can be ready the day the role opens.
- Is fast shortlisting less accurate than slow manual review?
- No. Recruiters give each resume about 11 seconds on a first scan, which is too little time to judge anyone fairly. Ranking every candidate on the same fit criteria is faster and more consistent than a tired person skimming for keywords.
- What is the difference between shortlisting and screening?
- Screening removes people who fail a pass or fail bar. Shortlisting ranks the rest so you interview the strongest first. Fast shortlisting does both in one ranked pass, so nobody qualified is dropped over a keyword.
- Does faster shortlisting mean ignoring cultural or team fit?
- It gives you more time for it. When the mechanical screening takes minutes instead of days, you can spend the hours you save on interviews, references and team fit, which are the decisions people should make.
- How many candidates should end up on a shortlist?
- Five to ten for most roles. That gives the hiring manager a real choice, and it is few enough that every name gets a proper interview. A ranked list means you can explain where you drew the line.
Sources
Next step
Try it on your next role
Unframed builds shortlists by ranking people on proof of fit.