When the Proctor Calls: How to Troubleshoot Common At‑Home Testing Failures

At-home testing can be a huge relief for families, but when a proctor interrupts a session, the stakes feel immediate. Whether the issue is camera angle, background movement, battery loss, app crashes, or an ISEE troubleshooting concern, the best response is to stay calm, document everything, and follow a clear escalation path. The good news is that most remote proctoring issues can be managed if you prepare like a test-center staff member would: check the environment, verify device readiness, and know exactly what to say when contacting ERB support. This guide walks parents and tutors through the most common failure points and gives you practical scripts, documentation steps, and appeal-ready recordkeeping.

ERB’s at-home administration is designed for structure and security, and that means the rules are strict. The second camera must show the student’s desk and hands, the testing room must stay quiet, and the device must remain plugged in throughout the exam. A small mistake can be interpreted as a test security risk, which is why a fast, accurate response matters. If you’re also building a stronger overall prep routine, it helps to think about your setup the way you would a high-stakes project plan; our guide on building a productivity stack without buying the hype is a useful mindset reset for families who want to avoid overcomplicating test day.

What Usually Goes Wrong During an At-Home ISEE

Camera angle and second-camera placement errors

The most common issue is not a catastrophic tech failure at all, but a visibility problem. The remote proctor needs a stable view of the student’s hands, workspace, and keyboard area, which is why the second device must be placed about 18 inches away and angled to avoid blind spots. If the camera is too low, too high, or drifting on a soft surface, the proctor may pause the exam or warn that the setup does not meet requirements. Families sometimes underestimate how sensitive the camera view is, so it helps to run a mock session before test day and adjust the stand until nothing shifts when the student writes, clicks, or reaches for scratch paper.

This is where a prep routine becomes a test-security routine. Keep the second device plugged in, turn off notifications, and confirm the camera is framed before the exam begins. For a broader reminder about keeping digital environments stable, see our article on smart cameras for home lighting, which offers a helpful analogy for placement, angle, and visibility. The same principle applies here: if the system cannot “see” what it needs to see, the proctor cannot validate the session.

Background movement, noise, and accidental interruptions

At-home testing is unforgiving about movement in the background. A sibling walking behind the student, a pet jumping on a couch, or a parent entering the room can trigger a warning because proctors must preserve exam integrity. This does not always mean the test is automatically canceled, but it can create a chain reaction of pauses, reminders, and possible invalidation if the interruption seems repeated or intentional. Families should assume the room must behave like a controlled testing center, not a typical study room.

One practical strategy is to run a “silent perimeter check” 15 minutes before launch: close doors, place a note on the front of the house, silence phones, and tell everyone in the household the room is off limits. Parents who manage multiple children often benefit from the same scheduling discipline used in other family systems; our piece on resilient routines for parenting shows how structured routines reduce avoidable chaos. In the testing context, fewer moving parts means fewer reasons for the proctor to interrupt.

Battery loss, charging failures, and power management mistakes

Device power is one of the easiest problems to prevent and one of the hardest to fix mid-test if you have not planned ahead. The second camera device must stay plugged in, and the primary testing device should be fully charged even if it is also plugged in. Batteries degrade unexpectedly, cords get loose, and some chargers do not deliver enough power under sustained use. If the proctor notices a battery issue, they may halt the session until the student complies with the power requirement.

Families should use the same logic as a travel checklist: don’t just bring a charger, test the charger. Our guide on power bank planning for travelers is not about exams, but it reinforces a useful habit—assume power is a critical dependency, not an afterthought. For at-home testing, that means charging both devices overnight, checking cables for damage, and keeping a backup charging option nearby if the test rules allow it.

How to Troubleshoot the Most Common Remote Proctoring Issues

If the camera angle is rejected

Start by stopping any unnecessary movement and asking the student to keep hands visible and still. Then tilt the second camera slowly so the desk, keyboard, and writing surface are in clear view, with no glare blocking the frame. If the issue is the stand itself, move the device onto a firmer surface or use a stable prop that cannot wobble. Do not keep adjusting the camera repeatedly while talking over the proctor, because that can look like noncompliance rather than troubleshooting.

If the proctor has already interrupted the session, acknowledge the issue in one sentence and state the corrective action. A good technical support script is: “We understand the camera view is not adequate. We are repositioning the device now so the desk, keyboard, and hands remain visible for the rest of the exam.” If the problem continues, write down the exact time, the proctor’s instruction, and what was changed. That record becomes important if you later need a test cancellation appeal.

If background movement triggers a warning

When the proctor flags background movement, the immediate goal is to remove the cause and demonstrate control. Pause only when instructed, have the student stay seated, and stop all traffic around the room. If a pet or sibling caused the problem, note it separately for your records, but do not argue in the moment. The proctor is watching for whether the environment can be stabilized, not whether the family intended disruption.

A practical response script is: “We’ve identified the interruption and are securing the room now. No one else will enter, and the testing area will remain still and quiet.” Families sometimes think a single interruption is harmless, but during secure testing even minor movement may be treated as a test security concern. That is why prevention matters so much; it is easier to protect the session than to explain it after the fact.

If the battery drops or the device loses power

Power loss is one of the most serious at-home failures because it can create a partial exam record, force a restart, or trigger a cancellation. If the device is still alive, plug it in immediately and confirm the charger is working. If the device has already shut down, restart only if the proctor instructs you to do so. Keep your phone nearby to document the sequence of events, including the percent charge before failure and any messages that appeared on screen.

The most useful communication is direct and factual: “The primary device unexpectedly lost power at [time]. The device is now connected to a charger, and we are waiting for instructions before taking any further action.” If this is your first at-home test, consider a pre-test checklist similar to one used in high-stakes digital environments; our overview of future-proofing devices is a reminder that hardware readiness is a real performance factor, not just a convenience.

If the app crashes or the secure test environment freezes

Application crashes are stressful because they can make students feel like they did something wrong when the cause is often software instability, cache conflicts, or connection disruption. The right move is to avoid random clicking and wait for proctor instructions if the crash happens during a live session. If you are prompted to relaunch the app, do so only as directed, because opening the wrong application can violate the secure environment. Keep track of error messages exactly as they appear, even if they seem technical or confusing.

A helpful support script is: “The secure testing app froze and is no longer responding. We have not opened any other applications, and we are waiting for guidance before relaunching.” If you want a broader understanding of how locked-down environments work, the discussion in staying secure on public Wi-Fi offers a useful parallel: in both cases, the system is designed to reduce risk by limiting what the user can do. During an exam, that limitation is a feature, not a flaw.

What to Say When You Contact ERB Support

A clear technical support script you can use

When you contact support, your goal is not to tell the whole story emotionally; it is to give ERB the facts needed to decide whether the issue was environmental, technical, or procedural. Start with the student name, test level, scheduled time, device type, and a one-sentence description of the failure. Then provide the exact time the issue began, what the proctor said, and whether the session was paused, ended, or resumed. If possible, send screenshots or photos only when instructed and only through the approved channel.

Here is a simple script parents can adapt: “We are calling about an at-home ISEE session scheduled for [time]. At approximately [time], we experienced [camera issue / battery loss / app crash / internet drop]. The proctor instructed us to [pause / reposition / wait / restart]. We are requesting guidance on next steps and documenting the incident for our records.” For families who prefer a more organized communication style, our piece on tracking a package like a pro provides a surprisingly relevant framework: list what happened, when it happened, and what action was taken next.

What facts matter most in the first call

Support teams respond best to chronological, specific information. Include whether the issue affected the primary device, the second camera, or both. Mention whether the internet dropped, whether the student was actively answering a question, and whether the proctor had already issued warnings. If you restarted any device, note who authorized it. The more precise the record, the easier it is for ERB to determine whether the exam can be salvaged or whether a retest/appeal path is appropriate.

It also helps to use calm language that signals cooperation. Avoid saying “the app is broken” or “the proctor made a mistake” unless you have documentation. Instead, say “the app became unresponsive” or “we were told to adjust the camera,” then let the support process sort out responsibility. This is similar to the discipline needed in reproducible test environments: the cleaner the incident record, the easier it is to diagnose the failure.

How to escalate without sounding adversarial

If you believe the issue was handled incorrectly, focus on requesting review rather than demanding reversal. Ask whether there is a formal appeal process, what documentation they require, and how deadlines work. A good escalation script is: “We would like to understand the appeal steps for this incident and whether there is a submission deadline for supporting documentation.” That phrasing keeps the conversation procedural and gives you a clear next action.

When families are stressed, they may accidentally increase friction by arguing about fairness in the moment. A better approach is to save your energy for the written record and the appeal packet. That mirrors the mindset behind psychological safety in high-performance teams: calm, respectful communication leads to better outcomes than reactive escalation. In testing, the fastest path to help is often the most disciplined one.

How to Document Incidents for a Test Cancellation Appeal

Build a time-stamped incident log

If there is any chance of a cancellation or invalidation, create an incident log immediately after the session ends. Write down the date, scheduled test start time, actual start time, the sequence of events, and every instruction the proctor gave. Include device names, operating system versions if known, battery percentage before failure, internet status, and whether the second camera was plugged in. If multiple adults were present, have one person write the log while the other handles communication.

The goal is to preserve memory before it blurs. Even small details can matter later, such as whether the failure happened before or after a section break, or whether the proctor had already issued one warning. Think of this as the testing equivalent of a forensic record. In the same way a team might use a reliability benchmark to identify weak points, your incident log should reveal the exact weak point in the testing sequence.

Capture screenshots, photos, and device evidence

If the system allowed it and if you were instructed to do so, take screenshots of error messages, app freeze screens, or reconnect prompts. Photograph the physical setup after the issue, especially if the camera angle or cable position could be relevant. Save any automated emails from ERB or the testing app, and keep them in a dedicated folder. If a reboot or reconnection happened, note how long it took and whether any data appeared to be lost.

Be careful not to violate test rules while documenting. Do not use a secondary device to photograph the secure screen unless that is permitted and you are already out of the testing flow. Keep your documentation process separate from the exam process. For families who like checklists, it may help to borrow the mindset of pre-event planning: the smoother the setup, the less likely you are to miss critical details under pressure.

Organize your appeal packet logically

A strong appeal packet usually includes a short cover note, a chronological summary, supporting evidence, and any relevant correspondence. Keep the summary factual and concise, and attach screenshots or photos in the order the events occurred. If the proctor gave a direction that may have affected performance, quote it as accurately as possible. If the issue involved connection instability, include your internet provider name, router model if known, and whether other devices were affected at the same time.

Parents sometimes try to write a long emotional explanation, but decision-makers usually need a clean timeline first. Save the emotional context for a short closing note if required, and focus the main body on evidence. For a useful parallel on how to present information clearly under pressure, see How to track any package like a pro; the underlying principle is the same: trace the path, note the stops, and identify where the chain broke.

How to Prevent the Most Common Failures Before Test Day

Run a full mock test with both devices

The single best prevention strategy is a complete rehearsal: same room, same devices, same charging setup, same camera placement, and same app downloads. A mock test helps uncover weak Wi-Fi, poor lighting, and camera drift before they become official problems. It also gives the student practice staying calm while being observed, which is an underrated skill in remote proctoring. Do not assume a quick five-minute check is enough; use enough time to simulate the actual start-up sequence from login to final position check.

In tutoring, we often see students do well academically but get derailed by setup friction. That is why practical prep matters as much as content review. If you want a broader framework for organizing high-value preparation without overbuying tools, the ideas in building a productivity stack without buying the hype apply nicely: choose a small set of reliable tools and practice using them consistently.

Reduce household risk factors

Test day should be treated like a household event. That means disabling alarms, pausing loud appliances, informing siblings, and securing pets in another part of the home. If your internet connection is shared by multiple people, ask others to avoid streaming, gaming, or large downloads during the exam. If possible, connect the primary device by the most stable method available and leave the network alone once the session begins.

Families with busy homes should also think about routines, not just rules. The article on parenting routines and technology is useful because it frames stability as something you build ahead of time. The less you depend on reminders in the moment, the fewer chances there are for avoidable disruptions.

Know when the issue is likely to be non-recoverable

Sometimes a session can be rescued, and sometimes the best outcome is a clean cancellation rather than a compromised test. If the app repeatedly crashes, the internet drops multiple times, or the proctor cannot verify the testing environment, the probability of a valid score may fall quickly. It is better to preserve evidence and prepare for an appeal than to keep forcing a broken session. The key is not whether something went wrong; it is whether the problem can be fixed without creating a security violation.

This is also where families need realistic expectations. At-home testing is successful for most students, but it is still dependent on the reliability of the home environment. ERB’s model has been used successfully at scale, yet the system assumes a prepared household. Treat that assumption seriously, and your odds improve dramatically.

Comparison Table: Common Failures, Likely Cause, First Response, and Appeal Evidence

Pro Tips for Parents and Tutors

Pro Tip: Treat the at-home test like a lab experiment. The fewer variables you change on test day, the easier it is to prove that any failure came from the system rather than the student.

Pro Tip: Keep a printed one-page checklist beside the student. If the proctor calls out a problem, the checklist helps adults avoid improvising in ways that could violate secure testing rules.

Pro Tip: If you ever need to appeal, evidence collected in the first 10 minutes after the incident is usually more useful than a long memory-based explanation written days later.

Frequently Asked Questions

Final Takeaway: Calm, Document, Escalate

At-home testing succeeds when families prepare for the predictable failures before they happen. The most common problems—camera placement, background movement, battery loss, app crashes, and internet drop—are manageable if you treat them as operational issues rather than surprises. Keep your room controlled, your devices charged, your scripts ready, and your documentation organized. That approach protects both the student’s concentration and the integrity of the test.

If you want to strengthen the academic side of the process too, pair your technical prep with study support and structured review. Our guides on ISEE at-home testing, planning under pressure, and reliability-focused systems all reinforce the same lesson: stable outcomes come from deliberate preparation. When the proctor calls, the family that is ready to respond calmly is the family most likely to finish strong.

Related Reading

• ISEE Online At-Home Testing: What You Need to Know - A practical overview of devices, rules, and the at-home testing workflow.
• How to Build a Productivity Stack Without Buying the Hype - Useful for setting up a simple, reliable prep system.
• Resilient Routines: Harnessing Technology to Streamline Parenting - Helpful for reducing household disruption before test day.
• How to track any package like a pro: step-by-step tracking for online shoppers - A great model for writing clear incident timelines.
• Networking While Traveling: Staying Secure on Public Wi-Fi - Explains why locked-down environments can fail when networks are unstable.