Screening and selection · 6 min read
How to shortlist applicants fairly
A fair shortlist comes from rules you set before you read a single application, applied the same way to everyone. This guide shows how to set those rules, score against them and record each decision.
What a fair shortlist looks like
Shortlisting is the point where a long list of applicants becomes the few people you will interview. It is also where many unfair decisions happen, because it is fast, often done by one person, and rarely written down. A fair shortlist is not about being generous or strict. It is about being consistent.
In practice, a fair shortlist has four features:
- The criteria were agreed before anyone read an application.
- Every applicant was judged against the same criteria, in the same way.
- The reason for each decision is written down in a sentence or two.
- Someone other than the first reviewer checked a sample of the decisions.
This guide covers the decision rules and the process around them. For the skill of reading an individual CV against the job, see our guide to screening CVs against job requirements.
Set the decision rules before you open applications
The most useful work happens before the job goes live. Sit down with the hiring manager and turn the job description into a short list of criteria. If the job description is vague, fix it first. Our job description templates give a starting point for common roles.
Split the criteria into two groups.
- Must-haves: requirements the person cannot do the job without on day one. Keep these to three or four. A legal right to work, a required licence or a core technical skill are typical examples.
- Strengths: things that make someone a stronger candidate but can be learned or worked around. These are scored, not used to reject.
Then agree three more rules, in writing:
- How each strength is scored. A simple scale works: 0 for no evidence, 1 for some evidence, 2 for clear evidence.
- What size the shortlist should be. Decide a target, such as six to eight people for interview, and what happens if more or fewer people qualify.
- How ties are broken. For example, by the score on the most important strength, not by gut feel or how polished the CV looks.
Test each must-have with one question: would we really reject an excellent applicant who lacks this? If the answer is no, it is a strength, not a must-have. Inflated must-haves shrink your pool for no good reason, and they tend to screen out people with non-traditional backgrounds who could do the job well.
Build a shortlisting grid
Put the rules into a grid that every reviewer uses. A spreadsheet works for a single role, though it gets hard to manage across many roles and reviewers. Here is a sample for a customer success manager:
- Must-have 1: At least two years in a customer-facing role. Yes or no.
- Must-have 2: Experience managing a list of accounts. Yes or no.
- Strength A: Renewal or retention results described. Score 0 to 2.
- Strength B: Experience onboarding or training customers. Score 0 to 2.
- Strength C: Clear written communication shown in the application. Score 0 to 2.
- Notes: one or two sentences explaining the scores.
- Decision: shortlist, hold or decline.
Notice what is not on the grid: the school someone went to, the companies they worked for, gaps in their history, their name, their age or where they live. If one of these really matters for the job, write the actual requirement instead. 'Can reach the office three days a week' is a requirement. 'Lives nearby' is a proxy.
Run the shortlist step by step
- Check must-haves first, for everyone. Go through every application and answer only the yes or no questions. Anyone who clearly fails a must-have is declined, with a short note saying which one.
- Score the strengths for everyone who passed. Score one criterion across all applicants before moving to the next, rather than scoring one applicant on everything. This keeps your standard steady and stops a strong first impression from colouring the rest.
- Total the scores and rank. Apply your tie-break rule where needed.
- Draw the line at your target size. Look closely at the applicants just above and just below the line. These are the decisions most likely to be wrong, so read them a second time.
- Have a second reviewer check a sample. Ask them to score a handful of applicants without seeing your scores, including some you declined. If your scores differ a lot, discuss the criteria, not the people, and adjust.
- Confirm the shortlist with the hiring manager. Share the grid, not just the names, so the conversation is about evidence.
Try to complete the shortlist in as few sittings as you can. Standards drift over days, and the applicants reviewed at the end of a long afternoon often get less care than those reviewed first. In Spark Careers Enterprise, each applicant gets a fit score against the job's requirements, with matched and missing skills listed and applicants ranked, so the first pass starts from the same criteria for everyone. Reviewers still make the shortlist decision and add notes for the team.
Handle the hard cases
Rules need a plan for the cases that do not fit neatly. Agree these with the hiring manager at the start too.
- Too many qualified applicants. Do not add new must-haves halfway through. Raise the cut-off score instead, or hold a short phone screen with a slightly larger group.
- Too few qualified applicants. Look again at your must-haves before lowering the bar on everything. One of them may really be a strength. If the pool is still thin, the problem is usually the job ad or where it was posted.
- Internal applicants and referrals. Score them on the same grid. Note the referral, but do not let it change the score.
- Strong applicants for a different role. If someone is not right for this job but would suit another, add them to your talent pool rather than forcing them onto this shortlist.
- Late applications. Decide in advance whether you accept them once shortlisting has started, and apply that rule to everyone.
Record decisions and close the loop
Write a reason for every decline, even a short one such as 'no account management experience'. This takes seconds per applicant and has three benefits. It lets you answer if someone asks why they were not taken forward. It helps you spot patterns, such as a must-have that rejects almost everyone. And it gives you a record that the process was consistent.
Keep these records only as long as you need them. Check the employment and data protection rules where you hire on how long you may keep applicant data and what applicants are entitled to see.
Finally, tell people. Applicants who were declined should hear back promptly, and those on the shortlist should know what happens next. A short, clear message is better than silence. The shortlist then feeds into your interviews, where an interview scorecard keeps the same discipline going.
Shortlisting checklist
- Criteria agreed with the hiring manager before the job went live
- Three or four must-haves, each tested with the 'would we really reject' question
- Strengths scored on a fixed scale
- Target shortlist size and tie-break rule written down
- Must-haves checked for every applicant before any scoring
- Strengths scored one criterion at a time
- Applicants near the cut-off line read twice
- A second reviewer checked a sample without seeing the first scores
- A short reason recorded for every decision
- Every applicant told the outcome
Your next hire, start to finish, in one place.
Free workspace. No card. Full scoring free for 7 days.