Strategic candidate sourcing: A one-page plan for every req

A short, repeatable sourcing plan for agency and independent tech recruiters running several client reqs at once

Written by Mihailo Bozic
woman interviewing on a blue sofa with a laptop

Strategic candidate sourcing is a written plan for finding the right people for one req before you start searching. It sets who you target, where you look first, and how you'll know it's working.

This matters more when you recruit for several clients, because each one has its own market, its own bar, and its own sense of what fast means. Without a plan per client, you end up running the same search for every req and hoping the right people reply.

Key takeaways

  • Write one short sourcing plan per client req instead of one plan for your whole desk.
  • Lock the target profile at intake, including off-limits companies and work authorization limits.
  • Start with people you already know before you open a job board.
  • Agree on a submittal target and a date with the client, then review what's working every week.

What strategic candidate sourcing means

It means you search on purpose for a defined group of people instead of reacting to whoever applies. You choose the targets, the channels, and the checkpoints before the first message goes out.

Most sourcing advice is written for in-house talent teams that have an employer brand and a careers site pulling in applicants. You don't have either. Your name isn't on the job, and the people you want may never have heard of your client.

That makes outbound work the core of what clients pay you for. You can't wait for applicants who have never heard of your client, so you have to go find them.

Who you targetWhoever applies or repliesA named list of companies and titles
First channelPost the job and waitPeople already in your network
What you measureResumes receivedQualified submittals per channel
When you adjustWhen the client complainsAt a set weekly review

How to build a candidate sourcing strategy for each client

Build it in five steps and write the result on a single page. On an agency desk, a sourcing strategy for recruitment has to be rebuilt for every client. The steps stay the same, so each new plan gets faster to write.

Define the target profile at intake

Use the intake call to pin down the profile, because your plan can only be as good as that call. Clients often describe a person they can't hire, and your job is to turn that wish list into something you can search for.

Ask for these before you hang up:

  • Must-haves: the two or three skills the person can't do the job without.
  • Nice-to-haves: skills that break a tie but won't sink a strong candidate.
  • Off-limits companies: clients, partners, or firms the client won't recruit from.
  • Work authorization: whether the client will sponsor or transfer a visa.
  • Location and relocation: onsite, hybrid, or remote, and whether they'll pay to move someone.

Read the list back to the client and get a clear yes on each point. That short step saves you from a round of rejected submittals two weeks later.

Map the market

Next, figure out where these people work today. Start with target companies that build similar products or use the same stack. Then add the job titles those companies use, since one role can carry several different titles.

After that, list adjacent skills that the client might accept. A client may take a backend engineer from a related language. Ask which swaps they'll accept.

Finally, look at how big the pool is and where it sits. If a quick search turns up only a handful of people, tell the client right away. The time to loosen a must-have or widen the location is during week one.

Pick your first channels, starting with people you know

Start with people already in your database, then work outward from there. Rediscovery means going back to past candidates in your ATS or CRM (your applicant tracking or contact system). After that come direct outreach to your target list and referrals from people you've placed.

People in your database already know your name, which makes them the warmest place to start. Save job boards for later, if you use them at all.

Pick two or three channels per req. With more, you can't tell which one produced the hire.

Set a submittal target and a date with the client

Agree in writing on how many candidates you'll submit and by what date. A submittal is a candidate you've screened and sent to the client for review. Even a rough number and date are better than an open-ended promise.

The client knows what to expect, and you have a clear point at which to raise a flag. Base the number on what your market map showed rather than on what the client hopes for.

Check results weekly before the gap grows

Set a fixed weekly review for each req and look at what each channel produced, rather than just the total. Track these for every channel:

  • Reach: how many people you contacted.
  • Replies: how many responded, even to say no.
  • Screens: how many passed your first call.
  • Submittals: how many you sent to the client.
  • Client feedback: why the client passed on anyone they rejected.

If one channel produces replies but no screens, your targeting is off. If screens don't turn into interviews, go back to the client and recheck the profile.

Turn your intake notes into a search

Book a demo

Keep one strategy per client when you run several reqs

Give every client its own one-page plan and keep it where you can open it in a minute. Juggling reqs makes one client's bar blur into another's.

The load is heavy even for recruiters who work for a single employer. SHRM's 2026 benchmarks found median requisitions per recruiter rose 67% at extra-large employers. Yours is split across several companies, each with its own rules.

Here's what each plan should hold:

  • Client and req: the company, the role, and the hiring manager.
  • Target profile: must-haves, nice-to-haves, and off-limits companies.
  • Constraints: work authorization, location, and relocation terms.
  • Market map: target companies, titles, and adjacent skills.
  • Channels: the two or three you'll use first, in order.
  • Commitment: the submittal target and the date you agreed on.
  • Review log: one line per week on what worked and what you changed.

Strategic sourcing in recruitment comes down to this page. If you can't fill it in yet, you're not ready to start strategic candidate sourcing for that req.

AI can run the search, but check what it misses

AI is best at running searches fast and weakest at judging fit, so you still own the parts that win the placement.

In-house teams are already moving in this direction. In a SHRM survey of over 2,000 HR professionals, 43% said they use AI to support HR work. Most of them use it for recruiting, including to automate candidate searches.

Let a tool run the search from your target profile and return a first list, but keep the market map, the pitch, and the client relationship for yourself. A tool can't know that your client quietly passed on two people from one company last month.

Before your next intake call, write the seven plan headings on one page for strategic candidate sourcing. Then fill them in while the client is still on the line.

Search with the client's terms built in

Book a demo

Frequently asked questions

How long should a sourcing plan take to write?

Aim for one page that you can finish right after the intake call. If it takes much longer, the intake probably left gaps, so go back to the client with specific questions.

Should I share my sourcing plan with the client?

Share the parts that set expectations, like the target profile, the submittal target, and the date. Keep your channel details and market map to yourself, since those are part of what the client pays you for.

What if the client changes the profile mid-search?

Update the plan and reset the submittal date in writing. A profile change often means a new market map, so treat it as a restart.

When should I tell a client the req is unrealistic?

Tell them as soon as your market map shows a thin pool. Bring options with you, such as dropping a must-have, widening the location, or adding a relocation budget.

About the author

Mihailo Bozic
Mihailo Bozic

Founder & CEO @ Rotto

Founder & CEO of Rotto, building tools that help tech recruiters source better candidates, faster.

Related articles

Rotto

Built for recruiters who work from a brief, not a boolean.

rotto.com