How to Write an Executive Search Brief That Actually Works
A search brief is not a job description with extra detail. It is the rubric the entire search will be run against: who enters the pool, who gets cut, what gets researched, what the shortlist can argue.
Which means a vague brief does not produce vague research. It produces confident research aimed at a target nobody agreed on, and the vagueness gets resolved silently by whoever happens to be doing the work.
The test: can this criterion produce a result?
Every requirement in a brief should be checkable against evidence. Hold it up against a real person’s record and it should produce one of three answers: yes with a source, no, or ambiguous for a stated reason.
Requirements that fail this test are not requirements. They are moods.
- “Strong operational leadership” — every candidate passes if you like them.
- “Entrepreneurial mindset” — unfalsifiable.
- “Proven track record of driving results” — describes everyone who has held a job.
- “Cultural fit” — real, important, and not something research can evaluate.
The last one is worth separating out. Some of what a client cares about genuinely cannot be assessed from evidence, and pretending otherwise is worse than admitting it. Those things belong to the interview stage. The problem is not that they exist; it is when they sit in the brief as though research will handle them, and then nobody handles them.
Sharpening the vague ones
Most vague criteria are compressed versions of something specific. The intake conversation is where they get decompressed.
“Scaled a business.” Scaled from what to what, on which axis? Revenue, headcount, sites, geographies, product lines? “Took a single-site operation to three sites” is checkable. “Scaled a business” is not.
“Strong operational leadership.” What was the span — people, sites, countries? Was there a P&L, and how large? How many layers below them? “Held P&L responsibility for two or more manufacturing sites simultaneously” produces a result.
“Experience in a regulated environment.” Which regime? FDA and financial services regulation demand different instincts. Name it.
“International experience.” Lived and worked in-market, or managed a team from a distance? These are different capabilities that share a phrase.
“Change management.” Growth, turnaround, integration, or wind-down? These are four different jobs producing the same line on a CV.
The question that does most of this work in the room: what would I have to see in someone’s history to believe this? The client’s answer to that is the criterion. Write down their answer, not their original phrasing.
Separate must-haves from preferences — honestly
Every brief contains requirements that are in the document because they were in the last document. Finding them takes one question, asked of each item:
“If a candidate met everything else but missed this, would you still want to see them?”
Yes means it is a preference. No means it is a must-have. The answers are frequently a surprise to the client, which is the point.
Aim for a small number of true must-haves — most searches have three to six. A brief with twelve must-haves is either a role that does not exist or a client who has not prioritized, and in both cases the research will find out the expensive way. Long must-have lists also tend to produce searches that fail on paper while the actual right candidate sits in the near-miss pile.
Say what the role is really for
The requirements describe a person. They rarely describe the job.
Two VP Operations searches with identical requirement lists can be completely different searches: one is stabilizing a business that grew too fast, the other is preparing an operation for sale in eighteen months. The evidence you would look for is different in each case, and so is the profile that fits.
So the brief should carry a short, plain statement of the actual mandate: what has to be true in two years that is not true now, what specifically is broken or being built, why the role is open, and what happened to the last person in it. This is the section that makes the lateral pass possible — you cannot recognize someone with the right substance and the wrong label unless you know what the substance is for.
Be explicit about the boundaries
Three constraints cause more late-stage collapse than anything else, and all three take two minutes to nail down at intake:
Compensation. A range, and what is flexible in it. Discovering the ceiling after a candidate is engaged wastes everyone’s time and costs you the candidate for the next search too.
Location. In-office, hybrid, or remote — and if relocation is on the table, whether it is actually funded.
Hard exclusions. Non-competes, named companies that are off-limits, sectors the client will not take from. Better stated at the start than discovered at the shortlist.
What thin briefs cost downstream
An underspecified brief does not slow research down. It sends it in a slightly wrong direction at full speed, and the cost compounds at every stage:
- Discovery casts against a fuzzy target, so the pool is subtly off. Nobody notices, because a pool of two hundred always looks like work.
- Filtering becomes taste. With no evaluable criteria, cuts happen on impression, and the reasoning is not recorded because there is no reasoning to record.
- Deep research confirms things nobody asked about and misses the thing that turns out to matter.
- The shortlist cannot argue its case. Entries say “strong background in operations” because the brief said “strong operational leadership” — the vagueness passes straight through.
- The client meeting becomes a re-litigation of the brief with six candidates on the table as evidence. That conversation should have happened at intake, for free.
A structure that holds
Not a template — fields worth having answers to before research begins:
- The mandate. What the role is for, in three or four sentences.
- Must-haves. Three to six, each checkable against evidence.
- Strong preferences. Things that change where a candidate sits, not whether they exist.
- Explicitly not required. What failed the must-have test, written down so it does not resurface.
- Scope markers. Span, P&L size, org depth, constraint set — the shape of the job, not the title.
- Constraints. Compensation range, location, hard exclusions.
- Signals worth weighting. Sector adjacencies to explore, regulatory exposure that transfers, the kinds of laterals the client is open to.
- Assessment split. What research will evaluate, and what is being left to interviews.
That last field is the one most briefs omit and the one that prevents the most arguments. It makes the seam explicit: the research establishes what is true and which requirements it satisfies. The judgment about who is right stays with the people who have the context to make it.
Related reading: executive succession planning, executive search best practices for candidate research, how a CEO search actually works, what a good shortlist contains, and how to screen executive candidates.
Frequently asked questions
What makes an executive search brief different from a job description?
A brief is the rubric every downstream decision gets run against. Every requirement in it should be checkable against evidence and produce a yes, no, or ambiguous answer — a job description's language usually cannot do that.
How many must-have requirements should an executive search brief have?
Most searches have three to six genuine must-haves. Ask of each item whether you would still want to meet someone who cleared everything else but missed it — a 'yes' means it is a preference, not a must-have.
What's a quick test for whether a search requirement is actually usable?
Hold it against a real person's record. It should produce yes with a source, no, or ambiguous for a stated reason. 'Strong operational leadership' fails that test; 'held P&L responsibility for two or more sites' passes it.
Should a search brief include things like cultural fit that can't be evaluated from evidence?
It can name them, but separately — as belonging explicitly to the interview stage rather than sitting in the brief as though research will assess them, since research genuinely cannot evaluate fit from evidence.
What happens if a search brief stays vague instead of getting specific?
It does not slow research down. It sends the search in a slightly wrong direction at full speed, and the vagueness resurfaces at the shortlist review as an argument, with candidates on the table standing in for the conversation that should have happened at intake.