A useful brief connects the role to real work, clear selection criteria and an agreed decision process. Here is what to prepare before the search begins.
A job title is a starting point for a hiring conversation. It does not tell a recruiter which problems the person will work on, who they will work with or how the hiring manager will assess them. A useful brief makes those things explicit before candidate conversations begin.
Treat the brief as a working agreement between the hiring manager and recruiter. It should be short enough to use during a screening conversation and specific enough to explain why a candidate moves forward. Start with the work, then add the context that makes the role different.
Choose the main responsibilities and explain what completing them involves. Instead of “support operations”, describe the records, customers or processes the person will handle. Name the decisions they can make and the situations they should bring to their manager.
Explain why the role exists now. You may be replacing someone, building a new function or redistributing work across a team. Share that context without presenting assumptions about future growth as settled plans. The recruiter needs to understand both the immediate need and what remains open.
For each requirement, ask what part of the job makes it necessary. A particular system may be essential if the person must use it independently from the outset. In another role, experience with a comparable system and time to learn may be enough.
Keep the distinction visible in the brief. If everything is essential, it becomes difficult to discuss trade-offs. Agree which capabilities must be demonstrated and which can be developed with support. Use criteria connected to the work rather than vague descriptions of personality or background.
Confirm the location, working arrangements, contract type and reporting line. Discuss compensation internally and agree what the recruiter may communicate. Where something is still being decided, name the owner and avoid asking candidates to rely on an arrangement that has not been approved.
Describe the people the new hire will work with. The purpose is to explain collaboration: who provides inputs, who reviews the work and where responsibilities meet. Replace “good cultural fit” with the working behaviours your team can discuss and assess consistently.
Write down who screens, who interviews and who approves the offer. Give each conversation a purpose so candidates are not asked to repeat the same discussion without learning anything new about the role. Decide where interview notes and feedback will be recorded.
Agree how the hiring manager will respond when a shortlist reveals a mismatch in the brief. Perhaps the role combines responsibilities that need separate attention. Perhaps a preferred requirement matters less than expected. Review the criteria openly rather than changing them silently between candidates.
A brief becomes less useful when different people work from different copies. Give it an owner, record agreed changes and share the current version with everyone involved in selection. Candidate communications should reflect those changes too.
Before the search starts, ask the recruiter to explain the role back to you in plain language. Listen for missing context or competing priorities. That conversation can surface questions a document alone leaves unanswered, and gives both of you a clearer basis for the next step.
Choose a starting process by looking at its boundaries, decisions and handovers. These questions help turn a broad need for support into a brief you can discuss.
Use year end to check payroll records, employment documents and the owners of upcoming submissions. Keep a clear record of questions that need specialist advice.
A team lead connects the daily work with the people who make decisions. Clear ownership, useful updates and a shared record keep that relationship practical.
Tell us what is slowing your team down. We’ll come back with a plan, the people, and the next step.
