Keep a candidate slate version log for executive searches

Name the slate version

A candidate slate changes as interviews are added, references arrive, and the hiring executive gives feedback. Without a version log, two reviewers can discuss different lists while believing they are looking at the same search. The log should identify the slate date, the candidates included, the source of each addition, and the person who approved the version. Record the evidence and the next owner before the case leaves the queue. Keep the note factual enough for a later reviewer to continue.

Use a simple change history rather than a folder of files named final. Record the previous version, the new candidate, the reason for the change, and the time it took effect. If a candidate is removed, keep the reason and the stage they reached. A later reviewer may need to know whether the removal was a withdrawal, a rejection, or a scheduling problem.

Keep the log close to the search record, not in a private spreadsheet. The hiring executive should be able to see which slate was reviewed at a decision meeting and which candidates were available at that time. A clean current list without a history is not enough for an executive search. Record the evidence and the next owner before the case leaves the queue. Keep the note factual enough for a later reviewer to continue.

Separate the slate from the pipeline

The slate is the short list presented for a decision. The pipeline is the larger set of people who have been contacted or considered. Mixing them makes the search look more advanced than it is and can create false expectations about who has been interviewed. Record the evidence and the next owner before the case leaves the queue. Keep the note factual enough for a later reviewer to continue.

Label each candidate by stage: sourced, screened, interviewed, referenced, finalist, or closed. Add the date of the latest meaningful event. A candidate who has been sourced but not contacted is not equivalent to one who has completed a panel. The label should reflect evidence, not optimism.

When the hiring executive asks for the slate, state the version and the decision it supports. If the slate is being used to choose interview candidates, say so. If it is being used to discuss an offer, the list should include the candidates who reached that stage and the evidence already collected. Record the evidence and the next owner before the case leaves the queue. Keep the note factual enough for a later reviewer to continue.

Protect confidentiality in the log

Executive searches often involve candidates who do not want their interest known. The log should use the approved record system and restrict access to the search team. Do not put candidate names, compensation details, or reference comments in a general channel or an unapproved personal file. Record the evidence and the next owner before the case leaves the queue. Keep the note factual enough for a later reviewer to continue.

Record only the information needed for the decision. A candidate's current employer, scope, and relevant experience may be necessary; personal contact details or family information usually are not. If a sensitive note is needed, link to the approved document rather than copying it into the slate. Record the evidence and the next owner before the case leaves the queue. Keep the note factual enough for a later reviewer to continue.

Review access when the search team changes. A coordinator who leaves the search should lose access to the slate and the candidate documents. The exit check should include shared drives, messaging channels, and any exported files used for interview scheduling. Record the evidence and the next owner before the case leaves the queue. Keep the note factual enough for a later reviewer to continue.

Make changes visible to the reviewer

A version log is useful only when the reviewer knows it exists. At each decision meeting, show the slate version and a short summary of changes since the prior review. The reviewer can then ask why a candidate was added or removed instead of reconstructing the search from memory. Record the evidence and the next owner before the case leaves the queue. Keep the note factual enough for a later reviewer to continue.

If a candidate is added after a decision, record the reason and the person who approved reopening the slate. A late addition can be legitimate, especially when a search is difficult, but it should not appear as though it was always part of the plan. The record should preserve the sequence. Record the evidence and the next owner before the case leaves the queue. Keep the note factual enough for a later reviewer to continue.

Close the search with a final slate version that identifies the selected candidate, the alternatives considered, and the decision date. That version becomes the reference for onboarding and for any later question about the search. Without it, the final choice can look arbitrary even when the process was careful. Record the evidence and the next owner before the case leaves the queue. Keep the note factual enough for a later reviewer to continue.

Audit the version log quarterly

Sample a few completed or active searches and check whether the slate version matches the decision notes. Look for missing approvals, unexplained removals, and candidates who appear in the final list without a documented stage. The pattern may reveal a training gap or a weak handoff. Record the evidence and the next owner before the case leaves the queue. Keep the note factual enough for a later reviewer to continue.

Do not use the review to rank recruiters by the number of changes. A difficult search may legitimately have many versions. The useful question is whether each change is traceable and whether the hiring executive reviewed the version that was actually used. Record the evidence and the next owner before the case leaves the queue. Keep the note factual enough for a later reviewer to continue.

Choose one improvement and test it: a required change reason, a slate summary field, a meeting template, or an access review at search close. Assign the owner and the next review date. The goal is a search record that a new stakeholder can understand without a private explanation. Record the evidence and the next owner before the case leaves the queue. Keep the note factual enough for a later reviewer to continue.

Frequently asked questions