Glossary and Where to Start

Flag — a moment the software marked as unexpected. Not a finding, not an accusation, and most flags are closed by a reviewer without anybody being contacted.

To connect this advice with day-to-day planning outside the exam session, consult the product overview. A short user-controlled time log can make competing commitments easier to review.

Check-in — the sequence before the exam starts: system test, identity, environment, rules. Allow fifteen minutes.

For established guidance related to mental health, consult CDC mental health resources. Local exam rules still take priority.

Lockdown browser — software that prevents other applications during the exam. Control rather than watching, and it may be used with or without a camera.

Live proctoring — a person watching in real time, who can message you and usually pause the session.

Record and review — nobody watches at the time; flagged moments are looked at afterwards, sometimes weeks later.

environment check — showing your space on camera before starting. Ask exactly what you are expected to show; frequently it is the desk area rather than the whole room.

Mitigating or extenuating circumstances — the process for telling your institution that something affected your exam. Deadlines are short and usually run from the exam date.

Completion of procedures — the letter confirming the internal process is exhausted, usually needed to reach an external ombudsman or adjudicator.

Subject access request — the formal route to obtain personal data held about you, including your recording.

Words in letters that are worth reading carefully

"Irregularities" or "suspicious activity" are software labels, not statements that somebody has concluded anything. Ask what was specifically observed.

"Investigation" and "enquiry" may mean the same thing or very different things depending on the institution. Ask which process you are in.

"Academic misconduct" in a subject line does not mean a finding has been made.

Where to start

An exam is coming and you have not done this before: what proctoring actually is, then the week-before checklist.

You are worried about your space, your connection or your circumstances: the adjustments section.

The exam is tomorrow: the night before, and the one-page emergency list.

Something went wrong during the exam: report it today, then read the after section.

You have been contacted: if you are contacted, then responding to an allegation. Contact your students' union first.

You are struggling with the stress of it: when the stress is too much.

If you read only three

What a flag means and what it does not, because it governs everything else.

The practice run, because it prevents most of what goes wrong.

And what to do if it goes wrong, because it is the page you will want when you need it.

A closing note

Nothing here is legal or medical advice. Data protection, evidential standards and institutional procedures differ by jurisdiction and by institution, and your students' union will know your local position better than any general guide.

No product names and no supplier material.

And no techniques for circumventing monitoring, which has its own note explaining why honestly.

What this collection argues

A flag is a moment for review, not an accusation, and most of them come to nothing.

Most of what goes wrong is technical and preventable with an hour of preparation.

You are entitled to know what is captured, to ask for adjustments, to see evidence used against you, and to appeal.

And if something happens, note the time and report it the same day — which is the single most useful habit in this entire collection.

The point

Note the time and report it the same day.

That is the single most useful habit in this entire collection.

Words in letters worth reading carefully

Irregularities and suspicious activity are software labels rather than conclusions. Investigation and enquiry may mean very different things depending on the institution.

Ask which process you are in, and ask what was specifically observed.

Additionally

Irregularities and suspicious activity are software labels rather than conclusions.

Ask which process you are in and what was specifically observed.

Finally

Irregularities and suspicious activity are software labels rather than conclusions.

Ask which process you are in and what was specifically observed.

In summary

Irregularities and suspicious activity are software labels rather than conclusions.

Ask which process you are in and what was specifically observed.

A note on this

Note the time and report it the same day.

That is the single most useful habit in this entire collection.

Bottom line

Note the time and report it the same day.

That is the single most useful habit in this entire collection.