Executive search

Contact exceptions in executive search: record the decision before outreach

Document one proposed contact exception with the governing restriction, decision authority, permitted action, conditions and a reviewable record before outreach.

By LaisyPublished

A consultant sees a strong potential candidate at a restricted company. Someone says the restriction probably does not apply because the individual knows a partner. Research continues, a message is drafted, and the important question is left behind: who established what the firm was actually allowed to do?

A contact-exception review makes that question explicit. It attaches a particular proposed action to the applicable restriction, the person authorized to interpret or decide it, and the precise limits of the decision. It records a decision; it does not manufacture authority to make one.

This guide concerns a single exception request. A wider off-limits register still needs its own ownership, accurate scope and maintenance. Neither a useful candidate profile nor an introduction route establishes permission to depart from an agreement.

Copyable contact-exception record

FieldRecord for this request
Assignment and request referenceThe mandate and this specific proposed exception
Proposed actionWho would do what, through which route, for what purpose
Restriction sourceCurrent agreement, policy or instruction and the relevant provision
Applicability questionThe exact uncertainty requiring interpretation or a decision
Request ownerPerson responsible for assembling and following up the request
Decision authorityAuthorized role, person and basis for that authority
DecisionPermitted, declined, conditional or awaiting clarification
BoundaryPerson, entity, role, channel and time conditions where applicable
EvidenceDated decision record and source version
Execution ownerPerson who receives and acknowledges the actual instruction
Recheck triggerChanged employment, purpose, agreement or other material condition

Use a request identifier that remains stable when the proposal changes. Keep the proposal and the eventual instruction distinguishable. A draft request forwarded by a partner is still a request until the responsible authority has decided it.

The mandate kickoff checklist helps establish the initial search boundary. This record handles a specific question that arises within that boundary later.

Establish which restriction is in question

Start from the current source rather than a remembered label. Ask which entity, person, assignment and activity the restriction covers. If the relevant document is unclear or unavailable, record the gap and seek the appropriate internal or client clarification. Do not fill it with a convenient interpretation.

Bullhorn Recruitment Cloud documents off-limit line items with active status, start and end dates, and reasons for enabling or disabling them. These are that supplier's controls, not a definition of your client agreement.

A company flag and an individual flag can prompt different checks without either settling the substantive question. The record should point to the governing source and explain how the displayed flag relates to it. A missing flag does not prove there is no restriction.

Keep commercially sensitive terms in the appropriately restricted source. The working record can carry the operational instruction and a reference for authorized reviewers, rather than copying the entire agreement into every candidate note.

Define the action narrowly enough to decide

“Can we speak to this person?” is often too broad. It could mean asking an intermediary whether an introduction is possible, discussing an unrelated topic, presenting an assignment or seeking a reference. Those actions may expose different information and require different decisions.

Write the proposed action as a sentence: “The named consultant proposes asking the designated relationship owner whether an introduction request may be considered, without identifying the client or discussing a role.” That is a narrower request than an unrestricted approach. It is an example of useful specificity, not permission to perform that action.

Also record the alternative if the request is declined. The team might continue research within the existing boundary, seek another route after proper review, or leave the person out of the current work. An alternative helps the request remain a decision instead of pressure to approve the only apparent path.

Do not add an asserted emergency merely because a delivery date is approaching. Urgency can be recorded as context; it does not change the decision maker's authority or the substance of the restriction.

Identify the authority behind the decision

The requester, relationship owner, client sponsor and person authorized to interpret an agreement may be different people. Ask what authority the proposed approver holds for this specific decision, and whether another party must be involved.

A system administrator's ability to disable a warning establishes a technical capability. It does not by itself establish commercial authority. Likewise, a colleague's willingness to make an introduction says something about that colleague's willingness, not necessarily about the firm or client's restriction.

If several approvals are required, keep their scopes separate. One person may confirm an entity interpretation while another decides whether the firm should proceed. The record should show which question each response answers, including any question that remains open.

Where interpretation has legal or contractual significance, use the firm's appropriate professional and governance route. This template is a practical documentation aid and cannot determine the meaning or enforceability of an agreement.

Preserve the difference between a request and an instruction

A request contains the proposed action and supporting information. A decision records what was accepted or declined. An execution instruction tells the person doing the work what they may actually do now.

These can live in the same controlled record, but should have visible headings and dates. If the proposed action changes after approval, return the changed question for review rather than relying on the original answer as general cover.

Google Docs version history provides named versions as one way to distinguish document states. In any tool, record the version that was reviewed. A version name improves traceability; it does not prove that an authorized person approved its contents.

Attach relevant factual context through the candidate research-note structure. Keep unsupported assumptions out of the rationale. “The candidate would probably welcome contact” is not a substitute for evidence about the applicable boundary.

Worked example: two proposed actions, one limited answer

This is a fictional documentation exercise, not an interpretation of a real restriction. Request ER-07 concerns assignment A17 and restricted company C. Its source is agreement AG-2, revision 4; the request owner has identified the provision and the authority route before seeking a decision.

Record componentFictional completed instruction
Decision evidenceDated response DR-07 from the person designated for this question in the firm's authority record; AG-2 revision 4 identified explicitly
Action 1Consultant asks the designated relationship owner: “May I submit an introduction request for review?”
Conditions on action 1Do not identify the client, describe the role or contact the candidate; use only the designated internal route
Action 2Candidate approach about the assignment: not approved
Execution ownerNamed consultant acknowledges DR-07 and its conditions before taking action 1
Recheck triggerChanged agreement version, employer, purpose, recipient or proposed contact route; return the changed question for review

The operational readback is: “ER-07 permits the internal route question only; candidate approach remains unapproved.” It must not become “exception approved.” A response offering a direct introduction creates a new proposal, not permission to send it. The consultant holds that step and returns it to the recorded authority.

If the authority record does not establish who can decide, ER-07 stays pending. A filled template, a relationship owner's enthusiasm or an approaching deadline cannot supply the missing authority.

Give the execution owner a usable boundary

The person who acts needs the operational instruction, not a reassuring green status. Include the allowed purpose, route, information limits and any condition that must be checked immediately before action.

Ask the execution owner to acknowledge the instruction and raise anything that cannot be followed. A record stored somewhere in the firm is not evidence that the consultant about to send a message has seen its conditions.

Use the assignment handover structure when the work changes hands. Carry the exception reference, live conditions and unresolved questions into the handover. Do not require the receiving colleague to infer the instruction from a long chain of requests and replies.

When an action is completed, record what occurred and any material departure or uncertainty. Do not retrospectively alter the original approval to make it resemble the action that happened. Preserve the distinction and follow the firm's appropriate review route.

Control where the decision is shared

Exception records can reveal confidential client relationships, commercial restrictions or candidate context. Decide which readers need the full decision evidence and which need only a restricted operational instruction.

Google Drive's folder-sharing guidance explains inherited access. A document placed inside a broadly shared location may not have the audience its author assumed. Check the actual sharing boundary in the chosen system before adding sensitive supporting material.

Keep enough detail for the responsible reviewer to establish the decision, but avoid duplicating personal or commercial material without a reason. A link is useful only if its intended reader can access the correct source; making the source public is not an appropriate repair for an access problem.

Recheck when the underlying question changes

An exception is attached to its circumstances. A changed employer, different role, altered assignment or revised client instruction may change the question. The original record should state relevant recheck triggers rather than imply indefinite permission.

Review an expired or superseded decision before reusing a historical contact route. Preserve the old record according to the applicable policy, with its status visible, instead of treating a past approval as a permanent property of the person.

For a bounded workflow trial, use the pilot success criteria to agree whether another reviewer can recover the precise permitted action, its authority and its conditions from selected permitted materials. That is a reviewable process question; it is not an automatic authorization or a promised reduction in risk.