Remote proctoring lets a candidate in a small town sit the same exam as someone next to a test center. It also puts a camera in their kitchen. Both facts matter, and a program that only thinks about the first will lose the trust of the people it tests.

Proctoring deters, detects and documents. It does not stop every attempt to cheat, and a program should be wary of any claim that it does. What it can do is protect the value of a score while treating each candidate as a person taking a test, not a suspect.

What proctoring is for

Start by writing down what you are protecting. For most programs it is two things: the item bank, which costs a great deal to replace, and the meaning of a pass, which the public relies on.

Then match the level of proctoring to the stakes. A low-stakes practice quiz needs none. A course final may need a locked browser and a recording. A licensing exam may justify a live proctor. Using the heaviest option everywhere adds cost and intrusion without adding much protection where the stakes are low.

Two modes, two trade-offs

Most programs choose between record and review and live proctoring, or use both for different exams.

  • Record and review. The session is recorded and events are flagged for a person to review afterward. Candidates test when it suits them. In Exampit, a trained reviewer looks at every flag within two business days. Indicative price from $6 a session.
  • Live. A proctor watches in real time and can talk to the candidate. Problems such as a frozen camera are fixed during the session. Exampit live proctors watch up to six candidates each. Indicative price from $18 a session.

Live proctoring is more personal and more expensive. Record and review is more flexible and depends on the quality of the review. Neither replaces good exam design. A deep item bank and several rotating forms limit what any one leaked item is worth, and a camera cannot do that.

Some programs mix the two: live proctoring for the first attempt at a high-stakes exam, record and review for retakes or shorter modules. Whatever the mix, write down which exams use which mode and why, so candidates and staff can see the rule rather than guess at it.

Tell candidates before test day

Surprises are where most complaints start. A candidate who learns about the room scan at check-in feels watched; one who read about it a week earlier feels prepared.

Send a plain-language notice when the candidate books. It should cover:

  1. What is recorded: camera, microphone, screen, or all three.
  2. What the room check involves, and what to clear from the desk.
  3. What is allowed: water, scratch paper, a calculator, medical items.
  4. What happens if a connection drops, and how to reach support.
  5. Who sees the recording, and for what purpose.
  6. How long recordings are kept, and when they are deleted.
  7. How to request an accommodation, and by when.
  8. How a flag is reviewed, and how to appeal a decision.

Offer a practice session with the same check-in and software, at no cost to the candidate. It catches webcam and bandwidth problems before they matter, and it lowers anxiety on the day.

Keep the record proportionate

Collect what you need to decide whether a session was valid, and nothing more. That principle covers most privacy questions.

  • Do not record outside the exam session.
  • Limit the room check to the testing area, and say so in the notice.
  • Restrict access to recordings by role: reviewers and the integrity staff who handle cases.
  • Set a retention period in your policy and apply it. Keep longer only when a case is open.
  • Make sure your contract with the proctoring provider says where data is hosted and how it is deleted.

Exampit hosts data in the United States, encrypts it in transit and at rest, and deletes our copies within 30 days of exit after a full export. The details are on our security page. Your own counsel should review the privacy notice against the laws that apply to your candidates.

A flag is not a finding

Software notices events: a face leaves the frame, a second voice is heard, a window loses focus. Each is a reason to look, not a conclusion.

Many flags have ordinary explanations. A candidate looks away to think, reads aloud to themselves, or uses a screen magnifier that moves their eyes across the screen. A child walks in. The doorbell rings.

A fair process puts a trained person between every flag and every consequence:

  • The reviewer watches the flagged moment and the context around it.
  • The reviewer records what they saw and their reasoning.
  • Only a confirmed concern goes to the integrity team.
  • The candidate hears what was observed and can respond before a decision.
  • Appeals go to someone who was not part of the first decision.

Where AI helps flag events, it proposes and a person decides, with the decision and its reason kept in the audit trail.

Accommodations come first

Proctoring rules written for a typical candidate can quietly exclude others. Plan accommodations as configuration, set before the window, not exceptions improvised by a proctor.

Common examples include extra time, extra breaks, a screen reader or magnifier, speech to text, a service animal in the room, a caregiver nearby, medical devices on the desk, and permission to stand or move. Each should be approved, recorded against the candidate and visible to the proctor or reviewer, so a permitted behavior does not become a flag.

Some candidates cannot test at home at all: no private room, no reliable connection, no webcam. Keep a test site or a loaner option for them. Our accessible exam checklist lists accommodations and how each is usually configured.

Example: one flag, handled well

Example scenario. Say a candidate on a record and review licensing exam is flagged four times for looking off screen. The reviewer opens the session and sees the candidate has an approved accommodation for a second monitor with screen magnification.

The reviewer notes that the eye movement matches the magnifier, records “no concern, approved accommodation” and closes the flag. The candidate never hears about it, because there is nothing to hear. The record shows who reviewed it, when, and why.

Now say the accommodation had not been recorded. The same review would end with a question to the candidate, not an accusation, and a fix to the accommodation process so it does not happen again.

Measure fairness, not just flags

Track a few numbers each window: flag rates, confirmed concerns, appeals, technical failures and candidate complaints. Look at them by group where you can, such as device type or testing location, to see whether one group is flagged much more often for reasons unrelated to conduct.

If a pattern appears, look at the rules before the candidates. A setting that flags every glance away will fall hardest on candidates with certain disabilities or in busy homes.

If you already suspect a problem with an exam, our Integrity Review program (indicative, from $3,500 per exam) reads response patterns, timing and proctoring records calmly, before anyone is accused.

What to do this week

  1. Read your current candidate notice and check it against the eight points above.
  2. Find out who reviews flags today, how they were trained and how long reviews take.
  3. Confirm that approved accommodations reach the proctor or reviewer.
  4. Write down your recording retention period, or note that you do not have one.
  5. List the exams where you use proctoring, and ask whether each one needs that level.

Our remote proctoring software offers record and review and live modes on the same record as the exam, with accommodations and review notes kept together. We are happy to walk through how a flag moves from event to decision in a 30-minute demo.