Runner-up candidates, sometimes called silver medallists, are the people who reached the final stage of a vacancy but were not hired. They are only worth something later if your Applicant Tracking System records why they were runner-up, what they want next, whether they agreed to stay in your talent pool and until when, and who will contact them again on which date. With those fields in place, the Applicant Tracking System can show the pool first whenever a similar vacancy opens, before anyone starts a new search. Without them, a strong candidate disappears into a closed vacancy and is found again only by chance.
The approach is the same in every segment, but the reasons to use it differ. Recruitment agencies often see similar client orders return within months. Staffing desks need people who are available quickly and already known. Secondment teams look for professionals whose next assignment can follow on from a previous process. Executive search firms build long relationships with a small number of senior candidates. In-house recruitment teams can offer a runner-up a different role inside the same organisation.
Why strong runner-up candidates get lost
The same patterns appear on many desks:
- The candidate receives a polite rejection and the record is closed with the vacancy, without any note that they were a close second
- Interview notes that explain why the candidate was strong sit in an email or a notebook, not in the candidate record
- Nobody asks whether the candidate wants to be contacted again, so later outreach is either skipped or happens without a basis
- When the next vacancy opens, the desk starts with job boards because searching old vacancies by hand takes longer
- The same person is contacted by two recruiters at once, or not at all, because nobody owns the follow-up
A bigger database does not solve this. A few recorded facts per runner-up candidate do.
What to record when a runner-up candidate leaves the vacancy
- Outcome and reason — close the candidate on the vacancy with a standardised rejection reason such as runner-up, strong fit, so the pool can be filtered later; if the candidate withdrew instead, use the recorded withdrawal reason
- Stage reached — final interview, client interview or offer stage, recorded by the Applicant Tracking System when the candidate moved, not typed in afterwards
- Why they were strong — a short summary based on the written interview outcomes, in words a colleague can use without having met the candidate
- What they want next — role types, location, working pattern and availability as the candidate stated them, with the date they said it
- Consent and retention — whether the candidate agreed to stay in the talent pool, for which purpose, and the retention date that applies to the record
- Owner and re-contact date — one named person and a next-action date, so the follow-up appears in someone's list instead of in someone's memory
Consent and retention come first
A talent pool is only useful if you are allowed to use it. Ask the candidate at the moment you share the outcome whether they want to be considered for future vacancies, and record the answer, the date and how it was given in the Applicant Tracking System. Keep that permission separate from the consent for a specific client submission: agreeing to stay in your pool is not agreeing to be presented to any client. When the retention date approaches, the candidate is either asked to renew the permission or the record is handled as your privacy policy describes. Privacy legislation such as the General Data Protection Regulation sets the frame; your own policy sets the periods, and the Applicant Tracking System makes sure they are applied to every record in the same way.
Check the pool before you start a new search
When a new vacancy opens with a structured brief, the owner of the role first filters the talent pool on role type, location, stage reached and availability, and reads the summaries of the best matches. That check takes minutes when the fields above are filled, and it is a step the Applicant Tracking System can prompt automatically when a vacancy is created, as described in which recruitment steps to automate. Only the selection of who to contact stays a human decision. Before contacting anyone, check that the record is not a duplicate of a newer profile with more recent information.
How to re-contact without losing trust
- Write a personal message that refers to the earlier process and the new vacancy, not a bulk mailing to the whole pool
- Let one person contact the candidate, so they do not hear from two colleagues about the same role
- Record the response on the candidate record: interested, not now with a new re-contact date, or no longer interested
- When a candidate asks to be removed, remove them from the pool and handle the record as your policy describes
- Keep the conversation with the client contact person in the candidate and client relationship records beside the pipeline, so it is clear who knew what and when
Report on the pool honestly
If you want to know whether the talent pool works, record talent pool as the source when a runner-up candidate is linked to a new vacancy, in the same way you record the source at first application. Then you can count how many vacancies were filled from the pool and how long they took, using the same definitions as in reliable time-to-fill reporting. Report the actual counts from your own records, show how many vacancies sit behind each figure, and do not quote general benchmarks you cannot verify. A small, honest number tells you more than a large, estimated one.
Where artificial intelligence may help — and where it must not
Artificial intelligence may suggest runner-up candidates whose recorded summary and preferences resemble a new brief, draft a first version of a personal message, or point out pool records with a retention date that is about to expire. It must stay secondary. Artificial intelligence does not replace recruiters, does not decide who is contacted, does not send messages on its own, and does not add candidates to the pool without recorded permission. The Applicant Tracking System holds the facts; the owner of the vacancy decides and makes the contact.
A practical week to get started
- Add runner-up, strong fit as a rejection reason and agree which stage a candidate must have reached to qualify
- Add the consent question for the talent pool to the message or call in which you share the outcome
- Look back at vacancies closed in recent months and mark the runner-up candidates you can still identify, with a note that the entry was added afterwards and without assuming consent that was never given
- Give each marked candidate an owner, a retention date and, where permission exists, a re-contact date
- Agree that every new vacancy starts with a check of the talent pool before the first job advertisement goes out
The first pool will be small. That is fine: it contains people you know, who agreed to hear from you.
Keep your best second choices within reach
A runner-up candidate is the closest thing to a ready shortlist that a recruitment desk has. Record why they were strong, what they want, their permission and retention date, and who follows up when, and check the pool before every new search. Then explore the product or book a demo — we walk through talent pools and runner-up follow-up in BoldATS for your segment.