Skip to content
← All resourcesTRUSTEXAM RESOURCES

Why video alone is not enough for exam integrity

Video, device checks and human review: how to combine session evidence without treating a risk signal as a proven violation.

Video shows what happened in front of a camera. It does not fully describe the participant’s device, available applications or activity outside the frame. For exams that affect admission, qualification or access to work, those limits matter.


What can remain outside the frame

Unauthorised help may arrive through another device, remote access or a person outside the camera view. Participant impersonation and a substituted video source also require their own checks. Calm behaviour on camera does not establish that these risks are absent.


The reverse is equally important: a glance away, a pause or a movement does not prove misconduct. Monitoring should produce material for review, rather than interpret every deviation as cheating.


Five parts of an integrity workflow

Identity

Confirm who begins the exam and agree when another identity check is appropriate. Choose procedures that reflect the stakes, age and needs of participants.


Exam environment

Define permitted materials, applications and devices. Controls should fit the task: a coding assessment may require tools that are prohibited in another exam.


Device checks

Supported technical checks can help identify configuration changes or signs that need investigation. Validate the actual checks, device support and permitted exceptions in the selected delivery mode.


Event context

Camera footage, screen recordings and device events are useful when reviewers can compare their timing. Related signals may justify closer inspection, but they do not remove the need to consider innocent explanations.


Review and appeal

Reviewers need the underlying evidence, decision criteria and a way to record their reasoning. Participants need a clear appeal route. An automated risk assessment is not a proven violation.


Assign responsibilities

The organiser defines exam rules and permitted exceptions. The technical team validates the integration, devices and infrastructure. The people responsible for data agree access, storage and deletion. Reviewers assess events and record their reasons; the designated appeals process handles disputed decisions.


Begin with a focused pilot

Choose one exam type and the smallest set of controls that meets its needs. Prepare instructions, run practice sessions and pilot the process with representative participants and reviewers.


Before expanding, evaluate successful starts, support requests, review time, consistency of decisions and appeal outcomes. The number of automated flags alone says little about the quality of the process.


How TrustExam fits

TrustExam connects identity checks, configured environment controls, content protection and session review. Demonstrate the complete path from participant access to a reviewed result and an appeal. Video remains part of this workflow; its value comes from linking events to the technical context and the programme’s rules.


Explore the TrustExam workflow · Review signals and appeals


Related reading

YOUR PROGRAMME. YOUR NEXT STEP.

Let’s explore how this works for you.

Request a demo