You are forty minutes into a two-hour final. You have finally found your rhythm. And then the screen freezes. Or the proctoring software throws an error. Or your internet drops for what feels like an eternity but is probably eleven seconds. Your stomach does the thing it does, and for a moment the exam content is the last thing on your mind, you are just staring at a spinning wheel wondering if months of studying are about to evaporate because of a router.
Technical failures during online exams are more common than most students realize, and the difference between a minor hiccup and a genuine disaster almost always comes down to what you did before the exam started, not just how you react in the moment. This post covers both halves: the preparation that prevents most problems, and the exact steps to take if something still goes wrong.
Pre-Exam Technical Preparation to Minimize Failure Risk
Most catastrophic online exam failures are actually preventable failures wearing a disguise. A router that has not been restarted in three months, a laptop running on 4% battery with the charger “somewhere in the house,” a browser with fourteen tabs and a memory leak, these are not bad luck, they are unaddressed risk. Here is the checklist worth running through the day before, not the hour before.
The Day-Before Checklist
- Restart your router and computer at least a few hours before the exam, not five minutes before. A fresh boot clears out background processes and memory leaks that can cause slowdowns or crashes at the worst moment.
- Test your internet speed and, if possible, connect via ethernet cable instead of Wi-Fi. A wired connection is dramatically more stable and removes an entire category of failure risk.
- Close every unnecessary application and browser tab, and disable auto-updates for your operating system so a surprise update does not launch itself mid-exam.
- Fully charge your device and plug it in during the exam regardless of battery percentage. Never trust a laptop battery’s reported “hours remaining” under exam-day stress.
- Run the proctoring software’s system check in advance if one is provided. Most remote-proctoring platforms (Proctorio, Respondus, ExamSoft, and similar) offer a pre-exam compatibility check. Actually run it, do not assume your setup is fine because it worked once before.
- Know your backup device and backup connection. If you have a second laptop or can tether to your phone’s hotspot, know exactly how to switch to it before you need to, not while you are panicking.
Have the Right Information on Hand, Physically
Write down, on paper, not just saved in a browser tab that might be inaccessible during a crash:
- The exam proctor or IT support phone number and email
- Your student ID and exam confirmation number
- Your professor or exam coordinator’s direct contact information
- The official policy document link or reference number for technical issues, if your institution provides one
Having this information on paper matters more than it sounds like it should. If your computer is the thing that failed, your notes app is not a reliable place to find a phone number.
Immediate Steps When Technology Fails During an Exam
Even with perfect preparation, things sometimes go wrong. When they do, the order of operations matters, because panicked improvisation tends to make small problems bigger.
Step 1: Do Not Immediately Restart Everything
The instinct when something freezes is to slam the power button and reboot. Resist that instinct for the first thirty seconds. A brief freeze often resolves itself, and a forced restart can sometimes cause you to lose more progress than the freeze itself would have, or trigger a proctoring software flag for an “unexpected exit” that then requires additional explanation later. Give it a moment. If it is a proctoring software crash specifically, check whether it has an auto-save or resume feature before you do anything drastic.
Step 2: Document Everything, in Real Time
The moment you notice a problem, take a photo of your screen with your phone. This single habit protects you more than almost anything else on this list. A screenshot from the frozen device itself may not be possible, but a phone photo showing the error message, frozen screen, or timestamp is concrete evidence you can reference later. Note the exact time the issue started and, once resolved, the exact time it ended. This timeline becomes essential if you need to request extra time or dispute a score later.
| What to capture | Why it matters |
|---|---|
| Phone photo of the error/frozen screen | Proof the issue occurred, with visible timestamp if possible |
| Exact start and end time of the disruption | Basis for any time-extension request |
| Screenshot of any error codes or messages | Helps IT support diagnose and helps you cite the issue precisely |
| Confirmation email or chat log with support | Creates a paper trail showing you reported it promptly |
Step 3: Contact Support Immediately, Not After You’ve Tried to Fix It Yourself for Twenty Minutes
This is where a lot of students lose valuable time and goodwill. There is a strong temptation to try to solve the problem quietly and just get back to the exam as fast as possible, hoping nobody notices there was an issue at all. Resist this. Contact your professor, exam proctor, or technical support the moment a significant issue occurs, using whatever channel is fastest, phone, live chat, or email with “URGENT: Exam Technical Issue” in the subject line. The earlier you report it, the more credible your account is and the more options are typically available to fix it, including pausing your exam time, resetting your session, or arranging a makeup exam.
Step 4: If You Cannot Reach Anyone, Keep Trying and Keep Documenting
Sometimes support lines are slow, especially during peak exam periods when hundreds of students are testing simultaneously. If you cannot get through immediately, do not give up after one attempt. Try multiple channels, phone and email and chat, and log each attempt with a timestamp. If you eventually get back into the exam on your own, note that too, along with how much time you believe you lost. This documentation is what makes a fair resolution possible after the fact, even if nobody was available to help in the moment.
Exam Body Policies for Technical Failures and Score Disputes
Almost every institution and major certification body has an established policy for technical failures during exams, and knowing it in advance changes how confidently you can act if something goes wrong.
What to Look Up Before Exam Day
Search your institution’s or certification provider’s website for terms like “technical issue policy,” “exam disruption,” or “proctoring software failure.” Most policies cover:
- Time extensions for verified technical disruptions, often calculated based on documented downtime
- Exam rescheduling or retake eligibility if the disruption was severe enough to invalidate the attempt
- Score dispute or appeal processes, usually requiring documentation submitted within a specific window (often 24 to 72 hours)
- Explicit instructions for what to do in real time, which sometimes differ from what feels intuitive (for example, some proctoring platforms specifically instruct you not to close the browser, even if it appears frozen)
Certification bodies for professional exams (CompTIA, PMI, AWS, and similar) generally publish these policies clearly precisely because remote testing failures are common enough to require a standard process. Reading this policy before your exam, not after a crisis, means you already know exactly what evidence you need to gather and what the realistic resolution options are, instead of trying to research your rights while also panicking about a frozen screen.
After the Exam: Filing a Dispute the Right Way
If your exam was significantly disrupted and you believe your score does not reflect your actual performance, file a dispute promptly using the documentation you gathered. Be factual and specific rather than emotional in your written account: state the exact times, attach your screenshots, reference your support contact attempts, and clearly state what resolution you are requesting (extra time, a retake, or a score review). Institutions and certification bodies handle far more of these requests than students expect, and a clear, well-documented case is resolved far more smoothly than a vague complaint filed weeks later from memory.
The Bottom Line
A malfunctioning computer during an exam feels like a uniquely personal disaster in the moment, but it is a well-understood, well-documented problem that testing bodies deal with constantly, and there are established paths to a fair outcome. The preparation that prevents most issues takes twenty minutes the day before. The in-the-moment response that protects you if something still goes wrong takes a level head, a phone camera, and a habit of documenting everything as it happens rather than after the fact. Technology will occasionally fail you. A calm, prepared response ensures it does not also cost you the exam.
