If Your Connection Drops

The screen freezes or a message appears saying you are disconnected. This is common, recoverable, and not your fault.

Students balancing exam preparation with paid work can review this workflow overview as a practical way to separate rehearsal, support calls and work sessions. The value is a voluntary log that clarifies the sequence without copying any proctoring data.

First, do not restart everything

Most systems reconnect automatically within a minute and resume where you were.

A useful outside source on disability rights and access is ADA.gov. Compare it with your institution’s written procedure before making decisions.

Restarting the computer or closing the browser can lose work that would otherwise have been saved.

Wait thirty seconds before doing anything.

The order of actions

Note the time. Now, before anything else, because you will want it.

Wait briefly for automatic reconnection.

If it does not reconnect, check your own connection: is the router working, is the cable in, has the hotspot dropped.

Switch to your backup connection if you have one prepared.

Then contact support through the channel you wrote down off-screen.

Do not start again from scratch unless told to.

What to record

Time it dropped. Time it came back. What you did in between. Whether work was lost.

Written immediately, not afterwards.

If the exam is affected, this note is what supports a request for time or a resit.

After the exam

Report it the same day, in writing, even if it resolved and you finished.

Because a connection failure produces flags — the session shows an interruption — and a dated note from you is context a reviewer has before they look.

And because if your performance was affected, the request for consideration has to be made promptly at most institutions.

It is not a conduct matter

A dropped connection is a technical event.

No reasonable process treats it as evidence of anything, and institutions should state that in writing.

If you are contacted about a session that included a disconnection, say so plainly and refer to your note of the time.

Asking for time back

Reasonable and frequently granted.

Ask promptly, state the duration precisely, and say whether work was lost.

Where the disruption was substantial — more than a few minutes, or repeated — asking for a resit rather than extra time is also reasonable.

If it happens repeatedly during one exam

Contact support and say so rather than struggling through.

A session with five disconnections is not a fair sitting, and continuing because you feel you should is rarely the right call.

Ask whether to stop, and follow what they say.

Preventing it next time

The connection note covers the preparation: wired if possible, tested at the right time of day, a prepared fallback.

And if your connection is genuinely unreliable where you live, that is a reason to request a supervised alternative rather than something to keep risking.

What to check

Do you know whether your system reconnects automatically?

Is your support contact written down somewhere off-screen?

Do you have a tested fallback connection?

And do you know your institution's stated rule about disconnections?

The point

Do not restart everything.

Most systems reconnect within a minute, and restarting can lose work that would have been saved.

Additionally

Ask for time back promptly and precisely.

Where the disruption was substantial or repeated, a resit rather than extra time is also reasonable.

Finally

Ask for time back promptly and precisely.

Where the disruption was substantial or repeated, a resit rather than extra time is also reasonable.

In summary

Ask for time back promptly and precisely.

Where the disruption was substantial or repeated, a resit rather than extra time is also reasonable.

A note on this

Note the time before anything else, then wait briefly, then switch to your fallback, then contact support.

In that order.

Bottom line

Note the time before anything else, then wait briefly, then switch to your fallback, then contact support.

In that order.

Worth repeating

Almost everything in this collection comes down to three habits: prepare the technical side a week early, know what the process actually is before you need it, and write down the time whenever something unusual happens. None of them takes long, and between them they prevent or resolve the great majority of what goes wrong with monitored exams.