A shortlist can change after its first submission. A candidate may withdraw, new evidence may alter suitability, the hiring manager may ask for a different emphasis or another candidate may be added. Without clear version control, an earlier shortlist can continue circulating after the recruitment team has moved on.
A shortlist version register gives each submitted set of candidates a defined identity and records why a later version replaced it. The purpose is not to create paperwork around every note, but to keep material hiring submissions traceable.
Define what counts as the submitted shortlist
Identify the vacancy and the candidate set formally provided to the hiring contact at a particular point. Keep internal longlists, research notes and draft selections separate from the submitted version.
This prevents working material from being mistaken for a recommendation already sent to the client or hiring team.
Give each material revision a clear version
When the submitted candidate set changes, record a simple version or dated revision that colleagues can distinguish from the earlier submission. Use the team's normal naming convention where one exists.
A useful version marker should make the current shortlist obvious without requiring somebody to compare several attachments manually.
Record why the shortlist changed
Note the factual reason for a material revision, such as candidate withdrawal, an authorised requirement change or an additional candidate submission. Avoid rewriting earlier history to make the latest version appear to have existed from the start.
The change reason helps hiring contacts interpret differences between versions.
Preserve candidate-specific recruitment history
Removing a candidate from the current shortlist should not erase the underlying candidate journey or the reason their status changed. Keep that information in the appropriate candidate record.
The shortlist register should reference the current submission, not become the sole repository for candidate history.
Make the current version clear to the hiring contact
When a revised shortlist is sent, identify it as the current submission and explain whether it replaces or supplements the previous version. Avoid sending a new file with no indication of how it relates to the earlier one.
This reduces the chance of feedback arriving against candidates who are no longer in the active set.
Align internal consultants to the same version
Ensure recruiters working on the vacancy can identify which shortlist is current and which candidate actions remain live. Retire obsolete working copies from active use according to the team's normal process.
Internal clarity matters as much as the client-facing submission.
Close the register with the next hiring stage
Once the hiring team has responded, connect interview or follow-up actions to the appropriate shortlist version. Keep any unresolved candidate status visible rather than assuming silence means rejection or progression.
Clear shortlist version control allows recruitment teams to revise a submission without creating competing candidate sets. It gives hiring managers and consultants one shared reference for the current stage of the vacancy.