Incomplete AI screening interview? A recruiter recovery checklist

You open an interview report and find that some answers are missing. The hiring manager needs a shortlist, but you don't yet know whether the candidate stopped, lost their connection or completed an interview whose evidence is still being processed.

An incomplete AI screening interview needs a recovery decision before it can support a hiring decision. Start by checking what was saved, what information is missing and what the candidate experienced.

Skill Society's AI screening interviews page identifies three completion states: complete, partial and incomplete. Its assessment guidance asks hiring teams to check completion and investigate missing information before using a report to support a decision. A status gives you a starting point; it doesn't establish why the interview ended.

This checklist helps recruiters and hiring managers resolve the gap, coordinate candidate contact and record the next step. Candidates will also find guidance on what to tell the hiring team when an interview is interrupted.

Plan the exception as well as the interview. Book a demo to walk through Skill Society's interview evidence and your team's review process.

What should you verify before sending another invitation?

Official product guidance illustrates two important checks:

• Completion and evidence need checking together. Skill Society describes complete, partial and incomplete interviews alongside recordings, transcripts and evaluations. Inspect the material actually available for this application rather than assuming every attempt produced a full report.
• Recovery depends on where the interruption happened. HireVue's disconnection guidance distinguishes a connection loss between questions from one during an answer. It also directs candidates to the hiring company when a retake may be needed.

The HireVue example describes that platform's behaviour. It isn't a promise that another system resumes at the same point or restores an interrupted answer. Before telling someone to restart, confirm the supported recovery path for their interview.

What does an incomplete interview tell you?

It tells you to investigate the available evidence and the workflow. It does not, by itself, tell you whether the person meets the role requirements or wants to continue.

Keep these questions separate:

1. What happened to the interview attempt?
2. What can the hiring team assess from the answers it has?
3. What additional information or action is needed?

A candidate may report a technical problem, need more time, request another way to participate or confirm that they have withdrawn. If you haven't established the reason, record it as unknown.

The following categories can help organise your investigation. They are suggested working notes, not definitions of Skill Society's product statuses.

What you know	Next check and owner
The candidate hasn't started	Recruiter: check invitation delivery, access, deadline and continued interest.
Some answers are available	Recruiter, with support if needed: identify usable answers and where the attempt stopped.
The candidate says they finished but the report is missing	Support or workflow owner: check submission and processing before asking them to repeat work.
Audio or transcript content is missing or unclear	Reviewer and support: check access to the original evidence and identify what remains unusable.
The candidate reports a participation barrier	Named candidate contact: discuss what support or alternative process your team can arrange.
The candidate confirms withdrawal	Recruiter: confirm which application they are withdrawing and which outstanding tasks should end.

A five-step recovery checklist

1. Inspect the application before changing it

Confirm the role, candidate, interview attempt and recorded status. Check any available recording, transcript, question-level answers and recent activity. Note whether processing is still underway or whether the status is uncertain.

Preserve the original evidence and the history of the attempt. Avoid overwriting a record or creating a new invitation simply to make the dashboard look complete.

For example, “Recording available for questions one and two; no answer visible for question three; cause not confirmed” is more useful than “candidate failed interview”.

2. Identify the missing role evidence

Map the available answers to the role requirements. State which requirement remains unassessed and why. An unanswered question should remain an evidence gap rather than quietly becoming a negative judgement about the candidate.

If a summary or overall evaluation is available, check whether it addresses only part of the interview. Don't compare it with completed interviews as though each contains the same evidence.

Our human-in-the-loop screening playbook explains how to keep requirements and source material central to review. Use the same approach when only part of the material is available.

3. Contact the candidate with a specific question

Describe what your team can see and ask what happened. Keep the tone neutral. A useful first contact names the role, explains the gap and provides a person to reply to.

Ask for the approximate time and any error message if they encountered a technical problem. You may also need the device and browser to help support investigate. Don't ask the candidate to reconstruct information your team already has.

Confirm whether they still want to continue and whether the original deadline remains practical. If they need a different way to participate, route that request to the person who can discuss the options. See our guide to accessibility before assessment for planning a clear support route.

4. Agree a supported recovery step

Choose the next action after checking the evidence and your process. Possible routes include:

• Waiting for a submitted interview to finish processing, with a named owner checking it.
• Helping the candidate regain access through the platform's documented support process.
• Arranging an approved retake or extension when appropriate.
• Holding a focused follow-up conversation to collect missing evidence, where your assessment process permits it.
• Recording the candidate's confirmed withdrawal.

Verify which options the platform and your team can actually provide. Don't promise automatic resumption, recovered audio or unlimited retries without checking.

Keep the role requirements and review standards clear when using a different format. Explain what the candidate needs to do, what happens to the earlier attempt and when they will next hear from you. Apply the same recovery principles to comparable situations and document the reason for exceptions.

5. Review the recovered evidence and close the loop

After the agreed step, confirm what arrived. Link the new evidence to the earlier attempt through your approved record-keeping process. Ask the reviewer to assess the relevant requirements and record any remaining uncertainty.

Update the workflow and the candidate separately: a changed status does not necessarily mean a message was sent. Check for outdated reminders before another contact goes out.

If nothing arrives by the agreed review date, follow your documented follow-up process. Record the evidence available and the decision owner's next action. Silence does not establish the technical cause or prove that the person chose to withdraw.

A candidate message you can adapt

Use this only after checking what is actually available. Replace the placeholders and make the next update date realistic.

Hello [Name], we're reviewing your interview for [Role]. We can see [the answers or status available], but we're missing [specific part]. Did you encounter a problem, or do you need help with the next step? Please let me know whether you'd like to continue. I'll confirm the appropriate recovery option and update you by [date]. If another way to take part would help, we can discuss the available options. Thank you, [Recruiter and contact details].

If the candidate says they completed everything, acknowledge that before asking them to repeat anything. Check the submission with support and give them a next update while you investigate.

Use the candidate follow-up guide to agree who owns that update when more than one recruiter is involved.

Example: two saved answers and one missing requirement

Consider this illustrative customer-service hiring scenario, not a customer result.

A candidate has answered two questions about handling enquiries. Their third answer, about escalating a complaint, is unavailable. The candidate reports that the connection dropped during that answer.

The recruiter checks the saved material and records that escalation judgement remains unassessed. Support confirms what can be recovered. Under the team's agreed assessment process, the hiring manager arranges a focused conversation covering the missing requirement and tells the candidate what to expect.

The reviewer then considers the original answers and the follow-up evidence against the role criteria. The record explains the interruption, the additional step and the decision. It doesn't treat the missing recording as an answer the candidate gave.

Why can an incomplete interview remain unresolved?

The status becomes a substitute for investigation

A label is quick to scan, but it may leave the reason unclear. Assign someone to inspect the evidence and record the next action.

Reminders continue without new information

Another reminder won't resolve a broken link, unclear deadline or inaccessible format. Check the contact history and address the reported problem before adding more messages.

Technical support and hiring decisions have different owners

Support can investigate the attempt; the hiring team needs to decide how to collect the evidence it requires. Make the handoff explicit so the candidate isn't left moving between the two.

The useful outcome is a clear next step, an owner and an update date for every unresolved attempt.

What should you track across repeated cases?

Keep a small exception log in your approved hiring system. Record the role, invitation date, observed completion state, candidate-reported issue, recovery action and eventual review outcome. Separate the candidate's explanation from a technical cause confirmed by support.

Count unique applications as well as attempts. One person who retries twice should not be counted as three different candidates. When reporting a completion rate, count each application with a completed interview only once. Define the denominator, the observation date and whether late completions are included. For the same group of applications, dividing that completed-application count by all applications invited to interview answers a different question from dividing it by applications whose interview was started.

Use the log to investigate patterns: a confusing invitation, an unrealistic window or a recurring access problem. Treat those patterns as questions to check, not proof of the cause. This is a suggested operational log, not a claim that Skill Society automatically produces every measure described here.

How Skill Society supports the review

Skill Society's AI screening interviews collect audio answers to role-specific questions on mobile or desktop. The workflow includes a microphone check and configurable interview windows. Hiring teams can track completion states and review available recordings, transcripts and evaluations.

Use that evidence to identify what still needs attention. The assessments page describes reports as a starting point for human review: your team investigates missing or uncertain information and decides whether further interviews or checks are needed. Confirm the recovery options for your account and interview setup before promising a candidate a particular route.

Give your team a clear review process. Book a demo and include an incomplete interview in the workflow you discuss.

FAQ

Q: Should an incomplete AI screening interview trigger rejection?

A: First establish what happened and what evidence is available. Resolve the gap through your assessment and follow-up process, with a named person responsible for the decision.

Q: Can candidates restart from where they stopped?

A: That depends on the platform, the interview setup and the point of interruption. Check the documented recovery route before asking them to reopen or restart the interview.

Q: Can we use the answers that were saved?

A: Review usable answers against the requirements they address. Record the missing evidence separately and decide what follow-up is needed before making a broader judgement.

Q: How long should we wait for a candidate to respond?

A: Use your communicated deadline and follow-up policy, taking account of a reported issue or agreed extension. Give the candidate a clear next update rather than leaving the application indefinitely unresolved.

Q: What should a candidate report after an interrupted interview?

A: Tell the named recruiter which role and interview were affected, approximately when it stopped, and any error shown. Follow the platform's support instructions and ask the hiring team to confirm the next step.

Ready to resolve the next incomplete interview?

Check one unresolved application, write down the missing evidence and assign the next contact. Then book a demo to explore how Skill Society fits your team's screening and review process.

Sources

• Skill Society: AI screening interviews
• Skill Society: Assessments
• HireVue Candidate Help Center: Disconnected During the Interview

Sources checked on 12 October 2026. The checklist, message and scenario are practical examples to adapt to your process, not measured customer outcomes.