Keep an Exam Proctoring Exception Log

Define an exception

An exam proctoring exception is an event that prevents the session from following the standard process. Examples include a failed identity check, a platform outage, a lost connection, an accommodation that was not applied, or a suspected policy violation. The definition should be written before the exam window.

Not every technical hiccup is an exception. A brief page reload may be recoverable without review. Define the threshold, the required evidence, and the owner so the log does not become a transcript of every click.

Record the facts

Record the student, exam, session, time, exception type, observed evidence, action taken, and owner. Use objective language. Do not include guesses about intent or sensitive personal details that are not needed for the review.

Preserve the relevant logs or screenshots according to policy. If the evidence includes identity documents or personal information, limit access and follow the retention rule. A proctoring exception log is not a general student record.

See how the related specialist service can support this operating lane while your team retains accountable decisions.

Route by exception type

A technical exception may go to the platform owner, an accommodation exception to the accommodation office, and a suspected violation to the academic integrity owner. Each route needs a response expectation and a decision owner.

The proctor or assistant can document and route. The decision to invalidate an exam, grant a retake, or impose a sanction belongs to the authorized academic owner. The log should not imply a decision that has not been made.

Communicate with the student

Use neutral language. Tell the student what will happen next, who will review the issue, and when to expect an update. Avoid accusing the student or promising that the exam will be reset.

If the student needs to take an action, such as uploading evidence or contacting the instructor, state it clearly. Keep the communication with the exception record.

Continue with this related education workflow guide.

Review patterns

Review exceptions by type, platform, time, and accommodation status. A cluster of connection failures may indicate a platform problem, while a cluster of identity failures may indicate a confusing check or a device issue.

Use the pattern to improve the exam instructions or the platform. Do not use it to rank proctors or students without context. The goal is a fair and reliable assessment process.

Pilot one exam window

Run the log for one exam window and a defined group. Review the exception types and the routing. Adjust the definitions before the next high-stakes window.

The goal is a record that supports a fair review without turning the proctoring team into judges.

Common questions