Too many qualified applicants? Decide who to interview next
Narrow a shortlist of qualified applicants without inventing new requirements. Compare extra interviews with another task, including staff and candidate time.
· 11 min read

A hundred applicants appear to meet the requirements, but your manager has ten interview slots. You need to choose whom to meet without pretending everyone else is unqualified.
Choose on the job’s agreed priorities, not new requirements invented to produce a shorter list. First compare the evidence you already have. Then resolve important gaps and decide whether another assessment is worth the work.
Follow the decision from 100 qualifying applications to a close group of 12. Interviewing two extra people can take less work than giving everyone another test.
How do you narrow a shortlist when many applicants qualify?
Meeting the essentials makes an applicant eligible for consideration; it does not guarantee one of ten interview places. When several applicants qualify, compare how strongly their evidence addresses the priorities already set for this vacancy.
Keep both findings in the record. Someone can meet the minimum and still be passed over for an applicant with stronger relevant evidence. That is not the same as failing a requirement.
Ask the manager which agreed responsibilities should carry most weight. Then compare the evidence for those responsibilities, not a collection of convenient tie-breakers. An extra year, familiar employer or optional qualification should not become decisive merely because it produces a list of ten.
Singapore’s TAFEP guidance calls for job-related selection criteria. For Great Britain, Acas recommends fair selection against the job description and person specification, ideally involving at least two people. Use those agreed criteria for the comparison rather than shifting them after an appealing application arrives.
The manager may discover that the role needs something different. Record the change to the brief and agree how to inform and reassess affected applicants. Keep the earlier assessment clear about the requirements used at the time.
Compare candidates against the same job priorities
Use an operations vacancy whose minimum requirement is experience handling order problems. The advertised priorities also include investigating recurring errors and checking whether changes help. The team will teach its software.
A large project title is not automatically stronger evidence than a small, well-explained improvement. Look for the applicant’s own investigation, action and check of the result.
When that contribution is missing from the full application, ask:
Your CV mentions an improvement project. What did you handle yourself, and what happened next? One example is enough.
Use the same clarification approach for comparable gaps. Then compare the work described, not whose answer sounds grander.
Compare three qualified applicants
All three applicants meet the basic order-handling requirement. The narrower comparison is who describes investigating a recurring problem and checking a change. Monitoring errors does not, by itself, establish that errors fell.
| Applicant | Relevant evidence | Comparative decision |
|---|---|---|
| Alex | Resolves individual order issues and explains them clearly to customers. | Meets the stated minimum. Prevention experience is not yet established. |
| Beth | Traced repeated picking errors to confusing item descriptions, changed the checks and monitored later errors. | Describes investigating a recurring problem and checking a change. Ask how the cause was identified and what the monitoring showed. |
| Casey | Lists a large improvement project but leaves their own contribution unclear. | Clarify the relevant contribution before treating the project as stronger or weaker evidence. |
Beth’s account addresses the advertised investigation priority. Alex meets the minimum but has not supplied that additional example. Casey needs clarification before the project can support a comparison.
Continue the example with Casey’s reply:
I kept the issue log and chased overdue fixes. The analyst compared the order data and identified the cause. I did not do that analysis.
Casey has now described coordination work, not an unresolved claim to have done the investigation. On the evidence available, Beth has the stronger account of the advertised investigation priority. Write that reason down without calling Alex or Casey poor problem-solvers.
Keep the advertised priorities fixed during the comparison. Beth's example is relevant because recurring-error prevention was already part of this vacancy. It should not become a new criterion simply because one appealing CV mentions it.
Compare the applicant's contribution as well as the outcome they report. A large project result does not establish who did the work; an applicant without access to company-wide figures may still explain their checks clearly.
When reviewers disagree, identify the disputed passage or requirement. Did one give Casey credit for the whole project, or dismiss Beth's example because it came from an unfamiliar setting? Resolve that reading before combining the recommendations.
After comparable clarifications, some applicants may remain similarly strong. Keep that conclusion. A calendar with ten slots does not create evidence that the eleventh person lacks a skill.
Work through all 100 before filling the ten places
Use a short comparison note for each application, with a link to the original answer. For this vacancy, record the recurring problem the applicant describes, what they did themselves and how they checked the change. Keep those headings tied to the advertised priorities; they are not new minimum requirements.
Work through the whole group before allocating the final places. You can identify promising applicants as you read, but the first ten good examples should not end the comparison while other applications remain unread.
Bring the manager the strongest supported recommendations and the close decisions. For Beth and Casey, the note can now say: “Both handled order problems. Beth describes investigating a recurring error; Casey coordinated fixes based on an analyst’s investigation. Beth’s example more directly addresses this vacancy’s stated priority.”
Use a score where your agreed rubric supports it, but keep this reason beside the number.
Resolve material gaps through the same clarification approach, then compare again. When the remaining applicants are genuinely tied, move to the capacity decision rather than keep rereading until a minor difference looks decisive.
Is another assessment less work than two extra interviews?
Suppose that comparison leaves 12 applicants with similarly strong evidence for ten interview slots. Would another task help distinguish them, or would it be easier to arrange two more interviews? The other applicants may still meet the minimum; this is a choice about the strongest next-stage evidence.
Compare the routes using one set of assumptions. A 30-minute interview requires 15 more staff minutes for preparation and notes. Each appointment therefore uses 45 staff minutes. The proposed task takes an applicant 15 minutes and a reviewer 10 minutes to assess.
For this calculation, one person conducts each interview, one person reviews each task and everyone finishes. Task design, scheduling, applicant preparation and travel remain outside the totals. Add them when deciding what your own team can support.
| Option | Total staff time | Applicant time across the whole group |
|---|---|---|
| Interview all 12 | 9 hours | 6 hours |
| Give all 12 the task, then interview 10 | 9 hours 30 minutes | 8 hours |
Interviewing all 12 saves 30 minutes of staff time and 2 hours of applicant time across the group, before task design and administration. The extra task is not the lower-workload option under these assumptions.
The manager's time may be the constraint rather than total team time. A qualified colleague could spend two hours reviewing the tasks, leaving the manager with seven hours and 30 minutes of interviewing instead of nine. That saves manager time but adds work overall.
The task may still be worthwhile if it shows a skill the interviews cannot assess. But for a test added only to avoid two appointments, the practical request is simpler:
We have 12 similarly strong applicants for ten slots. Interviewing all 12 needs 90 more manager minutes. A task for all 12 would take two review hours and add work overall. Can we find two more slots, or is there an untested skill that makes the task necessary?
What if you give all 100 applicants a task?
A fifteen-minute task for each of the original 100 applicants asks for 25 hours of their time. At ten minutes per answer, your team needs 16 hours 40 minutes to review the work, before interviews or task design. The task needs to provide useful evidence to justify that effort.
See the calculation and the effect of adding an interviewer
Interviewing all 12 uses 12 × 45 = 540 team minutes, or 9 hours. Applicants spend 12 × 30 = 360 minutes, or 6 hours.
The task option uses 12 × 10 = 120 review minutes, plus 10 × 45 = 450 interview minutes. The total is 570 minutes, or 9 hours 30 minutes. Applicants spend 180 minutes on tasks and 300 in interviews: 8 hours in total.
If two interviewers attend every interview and each needs 15 minutes for preparation and notes, interviewing all 12 takes 18 staff-hours in total. The task option takes 17 hours of staff time before setup. That changes the team's time comparison, but not the applicants' time.
Ask “What could this task tell us that would change the interview list?” All 12 applicants may pass. A task that only confirms the existing evidence leaves the original selection problem unresolved.
Withdrawals can make the list smaller too. That is not evidence the task identified stronger candidates. Keep the assessment results separate from the people who chose not to spend more time on the process.
If the task is already necessary to assess writing or another essential skill, placing it before the manager interview may be sensible. That is different from designing a new task solely to avoid two appointments. Compare the actual sequence and staff constraint, not the number of interviews alone.
What should you do when qualified applicants remain tied?
Separate a genuine tie from missing evidence. If a relevant skill remains untested, use the assessment designed for it: a customer reply for writing, for example, rather than another questionnaire about experience you have already established.
If the relevant evidence is complete and still tied, return to interview capacity or the campaign’s agreed selection rule. Do not keep adding tasks until someone withdraws or a minor difference looks decisive.
Set the task up so people can demonstrate the intended skill. Supply the necessary company information, explain the time and permitted tools, and provide an adjustment route. Use a practice problem rather than unpaid client work.
Track missing submissions separately from weak answers. A withdrawal or unresolved support request can shrink the group without telling you anything about the person's skill.
If you choose to compare all 12 through interviews, give each person that opportunity before selecting. Someone's later appointment should not count against them.
Take a genuine tie to the person responsible for hiring policy. Explain the evidence and the available capacity, then agree a selection method consistent with the advertised process. Record it as a selection between qualified applicants, not a skill deficit you did not find.
Confirm the interview list and available times
Get the approval your process requires before inviting anyone. Where the manager approves the list, send the application link with a specific reason:
I recommend interviewing Beth. They traced repeated picking errors to confusing item descriptions, changed the checks and monitored later errors.
Please explore how they identified the cause and what the monitoring showed. Can you approve the interview and confirm a time?
Agree who to interview and which slots you can offer. An automated recommendation isn't the same as the team's approval to send an invitation.
What do you tell qualified applicants who are not shortlisted?
Explain whether the decision is still pending or the shortlist is complete. Do not describe a qualified applicant as failing an essential requirement when the decision was a comparison between several suitable people.
A candidate still waiting for a decision needs a clear update:
We're still deciding whom to invite to interview. I'm sorry to keep you waiting.
I'll update you by Thursday, even if we're still reviewing applications. You don't need to send anything else while you wait.
Use a date you can meet. The promise is to send an update, not necessarily to finish the decision by then.
Once the shortlist is agreed, tell the other applicants. Give a more specific reason only when it matches the assessment and your feedback policy.
A message for that decision could read:
Thank you for applying. We've completed our shortlist and won't be inviting you to interview for this role. We had more applicants meeting the requirements than we could interview.
Use that explanation only when it matches the decision. Promise consideration for future roles only when the team has a process for doing it and an appropriate basis for retaining the information.
Finish the meeting with the interview group, the reasons for choosing it and real appointment times. Assign the updates for everyone else before the team moves to the next vacancy.
The manager’s ten slots limit the interview plan, not the number of qualified applicants. Leave with a choice you can explain, enough time to carry it out and an update for everyone who is still waiting.


