Interview scheduling automation: a practical agency workflow

Begin with an authorised interview request

Scheduling should only start after a consultant has decided a candidate is progressing to interview and the client has agreed. The automation arranges the time; it does not decide who gets an interview.

Make the trigger explicit, for example a consultant changing the candidate's status in your ATS to interview requested, with the client, role and interview format recorded.

Availability, confirmation and rescheduling rules

Agree the rules before building anything. Whose calendar is the source of availability: the client's, the consultant's or both? How long is each interview, and is there a buffer between them? How much notice is needed?

Calendar tools can handle much of this. Google Calendar appointment schedules (opens in a new tab), for example, let you set availability, appointment length, time zone, booking lead times and buffers, check calendars to avoid conflicts, and send confirmations and reminders. Some features need an eligible subscription, and other calendar tools work differently.

• How many time options a candidate is offered, and how long they stay open
• What happens if nobody picks a time: a reminder, then a task for the consultant
• Who can reschedule, and how much notice is required
• Whether reschedules go back through the client for approval

Time zones and changes by either party

Candidates relocating, clients with offices in different states and video interviews all introduce time zones. Store every interview with its time zone, show each person the time in their own zone, and include the zone in every confirmation.

Either party may need to change the time. Design for both. If the client cancels, the candidate is told promptly and offered new times. If the candidate cancels, the client is told and the consultant is alerted. Google Calendar's help (opens in a new tab) notes that cancelling a booked appointment emails the person who booked and frees the time, that deleting an appointment schedule does not cancel appointments already booked, and that someone with a forwarded confirmation email can cancel. Check how your own tools behave, because those details affect who can change what.

An example workflow

The steps below show one way to organise scheduling. They are illustrative; adjust them to your tools and clients.

Keep progression decisions separate

The workflow ends when the interview has taken place and the consultant has been prompted for feedback. Whether the candidate progresses, receives an offer or is told they were unsuccessful is a decision for people, communicated by people.

Avoid automating outcome messages based on interview attendance or feedback fields. A candidate who missed an interview because of an emergency deserves a conversation, not an automated rejection.

Protect candidate information

Scheduling only needs names, contact details, times and joining links. Do not pass CVs, notes or assessment information into calendar invitations or scheduling tools. The OAIC explains (opens in a new tab) that the employee records exemption does not cover unsuccessful applicants, so candidate information may well be covered by privacy law.

Testing checklist

Run through each scenario before relying on the workflow.

• Scheduling starts only from an authorised status change
• Offered times respect availability, buffers and notice periods
• Times show correctly for a candidate in another time zone, including around daylight saving changes
• Confirmations reach the candidate, client and consultant with the right details
• Cancellations and reschedules by either party notify everyone and update the ATS
• No candidate picks a time: reminders are sent, then the consultant gets a task
• Calendar invitations contain no CV or assessment details
• After the interview, the consultant is prompted for feedback and no outcome message is sent automatically

Measure whether it helps

Record a baseline before switching the workflow on, then compare after a few weeks.

• Messages or calls needed to arrange each interview
• Time from interview request to confirmed time
• Reschedules and no-shows
• Consultant time spent on scheduling each week

Ask candidates and client contacts for informal feedback too. A workflow that saves consultants time but confuses candidates needs adjusting.

Next steps

Most scheduling workflows depend on your ATS or CRM. Before connecting anything, read what to ask before automating your recruitment ATS or CRM. When you are ready, discuss your scheduling workflow with a recruitment automation specialist or see how the free consultation works.