Off-Limits Company Lists for Executive Search 2026

A researcher finds the ideal operations director. Ten minutes before outreach, a partner remembers the person’s employer became a client last quarter. The firm had an off-limits list. It lived in a spreadsheet last edited by somebody who left in May.

What is an operational off-limits list?

An off-limits list tells the search team which organisations, business units or relationships must not be sourced for a defined mandate, why the restriction exists, who approved it, when it began, when it will be reviewed and how exceptions are decided.

It is not a permanent blacklist and should not silently label every employee at a group company. Contractual restrictions, client promises, conflicts, candidate confidentiality and commercial policy need separate reason codes and evidence because their scope and duration differ.

Run the check before researchers reveal a confidential role or start contact. A warning after outreach protects neither the client relationship nor the candidate who received the message.

Define the restriction as precisely as the evidence allows

Record the legal entity, relevant business unit, geography, relationship and mandate rather than one familiar brand name.

Large corporate groups create false certainty. A search agreement with one subsidiary may or may not cover its parent, sister companies, acquired businesses or portfolio holdings. Read the actual terms and client instruction. Do not let a researcher infer the scope from a logo or CRM account hierarchy.

Capture known aliases, domains and ownership changes so matching works. At the same time, avoid automatically expanding a restriction to every entity in a group. Overbroad controls can exclude much of a niche market and make a search impossible without any contractual basis.

State whether the boundary concerns all employees, particular teams, recent placements, introduced candidates or client contacts. An employee can also have an individual non-contact instruction independent of the employer-level rule.

• Legal entity and any evidenced group scope.
• Mandate, geography, business unit and role population.
• Reason category and source document or client decision.
• Start, review and expected expiry dates.

Separate contract, conflict and courtesy rules

Different restrictions need different owners, evidence and escalation paths.

A written non-solicitation clause is not the same as a partner’s commercial courtesy. A conflict involving a board member is not the same as a recent placement warranty. Label the reason accurately so the firm knows whether an exception is legally unavailable, commercially sensitive or possible with documented approval.

Have qualified people interpret unclear contract language. The CRM can surface the clause and prevent casual outreach; it cannot decide how a court would interpret “client group” or whether a national restriction is enforceable. Keep the operational rule aligned with current legal advice.

Do not use off-limits flags to hide weak client relationships from the wider team. If the reason is purely account ownership, use an account-routing workflow. Mixing sales territory with candidate-contact prohibitions makes both controls unreliable.

Give every restriction an owner and an expiry review

A boundary without ownership ages into folklore.

Assign the client partner or compliance owner who can confirm scope, answer researcher questions and approve a documented exception. A departed partner’s initials are not enough. Ownership should transfer during offboarding and mandate handover.

Use an actual review date even where a restriction has no fixed contractual end. Client status, acquisitions and search agreements change. Review recent placements, terminated agreements and group structures against current evidence rather than carrying every old flag forward.

Expiry should not silently release a company into outreach either. Route it to review, state the evidence checked and record the decision. Automatic expiry can be useful for low-risk courtesy periods, but contractual controls deserve confirmation.

Check at research, shortlist and outreach stages

One early check misses records added later and one late check wastes research or reveals the mandate.

Screen target companies during market-map design so the search strategy reflects the available market. Check again when a person enters the longlist because employment data can be stale or ambiguous. Run the final control immediately before outreach using the latest company and relationship information.

Use warnings that explain the restriction and escalation route without exposing confidential client details to everybody. A red icon with no reason invites workarounds. A full contract shown to every researcher exposes too much. Present the minimum useful control information.

Treat aliases and career moves carefully. A candidate who left an off-limits employer six months ago may be contactable, while a profile still showing the former company could create a false block. Verify current employment proportionately rather than assuming database data is perfect.

Design exceptions as a controlled decision

An exception needs a named approver, evidence, scope, time limit and candidate-safe contact plan.

Typical cases include a client expressly releasing a business unit, a person who independently approached the firm, an expired placement restriction or an entity outside the agreed group. None should become a chat message saying “partner says fine.” Attach the source and specify exactly what is allowed.

Consider what the candidate expects. An inbound enquiry does not necessarily authorise the firm to reveal a confidential assignment or bypass a valid contractual boundary. Separate permission to talk with the person from permission to recruit for this mandate.

Log denied exceptions too. Repeated requests can show that the market map is unrealistic or the brief conflicts with a major client portfolio. The answer may be client recalibration, not creative routing around the control.

An exception is a new scoped rule, not the disappearance of the original boundary.

Keep personal data out of company-level controls where possible

A company restriction rarely requires a hidden dossier on every employee.

Store entity, reason, dates and source. Add named individuals only when the restriction genuinely concerns them, such as a protected candidate relationship or recent placement, and document the purpose. Avoid speculative notes about loyalty, family connections or who might “tell the client.”

If a person asks not to be contacted, maintain that instruction in the candidate control designed for it. Do not rely solely on their employer appearing on an off-limits list; they may change jobs and receive outreach the next week. Company and person-level restrictions solve different problems.

Apply access controls to sensitive conflict reasons. Researchers need the action and escalation route, not every commercial dispute or board relationship behind it. Data minimisation applies inside the agency too.

Reconcile the list with the CRM and client register

The off-limits control should react to current client and company data instead of living as a duplicate database.

Connect restrictions to canonical company records and client engagements. Detect spelling variations, renamed entities and acquisitions for human review. Do not let fuzzy matching block a similarly named unrelated company without evidence.

Create change alerts when a new client, placement or contract could affect active searches. The search owner should see the potential conflict before the next outreach batch. Likewise, a released restriction should update the market map only after the review completes.

Track synchronisation failures. If a spreadsheet import rejects an entity or an integration stops, the team needs an alert and a temporary control. Silent stale data is worse than a visible manual process.

Audit decisions and test the control

Sample real searches to see whether the right warnings appear and whether people follow them.

Review blocked contacts, overrides, expired restrictions and outreach stopped at the final check. Look for false positives that waste researcher time and false negatives discovered only through partner memory. Correct the entity map and rule, not just the single candidate.

Test role permissions. A researcher should be able to identify and escalate a restriction but not rewrite it. Partners should not be able to remove contractual boundaries without the defined approval. Keep the change history separate from casual notes.

Useful metrics include restrictions without owners, overdue reviews, exceptions lacking evidence and outreach attempts prevented. Do not celebrate the largest list. A precise, current list is safer than a massive one nobody trusts.

Off-limits company-control fields

This structure makes the sourcing boundary clear without turning it into a permanent, opaque blacklist.

Limits of off-limits software

This guide does not interpret non-solicitation clauses or determine whether a restriction is enforceable. Contract wording, governing law, client relationship and individual facts need qualified review.

Company matching cannot be fully automatic. Corporate groups, acquisitions, aliases and outdated candidate employment data create ambiguity; human review remains necessary before sensitive outreach.

Off-limits list questions

Practical answers for executive-search teams balancing client commitments, candidate trust and a reliable market map.

Should every current client be automatically off-limits?

Not without checking the actual agreement and policy. Record the evidenced entity, population, geography, duration and reason. Automatic global blocks can exceed the real commitment.

Can a partner approve an exception in a message?

Use the firm’s defined authority and preserve evidence, scope and duration in the control record. A casual message is easy to misread and difficult for the next researcher to audit.

What if a candidate contacts the agency first?

Inbound contact changes the practical context but does not automatically cancel contractual or confidentiality restrictions. Review the specific boundary and agree what conversation is permitted.

How often should off-limits records be reviewed?

Review on client, contract, placement and corporate-structure changes, with a dated periodic backstop. Higher-risk contractual and board conflicts deserve closer oversight.

Official sources for lawful and proportionate controls

AESC describes off-limits and conflict questions in executive search; the GDPR and EDPB explain purpose limitation, data minimisation and lawful processing.

• Association of Executive Search and Leadership Consultants: Global guide, including off-limits and conflicts
• EUR-Lex: General Data Protection Regulation — principles, rights and security of processing
• European Data Protection Board: Process personal data lawfully

Connect sourcing controls to the mandate

Close a search mandate with accountable handover · Track candidate-data provenance · Build evidence-led candidate shortlists · Explore Yena for executive search