Every score change needs to be explainable a year later
Scores get corrected — an item is voided, a key is fixed, a session is regraded. Whether that is defensible depends on what was recorded at the time.
Proctoring produces evidence about a room, not a verdict about a person. Treating its output as a decision is where institutions get into trouble.
2 min read
Written by
Seratlas Team
Engineering and delivery
2 min read
We build and operate assessment software. We write here about the parts that are harder than they look.
A proctoring system observes a webcam feed, some browser events, and occasionally a desktop. From that it produces flags: a face left the frame, a second voice was audible, a window lost focus. Every one of those is a fact about a room.
None of them is a fact about cheating, and the distance between the two is where most of the harm in this field happens.
Flags arrive in a queue, sorted by a confidence score, in an interface that asks for a decision. Everything about that presentation implies the system has found something, and the reviewer's job is to confirm it. The base rate works the other way round: most flags in most exams are innocent, because looking away from a screen is what people do while thinking.
A reviewer processing two hundred flagged sessions under time pressure is not applying a prior. They are clearing a queue.
Matching a candidate to a credential at the start of a session is the part of proctoring that works, and it addresses the substitution case, which is the most consequential form of exam fraud.
A room scan establishes what was visible for the seconds it took. It does not establish what was outside the frame, which is most of the room.
No signal available to a proctoring system distinguishes consulting a note from looking at a wall. The inference is entirely the reviewer's, and the system's confidence score describes how unusual the signal was, not how likely the conclusion is.
Separate the flag from the finding, in the record as well as in the procedure. A session log should say what was observed; a decision record should say who concluded what from it, and on what other evidence. Systems that store a verdict where the observation belongs make an appeal impossible to conduct, because the original signal is no longer recoverable.
Give the candidate the material. An allegation supported by a recording the candidate cannot see is not one they can answer, and in several jurisdictions that is not merely unfair but unlawful.
Keep a human decision in the loop and make its authorship explicit. "The system flagged you" is not a decision anyone can be held to, which is exactly why it is the sentence institutions reach for.
Proctoring is often bought to make a claim to an accreditor rather than to detect misconduct, and it succeeds at that regardless of whether its flags mean anything. That mismatch is worth naming internally before the first appeal arrives, because the appeal is where the claim gets tested.
Scores get corrected — an item is voided, a key is fixed, a session is regraded. Whether that is defensible depends on what was recorded at the time.
Static hosting removes a class of outage from the pages candidates see first, and costs less than the runtime it replaces.
If a candidate cannot operate the interface, the score measures the interface. That makes accessibility a measurement concern, not a compliance one.
A bank that is too small stops measuring knowledge and starts measuring who has seen the questions. The arithmetic is unforgiving and easy to check.
If any of the above is a problem you are currently having, we are happy to talk about it without a sales process attached.