Talent SummonerA Practical Sourcing Brief Template for Small Teams
Use this copyable sourcing brief template to define role outcomes, must-haves, evidence, boundaries and the next action before searching.
A sourcing brief turns a vague request such as "find a strong engineer" into an agreed search question. That matters on a small team because the founder, hiring manager and reviewer may be sharing work between other responsibilities. A short brief gives them one reference point, without pretending a profile proves ability or interest.
Copy the template into your hiring notes. Complete it with the role owner, then ask one reviewer to challenge any requirement that is unclear, unnecessary or impossible to verify. Keep the language job-related and describe what the person must accomplish, not an idealised personality.
Copyable sourcing brief template
ROLE
Role title:
Team or manager:
Location and working pattern:
Hiring owner:
Reviewer:
ROLE OUTCOME
By [time or milestone], this person will [observable result].
The problem this role owns is:
MUST-HAVES
1. [Capability or constraint] - evidence to look for:
2. [Capability or constraint] - evidence to look for:
3. [Capability or constraint] - evidence to look for:
PREFERENCES
- Useful, but not required:
- Useful, but not required:
EXCLUSIONS / BOUNDARIES
- Do not require:
- Out of scope for this search:
- Location, work-authorisation or schedule boundary:
ADJACENT BACKGROUNDS
Consider people from [related role, industry or technical context] when they show [transferable evidence].
EVIDENCE
Strong evidence would include:
Weak or ambiguous evidence includes:
Evidence that still needs verification:
UNKNOWNS
- Unknown to verify:
- Who will verify it:
- By when:
REVIEWER
Name:
What this reviewer is checking:
Decision rule for changing the brief:
NEXT ACTION
Owner:
Action:
Due:
What will count as enough evidence for the next step:How to complete the brief
Start with the role outcome
The role outcome is the work the hire is expected to own. Write one observable result and the problem behind it. "Own the first version of our customer data pipeline" is an example; it is not a market benchmark or a promise about what a hire will deliver. An outcome keeps the search anchored to contribution rather than a long list of tools or an impressive-sounding title.
Separate must-haves from preferences
Must-haves are requirements that genuinely determine whether the person can do the role or meet a stated constraint. Give each one an evidence prompt. For example, "production data pipeline experience" is more useful when the reviewer knows to look for a system the person built, operated or improved. Preferences can improve the match but should not silently become rejection rules. Keeping the two lists separate makes later feedback more precise.
State exclusions and boundaries
Exclusions prevent the search from drifting. They might cover a different seniority level, an unavailable working pattern, a technology that is explicitly out of scope, or information the team does not need. Boundaries should be related to the job. Do not use protected characteristics, speculative "culture fit" or personal preferences as hidden filters. A boundary can also say what the brief does not claim: a public profile cannot confirm availability, motivation or interview performance.
Make adjacent backgrounds explicit
Small teams often reject useful people because the job title does not match exactly. Name acceptable adjacent backgrounds before reviewing results, then describe the transferable evidence required. For example, a platform engineer may be relevant to a reliability role if the profile shows the required operational work. This is an example for the template, not a rule for every role. The reviewer should decide whether the adjacent path still meets the must-haves.
Define evidence and unknowns
Evidence is what would support a requirement: a project, responsibility, domain context, credential or other job-related signal. Unknowns are different. They are questions the available profile cannot answer yet, such as scope, recency, language level or willingness to work in the stated pattern. Marking an unknown avoids treating missing information as either proof or automatic rejection. Record who will verify it and at which stage.
Assign a reviewer and a next action
The reviewer is accountable for checking the brief, not rubber-stamping a shortlist. Ask them to test whether each must-have is necessary, whether the evidence prompt is understandable and whether adjacent backgrounds are fairly represented. The next action should be one concrete hand-off: revise the brief, run a search, inspect evidence, contact a candidate or move to the normal assessment step. Include an owner and due point so the brief stays operational.
Use the brief in a sourcing workflow
Once the brief is agreed, you can use Talent Summoner's candidate-sourcing workflow as our product. Its live page, checked 19 August 2026, says a role description can be searched across LinkedIn, GitHub and other public sources across 200M+ profiles, returning a ranked shortlist with must-haves, nice-to-haves and plain-English reasoning. Feedback and preference edits can adjust a later search and its weighting. Treat the result as a review queue: inspect the evidence, record unknowns and decide what to verify before outreach.
If applications or referrals have produced CVs, use the separate candidate-ranking tool for that existing pool. The live page, checked 19 August 2026, supports up to 50 CVs in PDF, DOCX, MD or TXT format, needs no account and creates a shareable report. Sourcing and ranking answer different questions, so label whether evidence came from a public profile, CV or later conversation. Talent Summoner is not an ATS and does not manage your application pipeline or automatically reject candidates. Review the pricing page for current sourcing options.
FAQ
What is a sourcing brief?
A sourcing brief is a short, agreed description of the role outcome, requirements, boundaries, acceptable adjacent backgrounds, evidence and next action. It gives anyone searching or reviewing candidates the same criteria to work from.
How long should a small-team sourcing brief be?
Keep it short enough to review in one sitting. The copyable template can fit on one page when filled in, but the right length depends on the role. Add detail where it changes the search or the verification step, and remove requirements that do neither.
Should preferences be used to reject candidates?
Not automatically. Preferences are useful signals, while must-haves and job-related boundaries define the essential test. If a preference becomes essential, record why, revise the brief and state the evidence that will support it.
Can Talent Summoner replace a sourcing brief?
No. Talent Summoner is our product for role-based candidate sourcing. It can search a brief and explain ranked results, but your team still defines the outcome, checks evidence, verifies unknowns, chooses outreach and makes the hiring decision.
Next step
Copy the template for one open role, fill in the must-haves and evidence prompts, and ask the named reviewer to challenge it. Then start a focused sourcing search or use the next action to improve the brief before anyone reviews names.
Talent Summoner product facts read from our live candidate sourcing, candidate ranking and pricing pages, verified 19 August 2026. We re-verify this page quarterly — tell us if something changed.
