How do you resurface a silver medallist?

The moment a strong runner-up is turned down is the only moment when the whole team still remembers why. Two months on, the interviewers have moved to other panels, the scorecards read as ratings without context, and nobody can reconstruct whether the person lost on a genuine gap or on a marginal preference between two good candidates. That distinction is the entire value of the record, because one of those people is worth calling first for the next similar role and the other is not. Teams that try to build a silver medallist pool retrospectively usually find they are rebuilding a judgement rather than retrieving one.

Four fields, and they are worth being strict about because each answers a question you will actually ask later. The furthest stage reached, which tells you how much evidence you already hold. The reason they were not selected, written as a sentence rather than a dropdown, since the useful reasons rarely fit categories. What the interviewers specifically rated well, which is what you will quote when you write to them again. And whether they agreed to be contacted about future openings, recorded as their answer rather than assumed from silence. Anything beyond those tends not to get filled in, and a field nobody completes is worse than no field, because it makes the record look richer than it is.

By searching before you post, and by searching on the right thing. The instinct is to search on job title, which fails immediately because the person applied for a role your organisation has since renamed. Searching on the stage reached, the skill or two that were actually assessed, and the date range is more reliable. The discipline that matters more than the query is sequencing: make searching the existing pool the first step of opening a requisition rather than something you remember after the job advert has been live for a fortnight and the pipeline is already full of new applicants.

Acknowledge the history plainly, because pretending it did not happen is the thing people find grating. Name the role they went for and the stage they reached, say what is different about this opening, and be specific about why they came to mind — the thing an interviewer praised is usually the right detail. Be honest about the process ahead: if they would need to interview again, say so, and if some of the earlier assessment can carry over, say that too, since it is a genuine reason for them to engage. The message that fails is the one that implies the job is theirs, because it converts an easy conversation into a second disappointment.

More often than the enthusiasm for the tactic suggests. Somebody who lost on a specific capability gap has not acquired it by waiting, and approaching them for the same shortfall wastes their time and yours. Somebody who withdrew because the compensation or the working pattern did not suit is unlikely to have changed their mind unless the offer has changed. And somebody who had a poor experience last time — a slow process, an abrupt rejection — is being asked to volunteer for it again. Reading the reason field honestly is what stops a warm pool becoming a list of people who have already said no to you in a way you did not record properly.

Whether the rejection reason and the stage reached are structured enough to search on, whether the consent to future contact is stored as a field rather than a note somebody has to read, and whether a returning person joins the new process on the same record rather than as a duplicate applicant. That last one decides whether the interviewers see the earlier history at all. Run the whole loop during an evaluation on your own past candidates rather than a sample set: reject somebody with a reason, find them again a fortnight later by searching, and put them into a live requisition. It is the sequence the tactic depends on and the one demonstrations usually skip.