Multi-Interviewer Scheduling: Build Panel Quorum and Substitute Rules

Build panel quorum and substitution in eight steps

Use one agency-led client panel: one candidate, one hiring manager, one technical bar-raiser role, one cross-functional role, two approved substitutes, and one optional executive observer. The candidate uses Google, the client spans Microsoft and Google, and one substitute will not connect a calendar.

1. 1

   Write the interview outcome and decision quorum

   Name the interview stage, purpose, duration, date window, scheduling deadline, candidate time zone, format, decision owner, and the minimum roles that make the panel valid. Quorum is a rule about decision coverage, not the number of names somebody copied into the ATS.
   • The candidate and every required role are explicit.
   • The meeting cannot proceed by quietly dropping a role to find more slots.
   • The decision owner can explain why each required role is required.
2. 2

   Separate required roles, named people, and optional observers

   Create rows for role, required status, primary interviewer, approved substitutes, optional observers, notes recipients, company, provider, time zone, and approval owner. People receiving an update or scorecard do not automatically join the scheduling quorum. Optional attendance can improve a slot without blocking it.
   • Required versus optional status is visible before availability collection.
   • A named interviewer and the competency or decision role they cover are different fields.
   • Candidate-facing disclosure follows the agency and client privacy policy.
3. 3

   Define substitution authority before the first conflict

   For each required role, record who may approve a substitute, which people are eligible, whether candidate notice is needed, what disclosure changes, and whether prior approval or proposals remain valid. A substitution is a panel revision, not an informal calendar shortcut.
   • The recruiter cannot invent a substitute after seeing a convenient slot.
   • A changed person triggers a fresh privacy, availability, and approval check.
   • The candidate receives updated context when policy requires it.
4. 4

   Collect candidate availability once, in local time

   Ask for bounded windows inside the interview date range, plus hard constraints, notice needs, and the response deadline. Calendar connection is optional. Explain the duration, format, disclosed purpose, and how the response will be used. Do not ask the candidate to expose a full personal or current-employer calendar.
   • Ambiguous dates or zones receive one narrow clarification.
   • A correction supersedes old windows and invalidates affected proposals.
   • The candidate can decline, opt out, or ask the recruiter to take over.
5. 5

   Resolve client availability by role

   Read approved Google and Microsoft free/busy for connected interviewers. Request bounded windows from anyone unconnected. Normalize source, retrieval or reply time, zone, consent, freshness, and provider errors. For each required role, create availability as the union of its eligible approved interviewers, then preserve the exact person behind every candidate slot.
   • Provider failure is missing evidence, not open time.
   • A substitute’s availability counts only while their eligibility is current.
   • Private event titles, descriptions, and unrelated attendees stay out of the search record.
6. 6

   Find slots that satisfy role quorum

   Intersect the candidate with the hiring manager and every required role. Rank survivors for primary-interviewer attendance, optional observer coverage, working hours, time-zone fairness, buffers, notice, and the interview deadline. Store the exact role-to-person assignment and evidence versions behind each proposal.
   • A slot never shows as valid when one required competency or decision role is missing.
   • The client sees who will attend before approving the proposal.
   • No-overlap names the smallest role, substitute, duration, or date decision that could help.
7. 7

   Approve the panel assignment and invitation together

   Bind approval to the candidate, stage, meeting revision, selected slot, role-to-person assignment, optional-attendee decision, organizer calendar, and event wording. Re-check fresh required availability before one idempotent event write. If a person changes, the panel returns to approval rather than inheriting the old decision.
   • Repeated booking commands cannot create duplicate candidate invitations.
   • The final event includes the approved required people and only approved optional people.
   • An uncertain provider response enters reconciliation before retry.
8. 8

   Recover the smallest broken role

   When an interviewer declines or becomes busy, preserve the candidate window, stage, disclosure, and unaffected role assignments. Re-open only the broken role and its approved substitutes. Re-check the resulting panel, obtain any required approval, update one canonical event, and verify every invitation.
   • The workflow does not restart a full candidate poll for one client-side change.
   • Every wait and exception has a deadline, owner, and next action.
   • The recruiter receives one decision instead of reply-all archaeology.

Compare panel scheduling by whether role quorum survives

The test is not whether a candidate can pick a time. It is whether the right decision roles, privacy rules, and approvals survive cross-company calendars and last-minute change.