What happens if a proctored exam is interrupted by a power or internet outage?
TL;DR: A well-built proctoring platform logs the disconnect with a timestamp, preserves everything captured up to that point, and lets the exam administrator decide how to handle the gap — resume, extend time, or flag for manual review. The disconnect itself isn't treated as a violation; it's logged as an event, the same way any other interruption would be.
The Evidence
Outages are a normal operational reality, not an edge case — home internet drops, laptops lose power, campus wifi hiccups. A proctoring system that can't distinguish "connection lost" from "candidate closed the tab to cheat" creates real unfairness: students in areas with less reliable infrastructure would be penalized for something entirely outside their control. The correct design treats an outage as a logged event with a timestamp, not an automatic violation — everything recorded before the disconnect stays intact, and the trust report shows exactly when monitoring stopped and, if the candidate reconnects, when it resumed.
What happens next is a policy decision, not a technical one: some institutions let the candidate resume from where they left off with adjusted time; others require the session be flagged for manual review before continuing; high-stakes exams may require a full restart with a fresh identity check. None of that decision should be made by the AI alone — it surfaces the gap clearly enough for a human to decide.
How Different Interruptions Should Be Handled
| Interruption | What gets logged | Typical resolution |
|---|---|---|
| Brief internet drop (seconds) | Timestamped gap, auto-reconnect | Exam continues, gap noted in trust report |
| Extended outage (minutes+) | Timestamped gap, session paused | Administrator reviews, decides on time extension or restart |
| Power loss / device crash | Session ends, prior evidence preserved | Candidate re-authenticates, administrator decides continuation |
| Repeated disconnects | Pattern flagged for review | Administrator investigates — could be infrastructure or evasion |
How to Prepare for This Before Exam Day
- Publish a clear outage policy in your exam instructions: what to do, who to contact, how time extensions work.
- Confirm your proctoring platform logs disconnects as timestamped events, not automatic violations.
- Set a threshold for what counts as a "brief" versus "extended" outage in your policy.
- Require re-identity-verification after any extended disconnect, so a resumed session is still tied to the right person.
- Review disconnect patterns across a cohort — one student losing connection once is normal; the same student losing connection at the same point in every exam is worth a closer look.
FAQ
Does a disconnect automatically count as a violation? No — it should be logged as a timestamped event for human review, not treated as cheating by default.
What happens to evidence captured before the outage? It's preserved — the trust report shows everything recorded up to the disconnect and picks back up if the session resumes.
Should candidates get extra time after a disconnect? That's a policy decision for the exam administrator; many institutions grant time equal to the outage duration, documented in the trust report.
Does Neuroxa require a fresh identity check after reconnecting? Administrators can configure re-verification after an extended disconnect to confirm the same person resumed the session.
By Pinal Dave Last updated: 2026-07-25