A shortlist presentation has one job: help the client decide whom to interview, and why. The strongest presentations restate the agreed brief, explain the field the candidates came from, show each candidate against the same requirements, separate evidence from judgement, and end with clear decisions. The candidates' CVs are supporting evidence; the recruiter's reasoning is what the client is buying.
This guide walks through each part of that meeting, using a fictional example shortlist you can download as a template. It also shows a weak fit note rewritten into a useful one, and ends with a printable meeting agenda.
What a shortlist presentation needs to help the client decide
By the shortlist stage the work has moved on from research. AESC, the executive search industry body, describes the sequence as approaching and evaluating candidates, creating a longlist, evaluating a shorter list, and then presenting "the shortlist of qualified, interested candidates". The presentation is where that work becomes a client decision.
The client usually needs to decide four things:
- Who to interview, and in what order.
- Whether the brief still holds. The shortlist often shows that one requirement is narrowing the field more than it is worth.
- What each interview should test. Your open questions become their interview plan.
- What happens if no one progresses. A fallback agreed now saves weeks later.
Everything in the document and the meeting should serve one of those decisions. Material that serves none of them belongs in your notes, not the deck.
Restate the agreed brief and explain the field
Open with the brief as it was agreed, not as you remember it. Clients' priorities drift between kick-off and shortlist; restating the brief makes any drift visible before you discuss individuals.
Then explain the field in two or three sentences. In the example: we checked 46 employers, identified 58 leaders within the remit, approached 17, held nine conversations and are presenting three. That one line tells the client the shortlist is the result of a defined search rather than whoever replied first. If a requirement removed strong people, say so here: in the example, the London-only requirement excluded most of the strongest field, and the client agreed hybrid working before approaches began.
Keep this section short. It is context for the candidates, not a second market report. If the client needs the full market view, what goes in a market map covers that deliverable separately.
Present candidates against consistent requirements
Give every candidate the same structure, in the same order, so the client compares like with like:
| Part of the candidate page | What it contains | Why it is there |
|---|---|---|
| Current role and location | Title, employer, base location, working pattern discussed | Establishes the starting point |
| Career facts | Relevant roles, dates and remit, with the source | Facts the client can rely on |
| Fit against the brief | A recruiter-authored note linking evidence to each key requirement | Your judgement, clearly labelled as such |
| Still to verify | What the interview or references need to test | Turns uncertainty into an interview plan |
| Status | Contacted, interviewed by you, interest confirmed, notice period as stated by the candidate | Shows where the candidate is in the process |
Keep facts and judgement visibly apart. "Leads around 90 engineers across seven teams, confirmed in interview" is a fact with a source. "The strongest evidence of regulated delivery on the shortlist" is your judgement. Both belong on the page, but the client should never have to guess which is which.
If you add a side-by-side comparison of the candidates against the requirements, label it as your assessment. A comparison table looks objective; its cells are still judgements.
Write a fit note that connects evidence to the brief
The fit note is the most-read and most-skimmed part of a candidate page. Most weak fit notes describe the person. Strong ones connect specific evidence to specific requirements, and admit the gap.
Weak:
Maya is an impressive engineering leader with a strong fintech background. She is a great communicator, passionate about building teams, and would be a fantastic cultural fit. Highly recommended.
Every sentence there is an assertion without evidence, and "cultural fit" tells the client nothing they can test.
Rewritten:
Maya leads payments and ledger engineering at a challenger bank: around 90 engineers across seven teams, confirmed in our interview. She led the migration to a new card-processing provider against a regulatory deadline, the closest match on this shortlist to your launch. The gap is scale: she has not yet led 140 engineers, and she has not reported directly to a board. We suggest your interview tests how she would structure the next layer of leadership. She is based in Manchester and has proposed two days a week in London.
The rewrite does four things: it gives a sourced fact about remit, links one achievement to the client's specific situation, names the gap plainly, and turns that gap into an interview question. It also avoids claims the recruiter cannot support.
Make uncertainty and contact status clear
A shortlist implies that candidates have been contacted, assessed and are interested. Make each of those visible rather than implied.
| Status item | Example wording | What to avoid |
|---|---|---|
| Contact | "Approached 12 September; two interviews with us" | Presenting someone who has not been contacted |
| Interest | "Confirmed interest in this role on 1 October" | "Open to opportunities", inferred from a profile |
| Package | "Expectations discussed; within the agreed range" | Salary guessed from public sources, or detail the candidate has not agreed to share |
| Notice | "Three months, as stated by the candidate" | A notice period presented as verified |
| References | "To be taken after first interview, with consent" | Implying references are complete |
Candidates should know what is being shared about them and with whom. Share only what is needed for the client's decision, and keep your private interview notes private.
Choose PDF, PowerPoint or a review link
The format depends on how the decision will be made.
- PowerPoint suits a presented meeting. You control the order, and the client can lift slides into an internal pack.
- PDF suits a document the client reads, files or forwards. It holds its layout on any device.
- A live review link suits a client who will comment asynchronously, or a panel that cannot meet together. Feedback arrives in one place rather than across email threads.
Many agencies present the deck in the meeting and send the PDF as the record afterwards. TalentMaps produces both from the same project: a branded PDF or PowerPoint in one of eight layouts, or a live review link where the client can leave feedback. Its report carries a brief page, with the client's requirements and your shortlist rationale, and candidate pages grouped by the tiers you assign. Recruiter-private notes never appear in the client-facing output. The fit notes, tiers and rationale are always written by you.
Ask for feedback that determines the next step
End the meeting with decisions, not "let us know your thoughts". Ask for one of three outcomes per candidate, each with a reason:
- Interview, with proposed dates and interviewers.
- Hold, with what would change the decision.
- Decline, with the reason, so the next candidates are better targeted.
Then agree the fallback. If none of the three progress, what changes: the location requirement, the scale requirement, or the borderline employer segment held back during research? Write down the answers before the meeting ends and confirm them by email the same day.
The annotated example
The example deck has eight slides. Here is why each one is there.
| Slide | What it shows in the example | Why it exists |
|---|---|---|
| Cover | Role, client, agency, date, and a confidentiality line | Makes the document safe to forward and file |
| The brief and how we searched | Agreed requirements, split into essentials and preferences, and the line from 46 employers to three candidates | Shows the shortlist came from a defined search |
| At a glance | A manually completed comparison of the three candidates against the essentials | A quick orientation, labelled as the recruiter's assessment |
| Candidate 1: Maya Collins | Regulated delivery at slightly lower scale; Manchester, hybrid | The closest match on the hardest requirement |
| Candidate 2: Daniel Osei | Closest on scale and location; inherited rather than built his organisation | A contrasting strength, so the client is choosing, not confirming |
| Candidate 3: Ruth Hamilton | Deep governance in a large bank; pace and product delivery to test | The adjacent profile that tests whether the brief can flex |
| Next steps | Decision needed per candidate, proposed interview dates, references, the fallback | Ends the meeting with owned actions |
| Closing slide | Where the template came from | Remove or replace with your own back page |
Three contrasting candidates make the meeting about trade-offs. If all three looked alike, the client would be choosing between near-duplicates rather than deciding which strengths matter most.
A printable shortlist meeting agenda
Allow 45 to 60 minutes with the hiring manager and anyone else who will decide on interviews.
- Brief check (5 minutes). Restate the agreed brief. Has anything changed since kick-off?
- The field (5 minutes). How the shortlist was built, and which requirement most narrowed it.
- Candidates (25–35 minutes). For each: the fit note, the gap, the question for interview. Take questions after each candidate, not at the end.
- Decisions (10 minutes). Interview, hold or decline for each candidate, with a reason.
- Logistics and fallback (5 minutes). Interview dates and interviewers, reference timing, and what changes if no one progresses.
- Confirm by email the same day. Decisions, owners and dates.
Related reading
For the stage before this one, where a mapped field becomes candidates you approach, see what is candidate mapping and what is executive search research. For how mapping and search fit together commercially, see talent mapping vs executive search.
To produce the deck itself, download the candidate shortlist presentation template, or build the shortlist in TalentMaps from your candidates' LinkedIn URLs and export it in your agency's branding.
Source for search-stage terminology: AESC, "The Executive Search Process: What to Expect", checked 7 October 2026.
Frequently asked questions
- What should a shortlist presentation include?
- The agreed brief, a short account of the field you researched, and one page per candidate covering career facts, an evidence-based fit note, open questions and contact status. Close with the decisions you need from the client and by when. Keep recruiter-private notes, assumptions about salary and anything you have not verified out of the document.
- How many candidates should be on a shortlist?
- There is no universal number. A shortlist is a small group of qualified, interested candidates the client can realistically meet and compare. Three strong, contrasting candidates usually make a better decision than eight that look alike. If you cannot reach a credible number, say so and explain what would widen the field.
- Should you send the shortlist before the meeting?
- Usually a short summary, yes, so the client arrives prepared, with the full document walked through in the meeting. Sending everything in advance invites decisions by email before you have explained the trade-offs. Agree the approach with the client, and make sure every candidate has consented to their details being shared.
- What is the difference between a longlist and a shortlist?
- A longlist is the wider set of potential candidates identified from the research, before full evaluation; many will not have been contacted. A shortlist is the smaller group who have been approached, assessed and have confirmed interest. AESC, the executive search industry body, describes the shortlist stage as presenting qualified, interested candidates.