What Actually Goes Into a Client-Ready Candidate Shortlist
Ask ten recruiters what belongs in a candidate shortlist and you'll get ten slightly different answers. It's one of those parts of the job that everyone does constantly and nobody was ever formally taught — which is why threads asking the basics still get real engagement from working consultants.
What to actually include
One consultant laid out their usual list and asked the room if it was right:
When sharing a shortlist with a client, I usually include: Candidate name, Current job title and company, Location, Notice period, Salary expectations, LinkedIn profile, Short professional summary, Key strengths and skills, CV. Is this too much, too little, or about right?
The follow-up comments pushed further — whether the assessment should map to an agreed scorecard, and whether a specific client checklist should get its own comparison grid rather than being buried in prose. None of it is exotic. It's the same handful of fields, over and over, because clients are making a hiring decision and need the same facts every time: who this person is, what they're doing now, whether they're actually available, and why the recruiter thinks they fit.
Should you rank them?
This one splits the room. In a separate thread, a consultant asked directly whether to rank candidates first-to-fourth or present them as equals and let the client decide:
Sometimes I do, sometimes I don't. It depends on the intake conversation... Unless they tell you to rank them, or you get a strong vibe that you should rank them, I am hesitant to rank.
Another consultant in the same thread takes a more deliberate approach to ordering, even without a hard numeric rank:
I wouldn't rank them, maybe put my favorite first. I toss one or two bad candidates towards the end, hiring managers usually feel a need to reject someone, if I don't put a bad one in chances are they'll reject my top pick.
Order is judgment, not formatting — and that judgment is exactly the part of the job that doesn't show up in a plain PDF or a stack of CV attachments.
The training world agrees it's a distinct skill
This isn't just a Reddit debate. James Caan CBE — the UK recruitment entrepreneur behind Alexander Mann and a former Dragons' Den investor — dedicates an entire module of his recruitment training series specifically to this moment, titled "Presenting a Candidate to a Client", with a chapter on preparing the pitch before the client ever sees the shortlist. If it needs its own training module, it's not a formatting afterthought — it's a skill.
Where it actually breaks down
None of the above is where things go wrong, though. The fields and the ordering are solvable with fifteen minutes of thought. What's harder is what happens after the shortlist is sent: a candidate accepts another offer, a client wants a different order, feedback comes back on one specific person — and now the "shortlist" is actually a deck plus a PDF plus a covering email plus however many follow-up threads it takes to reissue the corrected version. The client is left digging through their inbox to figure out which attachment is current.
That's a version-control problem wearing a recruiting hat, and it's not solved by getting better at writing the first email.
What we built instead
Sumor turns the shortlist into one link instead of a file. You still make every judgment call above — what to include, how to order candidates, when to flag a concern — but the link updates live when something changes. Remove a candidate who's withdrawn, reorder for a new client conversation, fix a detail: the same link the client already has just reflects it. No re-send, no "ignore my last email, here's v3."
It's free, there's no install for the client, and it carries your firm's branding, not ours. If sending shortlists is a thing you do every week, that's the part worth fixing first.