Pre-Flight A/V Checks: Stop Interview No-Shows at T-5

Pre-flight checks are not candidate niceties. They are a control that prevents SLA breaches, avoids unlogged exceptions, and keeps identity gating from failing at the worst moment.

IntegrityLens welcome visual
Pre-flight checks are identity gating for the interview itself. If the camera and mic fail at T-0, the workflow will invent an exception. Your job is to make that exception logged, time-boxed, and policy-bound.
Back to all posts

Real Hiring Problem

Implement pre-flight A/V checks because interview-day failures create unlogged exceptions that break SLAs and weaken identity gating. The high-stakes failure mode is consistent: device permissions, corporate VPN policies, browser updates, or last-minute device switching. The operational damage is not the troubleshooting time. The damage is the reschedule and the workaround. When the workaround becomes "dial in" or "we will count this as a pass," you create three downstream problems you can measure: - SLA drift: time-to-interview and time-to-offer variance increases because reschedules are not evenly distributed. - Evidence gaps: audio/video artifacts are missing or incomplete, so scoring is not evidence-based. - Fraud surface area: proxy interviewers benefit from confusion and channel switching. External indicators suggest this is a material risk in remote hiring: Pindrop reports 1 in 6 remote applicants showed signs of fraud, and Checkr reports 31% of hiring managers have interviewed someone who later turned out to be using a false identity.

  • How many interviews were delayed or repeated due to A/V issues last quarter?

  • How often did reschedules bypass verification steps?

  • Can you prove who approved the exception and what evidence they had?

  • What is the cost of the rework in interviewer hours and cycle-time slip?

WHY LEGACY TOOLS FAIL

Solve pre-flight as a workflow control, not as a support FAQ, because the failure spans multiple systems and owners. ATS and point vendors typically optimize their own step. Pre-flight requires coordination across scheduling, interview access, identity checks, and evidence capture. That coordination is exactly what legacy stacks do not provide. Common failure patterns: - Sequential checks: A/V issues are discovered only when the interview starts, forcing a reschedule waterfall. - No event logs: failures are discussed in chat but never written back to the ATS with timestamps and reason codes. - No unified evidence packs: you cannot reconstruct what happened across tools without manual forensics. - No SLAs: exceptions sit in someone's inbox, and the candidate is the one who experiences the delay. - No rubric discipline: when the session is compromised, teams still score from memory, which increases variance and weakens defensibility.

  • Pre-flight is a gating control that protects a privileged step: live evaluation.

  • Your goal is not fewer tickets. Your goal is fewer unlogged exceptions and less cycle-time variance.

OWNERSHIP & ACCOUNTABILITY MATRIX

Assign ownership explicitly so failures route into a review-bound queue instead of ad hoc troubleshooting. Use this division of responsibility as the baseline: - Recruiting Ops owns the workflow, templates, and SLAs. - Security owns identity gate policy, step-up verification rules, and audit policy. - Hiring Manager owns rubric discipline, scoring completeness, and decision thresholds. - People Analytics owns instrumentation, segmented risk dashboards, and time-to-event reporting. Sources of truth should be unambiguous: the ATS is the system of record, and all pre-flight outcomes must be written back as immutable events.

  • Recruiting Ops (R): Send pre-flight invite, monitor completion, trigger reschedule if needed.

  • Security (A): Approve exception policy, require step-up verification on device change.

  • Hiring Manager (R): Enforce no-score rule when evidence is incomplete.

  • People Analytics (A): Define metrics, dashboards, and weekly variance review.

  • Automate: A/V device test, permissions check, bandwidth sanity check, device fingerprint change detection, event logging.

  • Manual review: exception approval, accessibility accommodations verification, identity step-up decision.

MODERN OPERATING MODEL

Run pre-flight as an instrumented workflow with a gate, triggers, and evidence, because "tested earlier" only matters if it is logged and enforced. Model it like access management: you do not grant privileged access to an interview room until the candidate passes basic readiness checks and identity gating requirements. Minimum viable operating model:

  1. Identity verification before access: do not let pre-flight become an unverified alternate channel.

  2. Event-based triggers: invite, reminders, pass, fail, retry, escalation.

  3. Automated evidence capture: store results as structured fields plus artifacts where relevant.

  4. Analytics dashboards: time-to-pass, completion rate, failure reasons, reschedules, and exception counts.

  5. Standardized rubrics: if pre-flight fails and you proceed anyway, the rubric must reflect the degraded evidence and force a step-up or reschedule decision.

  • Pre-flight completion rate by stage and geo

  • Median time-to-pass (TTP) and 90th percentile

  • Failure reason mix (permissions, device missing, bandwidth, corporate policy)

  • Reschedule rate attributable to A/V

  • Exception approval count and SLA compliance

WHERE INTEGRITYLENS FITS

IntegrityLens fits as the ATS-anchored control plane that ties pre-flight readiness to identity gating and audit-ready evidence packs. It enables: - Biometric identity verification with liveness detection, document authentication, and face matching before the interview becomes a privileged step. - Fraud prevention signals that flag proxy patterns and deepfake risk for step-up verification instead of last-minute improvisation. - Immutable evidence packs with timestamped logs, reviewer notes, and tamper-resistant feedback linked to the candidate record. - AI screening interviews and technical assessments that can be sequenced only after pre-flight and identity gates pass. - Zero-retention biometric architecture options for environments that require minimized biometric storage footprints.

  • Fewer day-of reschedules

  • Cleaner audit trails for exceptions

  • Lower fraud exposure during channel switches

ANTI-PATTERNS THAT MAKE FRAUD WORSE

Avoid these patterns because they create unlogged alternate channels that proxy interviewers exploit: - Allowing phone dial-in or audio-only as a default fallback without step-up verification and a logged exception. - Letting candidates switch devices at the last minute without re-running identity checks and updating the evidence pack. - Scoring interviews that had compromised A/V as if they were complete evidence, instead of forcing a reschedule or degraded-evidence rubric.

  • They remove identity gating at the exact moment access is granted.

  • They create decisions without retrievable evidence.

  • They make reviewer accountability impossible to reconstruct.

IMPLEMENTATION RUNBOOK

1

Pre-flight invite at T-24h (SLA: within 5 minutes of interview scheduling) - Owner: Recruiting Ops - Automation: send a single link that runs camera, mic, and permissions checks - Log: preflight-invited timestamp, channel, locale

2

Candidate completes pre-flight (SLA: by T-2h) - Owner: Candidate action monitored by Recruiting Ops - Automation: device detection, permission validation, sample recording playback, bandwidth check - Log: preflight-passed or preflight-failed with reason code and device metadata

3

Retry loop (SLA: 2 retries, each within 10 minutes) - Automation: guided fixes with clear copy, then re-test - Log: retry-count, time-to-pass, failure reason progression

4

Escalation to review queue (SLA: decision within 30 minutes during business hours) - Owner: Recruiting Ops routes, Security approves exception policy - Manual review: accessibility accommodation needs, corporate device restrictions, step-up verification requirement - Log: exception-requested, exception-approved or denied, approver identity

5

Identity gate enforcement before interview access (SLA: complete by T-30m) - Owner: Security (policy), Recruiting Ops (execution) - Automation: require identity verification before joining interview if pre-flight failed, device changed, or risk signals triggered - Log: identity-verified timestamp, method, step-up reason code

6

Interview start rule (SLA: hard gate at T-0) - Owner: Hiring Manager - Enforcement: no scoring unless minimum evidence criteria met (audio + video captured, identity verified) - Log: interview-started, evidence-quality flag, rubric version

7

Post-interview evidence pack finalization (SLA: within 60 minutes) - Owner: Recruiting Ops for completeness, Hiring Manager for scoring, People Analytics for reporting - Automation: compile timestamps, artifacts, reviewer notes, and exception decisions - Log: evidence-pack-finalized, missing-evidence flags

  • "This check takes about 60 seconds. It confirms your camera and mic work so your interview time is used for evaluation, not troubleshooting."

  • "If you cannot pass the check, you can retry twice. After that, we will route you to a time-boxed review so you are not stuck waiting."

  • "If you need an accommodation, select it here. We will log the request and confirm the alternate format before your interview."

  • Pre-flight completion rate by role family and seniority

  • Reschedule rate and median reschedule delay (minutes)

  • Exception rate and approval SLA compliance

  • Fraud signal rate on interviews preceded by failed pre-flight

  • Offer cycle-time variance before vs after rollout (qualitative if early)

Related Resources

Key takeaways

  • Treat A/V readiness as a gate with timestamps, not a support issue. If the candidate cannot be seen and heard, the interview is not audit-ready.
  • Pre-flight checks reduce reschedules, which are where identity gating and evidence capture most often break.
  • Pre-flight must be accessible and measurable: completion rate, time-to-pass, retry rate, and exception reason codes.
  • A pre-flight runbook needs explicit owners and SLAs, plus an immutable event log that ties outcomes to the candidate record.
Pre-Flight A/V Readiness Policy (ATS-anchored)YAML policy

Use this as a control document to align Recruiting Ops, Security, and Hiring Managers on what is gated, what is logged, and when step-up verification triggers.

Designed to be implemented as workflow rules and a review queue with SLA timers.

policy:
  name: preflight-av-readiness
  version: 1.0
  objective: "Prevent interview-day A/V failures from creating unlogged exceptions and fraud exposure."

gates:
  - gate_id: av-preflight
    applies_to: ["live_interview", "ai_screening_video"]
    required_by:
      live_interview: "T-2h"
      ai_screening_video: "before_start"
    pass_criteria:
      camera: "detected_and_permission_granted"
      mic: "detected_and_permission_granted"
      playback: "candidate_confirms_audio"
    retries:
      max_retries: 2
      retry_sla_minutes: 10
    failure_reason_codes:
      - "no_camera_detected"
      - "no_mic_detected"
      - "permission_blocked"
      - "bandwidth_low"
      - "device_policy_restriction"
      - "accessibility_accommodation_requested"

enforcement:
  - rule: "No A/V pass by T-2h"
    action: "route_to_review_queue"
    queue: "preflight-exceptions"
    decision_sla_minutes: 30
    required_approvers: ["recruiting_ops", "security_if_identity_step_up_needed"]

  - rule: "Device change after preflight-pass"
    action: "require_step_up_verification"
    step_up_reason_code: "device_changed"

  - rule: "Exception approved to proceed with degraded A/V"
    action: "force_degraded_evidence_rubric"
    rubric_flag: "degraded_av"
    scoring_rule: "no_hire_decision_without_identity_verified"

audit_log_events:
  - "preflight-invited"
  - "preflight-started"
  - "preflight-passed"
  - "preflight-failed"
  - "preflight-retried"
  - "exception-requested"
  - "exception-approved"
  - "exception-denied"
  - "identity-verified"
  - "interview-started"
  - "evidence-pack-finalized"

retention:
  biometrics: "zero-retention (store verification outcome + timestamps; no raw biometric media)"
  evidence_pack: "retain per HR/legal policy; must include timestamps, approver IDs, and reason codes"

Outcome proof: What changes

Before

Interview-day A/V failures were handled in ad hoc channels. Reschedules and phone fallbacks were not consistently written back to the ATS, and exception approvals were not attributable to a named approver.

After

Pre-flight became a hard gate with an exception review queue. Every invite, pass, fail, retry, and workaround was logged as an immutable event and included in the candidate evidence pack.

Governance Notes: Security and Legal signed off because the policy creates attributable approvals, reason-coded exceptions, and ATS-anchored audit trails. The design minimizes biometric handling by storing outcomes and timestamps (and using zero-retention biometrics where required), which supports GDPR/CCPA-ready controls.

Implementation checklist

  • Define the pre-flight window (for example: T-24h to T-30m) and the stop conditions (no A/V, no interview).
  • Instrument three events in the ATS log: preflight-invited, preflight-passed, preflight-failed (with reason code).
  • Publish a recovery path with time-boxed retries and escalation to a review queue.
  • Require identity gate re-validation on any reschedule or device change.
  • Report weekly: preflight completion rate, median time-to-pass, failure reason mix, and reschedule rate attributable to A/V.

Questions we hear from teams

What is the minimum viable pre-flight check?
A minimum viable pre-flight is a gated test that confirms camera detected, mic detected, permission granted, and a short playback confirmation, with outcomes written back to the ATS as timestamped events.
How do we avoid making pre-flight feel like friction?
Make it predictable and time-boxed: a single link, a progress indicator, clear pass criteria, two guided retries, and a logged escalation path with a published SLA. Clarity creates perceived speed.
Do pre-flight checks help with fraud, or just tech issues?
They help with fraud when tied to identity gating and device-change triggers. The fraud risk comes from last-minute channel switching and unverified fallbacks, not from the device test itself.
What should we log for audit readiness?
At minimum: invite timestamp, start timestamp, pass or fail with reason code, retry count, exception request and approval with approver identity, identity verification outcome, interview start, and evidence pack finalization.

Ready to secure your hiring pipeline?

Let IntegrityLens help you verify identity, stop proxy interviews, and standardize screening from first touch to final offer.

Try it free Book a demo

Watch IntegrityLens in action

See how IntegrityLens verifies identity, detects proxy interviewing, and standardizes screening with AI interviews and coding assessments.

Related resources