An interview appointment is a small workflow with several owners. Candidate preferences, interviewer calendars, time zones and changes all affect whether it happens. A slot shown as available is only one part of the process.
Define the appointment before offering a time
Agree duration, participants, location or meeting format, and the calendar that owns the appointment. Decide how time zones will be displayed and whether buffers are needed between meetings. These details prevent a technically valid booking from becoming an impractical interview.
Identify which calendars and communication channels are connected for the deployment. Self-service selection, automatic calendar writing and conferencing links should be described according to the configured connections, not assumed from the existence of a scheduling conversation.
Distinguish availability from confirmation
A candidate's stated availability is an input. A proposed slot is a coordination step. A confirmed appointment means the agreed booking process has completed. Keep those states separate in the team view and in candidate messages.
Before sending confirmation, check the participants and the time representation the candidate will receive. If a connected calendar changes while a slot is being selected, the workflow needs a defined response rather than sending an outdated invitation.
Plan for changes and failed handovers
Rescheduling, cancellations and missing replies are normal parts of the journey. Give the candidate a clear way to request a change and show recruiters which appointments need attention. Repeated automated reminders are not a substitute for resolving a calendar or communication failure.
Keep the latest appointment state authoritative. An old link or reminder should not persuade someone that a cancelled slot is still valid. Record whether a new invitation was sent and whether the relevant system accepted the change.
Connect scheduling to the wider process
A completed interview can trigger a request for feedback or another agreed step. It does not by itself prove that feedback is complete or that a hiring decision has been made. Define those handovers with the recruiting team.
Shift coordination and mission deployment also use availability, but they include different readiness and assignment conditions. Use a distinct contingent-workforce process for those decisions rather than treating interview booking as a complete deployment solution.
Follow the appointment state
Illustrative appointment: Tuesday, 10:00 London time, 30 minutes.
Candidate availability received · interviewer unconfirmed
How to read it
The time is a proposal. Sending a final confirmation now could create conflicting expectations.
The next useful action
Resolve the interviewer calendar and booking ownership.
Compare all 3 cases
| Case | Known information | Next action |
|---|---|---|
| Proposed | Candidate availability received · interviewer unconfirmed | Resolve the interviewer calendar and booking ownership. |
| Confirmed | Booking accepted by the configured calendar | Send the agreed confirmation and change instructions. |
| Changed | Interviewer cancels after confirmation | Update the appointment state and route a rescheduling request or exception. |
Illustrative example. These controls explain the method; they do not access client records or execute workforce actions.
Make every message reflect the actual appointment state.
Explore the relevant EVA capabilitiesSources & further reading
This guide explains EVA's approach and illustrative methods. Follow the current offering and methodology pages for scope and examples.