How to Brief a Sourcer So the Long-List Works

The long-list comes back and half of it is wrong. Not because the sourcer is bad, but because the brief was thin. This is one of the most consistent friction points when recruitment agencies start working with external sourcing support, and it is entirely fixable.

Briefing a sourcer is not the same as briefing a candidate. You are not selling the role. You are handing someone a set of decision rules precise enough that they can make hundreds of small judgements on your behalf, without coming back to you after every one. If those rules are vague, every judgement call defaults to assumption, and assumptions compound across a long-list fast.

The Brief Is a Filter, Not a Job Description

Most consultants paste in the job description and assume that is enough. It rarely is. A job description is written to attract candidates. A sourcing brief is written to exclude the wrong ones at speed. Those are opposite tasks.

A job description says "strong communication skills and a track record of stakeholder management." A sourcing brief says "we need someone who has held a named relationship with a client side procurement or finance function, not just internal comms." One of those is actionable. The other sends a sourcer into LinkedIn with no filter finer than the job title itself.

When you engage talent sourcing support, the brief you hand over is the single biggest variable in the quality of what comes back. The sourcer's skill is real, but skill applied against a vague brief produces a usable long-list by luck, not by design.

What a Good Brief Actually Contains

There are six components that consistently separate a brief that produces a usable long-list from one that does not.

• The must-have versus the nice-to-have, stated explicitly. Not everything in a job spec carries the same weight. Tell your sourcer which two or three criteria are absolute knockouts, and which the hiring manager will flex on. If you do not tell them, they will treat everything as equal and you will get candidates who tick twelve boxes and fail on the one that matters.
• Who you do not want, not just who you do. If candidates from a particular background never make it past first interview, say so. If a certain job title on a CV usually signals a mismatch, flag it. Negative criteria cut the list faster than positive ones.
• Geography and mobility with precision. Hybrid, remote and on-site all mean different things to different people. State the actual office days, the commute expectation, and whether relocation is genuinely on the table or just something the job ad says.
• The salary bracket you are working to, not the one on the advert. If you know the client will stretch for the right person, the sourcer needs to know what stretch looks like in practice. If the budget is fixed, they need to know that too so they do not surface candidates who will immediately price themselves out.
• Which companies or sectors to target, and which to avoid. This is the shortcut most consultants leave out. If your client only wants people who have operated in a specific regulated environment, that is not always obvious from a job title alone. Steer the sourcer toward the talent pools that will actually convert.
• The tone and format of the outreach, if outreach is in scope. If the sourcer is making first contact on your behalf, they need to know whether to lead with the client name, keep it confidential, and what your agency's voice sounds like. A long-list delivered with the wrong outreach already in play is harder to recover than one that was never contacted.

What Consultants Routinely Leave Out

Beyond the six components above, there are a few omissions that show up repeatedly and are worth naming directly.

The first is urgency context. There is a difference between a role that needs to be filled before a project kicks off and one that has been open for months with no real pressure. That context changes how a sourcer prioritises and how aggressively they cast the net.

The second is what has already been tried. If you have already worked this role and the obvious candidate pool is exhausted, your sourcer needs to know. Send them a list of profiles already reviewed, or at minimum tell them which job boards and LinkedIn searches you have already run. Sending them back to the same well wastes time you are paying for.

The third is feedback from previous shortlists. If this role has been briefed to your own team or a previous supplier and the long-list was rejected, the reasons for that rejection are gold. A note that says "the client kept saying candidates were too junior even though their titles looked right" tells a sourcer to look past seniority signals like job title and dig into team size managed, budget held, or reporting line instead.

How RPO Services Handle the Brief Differently

When agencies work with structured RPO services rather than ad hoc freelancers, the intake process itself tends to force better briefing. A delivery team that runs sourcing at volume across multiple agencies develops a standard for what information they need before they begin, because ambiguity at their end costs time at yours.

That is partly why the brief matters more, not less, when you bring in external capacity. Your internal consultant might fill gaps by walking over to ask you. A sourcer working offshore cannot do that efficiently, and should not have to. The brief has to carry the conversation.

The agencies that get the most out of external sourcing support are the ones that treat the brief as a deliverable in its own right. They spend time on it before the sourcer starts, not after the first long-list disappoints.

A Simple Test Before You Send the Brief

Before you hand a brief over, read it and ask yourself: could someone who knows nothing about this client or this sector make a defensible yes or no decision on every CV they look at? If the answer is no, the brief is not finished.

That is not a high bar. It is the minimum that makes external sourcing actually work. And once you have built the habit of writing briefs to that standard, the long-lists come back usable the first time, which is the whole point.

If you are thinking about how sourcing support fits into how your consultants spend their time, the talent sourcing service page sets out how Logix RPO approaches delivery. Worth a read before you decide whether to trial it or not.