Build a shortlist you can explain in five minutes

A client asks why you put candidate A ahead of candidate B. The wrong answer is, “They scored higher.”

That is not because scores are inherently bad. A score can be a useful way to hold a large batch in your head. The problem is that it is the conclusion, not the explanation. If the only thing you can produce is 82 versus 74, the client has to either trust a black box or start the comparison again from scratch.

Neither is a good use of a recruiter’s work.

The test for a shortlist is simpler: could the person who made it explain each candidate’s place in five minutes, using the job requirements and the CV in front of them? If not, it may be a ranking, but it is not yet a decision.

Start with the comparison the client will make

Clients do not assess people as a single number. They ask a sequence of questions: Can this person do the core job? Have they done it in a context like ours? What would I need to probe in interview? What is missing, and is it actually important?

A useful shortlist should make those questions easier, not add a layer between the client and the answer. For each candidate, show:

• the essential requirements and whether the CV contains evidence for each;
• the strongest two or three reasons they are near the top;
• the gaps or uncertainties that need a recruiter’s judgement; and
• the exact CV evidence behind the assessment.

The last line is the difference maker. “Has enterprise SaaS experience” is an assertion. “Led implementation for 40 enterprise accounts at X” is evidence. The recruiter can agree or disagree with the interpretation, but they do not have to wonder where it came from.

Scores should be navigational, not magical

There is nothing wrong with weighting requirements. If production experience with a particular technology is essential, it should matter more than a bonus qualification. A weighted score helps a recruiter sort sixty plausible CVs into an order worth reviewing.

But do not pretend that the difference between 78 and 81 is a scientific fact. It is a prompt to look closer.

Treat the score as a navigational aid:

• A large gap can reveal a clear mismatch with the brief.
• A cluster of similar scores is a signal to compare the evidence, not to choose the highest decimal.
• A low score with unusually strong context may be exactly the candidate a good recruiter should rescue from the middle of the list.

This framing has a practical benefit. It prevents the system from becoming a quiet veto. Nobody disappears because a number says so; the number tells a person where to spend attention.

Name uncertainty instead of hiding it

The temptation in any candidate summary is to smooth the awkward bits away. The person sounds good, the client is impatient, and the recruiter wants the submission to feel decisive. But uncertainty does not disappear when omitted. It returns in interview, usually when the client discovers it first.

Good shortlists make uncertainty explicit and proportionate. “AWS appears in the skills section but not in the work history” is useful. “Likely weak on AWS” overstates what the CV proves. “Three short roles in two years; ask about the context” is a better recruiter note than inventing a story either way.

This is also where evidence protects candidates. Absence of proof in a CV is not proof of absence in a career. By separating what is present, what is uncertain, and what is genuinely missing, the recruiter can ask a fair question instead of making an unsupported assumption.

Make the final call visible

There should be a moment in the workflow where a recruiter changes “ranked” to “submitted,” and that moment should be deliberate. The shortlist is not a system output delivered to the client unchanged. It is a recruiter-owned recommendation informed by structured evidence.

That ownership matters when the client challenges a choice, when a candidate asks for feedback, and when a colleague inherits a role halfway through a process. The next person should be able to see what the original decision was, what evidence supported it, and where professional judgement was applied.

It also makes improving the process possible. If a client consistently hires candidates your rubric placed in the middle, you can inspect the pattern. Was a requirement weighted too heavily? Was the brief missing a real preference? Did the CV format hide relevant experience? Without the evidence trail, all you have is a vague feeling that the ranking was off.

The five-minute handover

Try this on your next live role. Hand the shortlist to another recruiter and give them five minutes to answer these questions:

1. Why is the first candidate first?
2. Which essential requirement is least evidenced for the second candidate?
3. What would you ask the third candidate before submitting them?
4. What changed between the original brief and the list in front of you?

If they can answer from the shortlist itself, it is doing its job. If they need to reopen every CV, reconstruct the brief from memory, or guess how a score was produced, the shortlist is asking the client to do your desk’s work twice.

The aim is not a prettier report. It is a hiring conversation that starts with the right evidence already on the table — and leaves the decision where it belongs, with the recruiter and the client.