Guides
How to build and maintain a talent pool instead of starting every role from zero
Every search turns up strong people you can't hire right now. Keep them, with consent, and your next opening starts with a warm shortlist instead of a blank job board.
Key takeaways
Pick the near-misses worth keeping
Strong runners-up and great-but-wrong-timing people.
Get consent + record it
Ask to keep their data for future roles; honour deletion.
Tag with role + strengths
Context that's still useful in six months.
Keep warm, search first
Occasional contact; query the pool before posting.
1. Decide who belongs in the pool
Be selective. The pool is for the near-misses you'd genuinely want next time: a strong runner-up, a great candidate for a role you've now filled, someone excellent who wasn't quite the right level yet, a promising person who withdrew for timing. A pool of everyone is a graveyard you'll never use; a pool of 20 to 40 people you'd actively reach out to is a real asset. Quality of the list beats size every time.
2. Get consent, then tag with context
Under the GDPR you can't simply keep an applicant's data indefinitely once their application is decided, you need a legal basis, and for a talent pool that means their consent to be kept for future openings. Ask explicitly ("may we keep your details for future roles?"), record the consent, and honour withdrawal and deletion requests. KI BMS is built for this: a candidate can carry a talent_pool status, and the retention sweep keeps the whole thing GDPR-clean. Once consent is in place, the value comes from context, tag each person with the role they fit, their strengths, why they're a near-miss, and how to re-approach them. A name with no context is unusable in six months.
No talent pool without consent
Keeping applicant data beyond the decision of the role they applied for needs a legal basis under the GDPR, in practice, the candidate's explicit consent to be held for future openings, with the right to withdraw and be deleted. Build consent into the flow rather than bolting it on; KI BMS tracks the talent-pool status and retention so this stays clean. This is general information, not legal advice.
3. Keep it warm, don't just hoard it
A pool you only open when a role appears feels exactly as cold as a cold outreach, the person has forgotten you. The trick is light, occasional, genuine contact: a relevant update about the company, a "thought of you when this came up", a quick check-in once or twice a year. You're maintaining a relationship, not a database row. Even a small amount of warmth means that when you do have the right role, the message lands as "good to hear from you" instead of "who is this?".
4. Search the pool first, every time
The whole point pays off here: when a new role opens, search your pool before you write a single job ad or pay for a single posting. A warm, pre-qualified shortlist of people who already know you and consented to be contacted is faster and cheaper than starting from scratch, and it often closes before the public posting would even attract its first applicant. In KI BMS the pool is filterable by the tags you set, so "who in the pool fits this opening?" is a query, not an archaeology project. A maintained pool turns hiring from a recurring cold start into a running advantage.
FAQ
Frequently asked
Try KI BMS
Free plan, no credit card. We host in Germany. You can export and delete everything self-serve.
Read next
How to set up an employee referral programme that actually brings applications
Make referring effortless and rewarding it visibly fair.
Read
The phone screen: a 15-minute guide that saves you hours of interviews
A short structured first call that filters before the expensive interviews.
Read
The intake meeting: how recruiting and the hiring manager actually agree on the role
Align recruiter and hiring manager before sourcing, not after the misses.
Read