Recruiting Agency Interview Scheduling: Candidate Holds and Expiry

Control candidate windows and holds in eight steps

Use one agency-led client interview with a candidate, hiring manager, two required interviewers, and one optional observer. The candidate shares bounded windows without connecting a calendar. The client spans Google and Microsoft. One interviewer answers late, and one proposed slot becomes stale before approval.

1. 1

   Open one interview coordination record

   Store search ID, candidate, client, role, interview stage, purpose, duration, format, bounded date window, scheduling deadline, candidate time zone, required and optional roles, approved substitutes, agency owner, client owner, privacy rule, outreach consent, approval mode, and ATS references. Define completion as one verified invitation or a bounded terminal decision.
   • The stage and required panel are explicit before availability collection.
   • Candidate contact authority and approved channel are recorded.
   • An ATS status, proposed time, or tentative hold does not count as a booked interview.
2. 2

   Define the four scheduling states

   Keep availability window, slot proposal, tentative hold, and confirmed interview separate. A window says a participant reported or appeared free. A proposal is derived overlap. A hold reserves a slot under declared policy. Only a confirmed interview has final approval, one canonical event, and verified invitations.
   • Every surface labels tentative and confirmed state clearly.
   • A hold cannot inherit confirmation language by accident.
   • State transitions have an owner, timestamp, meeting revision, and reason.
3. 3

   Collect candidate windows with an explicit expiry

   Ask for bounded windows in the candidate’s local time, plus notice needs, blackout periods, preferred channel, and how long the response should be treated as current. Explain the client, stage, duration, format, disclosed purpose, and response use. Calendar connection is optional; do not ask for a full personal or current-employer calendar.
   • Ambiguous date or zone language receives one narrow clarification.
   • A candidate correction supersedes old windows and invalidates affected proposals.
   • The candidate can decline, withdraw a window, or ask the recruiter to take over.
4. 4

   Resolve the external panel against current evidence

   Read approved Google and Microsoft free/busy for connected hiring-team calendars. Request bounded windows from anyone unconnected. Normalize participant role, source, retrieval or reply time, IANA zone, consent, freshness, and provider error. Intersect the candidate with every required role and score optional attendance only after quorum passes.
   • Missing provider access is not interpreted as an open client calendar.
   • An optional observer can improve a proposal without blocking it.
   • Private event titles, other searches, and unrelated attendees stay out of the record.
5. 5

   Create a hold ledger before placing calendar holds

   For each proposed hold, record proposal ID, exact slot, participants covered, evidence versions, candidate disclosure, client approver, hold owner, expiry, release rule, and whether a tentative provider event is authorized. If calendar holds are not approved, keep the reservation in the coordination record and label collision risk instead of writing hidden events.
   • One candidate window cannot become several unexplained holds across the same search.
   • A hold expiry is visible to agency and client owners.
   • Tentative event titles disclose no more search or candidate data than policy allows.
6. 6

   Approve or release before evidence goes stale

   Route the client one decision package: required role coverage, exact interviewer assignment, optional attendance, candidate window status, calendar freshness, hold expiry, and the smallest exception. On approval, re-check required evidence. On rejection, required decline, or expiry, release the hold and preserve unaffected candidate windows for the next proposal.
   • The candidate is not asked to solve an internal client staffing decision.
   • Approval binds to the current panel, slot, meeting revision, and disclosure.
   • Expired holds cannot be revived without fresh evidence and any required candidate confirmation.
7. 7

   Commit one confirmed interview

   Use one booking idempotency key tied to the approved proposal and revision. Re-check candidate and required interviewer evidence, write one canonical event, persist provider correlation and event identifiers, send invitations, and read the event back. Reconcile an uncertain provider timeout before repeating any write.
   • The final event includes the candidate and every approved required interviewer.
   • Repeated commands return the original result instead of another invitation.
   • Every unused tentative hold is released or closed according to policy.
8. 8

   Recover expiry without restarting the search

   When a candidate window, client calendar, approval, or hold expires, identify the smallest broken evidence set. Keep the stage, panel roles, privacy boundary, consent, and unaffected windows. Request only the needed update, rebuild proposals, and return one bounded decision to the recruiter or client owner. Trace every wait, reminder, expiry, release, booking attempt, and final invitation.
   • The candidate does not receive another broad availability request when one answer will do.
   • Every exception has one owner, deadline, and safe next action.
   • Recruiters can reconstruct the state without reply-all archaeology.

Compare interview scheduling by hold ownership

The useful agency workflow tells every party which availability is current, which slot is tentative, when it expires, who must decide, and what proves the interview is booked.