Published November 8, 2026.
A missed interview is not a single event. It is a signal about the candidate, the reminder process, the scheduling tool, or the hiring manager's calendar. A recovery sequence should find out which one before the team writes off the candidate or blames the assistant. The sequence also protects the interviewer's time, because a second missed slot costs the business twice.
Confirm the no-show before reacting
Wait for the agreed grace period before marking a candidate as a no-show. The grace period should be written in the scheduling policy and should match the hiring manager's expectation. Check the interview link, the calendar invite, and the candidate's last message before concluding that nobody attended. A technical failure can look exactly like a no-show. Record the time the interviewer joined, the time the candidate joined if at all, and the time the session was closed. If the interviewer was late, the candidate may have left before the session started. The record should show both sides, not only the candidate's absence. Ask the interviewer for a one-line note before the assistant sends anything to the candidate. A message that accuses a candidate who was actually waiting in the wrong lobby damages the relationship. The confirmation step is short and prevents an avoidable apology.
Send a neutral first message
The first message should be neutral and should offer a way back into the process. Use language such as we missed you at the scheduled time and ask whether the candidate would like to rebook. Do not use a subject line that sounds like a rejection. Include the original time and the time zone so the candidate can see what the team expected.
Give the candidate two concrete options rather than an open request to reply. Offer one slot within the next two business days and one later slot. If the candidate cannot make either, ask for a window that works. A message with no options creates another round of scheduling and another chance to lose the candidate. Record the message, the channel, and the time it was sent. If the candidate replies with a reason, record it in the candidate record, not only in the assistant's inbox. The reason is the evidence the team needs to fix the reminder or the scheduling path.
Escalate a pattern, not a single miss
One no-show may be a traffic problem or a family emergency. Two no-shows from the same candidate need a supervisor decision about whether to continue. Three no-shows across a role may point to a reminder that never arrives or a time zone that is recorded incorrectly. The assistant should be able to see the pattern without searching three systems.
Set a rule for when the assistant may rebook and when a supervisor must approve. A first rebook within the same role is usually safe. A second rebook, a request to change the interviewer, or a candidate who asks for a different location should go to the supervisor. Write the rule in the same page as the escalation path. Do not close a candidate record as unresponsive until the messages have been sent through the agreed channels and the waiting period has passed. A record closed too early hides the candidate from the next recruiter and loses a possible hire.
Protect the hiring manager's calendar
A no-show wastes an interviewer's slot, and the recovery should not waste a second one. Before offering a new time, check the interviewer's calendar and the panel availability. Do not promise a slot that has not been held. If the team uses a scheduling tool, confirm that the hold is visible to everyone who needs it.
Record the cost of the missed slot in the weekly review. A pattern of no-shows on a particular day or time may point to a reminder that is sent too late. The hiring manager should see the pattern, not just the individual case. The fix may be a reminder 24 hours before and a second reminder two hours before. If the interviewer cancels, the same recovery sequence applies in reverse. The candidate should receive a prompt apology and a new time. A team that only tracks candidate no-shows misses half of the reliability problem.
Learn from the reason without judging the person
Collect the reasons in a small set of categories: forgot, could not join, technical issue, changed mind, accepted another offer, or unknown. Do not force a reason when the candidate does not give one. The categories are for process improvement, not for a scorecard on the candidate. Review the reasons monthly and choose one change. A cluster of technical issues may need a different meeting platform or a test link. A cluster of forgotten interviews may need a confirmation step the day before. A cluster of changed minds may need a faster interview loop. Measure the no-show rate again after the change. Share the finding with the hiring managers without naming candidates. The goal is a process that respects both the candidate and the interviewer. A recovery sequence that only sends reminders will not fix a loop that takes three weeks to schedule.
Keep the record clean for the next recruiter
At the end of the sequence, update the candidate record with the outcome and the next action. If the candidate rebooked, link the new interview. If the candidate withdrew, record the reason and close the record. If the candidate is unresponsive, set a date for the next attempt rather than leaving the status open forever.
Do not delete the original interview event. The history shows what happened and helps the team improve. Add a note that explains the recovery rather than overwriting the calendar entry. A future recruiter should be able to see the full story in one place.