Talent Pools for Recruitment Agencies: When to Search for a Role, and When to Find the People First

Most agencies start sourcing when a client hands them a job. That works, but it means every search starts from zero. A talent pool is the other way round: you find good people first, learn what they want, and have a shortlist ready the day the client calls.

This post covers both ways of sourcing, when each one fits, and the one rule that keeps a talent pool honest.

Written in September 2026. The legal points below are how we read the rules, not legal advice.

What a talent pool is for an agency

Agencies often call it a bench. One staffing firm puts it simply: "A talent bench is essentially a pre-screened pool of candidates who are ready to step into open roles as soon as they become available." (Consultadd).

Two things make an agency's pool different from an in-house one. An in-house pool feeds one employer's jobs. An agency's pool feeds many clients, so the people in it are matched to the kind of roles your clients keep hiring for, not to one org chart.

And one clarification, because the word is overloaded: this is not "bench sales", the IT staffing practice of marketing consultants who are between projects. A talent pool is people you have found and screened, who have not been placed by you yet.

Two ways to source: for a role, or for people first

Searching for a live role is the classic model. A client has an opening, you tell candidates about it, and the people who reply are responding to a real job.

Building a pool first means approaching people before a specific job exists. You are not offering a role. You are offering to understand what they want and to bring them the right one when it comes up.

Both are legitimate. The rule that separates them: if you name a role, the role must be real. Candidates are right to be suspicious. Greenhouse reports that "In any given quarter, 18-22% of the jobs posted on the Greenhouse platform are classified as ghost jobs," and that "Three in five candidates say they suspect they've encountered a ghost job." (Greenhouse).

Some places write this into law:

• United Kingdom. The Conduct of Employment Agencies Regulations say an agency may not advertise "positions which hirers seek to fill unless the agency or employment business has" information about the specific position and the hirer's authority to advertise it (Regulation 27).
• Ontario. A publicly advertised job posting "must include a statement on whether the posting is for an existing vacancy or not". The rule does not apply to "a general recruitment campaign that does not advertise a specific position" (Government of Ontario).

The Ontario carve-out is the talent-pool case in one line: a pool campaign is fine as long as it does not pretend to be a vacancy.

Why a pool pays off

The best people are usually in a job. In the United States, "The median number of years that wage and salary workers had been with their current employer was 4.1 years in January 2026", and "the median tenure of workers ages 55 to 64 (9.6 years) was more than three times that of workers ages 25 to 34 (3.0 years)" (U.S. Bureau of Labor Statistics).

They are not looking, but many will talk. LinkedIn's older Talent Trends research put passive candidates at 75% of the workforce, and described "60% of the workforce not looking for a new job, but willing to discuss a new opportunity." Its advice for reaching them: "offer them an alternative way to share their background, and you probably want to do away with the application" (LinkedIn). Those are survey figures from a few years ago, so read them as direction, not as today's exact number.

That is why we built talent-pool campaigns next to role searches. Most agencies only search when a client hands them a job. But the best people aren't waiting for your job ad. So PlacementFlow also finds people first, learns what they want, and then helps the recruiter find them the right role.

Who gets the most out of a pool

Two kinds of agency, in our view:

• Specialists in a niche where the same kind of person gets hired again and again. The pool keeps paying off, search after search.
• Small agencies without a steady flow of client jobs. A pool of good people gives them something to take to employers before a job exists.

How PlacementFlow runs both

Every sourcing campaign is one of the two, and the difference is enforced by the product, not left to the recruiter's wording.

1. A role campaign names the role. The recruiter fills in typed fields: the job title, and optionally the area, the kind of client and a pay band. The first email then carries one sentence about that live search, written by the platform from those fields. The client is described (for example "an OEM client"), never named, in that first email.
2. A talent-pool campaign names no role. The email explains the process instead: reply, usually get a private link with a few quick questions, and a recruiter reviews the answers. No vacancy, no salary, nothing to be disappointed by later.
3. Screening is the same either way. The questions a recruiter marks as must-knows, such as the right to work, are asked first. A missing or wrong answer puts a flag on the response for the recruiter to read. It never rejects anyone automatically, and nobody gets an automated rejection message.
4. The recruiter decides who is worth pursuing. With no job attached, there is no score against a job. The recruiter reads the answers and makes the call.

Our cold sourcing emails candidates in the United States only. How the campaigns work in the app is in How Sourcing Campaigns Work, and choosing between the two modes is covered under "Vacancy Fill vs Talent Pool" in Creating an Effective Sourcing Brief.

After a recruiter says yes: finding them a role

Once a recruiter decides someone is worth it, the recruiter takes them to employers: first an anonymous profile that names nobody, and the candidate's real name only after they have agreed to it.

That order is not only good manners. The UK regulations say an agency may not disclose information about a work-seeker "without the prior consent of that work-seeker" (Regulation 28). In PlacementFlow, every send that names a candidate to an employer checks their recorded consent first. How screening and approval fit together is in How the Two-Stage Screening Gate Works.

Keeping a pool you can defend

A pool is personal data, so it needs an end date. Under GDPR, personal data must be "kept in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed" (GDPR Art. 5).

The UK regulator's draft guidance on recruitment records goes further for exactly this case: "If you wish to keep candidates' information for a new purpose, you must" meet extra conditions, including a lawful basis and telling the candidate (ICO). It is still a draft, but it shows where expectations are heading. Our retention settings are described in GDPR and Data Retention.

A checklist for your talent pool

• Pick the mode per search. A live role gets a role campaign. Everything else is a pool.
• Never name a role that is not live. If the search closes, stop saying it is open.
• Flag, don't reject. Let a person read the answer before anyone is turned away.
• Get consent before you share a name. Anonymous first, named only after the candidate agrees.
• Set a retention period you can explain. And tell people what you keep and why.