Executive Search Interview Scheduling: A Privacy-First Agency Runbook

Run confidential interview scheduling in eight steps

Use this workflow for an agency-led confidential search involving one candidate, an external hiring manager, two required panelists, and one optional adviser across Google and Microsoft. Decide the disclosure boundary before the first availability request.

1. 1

   Classify the search and appoint disclosure owners

   Record the search owner, client owner, candidate owner, confidentiality class, approved participant groups, and the person who can widen disclosure. Decide whether the candidate name, client name, role title, incumbent status, location, compensation context, and panel membership can appear in outreach, calendar events, or neither.
   • Every disclosure field has an owner and approved audience.
   • The recruiter can pause the workflow when a new participant changes the boundary.
   • Sensitive search notes never enter the general scheduling record.
2. 2

   Create a minimal scheduling identity

   Link the scheduling record to the ATS or protected search system with an opaque search ID. Use approved display labels such as ‘candidate conversation’ or a recruiter-managed alias only when they match the firm’s policy. Store stage, duration, format, date window, scheduling deadline, and time zone without copying evaluation notes, source details, or reasons for confidentiality.
   • The record contains enough information to coordinate and no hidden copy of the search file.
   • Aliases map to real identities only inside an access-controlled service.
   • The candidate and client can still identify legitimate outreach.
3. 3

   Lock required roles and approved substitutes

   List the candidate, recruiter, hiring decision-maker, required interview roles, optional advisers, and any client-approved substitutes. Keep the full panel hidden from participants who do not need it until the disclosure owner approves. A role substitution changes the scheduling revision and may change who can see the event.
   • Required and optional participation are distinct.
   • No slot is proposed without the candidate and all required roles.
   • A substitute is used only inside written client authority.
4. 4

   Collect bounded candidate availability

   Ask for windows inside the agreed date range, in the candidate’s local time, through the approved channel. Explain the meeting duration, format, response deadline, and the limited use of the answer. Do not ask for a full personal calendar or for the candidate to expose current-employer meetings.
   • Calendar connection is optional for the candidate.
   • Ambiguous dates or time zones receive one narrow clarification.
   • The candidate can decline, correct availability, or request recruiter contact.
5. 5

   Read client free/busy at the narrowest useful level

   Use approved Google or Microsoft availability operations for connected client participants. Normalize busy intervals, source, retrieval time, time zone, and errors. Keep event subjects, locations, descriptions, and unrelated attendee lists out of the search. For an unconnected panelist, request bounded windows under the same disclosure policy.
   • Provider failure is missing evidence, not an open calendar.
   • The scheduling service requests only the permission needed for availability or the approved write.
   • A participant’s private event reason never becomes a recruiter note.
6. 6

   Generate proposals inside the disclosure boundary

   Intersect the candidate with every required role. Score remaining slots for optional attendance, working hours, notice, buffers, time-zone fairness, and the deadline. Show the recruiter and client owner the exact people and evidence freshness. Show each participant only the information needed to respond or attend.
   • Do not expose vote grids or other participants’ unavailable times.
   • No-overlap returns the smallest role, duration, date, or substitute decision that could help.
   • A changed required participant invalidates prior proposals and approval.
7. 7

   Approve wording, recipients, and the booking together

   Bind approval to the current scheduling revision, exact recipient list, event title, description, conferencing details, organizer calendar, and selected slot. Re-check current required availability, write one canonical event, and verify invitations. If the candidate and panel need different context, send approved participant-specific messages without creating conflicting calendar records.
   • A repeated command cannot send another invitation or create a second event.
   • The final calendar fields match the approved disclosure template.
   • An uncertain provider write enters reconciliation before retry.
8. 8

   Close or retain records by declared purpose

   On booking, cancellation, withdrawal, or search close, record the outcome and apply the firm’s retention schedule to messages, availability evidence, aliases, logs, and event links. Keep the ATS process record separate from operational scheduling traces. Review access and exports for the small group that actually needs them.
   • Retention is defined before collection begins.
   • A participant correction updates active evidence and the authoritative record.
   • Audit data proves access and action without copying sensitive message content into every log.

Compare confidential scheduling by finished work and exposure

Privacy is not only a settings page. It is the amount of search information copied into every step while candidate, agency, and client calendars are being coordinated.