Recruitment brief template: agree the role before sourcing
Use a free recruitment brief template to agree role outcomes, must-haves, search scope and evidence. Includes a worked example and hiring-manager questions.
Vettara editorial team · · Updated
A recruitment brief is the working agreement behind a candidate search. It sets out what the person must accomplish, essential criteria, practical constraints, evidence to look for and who owns the next decision. Agree these points before sourcing, then use the same brief to review candidates and record changes to the search.
A recruitment brief template you can use today
Copy the fields below into your team's working document. Complete them with the hiring manager before candidate sourcing starts. Leave unresolved fields marked as open questions, with an owner; a filled-in template is not evidence that everyone has agreed.
This is an ungated planning template, not an application form or a claim that Vettara automatically imports it. Keep personal candidate information and confidential company details out of any public example or demo brief.
| Brief field | Your team's answer |
|---|---|
| Role and business need | We are hiring a [role] because [business need]. |
| Outcomes and ownership | This person will own [work] and be assessed against [agreed outcomes and review period]. |
| Essential capabilities | The role needs [capability] because [job-related reason]. Acceptable evidence: [example]. |
| Preferences and learnable skills | Helpful but not essential: [experience]. Can be learned with support: [skill]. |
| Practical conditions | Location: [ ]. Work pattern/travel: [ ]. Approved compensation: [ ]. Start window: [ ]. |
| Search boundaries | Relevant titles, company types and markets: [ ]. Why these boundaries matter: [ ]. |
| Evidence and unknowns | Research can establish [ ]. Human assessment must confirm [ ]. Unresolved questions: [ ]. |
| Decision owners | Brief approved by [ ]. Research reviewed by [ ]. Next review [ ]. Version/date [ ]. |
What is the difference between a recruitment brief and a job description?
A job description explains the role, responsibilities and requirements. A recruitment brief turns that description into an agreed search plan: why the hire matters, which requirements are essential, where to research, what evidence would support a shortlist and who resolves tradeoffs.
Use the job description as an input. If it says “regional experience,” the brief should identify the actual markets and responsibilities required rather than letting each reviewer interpret the phrase differently.
The job title is not the assignment
“Head of Operations” could mean stabilizing service delivery, opening new locations, managing a turnaround, or building processes for a growing company. Those are different searches, even if the title is identical.
Before requesting names, finish this sentence: “We need this person because the business must…” Then describe the work without mentioning a preferred employer, fashionable job title or vague personality label.
This reflects a basic selection principle: understand the job's tasks and relevant competencies before deciding how to assess people. The US Office of Personnel Management explains that connection in its guidance on job analysis. The practical framework below is our suggested way to make that conversation concrete; it is not a legal checklist.
Separate a requirement from a preference
An essential requirement should earn its place in the brief. What would fail if it were missing? Could the capability be demonstrated another way? Is it needed on day one, or could the person learn it?
If nobody can answer, it may be a preference wearing an “essential” label.
Consider a fictional business seeking an operations leader. Experience coordinating multiple locations may be central to the work. Experience at one named competitor may simply be familiar to the hiring manager. Treating both as equally necessary can narrow the research before anyone has examined the evidence.
Company lists are useful search boundaries, not certificates of competence. A familiar logo does not explain what someone personally owned or achieved.
Write down the evidence you would accept
“Strategic” is an adjective. “Has led a documented change to how an operation across multiple sites plans and measures delivery” is a question research and assessment can investigate.
For each important requirement, write three short entries:
Do not force every question into profile research. A public biography can suggest relevant experience; it cannot conduct a structured interview or establish a candidate's interest in your role.
- What we need: the job related capability or responsibility.
- What would support it: role history, a work example, an interview answer or another appropriate source.
- What research cannot settle: personal ownership of an outcome, current interest, or a fact requiring confirmation.
Stop hiding disagreements inside the brief
One stakeholder wants someone who has built a function. Another wants experience operating a mature one. Both expectations appear under “leadership experience,” so the contradiction survives until the interviews.
Bring that disagreement forward. State the tradeoff, record the decision and name the person who can approve changes. If the mandate changes after sourcing begins, version the brief and reconsider the research. Do not quietly assess the next candidates against a new standard.
Before launch, confirm the role's scope, reporting line, work arrangement, realistic market boundaries and unresolved commercial details. Keep confidential information out of public examples and restrict a real brief to the people who need it.
Use software after the decision is clear
Vettara supports brief led candidate research and shortlist review. That is useful when the team can explain what it is looking for. It is not a substitute for deciding what the job should be.
In a demo, start with a nonconfidential brief. Ask whether the research preserves its requirements, whether a reviewer can inspect the supporting information, and what happens when an assumption is wrong. Do not accept a long list as the only success measure.
The better question is: “Can our team explain why each person deserves the next conversation?”
Sources & further reading
Bring your brief and book a Vettara demo