Process and pipeline · 5 min read
Building a talent pool
A talent pool is a searchable record of people you might hire later, mostly past applicants who came close. This guide covers who to keep, how to stay within data rules and how to make searching the pool a habit.
What a talent pool is
A talent pool is a searchable record of people you might hire in the future. Most of it comes from people who have already applied to you: the strong runner-up for last quarter's role, the applicant who was a good fit for a different team, the person who withdrew because the timing was wrong. It can also include referrals, people met at events and former employees who left on good terms.
The value is simple. These people already know your organisation, and you already know something about them. Searching the pool before you post a job can give you a first shortlist quickly and at little cost. A pool only works, though, if it is kept tidy, tagged consistently and searched as a habit. If your applicant records live in inboxes and spreadsheets, that is hard to do, and the guide on choosing an applicant tracking system is a good place to start.
Decide who goes in
- Runners-up: applicants who reached a late stage and were rated well, but lost out to another candidate.
- Strong applicants for the wrong role: people who did not meet the must-haves for this job but would fit another.
- Withdrawn applicants: people who left the process for timing or personal reasons, not because of fit.
- Referrals: people recommended by staff, even when there is no current opening.
- Former employees: people who left on good terms and might return.
- Event and outreach contacts: people you met who agreed to be contacted about future roles.
Leave out applicants who clearly did not meet the basics for any role you hire for. A pool full of weak matches is slower to search than no pool at all, and it wastes the time of the people you contact.
Get consent and follow data rules
Keeping someone's CV for future roles is a use of their personal data beyond the job they applied for. Check the employment and data protection rules where you hire before you build a pool. In many places you will need to tell applicants you want to keep their details, explain why and for how long, and let them say no or ask to be removed later.
- Add a clear option to your application form or outcome message asking whether the applicant is happy to be considered for future roles.
- Set a retention period and record the date each person entered the pool.
- Review the pool on a fixed schedule and remove or re-confirm people whose period has ended.
- Make removal easy and act on requests promptly.
- Limit access to the pool to the people who hire.
Tag people so you can find them
A pool is only as good as its search. Agree a small, fixed set of tags and use them the same way every time. Too many tags, or the same tag spelled three ways, make the pool useless.
- Role family, such as sales, finance, engineering or operations. Use the same names as your job titles.
- Level, such as entry, mid, senior or lead.
- Key skills, taken from the requirements of the job they applied for.
- Location and work preference: on site, hybrid or remote, and whether they would relocate.
- Stage reached and the date, for example final interview in March.
- A one-line reason for inclusion, written by the recruiter or hiring manager. Write about skills and evidence, never about personal characteristics.
Keep the interview scorecards with each record. When the person comes up for a new role, the team can see what was assessed and what was not, instead of relying on memory. The guide on shortlisting applicants fairly covers how to use past evidence without giving anyone an unfair head start.
Search the pool before every job
The most common way talent pools fail is that they are built and then never used. Make searching the pool a fixed step at the start of each new search.
- When a role is approved, search the pool by role family, level, skills and location.
- Review matches against the current must-have requirements, not the requirements of the old job.
- Contact the best matches personally. Say why you thought of them and what the role involves.
- Invite those who are interested into the normal pipeline at the right stage. Do not skip steps that check something new.
- Post the job publicly as well, unless you have a clear reason not to, so the pool does not become a closed circle.
Spark Careers Enterprise keeps a talent pool of past applicants that you can search before you post a new job.
Pool applicants should go through the same stages as everyone else applying for the same role. The guide on designing a hiring pipeline covers how to set those stages.
Keep the pool warm
People in your pool will forget you if they only hear from you when you need them. You do not need a marketing programme, just a light and honest touch.
- Send a short, personal message when you add someone to the pool, saying what kind of roles you might contact them about.
- Contact people only about roles that genuinely fit. Irrelevant messages teach people to ignore you.
- Update records when you learn something new, such as a new job, a move or a new skill.
- Thank people who refer others or come back to you.
Give one person the job of looking after the pool, even if it takes only an hour a month. Without an owner, tags drift, old records pile up and nobody notices when consent periods run out.
Talent pool checklist
- Consent and a retention period are in place before anyone is added.
- Only people you would seriously consider are in the pool.
- Tags are few, fixed and used the same way by everyone.
- Scorecards and a reason for inclusion are kept with each record.
- Searching the pool is the first step of every new search.
- Pool applicants go through the same stages as everyone else.
- Old records are reviewed and removed on schedule.
Your next hire, start to finish, in one place.
Free workspace. No card. Full scoring free for 7 days.