Executive search
Executive search consultant onboarding: prove the workflow with a practice assignment
An onboarding checklist for a new search consultant: role-specific practice, synthetic assignment records, review feedback and a clear route into supervised live work.
A new consultant can finish a software tour and still be unsure how the firm expects them to handle an incomplete source, a changed instruction or an internal note that should not become client material.
Executive search consultant onboarding should give the new colleague a chance to practice those choices before they meet them on a live assignment. A small fictional assignment connects the firm's written process with the records, review conversations and working boundaries they will use.
This guide is about firm-level learning for a new starter. Transferring one live mandate between colleagues is a different task, covered by the assignment handover checklist. A practice exercise also does not replace the employer's induction, required training or performance process. It gives the manager and the new colleague a concrete piece of work to discuss.
Copyable consultant-onboarding practice plan
Adapt the plan to the new colleague's role and experience. A researcher, delivery consultant and partner may need different exercises even when they use the same system.
| Learning area | Practice task | Review question |
|---|---|---|
| Assignment context | Read a fictional brief and explain the working question | Can the consultant distinguish agreed instruction from an open request? |
| Evidence | Write a short note from selected public or synthetic sources | Are findings, interpretation and uncertainty distinguishable? |
| Collaboration | Prepare an internal handoff | Can the next colleague locate the source and next action? |
| Audience | Adapt a working summary for a specified recipient | Has internal discussion been reviewed appropriately? |
| Change | Respond to a fictional revision | Is the affected work identified before continuing? |
| Escalation | Encounter a deliberately unresolved question | Does the consultant know who can resolve it? |
| Follow-through | Review feedback and revise the artifact | Can they explain the correction and apply the lesson? |
This is an original learning structure, not a validated employment test. Tell the participant what the exercise is for and how it will be reviewed.
Begin with the role the person is joining
Ask the manager what the new consultant will actually do first. Identify the records they need to understand, the decisions they may make and the points where review is required. A generic onboarding list assumes every hire has the same starting knowledge.
Acas's induction-planning guidance tells employers to tailor an induction plan to the new worker and support them in putting training into practice. It also says a manager should review how the induction is going. This guide adapts those points to search operations. It does not prescribe the employer's full programme or a fixed period for becoming independent.
Include the consultant's questions when setting the practice plan. Someone experienced in search may know the market but need help with the firm's record conventions. Someone familiar with the software may need more discussion of evidence and review expectations.
Give each learning task an owner who can explain the firm's actual process. Where two colleagues give conflicting instructions, resolve the process question instead of expecting the new starter to pick one.
Build a small fictional assignment with purposeful gaps
Prepare a synthetic brief, a few public-source extracts or invented research records and a named intended audience. Label the whole exercise as fictional. Do not reuse an old confidential assignment as training material because it is easy to find.
Include enough information to complete each task and a small number of deliberate ambiguities. One instruction may still be a proposal, or a source may establish a company's activity without establishing a person's responsibility.
Use the mandate kickoff checklist as the model for the fictional baseline. The new consultant should be able to locate the instruction and explain what would need confirmation before the work expands.
Write down which gaps are intentional and give that list to the reviewer. Otherwise a reviewer can mistake a well-founded question for a failure to finish. Sometimes the right answer is that the supplied material cannot support a conclusion.
State what the artifact must let someone do
Tell the learner who will use the output and for what decision. "Prepare a good note" gives them little basis for judging their own work. "Prepare a note from which the reviewer can trace each consequential finding to its source" can be checked.
Use the firm's actual artifact conventions. The candidate research-note guide can support an exercise in separating evidence, attributed accounts and consultant interpretation. Ask the new colleague to explain the distinction using their own example.
Assess the work against the task's stated purpose. A differently worded but accurate note may be fine. A polished note containing an unsupported conclusion needs correction however closely its layout matches the sample.
Teach access and project membership as working boundaries
A software demonstration should explain what the consultant is seeing and why. Being able to open a workspace is different from being assigned to a piece of work or being entitled to distribute its content.
Clockwork's project-team documentation says a user must first be added to the system before they can be assigned to work on a project. That is one product's behavior. It shows why a firm should explain account setup and assignment membership separately; it does not authorize granting access during an exercise.
Use a training location and the employer's normal authorization process for any real account setup. The practice task should never require the learner to explore unrelated records or work around a restriction to show initiative.
Include one question the learner cannot answer without asking, and check whether they identify the right person. Stopping at the boundary and requesting clarification, with enough context for the owner to act, is the expected behavior.
Introduce a changed instruction after the first review
Once the first artifact is reviewed, issue a revised brief. Ask the consultant which part of the work it affects and which existing statements need reconsideration.
If the firm uses Google Docs, a named version can mark each training brief so the learner can compare them; browsing earlier versions needs edit permission on the file. The exercise still needs the reason for the change and who authorized it. A file edit explains neither.
The consultant should be able to explain why an old finding can stay accurate for its original question while no longer answering the revised one. Record tool friction separately from a misunderstanding of the process, so the review does not become a test of remembered clicks.
Worked example: the Kestrel practice assignment
Everything in this example is fictional: the firm, the practice assignment "Kestrel", brief versions K1 and K2 and the new consultant, Consultant J. It shows how a reviewer records decisions from one exercise. It is not a customer case, a validated score or a recommended timetable.
Consultant J joins a fictional boutique as a delivery consultant. Their manager sets the Kestrel exercise: brief K1 for a fictional operations-director search, six synthetic source extracts and a named reviewer. After the first artifact is reviewed, the manager issues K2, which confirms a second region for research only. The manager's list of intentional gaps includes an unconfirmed client question about compensation benchmarking.
| Practice task | What the reviewer saw | Decision | Next action and owner |
|---|---|---|---|
| Read K1 and state the working question | Separated the agreed instruction from the client's open question about a second region | Accepted | None; keep as a reference answer |
| Research note from six extracts | Findings carried source pointers; one sentence inferred a person's budget responsibility from a company announcement | Revise | Consultant J rewrites the sentence as unresolved; reviewer rechecks that line only |
| Respond to K2 | Flagged two affected statements but not the changed target-company boundary | Discuss | Manager walks through the affected-work check; Consultant J repeats it on a short K3 revision |
| Internal handoff to reviewer | Presented the compensation-benchmarking question as a confirmed deliverable | Repeat | New bounded scenario on instruction status; manager shows where confirmation is recorded |
| Escalation question | Did not know who resolves an instruction dispute | Fix the material | Manager adds the named route to the practice pack; this was a gap in the pack, not in the learner |
The reviewer does not average these rows into a rating. One task is accepted, one needs a single-line revision, two need a second attempt aimed at the specific gap, and one exposed a gap in the practice pack. The manager then agrees Consultant J's first supervised live task: research notes on one assignment, reviewed before anything leaves the team. Internal handoffs stay with the reviewer until the repeat exercise on instruction status is done.
One repeat that goes well is not evidence of readiness for every live assignment. It shows that this gap was understood in this scenario.
Give feedback the colleague can apply
Refer to a particular statement, decision or missing source. Explain what it would cause the next person to misunderstand and show how the firm's method handles it.
Say whether a correction concerns factual support, visibility, instruction status or house style. Treating every difference as equally serious makes feedback harder to use.
Let the consultant revise the artifact and explain the change. The conversation can expose a problem in the training material or an unclear firm convention as well as a learning need, as the escalation row above did.
Keep a proportionate learning record: task attempted, feedback, support agreed and next review. Keep personal judgments out of a general knowledge folder. Handle any separate performance matter through the employer's own process.
Move into live work through an explicit first task
Agree the first live task, its reviewer and its boundaries. Confirm what the consultant may do independently and what needs review before action. Keep required induction and access setup on their normal tracks.
When the consultant joins a live assignment already in progress, use the handover checklist so they receive the current state of that mandate instead of inferring it from historical records.
Revisit support needs after the first live task. A real assignment will present ambiguities the practice case did not.
If you want to try a workflow like this alongside existing tools, the pilot success criteria help define one bounded task with selected permitted inputs, reviewed output and an exit point. This guide promises no automatic onboarding, qualification, account access or fixed time to competence.