Agree disclosure boundaries before an executive introduction

Executive searches often involve sensitive timing, relationships, and expectations. A recruiter should agree disclosure boundaries before sending a profile or arranging an introduction. A clear sequence gives a candidate practical control over personal information and gives a client a dependable path for panel planning. Privacy depends on a record showing recipients, purpose, and release time.

Open discussion before collecting a résumé or detailed career story. Explain how search activity moves from initial discussion to employer name, panel details, profile review, and introduction. Ask which information needs separate permission. An executive’s name, current employer, compensation expectations, interview timing, home location, board activity, and professional relationships do not need identical treatment. One broad confidential note leaves room for conflicting interpretations.

Omar, a fictional recruiter, begins a call with Caroline, a fictional executive candidate. He says, “I will record your release choices before I send your details anywhere. We will name each employer, document, recipient, and purpose. If people or documents change, I will ask again.” Caroline asks, “Who receives my name, and do I see panel names first?” Omar replies, “Before profile release, I will identify the employer and proposed recipients. I will request approval for those recipients. The client will provide available panel information before a final interview request.”

Caroline says, “I know a board member socially, and my current bonus vests in four months.” Omar answers, “I will keep both details within our discussion. I will ask the client only for panel information needed for your decision.” He does not write her social connection in a profile note. He does not send bonus timing to a client contact. Each detail belongs to Caroline until she gives a specific release direction.

Omar records Caroline’s boundaries in plain language. Her name and résumé stay in the recruiter file until she approves an employer. A career summary without her name does not go to a client unless she approves both content and recipient group. Her social connection does not go to anyone without her direction. Her bonus timing informs availability discussion with Omar, not a negotiation message to a client. The record lists every boundary beside an owner and date instead of burying privacy terms in general meeting notes.

Clarity over an employer name deserves special care. Some candidates discuss an unnamed opportunity early before deciding whether a role fits their background. Once a client name is available, Omar asks a fresh question. “The employer is North River Health, a fictional organization. Proposed first recipients are Dana Lee, search lead, and Priya Shah, human resources partner. Do you approve sharing your résumé and career summary with Dana and Priya for initial review?” Caroline has room to approve, request a change, or decline without giving a reason.

The recipient list identifies people, not departments. Leadership team says little about access. Dana Lee, search lead, and Priya Shah, human resources partner gives Caroline a real release decision. If a client requests internal profile review, Omar asks for names or a named function with expected access. He does not accept an open ended promise of narrow distribution. If participants change later, earlier consent does not cover new people.

Document boundaries also deserve detail. A résumé contains employment history and contact information. A career summary might contain selected leadership experience without personal contact details. An interview availability note contains timing information. Omar writes which document Caroline approved, not a vague phrase such as “candidate details.” He also records purpose. Initial profile review differs from a request for an interview introduction. A recipient who receives a summary for one purpose does not automatically receive a résumé for another.

Panel planning follows a similar sequence. Omar asks which interview details Caroline needs before agreeing to an introduction. She wants names, titles, meeting format, general timing, and notice of any board attendance. Her answer needs no personal explanation. “Please confirm panel members before an interview invitation” is enough. Omar records her preference, tells the client he needs panel details before seeking acceptance, and avoids describing her social connection.

Suppose a client asks for Caroline’s résumé before sharing panel details. Omar responds, “Caroline approved a sequence where she reviews the employer and proposed recipients before profile release. For an interview discussion, she also needs planned panel details. Please send names, titles, and meeting format, and I will request her direction.” Omar does not present her boundary as a bargaining tool. He describes a clear process. The client either supplies enough detail or waits for a later search stage.

Compensation conversations need a narrower record than many recruiters expect. Omar records Caroline’s stated timing preference or general expectations for matching work. He should not forward a message about current bonus details, current employer concerns, or private relationship history unless Caroline approves every disclosure. If a client needs a range for internal planning, Omar asks Caroline how she wants expectations presented. “Share my target range after we discuss role scope” gives different permission from “share my expectations now.”

Consent needs an expiration point. Permission given during a Tuesday call should not sit in a file for months and travel to a changed client group. Omar records employer, content, named recipients, intended purpose, approval date, and expiration date. He notes whether approval covers an introduction only or an interview invitation. On expiry, he asks again before release.

Consider a fictional Friday change. Omar receives a note saying an outside adviser will join Caroline’s proposed panel. Earlier consent covered Dana and Priya, not an adviser. Omar pauses. He sends Caroline, “The client added Morgan Chen, an outside adviser, to the proposed panel. Meeting format stays virtual and requested time remains Wednesday at 10 a.m. Do you approve an introduction with Morgan included?” Silence does not equal approval. An earlier response does not cover Morgan.

At 4 p.m., Caroline replies, “Please share my résumé with Dana and Priya. Hold Morgan until I know why Morgan will attend.” Omar records her exact direction and sends a message only to Dana and Priya. He does not include Morgan in copied recipients. He asks Dana for Morgan’s role in the meeting and whether Morgan needs profile access before an introduction. Dana replies Monday morning: Morgan will advise on operating model discussion but does not need advance materials. Omar returns to Caroline with this limited explanation and asks whether she approves Morgan’s attendance.

Busy searches create accidental drift. Before every profile release, Omar compares intended recipients with Caroline’s permission note. Before every calendar request, he checks panel names and meeting format against her conditions. If an assistant prepares an email, Omar provides only approved details and reviews recipient fields before sending. These checks take little time and reduce memory based errors.

For practice, use a fictional candidate named Mara and a fictional employer named Cedar Lane Group. Write a consent note for her résumé, a two person recipient list, and permission ending next Friday at 5 p.m. On Thursday, let Cedar Lane add a third recipient. Write Mara a new approval question naming the employer, third person’s title, document, and Friday interview time. Save her response beside the original note, check recipients against both notes, then send only the approved introduction.