Candidate Interview Scheduling Software: An Agency Handoff Runbook

Run the agency-to-client handoff in eight steps

Use this workflow for the first client interview after the agency has qualified the candidate. It is deliberately narrower than a full interview-day build and earlier than a broken-panel reschedule. The job is to preserve candidate momentum across the agency-client boundary.

1. 1

   Open the interview record at candidate yes

   Create one record with search ID, candidate, client, role, interview stage, purpose, duration, format, target date window, scheduling deadline, candidate time zone, recruiter owner, client owner, and the source-of-truth ATS identifiers. Keep scheduling state linked to the ATS rather than hiding it inside a recruiter’s inbox.
   • The scheduling deadline is explicit before outreach begins.
   • Candidate contact authority and preferred channel are recorded.
   • Private candidate and client context stays out of calendar titles and shared notes.
2. 2

   Lock the client’s required roles before collecting times

   Ask the client to name the hiring manager, required interview roles, optional observers, approved substitutes, duration, format, and decision deadline. A role is not always a named person. Recording an approved substitute lets the workflow recover when a technical lead declines without restarting the entire handoff.
   • Required and optional participants are separate.
   • A missing required role blocks proposal generation.
   • A substitute can be used only inside client-approved policy.
3. 3

   Protect the candidate window first

   Collect a bounded set of candidate windows in the candidate’s local time, plus blackout periods, notice needs, and any disclosed decision deadline. Do not ask the candidate to expose a full personal calendar. Record whether availability came from connected free/busy or an explicit response, and attach a freshness time.
   • The candidate sees duration, format, client, and response deadline.
   • An ambiguous zone or date receives one narrow clarification.
   • A changed candidate deadline becomes a visible priority signal, not buried thread text.
4. 4

   Collect client-side evidence across calendar systems

   Read approved Google or Microsoft free/busy for client participants who connect calendars. Request bounded availability from anyone the workflow cannot read. Normalize both paths into participant intervals with role, source, time zone, retrieval or response time, and error state. Calendar connection is encouraged, not mandatory.
   • Event titles and private reasons never enter the shared interview record.
   • No provider response is missing evidence, not an open calendar.
   • Client silence from a required role escalates to the named client owner.
5. 5

   Find overlap against the candidate and required roles

   Intersect the candidate with every required interviewer or approved role substitution. Score surviving times for optional attendance, notice, working hours, time-zone fairness, interviewer buffers, and the scheduling deadline. Keep the evidence behind every proposal so the recruiter can explain a tradeoff without forwarding raw calendars.
   • Never present a slot that excludes the candidate or a required role.
   • Show optional absences and substitutions before booking.
   • A no-overlap result names the smallest date, role, duration, or substitute decision that can move the search.
6. 6

   Route exceptions to the person who can decide

   Send candidate-window changes to the recruiter, interviewer substitutions to the client owner, deadline conflicts to both, and sensitive relationship issues to a human-owned lane. The scheduler should not ask the candidate to solve internal client staffing. It should not ask the client to interpret candidate privacy context.
   • Every exception has one owner and one requested decision.
   • Reminder caps prevent the candidate from receiving repeated automated pressure.
   • A recruiter can pause or reclaim the workflow at any point.
7. 7

   Commit one interview and update both sides

   Bind approval to the interview record revision, exact candidate, required roles, selected people, time, format, and organizer calendar. Re-check current required availability, create one canonical event, and verify candidate and interviewer invitations. Return the confirmed result to the recruiter and client owner, then write the booking reference back to the ATS where supported.
   • A retry cannot create another event or send duplicate invitations.
   • The candidate receives one clear local time and joining location.
   • The ATS link, calendar event, and coordination record agree on the interview identity.
8. 8

   Measure handoff health without grading the candidate

   Track time from candidate yes to coordination start, time waiting on candidate, time waiting on client, clarification count, calendar-source failures, substitutions, reschedules, and final status. Use the data to repair the agency-client process. Do not turn response speed or calendar constraints into a hidden candidate-quality score.
   • Separate candidate wait from client wait.
   • Review repeated client-side blockers during search check-ins.
   • Keep recruiter judgment, candidate care, and client relationships human-owned.

Compare candidate interview scheduling by handoff completion

The agency needs more than a place to store the interview. It needs a coordination path that crosses the client boundary without making the candidate the dispatcher.