A proactive recruitment strategy identifies important hiring demand early, maps the people who could meet it, and builds relevant candidate relationships before a vacancy becomes urgent. The practical aim is not a huge database. It is a reviewed, reachable pipeline for a small number of roles where starting from zero would put delivery at risk.
That distinction matters. Posting every likely vacancy earlier is still advertising. Sending generic messages all year is still volume outreach. Proactive recruitment begins with a business forecast, turns it into a role portfolio, and assigns recurring sourcing work before a requisition arrives. When the role opens, the team has current market evidence and people with context, not a stale list of names.
This 90-day playbook is for the talent acquisition operator who has to make that change with the team and systems already available. It complements a broader talent sourcing strategy, but concentrates on cadence, ownership and the evidence required to call a pipeline ready.
Start With Hiring Risk, Not a Sourcing Tool
Proactive recruitment should cover roles where advance work changes an important outcome. Ask business leaders what must be delivered over the next two to four quarters, which capabilities that work depends on, and where the current workforce plan is exposed. The CIPD workforce planning factsheet describes workforce planning as balancing future demand for people and skills against supply, then turning the gap into action. Recruitment is one response; development, retention, redesign and external partners may be better responses elsewhere.
Score each possible role from one to five on four factors: business impact if unfilled, likelihood of demand, external scarcity, and time needed to build trust with credible candidates. Add the scores and start with three to five roles. A specialist security engineer needed by several product teams may qualify. A generalist role with predictable applicant volume probably does not.
Write the assumptions beside the score. A forecast is not a requisition, and leaders must be able to revise it without the sourcing team treating the change as failure. The portfolio exists to focus learning under uncertainty.
Define What Pipeline Ready Means
A pipeline is ready when a recruiter can explain who has been included, why they appear relevant, what remains unverified, how recently the information was reviewed, and what the next appropriate action is. A search result or exported profile list does not meet that standard.
| Readiness layer | Minimum evidence | Owner question |
|---|---|---|
| Role | Outcomes, must-have capabilities, acceptable adjacencies and location constraints | Would two reviewers search for broadly the same person? |
| Market | Target segments, title alternatives, likely employers and an estimated viable pool | Which assumptions could make the pool larger or smaller? |
| Candidate | Current public evidence, source, review date and explicit uncertainties | Can a human defend the relevance decision? |
| Relationship | Lawful contact route, interaction history, preference and next action | Would contact be timely and useful to this person? |
This definition prevents a common reporting error: celebrating the number of profiles while ignoring whether anyone has reviewed them or can contact them responsibly. It also makes quality observable without inventing a future hiring outcome.
Days 1-30: Baseline Demand and Map the Market
In the first month, establish the starting point. Review the previous twelve months for the selected roles: requisitions, applications, sources, days between key stages, agency use, declined offers and reasons searches were reset. Do not combine unlike roles into a single average. The purpose is to identify where the process actually lost time and where proactive work might help.
Next, hold a 45-minute role calibration with the hiring leader and a strong job incumbent. Replace a long list of credentials with five or six observable capabilities. Record what excellent performance would produce in the first year, which experiences are evidence for those capabilities, and which apparently similar profiles are false positives. Skills England's UK Standard Skills Classification provides a useful external vocabulary for connecting skills, knowledge, tasks and occupations when internal titles are inconsistent.
Build a first market map for each role: target and adjacent companies, title synonyms, professional communities, relevant locations, internal database matches and rough pool-size ranges. Keep observed evidence separate from estimates. The detailed method in the talent mapping guide can support discovery; at this stage, the output is a tested search hypothesis rather than a finished report.
Days 31-60: Discover, Review and Segment People
Search the existing candidate database first, then external professional sources. Previous finalists, referrals and candidates who were credible for a related role often contain richer evidence than a newly found profile. Use the agreed capabilities to search beyond exact titles, but keep the reason for every match. Natural-language or semantic search can widen recall; it cannot establish motivation, salary expectations, right to work or genuine interest.
Review results in small batches. For each person, record relevant evidence, confidence, missing information, source, last reviewed date and the segment they represent. Sample rejected profiles as well as accepted ones. If a search disproportionately excludes a plausible adjacent group, inspect the role criteria and search logic before expanding volume.
Use three practical segments: ready to approach, worth monitoring, and insufficient evidence. "Ready" means relevant enough for a human to write a specific approach, not that the individual has been silently judged suitable for employment. "Monitor" may include someone one career step away or outside the current location constraint. "Insufficient evidence" protects the pipeline from confident guesses.
Days 61-90: Start Useful Conversations
Proactive outreach should offer a legitimate conversation, not imply that an unapproved job exists. Explain why the person's work is relevant, what kind of future challenge the organisation expects, and whether the timing is exploratory. Ask about interests, constraints and preferred follow-up. A candidate who says "not this year" but permits a later conversation is more valuable than a nominal lead repeatedly sent irrelevant vacancies.
Limit the first test to a manageable cohort per role so a recruiter can personalise and learn. Compare messages and channels on response quality, not only response rate. A polite refusal containing useful timing or role preferences is evidence. A vague positive response that never advances is not automatically stronger.
The ICO's draft recruitment and selection guidance explicitly covers people identified through talent search as well as applicants. Before scaling, document the lawful basis, privacy information, data minimisation, retention period, candidate rights and responsibilities when data moves between an employer and an agency. Privacy review is part of pipeline design, not an administrative step after collection.
Run a Monthly Pipeline Operating Rhythm
After day 90, give every priority role a named sourcing owner and a business sponsor. The owner maintains the evidence and relationships; the sponsor confirms whether demand and role assumptions still hold. A short monthly review should cover forecast changes, segment coverage, ageing records, conversation themes, rejected profiles, market constraints and the next experiment.
Remove roles when demand weakens, the skill can be developed internally, or the external market proves easier than expected. Add a role only when its risk score is stronger than something already in the portfolio. Capacity is finite. An "always-on" model without stop rules becomes an ungoverned list-building exercise.
Measure Readiness Before Hiring Outcomes
Use leading indicators while no requisition is open: percentage of priority roles with a calibrated brief, reviewed prospects by segment, evidence completeness, contactability, records refreshed within the agreed interval, meaningful conversations and known candidate timing. Report ranges where the market evidence is uncertain.
Once hiring starts, add operational outcomes: time from approval to first reviewed shortlist, proportion of shortlisted candidates already known, stage conversion by source, candidate withdrawals, offer outcomes and quality measures already used by the organisation. Compare against similar historic searches, not a company-wide average. The latest CIPD recruitment guidance frames resourcing as support for current and future organisational needs, which is why a balanced scorecard should connect pipeline activity to workforce priorities rather than reward raw profile counts.
Worked Example: A Future Data Platform Lead
Imagine a scale-up expects to create a data platform lead role next quarter if a product expansion is approved. The operator scores it highly because the capability is central, the market is specialised and senior candidates may need several conversations. During days 1-30, the hiring leader defines outcomes around platform reliability, data governance and team leadership. The map includes platform engineering managers, senior data engineers with technical leadership, and selected infrastructure leaders from regulated environments.
During days 31-60, the sourcer reviews the ATS, referrals and external profiles, recording direct evidence against each capability. Several people with the exact title are rejected because their scope is too narrow; several adjacent-title candidates remain because their project evidence is strong. During days 61-90, a small group receives honest exploratory approaches. The quarter ends with better knowledge of the feasible profile and candidate priorities, even if the expansion decision is delayed. That learning is a valid result; a fabricated "pipeline value" is not.
Limitations and Human Review
Proactive recruitment cannot make an uncertain forecast certain, create scarce skills, or guarantee that a person will be interested later. Public profiles are incomplete and can be outdated. Contact details may be wrong. Search and ranking systems can reproduce narrow role assumptions or uneven source coverage. Every candidate recommendation therefore needs human review against job-relevant evidence, and every relationship needs a clear preference and refresh history.
Do not use inferred sensitive characteristics, covertly score personal behaviour, or retain data simply because storage is cheap. Keep a route for correction, objection and deletion. Involve legal or data protection specialists for the organisation's circumstances rather than treating this operational guide as legal advice.
Sources and Next Step
- CIPD: Workforce planning factsheet
- CIPD: Recruitment factsheet
- Information Commissioner's Office: Draft recruitment and selection guidance
- Skills England: UK Standard Skills Classification
Test the model on one difficult, likely role rather than launching a company-wide programme. Calibrate the outcomes, map the market, review a first cohort and inspect the evidence with the hiring leader. Yena Sourcer can help find, rank and enrich that cohort while recruiters retain control of relevance, outreach and the final shortlist. For the role split behind that work, see the guide to what a sourcer does.