What is the minimum viable pre-flight check for camera and mic?

Minimum viable pre-flight is a candidate-run check that confirms camera availability, mic input selection with detectable audio level, and granted OS/browser permissions, with a pass-fail result written back to the ATS with timestamps.

When should pre-flight failures trigger step-up verification?

Trigger step-up verification when failures cluster with integrity anomalies, such as repeated retries, device fingerprint changes close to interview time, or location changes that do not match prior activity. Security should own the trigger policy; Recruiting Ops should own the review queue SLA.

How do pre-flight checks help with audit readiness?

They create a reproducible record of prerequisites and exceptions: when readiness was tested, what failed, what remediation was taken, and who approved overrides. If those events are stored in an immutable evidence pack attached to the candidate record, decisions are easier to defend.

How do you keep pre-flight from slowing time-to-offer?

Run it in parallel with scheduling, make it self-serve, and time-box manual review with SLAs. The goal is to move failures earlier in the timeline, where they are cheaper to fix, rather than adding steps at the end.

Candidate-experience · Jun 1, 2026 · 14 minute read

Pre-flight Checks for Camera and Mic Before Interview Day

Pre-flight checks are not UX polish. They are an integrity control that prevents interview-day chaos, preserves audit defensibility, and keeps time-to-offer from stalling on avoidable A-V failures.

Lisa Wu

Candidate Experience Lead

Lisa focuses on reducing friction and improving accessibility in verification flows.

Interview-day A-V failures are not a UX problem. They are an SLA and audit problem because they happen at the exact moment your process is least instrumented.

Back to all posts

Real Hiring Problem

Pre-flight checks are an operational control for preventing interview-day A-V failures that trigger SLA breaches, inconsistent scoring, and audit gaps. When camera and mic failures happen live, you lose more than minutes. You lose chain-of-custody on who showed up and what conditions affected evaluation. Industry survey data indicates identity fraud risk is common enough that you should assume attempts will occur and design a logged gate accordingly.

Finalist joins panel interview. Camera blocked by OS permissions. Mic input wrong device. Panel spends 10-15 minutes troubleshooting.
Debrief slips. Hiring manager skips rubric detail. Time-to-offer pushes by 1-2 business days.
Candidate disputes outcome later. Ops cannot produce a single, timestamped record of readiness and identity conditions.

Operational risk: interview throughput drops and time-to-event delays cluster around unverified readiness.
Legal exposure: decisions become harder to defend when process steps are not logged and reproducible.
Fraud risk: chaos and exceptions increase proxy interview and off-camera assistance opportunities.

Why Legacy Tools Fail

Legacy stacks treat A-V readiness as a support ticket, not as a policy-controlled gate with audit trails. ATS, interview, and assessment tools rarely share immutable logs or unified evidence packs, so exceptions get handled in shadow workflows. Sequential checks increase cycle time because failures are discovered at the latest possible moment.

No unified evidence pack across scheduling, pre-flight, identity, and interview artifacts.
No SLA-bound exception queues, so urgent issues interrupt recruiters and interviewers ad hoc.
No standardized place to store attestation, overrides, or rubric versioning.

Ownership and Accountability Matrix

Assign ownership explicitly so pre-flight becomes a repeatable control rather than a best-effort practice. Recruiting Ops owns workflow design, exception SLAs, and completion metrics. Security owns policy triggers and audit requirements. Hiring Managers own rubric completion and decision evidence. Define sources of truth so every event can be reconstructed from the ATS record.

Recruiting Ops: pre-flight sequencing, reminders, exception queues, time-to-event dashboards.
Security: step-up verification triggers, access control policy, retention and audit requirements.
Hiring Manager: rubric discipline, decision rationale, escalation when conditions might bias evaluation.

ATS: canonical candidate record and lifecycle timestamps.
Verification service: identity and readiness event outputs written back to ATS.
Interview platform: raw session telemetry referenced by ID and attached to evidence pack.

Modern Operating Model

Implement pre-flight as an instrumented gate before high-stakes interviews: run it early, log it immutably, and route exceptions through SLA-bound queues. Use event-based triggers to parallelize what can be parallelized and avoid waterfall delays. Measure by timestamps: invite-to-pass, failure clustering, and exception SLA breaches.

Identity gate before access to interview links when policy requires it.
Event-based orchestration: pass, fail, retry, escalate, override, reschedule.
Automated evidence capture: device, permission state, retries, attestations, reviewer notes.
Dashboards: segmented risk and time-to-event analytics tied to funnel conversion.

Where IntegrityLens Fits

IntegrityLens functions as the ATS-anchored control plane for readiness, identity gating, and defensible evidence packaging, so interview-day exceptions do not become shadow workflows. It supports biometric identity verification (liveness, face match, document authentication) and writes results into the candidate lifecycle with timestamps. It generates immutable evidence packs and supports zero-retention biometrics to align with compliance expectations.

Single source of truth: readiness and identity events tied to the candidate record.
Audit-ready evidence packs: timestamped logs and reviewer accountability.
Risk-tiered funnel: step-up verification only when anomalies justify it.
Fewer live interruptions: failures discovered 24-48 hours earlier.
Clear retention controls: zero-retention biometrics option.

Anti-Patterns That Make Fraud Worse

Do not trade short-term speed for unlogged exceptions. The unlogged path is the path you cannot defend. Avoid out-of-band troubleshooting that breaks evidence chain-of-custody. Do not allow repeated reschedules to become a bypass of integrity controls.

Letting interviewers troubleshoot live and then proceed without logging device changes and identity conditions.
Accepting out-of-band evidence over SMS or personal email that never reaches the ATS audit trail.
Rescheduling repeatedly without risk-tiering and step-up verification triggers.

Implementation Runbook

Implement pre-flight checks as a timed gate with explicit SLAs, owners, and evidence requirements per step. Default to self-serve recovery paths, then route edge cases to a review queue with measurable response times. Package the entire sequence into an immutable evidence pack attached to the candidate record.

Trigger pre-flight within 1 minute of interview scheduled. Owner: Recruiting Ops. Evidence: invite event timestamp.
Candidate completes within 24 hours. Owner: Candidate, accountable: Recruiting Ops. Evidence: pass-fail, metadata, retries.
Exception queue first response within 4 business hours. Owner: Recruiting Ops. Evidence: ticket timestamps, resolution notes.
Same-day step-up reviews within 2 business hours when triggered. Owner: Security policy, Ops execution. Evidence: reviewer decision and rationale.
Rubric submitted within 24 hours post-interview. Owner: Hiring Manager. Evidence: rubric version, scorer identity, timestamps.

Pre-flight started, passed, failed, and retry events with timestamps.
Device and permission state at pass and at day-of re-check.
Candidate attestation text and acceptance timestamp.
All overrides with approver identity and reason codes.
Evidence pack ID attached to the candidate record.

Sources

31% of hiring managers say they have interviewed a candidate who later turned out to be using a false identity. Checkr (2025): https://checkr.com/resources/articles/hiring-hoax-manager-survey-2025

Close: Implementation Checklist

If you want to implement this tomorrow, focus on three outcomes: fewer interview-day failures, defensible decisions, and a lower fraud surface without slowing time-to-offer. Treat readiness as a logged gate, not a troubleshooting moment. Make timestamps and evidence packs the default artifact of every exception.

Add a required A-V pre-flight gate 24-48 hours before every remote interview.
Publish self-serve recovery paths and enforce an exception queue with a 4-hour first response SLA.
Define step-up verification triggers and assign Security as policy owner.
Make the ATS the single source of truth: every pre-flight event and override must be logged and attached to the candidate record.
Require evidence-based scoring: no rubric submission without readiness gate completion logged.
Instrument time-to-event metrics and review weekly: invite-to-pass, failure clustering, exception SLA breaches, and time-to-offer delays.

Related Resources

Key takeaways

Treat A-V readiness as an identity-adjacent access gate, not a last-minute troubleshooting task.
Instrument pre-flight checks with immutable timestamps so failures are triaged, not debated.
Use SLA-bound exception routing: self-serve fixes first, then step-up verification only when risk signals justify it.
Log what mattered: device readiness, permissions, network, and candidate attestation tied to the candidate record.
Clarity and accessibility reduce drop-off: explain what is tested, why, and what to do if it fails.

Pre-flight A-V Readiness Policy (SLA + logging)YAML policy

A single policy artifact that Recruiting Ops and Security can approve, version, and audit.

Defines timing, pass criteria, exception routing SLAs, step-up triggers, and required logged events.

preflight_policy:
  policy_id: "preflight-av-readiness-v1"
  effective_date: "2026-06-01"
  scope:
    applies_to:
      - "all_remote_interviews"
    exempt_roles: []
  timing:
    preflight_required_hours_before: 24
    day_of_recheck_required: true
  pass_criteria:
    camera:
      required: true
      allow_virtual_camera: false
    microphone:
      required: true
      min_input_level_detected: true
    permissions:
      camera_permission: "granted"
      mic_permission: "granted"
    network:
      connectivity_check: true
  reminders:
    first_reminder_hours_after_invite: 12
    final_reminder_hours_before_interview: 3
  exception_routing:
    self_serve_first: true
    manual_review_queue: "av-preflight-exceptions"
    manual_first_response_sla_hours: 4
  step_up_verification_triggers:
    - name: "device_swap_plus_geo_change"
      condition: "device_fingerprint_changed == true AND geo_country_changed == true"
      action: "require_step_up_verification"
    - name: "repeat_failures"
      condition: "preflight_fail_count >= 2"
      action: "route_to_manual_review"
    - name: "camera_off_after_pass"
      condition: "day_of_camera_disabled == true AND prior_preflight_pass == true"
      action: "require_step_up_verification"
  logging:
    required_events:
      - "preflight-invite-sent"
      - "preflight-started"
      - "preflight-passed"
      - "preflight-failed"
      - "preflight-retry"
      - "day-of-ready"
      - "exception-opened"
      - "exception-resolved"
    retention:
      evidence_pack_retention_days: 365
      biometrics_retention: "zero-retention"
  accessibility:
    wcag_target: "WCAG 2.1"
    provide_captions_instructions: true
    keyboard_navigation_supported: true

Outcome proof: What changes

Before

Interview-day A-V issues were handled ad hoc in chat and email. Reschedules were common, and exceptions were rarely attached to the candidate record. Post-hoc reconstruction for complaints required manual digging across tools.

After

Pre-flight became a required gate with self-serve recovery paths, an SLA-bound exception queue, and evidence packs attached to the ATS record. Hiring managers received fewer live interruptions and submitted rubrics against a consistent, logged readiness baseline.

Governance Notes: Security and Legal signed off because the process created a consistent chain-of-custody: explicit consent, timestamped readiness events, documented exception handling, and controlled retention (including a zero-retention biometrics option). Decisions became defensible because approvals and overrides were attributable to named reviewers and stored in an ATS-anchored audit trail.

Implementation checklist

Run pre-flight checks 24-48 hours before scheduled interviews, with a same-day re-check for final confirmation.
Require explicit candidate permission prompts and confirm camera and mic input selection.
Capture and store evidence: timestamps, results, device and browser metadata, and candidate attestation.
Route failures to an SLA-bound queue with predefined recovery paths (switch device, alternate browser, reschedule window).
Escalate to step-up verification when pre-flight anomalies correlate with integrity risk (multiple device swaps, unusual geolocation changes).

Questions we hear from teams

What is the minimum viable pre-flight check for camera and mic?: Minimum viable pre-flight is a candidate-run check that confirms camera availability, mic input selection with detectable audio level, and granted OS/browser permissions, with a pass-fail result written back to the ATS with timestamps.
When should pre-flight failures trigger step-up verification?: Trigger step-up verification when failures cluster with integrity anomalies, such as repeated retries, device fingerprint changes close to interview time, or location changes that do not match prior activity. Security should own the trigger policy; Recruiting Ops should own the review queue SLA.
How do pre-flight checks help with audit readiness?: They create a reproducible record of prerequisites and exceptions: when readiness was tested, what failed, what remediation was taken, and who approved overrides. If those events are stored in an immutable evidence pack attached to the candidate record, decisions are easier to defend.
How do you keep pre-flight from slowing time-to-offer?: Run it in parallel with scheduling, make it self-serve, and time-box manual review with SLAs. The goal is to move failures earlier in the timeline, where they are cheaper to fix, rather than adding steps at the end.

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.