Lean internal recruiting teams are asked to do two different jobs at once: serve the applications already arriving and find the people who will never see the vacancy. The second job needs a deliberate system.
That system does not have to be elaborate. It needs a clear intake, a repeatable search method, a way to inspect why a profile appears, and a respectful path from discovery to conversation. Without those pieces, sourcing becomes a heroic afternoon of Boolean strings followed by a spreadsheet that nobody trusts.
This playbook is for internal teams in European companies, particularly small and mid-sized organisations where one recruiter may cover several countries, business units, and hiring managers. It treats job advertising as useful infrastructure, while making the case for proactive sourcing when the market is thin.
Start with the work, not the tool
The quality of a sourcing search is usually decided before anyone opens a database. Ask the hiring manager what the person must accomplish in the first six to twelve months. Then separate that answer into four layers:
- Outcomes: the decisions, projects, customers, or operational improvements the hire will own.
- Evidence: signals that suggest someone has done comparable work, such as product launches, regulated environments, scale, or a particular type of technical system.
- Constraints: location, language, travel, working pattern, salary range, notice period, and any genuine legal or credential requirement.
- Signals to avoid: inflated title requirements, prestige proxies, and vague words such as “rockstar” that do not help a recruiter make a fair decision.
Write the resulting brief in normal language before converting it into filters. For example: “Find a finance leader who has managed a post-acquisition integration in a manufacturing business, can work with a German-speaking leadership team, and is within practical reach of Munich.” That is more useful than a stack of disconnected titles.
Have the hiring manager approve the brief in writing. This small step prevents the search from quietly changing after the first ten profiles and gives the recruiter a reference point when a stakeholder asks for “more senior” candidates without defining what that means.
Build a weekly sourcing rhythm
A lean team benefits from a cadence that protects focused work. Reserve a block for new searches, a block for review, and a block for conversations. Do not fill every hour with messages. Sourcing quality falls when discovery, judgement, and outreach are all treated as one task.
For each open search, use this sequence:
- Brief: confirm the outcomes, evidence, constraints, and salary conversation.
- Search: query the market broadly enough to discover adjacent backgrounds, then tighten the search using evidence rather than title alone.
- Review: mark profiles as yes, maybe, or no and write a short reason. A reason such as “strong integration work, unclear team size” is more reusable than a silent rejection.
- Contact: for selected profiles, use contact data where it is available and can be verified, then send a concise message tied to the person’s likely experience.
- Learn: look at the patterns in the reviewed set. If every plausible profile lacks a supposed must-have, revisit the brief with the hiring manager.
The review step is where a sourcing team compounds its advantage. It turns a vague feeling that “the market is bad” into a concrete conversation: perhaps the location is too narrow, perhaps the target companies are unrealistic, or perhaps the requirement is not actually needed for the first year.
A broader talent sourcing strategy can help the team decide which roles deserve this rhythm and which should remain primarily inbound. The point is not to turn every recruiter into a full-time researcher. It is to make scarce-role discovery predictable enough that it survives holidays, changing headcount plans, and a new recruiter joining the team.
Triage roles before launching a search
Not every vacancy deserves the same sourcing investment. At intake, score the role on scarcity, business impact, confidentiality, geographic restriction, and the strength of existing inbound channels. A recurring customer-support role with healthy application flow should not receive the same manual attention as a regulatory leader whose experience exists in a small group of companies.
Agree a service level with the hiring manager. For a scarce role, that might mean an initial market map, a reviewed sample, and a briefing adjustment before outreach begins. For a role with uncertain demand, it may mean publishing first and starting direct search only if qualified applications remain below an agreed threshold. This keeps sourcing connected to evidence rather than stakeholder anxiety.
It also protects candidate experience. A team that launches broad sourcing on every vacancy quickly accumulates names it cannot review or contact thoughtfully. A smaller, explainable list is more useful than a database filled with people whose relevance was never checked.
Use technology for discovery and memory
Internal teams often have enough information but cannot retrieve it quickly. Old candidates sit in an ATS, notes live in email, and a recruiter’s memory becomes the unofficial database. A modern sourcing workflow should make the market search and the internal record reinforce one another.
Yena’s Sourcer is designed for this part of the work. A recruiter describes the profile in natural language, reviews candidates with visible relevance evidence, and narrows the set with human decisions. For selected profiles, contact details may be revealed where the data is available and can be verified. The selected people can then be kept in the ATS or CRM and prepared for campaigns and outreach.
That is useful for a small internal team because it reduces context switching. It does not remove the need to validate a candidate’s actual experience, check the role constraints, or decide whether an approach is respectful. It makes those decisions easier to make consistently.
Keep the system honest with a few operating rules: record the search brief, retain the reason for a decision, separate discovered from contacted people, and make it easy to remove outdated records. Review access rights when people change teams. A practical candidate-data retention policy should cover sourced people as well as applicants.
Set privacy rules before the first search
European hiring teams should not treat publicly accessible professional information as unrestricted recruiting inventory. The General Data Protection Regulation requires a lawful basis, purpose limitation, data minimisation, accuracy, transparency, security, and respect for individual rights. Which lawful basis applies is a decision for the organisation, not a feature a software vendor can make on its behalf.
The European Commission’s guidance on when personal data may be processed makes the balancing point explicit: an organisation relying on legitimate interests must consider whether the person’s rights override those interests and use the least intrusive workable method. That assessment should reflect the role, source, geography, message, retention period, and reasonable expectations of the person concerned.
Where information was not obtained directly from the person, Article 14 transparency duties may apply. The Court of Justice of the European Union has confirmed that Article 14 can cover both information collected from another source and information generated from such data. Read the official judgment in Case C-169/23, then have privacy counsel translate the rule into an operational notice and timing standard for your markets.
Finally, define a route for access, objection, restriction, correction, and deletion requests. The Commission’s overview of individual data-protection requests is a useful operational reference. Recruiters should know who owns a request and how to stop campaigns while it is handled. This article is workflow guidance, not legal advice; national employment and communications rules may add further obligations.
Make outreach a conversation, not a pitch
Passive candidates are not failed applicants waiting to be persuaded. They are people with a current job, a reputation, and a reason not to spend time on another generic message. The first note should make it easy to decline and easy to ask one question.
Explain why you chose to write, give one or two concrete facts about the role, and disclose the next step. Avoid pasting a job description into a message. A useful opening might be: “Your work leading the integration of two production sites stood out. I’m helping a European manufacturer build that capability across three locations. Would a short, confidential exchange about the scope be relevant, or should I close the loop?”
Measure replies and qualified conversations, not just messages sent. If nobody responds, changing the sourcing tool may be the wrong diagnosis. The problem could be the role’s proposition, the timing, the audience, or a message that sounds like bulk mail.
Connect sourcing to the rest of recruiting
Sourcing should not become a separate island. When a candidate is worth a conversation, the recruiter should be able to move them into the same pipeline used for applicants, referrals, and agency introductions. The hiring manager should see the evidence and the open questions, not a mysterious score.
Campaigns can help with follow-up, but automation needs boundaries. Use a small, relevant sequence with a clear stop condition. Do not keep sending messages after a person declines or asks not to be contacted. A campaign tool should protect attention, not turn a thoughtful approach into a drip machine.
Every month, compare sourced and inbound routes by role type. Job ads may win for graduate hiring or broad operations roles. Proactive sourcing may win for a scarce engineer, a confidential leadership search, or a role in a location with little active movement. The right answer is usually a portfolio, not a slogan.
When evaluating the technology layer, compare how well tools preserve that portfolio. The candidate sourcing tools guide covers discovery options, while the in-house process should still have one accountable record for applications, sourced prospects, conversations, and consent or objection signals.
What good looks like after 30 days
After a month, a lean team should be able to answer practical questions. Which searches are genuinely difficult? How long does it take to produce a reviewed shortlist? Which evidence makes a profile credible? Which messages create real conversations? How many strong people can be reused for the next role?
If the answers are still buried in individual inboxes, fix the workflow before buying more channels. If the team can see the patterns but cannot search fast enough, improve the sourcing layer. If there are plenty of profiles but poor replies, work on the proposition and outreach.
For internal recruiters, the goal is not to abandon applications. It is to stop treating them as the only proof that a market exists. A small team with a disciplined search, visible evidence, and respectful outreach can create options before a vacancy becomes an emergency.
See the Yena candidate sourcing workspace for a practical example, or compare it with the broader English talent sourcing playbook when designing your team’s operating model.