October 2, 2026
A missed interview creates an immediate operational question: should the recruiter offer another time, close the application, or investigate a problem with the appointment? Without a shared rule, the answer often depends on who opens the record. One candidate receives three new chances, another is rejected after a broken video link, and a third stays in the pipeline for weeks because nobody owns the decision.
That inconsistency costs more than calendar time. Recruiters repeat judgment calls, hiring managers cannot tell whether an interview slot will be recovered, and candidates receive different treatment for similar events. In high-volume and frontline hiring, even a small number of unresolved no-shows can distort pipeline reports and leave a team planning around applicants who are no longer engaged.
A useful reschedule rule separates a candidate no-show from an employer-caused access failure, gives the recruiter a bounded response, and records enough evidence for a later review. It should not assume why a person missed an appointment or invite recruiters to make medical, family, disability, or other sensitive inquiries. The goal is a reliable hiring process, not a character judgment.
Define what counts as a no-show
Start with the appointment itself. A no-show should mean that the candidate did not join or arrive within a stated grace period and did not contact the approved recruiting channel before that period ended. The grace period should fit the interview type. Ten minutes may be reasonable for a short phone screen, while an onsite hiring event may need a different check-in procedure.
Do not use the label until the recruiter has checked the systems the candidate was told to use. Review the scheduling record, email or text delivery status, video-meeting attendance, reception log, recruiter voicemail, and any shared hiring inbox. Confirm the appointment time and time zone displayed to the candidate. A calendar marked “absent” is not enough if the invitation bounced or listed the wrong location.
Create distinct outcome codes for at least these situations:
- candidate did not attend and made no contact;
- candidate contacted the team before the appointment;
- candidate contacted the team after the appointment;
- employer instructions were incorrect or incomplete;
- technology or facility access failed;
- recruiter or interviewer was unavailable; and
- evidence is incomplete and needs review.
These codes matter because only the first situation is an unexplained no-show. Combining all missed appointments under one label hides defects that the employer controls.
Use one reschedule as the clear default
For many ordinary recruiting workflows, a practical default is to offer one reschedule after the first unexplained no-show. The candidate receives a short response window and a limited set of available times. If the candidate selects a new time, the appointment returns to the active pipeline. If the response window expires, the application closes under the approved disposition.
The default should be written as a sequence rather than “use judgment”:
- Verify the appointment and communication evidence.
- Apply the correct missed-appointment code.
- Send the approved reschedule message through the candidate's stated channel.
- Hold the application for the defined response interval.
- Confirm the new appointment or close the record when the interval expires.
This is not a universal legal or operational prescription. An employer may need different rules for union environments, public-sector hiring, regulated roles, hiring halls, internal applicants, or circumstances covered by an accommodation or other protected process. Qualified legal and human-resources owners should approve the rule for the organization and jurisdictions involved.
The value of a one-reschedule default is consistency. It gives a person one uncomplicated way back into the process without turning every missed appointment into an indefinite negotiation. It also prevents recruiters from quietly applying different standards based on intuition about who seems enthusiastic.
Reset the count when the employer caused the miss
An employer-caused failure should not consume the candidate's reschedule opportunity. If the interviewer did not join, the address was wrong, a security desk lacked the visitor's name, the link failed for everyone, or the invitation displayed conflicting time zones, correct the problem and offer a replacement appointment.
Treat mixed evidence carefully. Suppose the candidate joined eight minutes late because a mobile calendar converted the invitation incorrectly. The recruiter should record the displayed time, compare it with the scheduling configuration, and route the case to the scheduling owner if the cause is unclear. “Candidate was late” erases the information needed to stop the same problem from affecting others.
The same principle applies when the candidate requested an accessible format or accommodation through the approved route. Recruiters do not need diagnostic details. They do need to recognize the request, protect its confidentiality, and follow the organization's approved accommodation process rather than closing the application under a no-show code. The U.S. Equal Employment Opportunity Commission explains that employers generally must provide reasonable accommodation for applicants with disabilities unless doing so would cause undue hardship; its guidance on job applicants and the ADA is a useful starting point for policy owners.
Create a narrow exception route
A default cannot cover every case, but an exception route should be specific enough to prevent favoritism. Define who may approve another reschedule after the default has been used and the reasons that qualify for review. Examples might include a documented employer error, a declared emergency under the employer's approved practice, a protected-process requirement, or a hard-to-fill role where the recruiting leader has authorized a consistent alternative.
The recruiter should submit a small set of facts: appointment history, delivery evidence, candidate contact times, the applicable rule, and the requested action. The approver records the decision and a reason code. Do not collect personal details that are unnecessary to decide the scheduling question.
Avoid an exception such as “strong candidate” or “manager request.” Those labels invite unequal treatment and make the rule impossible to audit. If business conditions justify a different rule for a defined recruiting program, approve that program rule in advance and apply it to everyone in scope.
Set an escalation clock that matches the speed of the funnel. A same-day phone-screen process cannot wait four days for an exception decision. Name a backup approver for weekends, leave, and hiring events. When the clock expires, the system should alert an owner rather than silently closing or advancing the candidate.
Make the candidate message complete
The first message after an unexplained no-show should be factual and easy to act on. It can state that the team was unable to connect at the scheduled time, offer the available rescheduling route, give the response deadline, and identify a contact for access problems. It should not accuse the candidate of being unreliable or ask for private details.
For example:
We were unable to connect for your interview scheduled for Tuesday at 2:00 p.m. Central Time. If you would like to reschedule, please choose one of the available times at the link below by Thursday at 5:00 p.m. Central Time. If you had trouble with the link or need another way to schedule, reply to this message or call the recruiting number in your invitation.
When a candidate reschedules, send a fresh confirmation that includes the date, time, time zone, format, address or tested link, expected duration, interviewer or check-in contact, and the route for requesting an adjustment. Do not rely on the candidate finding the old invitation and mentally replacing one detail.
If the response period expires, send a closure message when the organization's approved process calls for one. State what happened procedurally and whether the person may apply to future openings. Avoid language that makes an unsupported judgment about dependability or job performance.
Keep the ATS record useful
The record should let another recruiter reconstruct the decision without reading private message threads. Useful fields include:
- scheduled date, time, time zone, and interview format;
- invitation and reminder delivery results;
- check-in or attendance evidence;
- candidate contact timestamp and channel;
- missed-appointment outcome code;
- reschedule offered date and response deadline;
- exception reviewer and approved reason code;
- new appointment or final disposition; and
- candidate notification delivery result.
Use role-based access for sensitive communications and follow the organization's retention rules. A free-text field should not become a place for speculation such as “probably not serious” or unnecessary descriptions of a candidate's health or family situation. Record observable events and approved decisions.
Automation can help with reminders, deadlines, and status changes, but it needs safeguards. A delivery failure should create a task rather than start the closure clock. A new message from the candidate should pause an automated close until a recruiter reviews it. A changed appointment should cancel old reminders. Test these paths with nonproduction records before relying on them.
Review no-shows as a process signal
Count no-shows by appointment type, scheduling channel, location, shift, recruiter, lead time, and reminder-delivery outcome where that analysis is lawful and useful. The purpose is to locate friction, not to rank individual candidates.
A rising rate after a new scheduling tool launches may indicate confusing time-zone handling. More missed onsite interviews at one building may point to parking or check-in instructions. A high rate for appointments scheduled far in advance may support offering closer dates or a reconfirmation step. If many candidates reply only after closure, the response window or contact channel may be unrealistic.
Pair the no-show rate with operational measures: percentage of invitations successfully delivered, percentage of cases coded within one business day, reschedule acceptance rate, attendance at second appointments, employer-caused miss rate, exception decision time, and records closed without evidence. Review a sample of cases, because a tidy dashboard can still rest on inconsistent coding.
Do not use attendance at a recruiting appointment as a shortcut for predicting turnover. The missed interview tells the team what occurred at one point in the process. It does not establish why it happened or how the person would perform if hired.
Run a short implementation test
Before applying the rule broadly, test it with one recruiting team or appointment type. Give recruiters a one-page decision tree and message set. Ask them to flag cases where the evidence did not fit a code, where the candidate could not use the rescheduling channel, or where an exception waited without an owner.
At the end of the test, review every employer-caused miss and a sample of candidate-coded no-shows. Confirm that recruiters checked the promised channels, deadlines were calculated correctly, replacement invitations contained complete instructions, and similar cases received similar outcomes. Fix the workflow before training more teams.
A reschedule rule works when it removes guesswork without removing legitimate review. Candidates know whether and how they can reconnect. Recruiters know the next action and deadline. Hiring managers see a pipeline that reflects real decisions instead of abandoned appointments. Most importantly, the organization learns when a “no-show” was actually a failure in its own hiring process.
For a related control after a candidate returns to the pipeline, see Build an Interview Panel Readiness Check. StopHighTurnover helps teams make the everyday hiring and employee experience more consistent, visible, and accountable.