Executive search
Executive search longlist calibration: review evidence before moving names forward
A longlist review worksheet for researchers and consultants: agreed criteria, source-backed findings, unresolved questions and explicit next research actions.
A longlist meeting can produce a clear-looking result without resolving the important questions. A name is familiar, a title looks relevant, a client likes a profile, or a researcher has found an interesting company. Those signals may deserve attention. The review still needs to establish which evidence is available and what should happen next.
Longlist calibration makes that research decision visible. It connects the current criteria, the findings and the gaps before the team turns a working list into a stronger claim about an individual. The practical output is an agreed set of next research actions, with owners and reasons.
This is an original research-stage worksheet. It is distinct from the shortlist feedback record, which helps reconcile later client comments. It does not provide an automatic ranking method, validate a selection instrument or prescribe how many candidates a search must include.
TL;DR
- Review against the current mandate, with the same definitions available to everyone involved.
- Separate source-backed findings, candidate statements, consultant interpretation and missing evidence.
- Give unresolved questions an owner and a next action. Blank information should remain distinguishable from a negative finding.
- Record the reason for the research decision and any limits on sharing the working record.
A copyable longlist calibration record
Use one record per research question that matters to a decision. A single profile can have enough evidence on one criterion while remaining unresolved on another.
| Field | What to capture |
|---|---|
| Assignment and criterion version | The instruction this review is using |
| Record reference | A stable reference to the permitted working profile |
| Criterion under review | The specific experience or question being investigated |
| Finding | What the available material actually establishes |
| Source and date | A source pointer and the period it describes |
| Interpretation | The consultant's reasoning, clearly attributed |
| Gap or contradiction | What remains unknown or inconsistent |
| Next research action | The work needed before the next decision |
| Owner and review point | Who accepts that work and when it will be reconsidered |
| Visibility | Who may see the working material and the reviewed summary |
Keep the record readable beside the underlying notes. A short, traceable explanation is more useful than a detailed matrix whose cells conceal the difference between observation and assumption.
Confirm which brief the review is using
Open the currently agreed mandate record before reviewing names. Identify changes since the research began and which earlier decisions they may affect. If the team is working from different versions, clarify the instruction before drawing a consolidated conclusion.
Ask whether the criteria describe work the leader needs to do or shorthand that has become convenient. A sector label, job title or company name can direct a research question without establishing the underlying experience.
In federal assessment, OPM's job-analysis guidance links job tasks and required competencies. Use that distinction to make the research question precise. The worksheet here is our process suggestion, not a federal requirement for retained search or proof that a particular criterion is appropriate.
Record any criterion that the client still needs to clarify. Give the team a bounded interim action, such as collecting relevant evidence while holding the dependent decision. Do not let a meeting's desire for a complete-looking list settle the unresolved instruction.
Build the evidence record before the meeting
Ask the researcher to supply a concise finding and a source pointer for each consequential statement. Preserve the source date, the reporting period and any uncertainty about what the material covers. The reviewer needs to be able to locate the evidence without reconstructing the whole research session.
Use the distinctions in the candidate research notes guide. A public statement, an account given by a candidate and a consultant's inference can all be useful, provided their origin is clear. They should not quietly become interchangeable facts in the summary.
When evidence concerns an organization, state the limit of that evidence. A company's activity does not show which responsibility an individual held. When information describes an earlier role, retain its period rather than presenting it as a current position.
Write the open question in a form someone can investigate. “Needs more research” leaves the next colleague to define the task again. “Confirm the person's responsibility for the operating change described in the source” identifies the gap while leaving the answer open.
Use consistent questions without pretending uncertainty is a score
Bring the same criterion definitions and evidence categories to each record. This helps reviewers notice when one explanation rests on a sourced account and another rests on a title alone. It also makes disagreements about interpretation easier to discuss.
OPM's structured-interview guidance describes predetermined questions and common rating standards. That is an interview methodology. A longlist discussion can borrow the organizational discipline of explicit questions while remaining a different, research-stage activity.
If the firm uses an existing assessment method, follow its defined purpose and review responsibilities. This article does not validate a new scoring system. Avoid creating numerical precision simply because a sheet can calculate it.
If evidence remains unavailable, record that outcome and refer the next decision to the agreed human review process. Do not hide the gap behind a completed task label.
An unresolved finding deserves an explicit status and a next action. It should not be converted into a low score or treated as evidence of a person's limitations. Discuss what the record supports, what it does not yet establish and which permitted follow-up could resolve the question.
Synthetic example: four records, different research questions
The following records and counts are fictional. They demonstrate review work, not candidate quality, hiring outcomes or a recommended longlist size.
A consultant and researcher review four example records against a current operating-experience criterion. Each record needs a different kind of clarification.
| Record | What the working material contains | Agreed next research action |
|---|---|---|
| A | Company-level information relevant to the mandate | Verify the individual's responsibility before drawing a stronger conclusion |
| B | A relevant account from an earlier period | Check whether the stated position and context are current |
| C | Two accounts with inconsistent dates | Preserve both references and assign a clarification question |
| D | Research based on a criterion that has since changed | Revisit the finding against the confirmed current instruction |
The meeting produces four owned research actions. It does not claim that four people meet the role requirements. The distinction matters because the action is about the evidence the team needs next.
For Record C, the consultant asks for the contradiction to remain visible in the handoff. The researcher is not asked to choose the more convenient date. For Record D, the brief owner confirms which revision applies before more work is commissioned.
At the next review, the team checks the answers and source pointers. An action can close because a question has been resolved, because the client has clarified its relevance or because the team has explicitly agreed to stop that line of research. Keep the reason with the outcome.
Discuss disagreements at the level of evidence and interpretation
Ask each reviewer to identify the statement they disagree with and the evidence they relied on. This can reveal several different issues: inconsistent definitions, missing context, different source periods or a genuine difference in judgment.
Keep a factual correction separate from a change in interpretation. If a source was misread, correct the finding through the team's record process. If the finding is sound but its relevance is disputed, preserve the reasoning and identify the person or client process needed to resolve that question.
Make the meeting outcome understandable to someone who was absent. A comment such as “not convinced” needs a more specific explanation before it can guide useful research. Ask what is unconvincing, which criterion it affects and what evidence would help.
Avoid recording disagreement as an account of a colleague's competence. The record exists to explain the work and the decision. Attribute professional interpretations appropriately and retain only the detail needed for that purpose.
Review sharing behavior before using client feedback fields
Check how the existing tool separates internal working notes from client-visible material. Review the record and intended audience before entering a comment whose visibility or notification behavior may have consequences.
For example, Clockwork's longlist documentation distinguishes reactions and comments, with client-visibility and email options. That describes Clockwork. A reaction count does not explain the underlying reason for an opinion, and it does not establish that a working note is appropriate to share.
Use the smallest reviewed explanation that serves the client discussion. Keep necessary source pointers and uncertainty available through an appropriate permitted route. Do not assume that a colleague has access to every linked record because they can view the list.
If the client provides feedback through a different channel, confirm its meaning before translating it into the working system. Preserve which part is a question, a preference or an instruction under the client's agreed decision process.
Turn the review into a clear next handoff
Before closing the meeting, read back the unresolved questions, accepted actions and dependencies. Ask each owner to confirm the task they are taking. If an action depends on a client response, name the consultant who will seek it.
The next client update should describe the useful progress and material questions accurately. The AESC Client Bill of Rights includes ongoing search communication for member firms. Keep that member scope clear; it is a professional reference, not evidence of Laisy membership or a guarantee of results.
Retain a version of the reviewed record that explains the current research state. At the next meeting, review what changed and what remains unresolved. Repeated discussion is easier to diagnose when the earlier question and promised action are visible.
Try one reviewed calibration task
Select a suitable part of a live assignment and agree the permitted records, the reviewer and the intended output. Define what would make the work useful: traceable findings, explicit gaps and a handoff with actions the next colleague can understand.
A Laisy discussion can start with that bounded task alongside your existing tools. Agree the selected inputs, output review and point to continue or stop. The offer does not promise automated candidate assessment, a particular research result or access to a full replacement platform.
Frequently asked questions
Does a longlist need a universal minimum number of names?
This guide makes no such claim. Agree the research scope with the client and explain coverage and limitations. A count alone does not establish the relevance or completeness of the evidence.
What should an empty criterion field mean?
Define it explicitly. Missing evidence, an unanswered question and evidence that does not address the criterion are different states. Preserve the distinction and assign a next action where appropriate.
Can the team use AI suggestions in the review?
Any suggestion needs checking against the agreed instruction and original sources. Keep human responsibility for interpretation and decisions. Do not treat an unverified summary or generated rating as established evidence.
When is a calibration action complete?
When its owner can show the agreed evidence or record the authorized reason for closing it, and the next reviewer can understand what changed. Updating a status without that explanation may leave the original question unresolved.