Executive search
An off-limits working record: document the instruction before researchers act
Record off-limits instructions with their source, entity scope, review owner and unresolved exceptions. A practical search-operations template, not an interpretation of contract clauses.
A researcher sees an off-limits flag beside a company. They still need to know what instruction it represents, which entity it covers and who can resolve an uncertain case. A label without that context can be easy to notice and difficult to use.
An executive search off-limits working record connects the visible instruction to its approved source and an appropriate reviewer. It should make uncertainty easy to escalate before an approach is prepared or made.
This guide concerns recording and checking instructions. It does not interpret engagement clauses, determine legal enforceability or provide automatic clearance to contact anyone. The firm's authorized decision-makers and applicable professional process remain responsible for those questions.
Copyable off-limits working record
Use the record to make an instruction usable by the people doing the work. Link to an appropriately restricted source instead of copying the whole engagement document into every profile.
| Field | What the researcher needs to know |
|---|---|
| Source instruction | Approved document or decision pointer, version and responsible contact |
| Relevant engagement | The assignment or client context in which the instruction applies |
| Entity scope | Exact company, group, division or individual covered, as confirmed |
| Operational meaning | What action the researcher should pause, exclude or refer for review |
| Timing | Applicable confirmed dates and review triggers, without inventing a standard period |
| Exceptions | Specific approved decision, its scope and evidence, if one exists |
| Uncertainty | Ambiguous identities, entity relationships or conflicting instructions |
| Review owner | Who accepts responsibility for resolving the question |
| Checked state | What was checked for this proposed step, when and against which source |
Keep “unresolved” available as a real state. Requiring every row to be cleared or excluded can encourage researchers to hide the very ambiguity the record should expose.
Start with the approved instruction
Locate the relevant source through the firm's normal process. A recollection that a client is “probably off limits” can prompt a question, but it should not be rewritten as an agreed contractual term.
For AESC member engagements, the Client Bill of Rights identifies off-limits among terms that may need written clarity. That is a member standard, not a universal duration or a statement that Laisy is an AESC member.
Connect the working instruction to the mandate baseline. If the source and the current working brief disagree, identify the conflict and its owner. Do not choose whichever version makes the proposed approach easier.
Ask the responsible person to confirm the operational wording where necessary. Researchers need an instruction they can apply, while the original source remains available to the people authorized to interpret it. A simplified working record should not silently expand or narrow the agreed boundary.
Specify which entity the record describes
Company names can conceal different legal entities, brands, subsidiaries or operating divisions. A group-level label may be insufficient for a researcher looking at someone whose current role is attached to a particular unit.
Record the confirmed entity scope and the source supporting it. If the source does not settle whether a subsidiary or newly acquired business is included, preserve that uncertainty and refer the case. This article does not supply a default answer.
The person record also needs appropriate identity context. A former employee, a current employee and an independent adviser can appear near the same company in a database while presenting different questions under the actual instruction.
Use the candidate research-note structure to expose source dates and unresolved employment context. A company association in a record should not be treated as verified present employment solely because it appears in a populated field.
Understand what the software flag actually does
A product can implement a flag in a specific way that differs from the wording of an engagement. The team needs to understand both the implementation and the instruction it is meant to support.
Test company-level and individual-level instructions separately in the actual system. For a company flag, ask which employment records and entity relationships it checks. For an individual instruction, ask what happens when that person's recorded employer changes. Record the observed behavior and unresolved cases; do not assume that either test establishes the engagement's scope.
Check the behavior in the actual system and account before relying on it. An imported company name, an incomplete employment record or a different object type can create a question the visible flag alone does not answer.
Keep the record useful even when the tool cannot represent the full instruction. The appropriate response may be a review dependency and a clear working note. Do not invent an automatic check or disable a restriction to make the interface appear consistent.
Separate coordination from exception authority
The person gathering evidence may not be entitled to approve an exception. Identify who can clarify the source, who can make the relevant decision and who should receive the confirmed operational instruction.
Atlassian's DACI play distinguishes coordination from approval and contribution. It can help frame that responsibility discussion. The client's actual governance and the firm's delegated authority decide who may resolve the particular case; a collaboration model does not create that authority.
If an exception is approved, record the precise scope and source of the decision. Include any condition the researcher must satisfy before the particular step proceeds. A decision about one person or proposed action should not become a blanket removal of a company restriction unless that broader change was explicitly confirmed.
If nobody can identify an authorized decision-maker, leave the question open and route it through the appropriate process. A deadline for preparing an approach does not resolve uncertainty about whether the approach should occur.
Fictional example: four cases behind a single company label
This example is invented. The organizations, people and case counts illustrate record handling, not a legal interpretation, a standard restriction period or a customer result.
A fictional firm is preparing research within a confirmed assignment. Four records are associated with a similarly named company group. The working instruction covers a specified entity, but the records have different employment and source contexts.
| Case | What the selected evidence establishes | Appropriate working state in this exercise |
|---|---|---|
| A | Current employment at the explicitly covered entity is established | Apply the confirmed operational instruction and retain the source pointer |
| B | The person works at an affiliate whose inclusion is unconfirmed | Hold the proposed step and refer the entity-scope question |
| C | The record describes historical employment; current context is unclear | Check the relevant current evidence before applying a conclusion |
| D | A colleague mentions an exception but no approved decision is linked | Keep the restriction question open until the responsible person confirms the decision |
The researcher sends the unresolved questions to the accepted review owner. They do not label the four people “cleared” because no additional warning appears in a search result. The reviewed response must explain the instruction relevant to each proposed next step.
The example deliberately supplies no universal answer for affiliates, former employees or exceptions. Those answers depend on the actual source and authorized decision. The template helps the team locate the question instead of guessing it away.
Keep timing and changes traceable
Record the applicable confirmed dates, the basis for them and the event that requires review. Do not assume a standard restriction period from a blog, a previous client or a default field in a tool.
An apparent expiry can still require context. The source may have been amended, another instruction may apply or the record may concern a different engagement. Have the appropriate person check the actual position before changing the operational state.
When the instruction changes, identify the affected working records and communicate the confirmed revision to the people using them. A central document update does not prove that a researcher holding an older export has seen it.
Preserve the distinction between when the underlying decision took effect and when someone entered it in the system. That helps a reviewer understand a historical action without pretending the current instruction was always visible.
Recheck earlier records before using them in a new search
Old research can be useful, but a new assignment creates a new context for the proposed action. Establish which instruction applies now rather than carrying forward an old “checked” label without its source.
The candidate-rediscovery guide describes reviewing earlier information against a current search question. An off-limits review adds the relevant operational boundary before anyone treats rediscovery as a reason for outreach.
Keep the search firm's internal record separate from a candidate's willingness to discuss a role. A resolved internal conflict question does not establish interest, availability or permission for every disclosure. Those remain distinct questions in the actual workflow.
Where records disagree, retain the discrepancy and its owner. The useful output is a reliable working instruction or a visible unresolved dependency. A confident summary with the source conflict removed is less useful to the next consultant.
Keep AI assistance within professional review
A generated summary can make an instruction easier to scan, but it can also omit a qualification, confuse related entities or treat a tentative exception as settled. Review the summary against the selected source before using it operationally.
The AESC Professional Practice Standards state that AI should support professional judgment rather than replace it. That member standard is relevant to the role of a drafting aid; it does not certify a particular model, workflow or Laisy capability.
Do not ask a draft to resolve a clause beyond the responsible person's instruction. Keep the unresolved question visible. A system's failure to find a conflict is not proof that none exists.
Test one preparation task with a clear exit
Select a suitable instruction-review preparation task and agree permitted inputs, the human reviewer and the required output. Check whether the result preserves source, scope and uncertainty in a form the researcher can use.
Use pilot success criteria to include review and correction effort. A Laisy discussion can begin with that bounded task alongside current tools, with a point to continue or stop. No automatic clearance, guaranteed access, legal determination or full migration is promised.