AI proctoring uses machine learning to watch a remote exam in real time and log timestamped events when behaviour breaks your rules. Instead of a human staring at every screen, software flags multiple faces, tab switches, prolonged absence from the camera, and suspicious audio so reviewers judge flagged cases, not every session.
Schedule a DemoWhen a university moves from hall invigilation to online delivery, the monitoring problem does not disappear. It shifts from “one person watching forty desks” to “someone has to watch four thousand browser tabs.” Hiring enough live proctors for that scale is expensive and inconsistent. AI proctoring automates the watch step.
During the attempt, models trained on exam-integrity signals analyse the webcam and microphone feed. When behaviour drifts from the rules you configured (extra faces, leaving the frame, switching tabs, background voices), the system records a timestamped event with supporting stills. Faculty or exam administrators then review only the sessions that triggered flags.
That workflow is what made 12,000 SPPU entrance candidates and 60,000 Natview fellowship sessions feasible without staffing a control room for every screen. AI handles continuous monitoring; humans stay in charge of outcomes.
Vendor marketing lists vary, but these five signal types cover most institutional exam rules. Use the table below when comparing tools: the difference is not whether AI can “detect cheating,” but how clearly it documents each event for your appeals process.
| Signal | What AI watches | Typical trigger | What reviewers see |
|---|---|---|---|
| Multiple faces in frame | Computer vision counts faces visible to the webcam during the attempt. | A second person enters the camera view or the candidate shares the screen with someone off-camera. | Timestamped still image showing how many faces were detected at that moment. |
| Absence from camera | Whether the candidate remains in frame for the duration of the quiz. | Looking away for notes, leaving the desk, or a poor webcam angle that hides the face. | Event log with duration and a capture from when the absence started. |
| Browser tab movement | Focus changes away from the exam tab while questions are active. | Searching for answers, messaging, or opening reference material in another tab. | Timestamped flag with configurable warnings before the event is logged. |
| Ambient audio | Microphone input for voices or sounds that suggest off-screen coaching. | Someone reading answers aloud or whispering from outside the frame. | Audio event entry alongside visual flags in the same review timeline. |
| Identity at start | Baseline photo capture when the quiz launches, with optional ID upload for higher-stakes settings. | Mismatch between enrolled student and person at the keyboard before questions appear. | Reference still from exam start for comparison during later reviews. |
Both approaches supervise remote exams. The operational split is who watches continuously and how cost scales with cohort size. Many institutions run a hybrid: AI for volume, humans for flagged or high-stakes sessions.
| Dimension | AI proctoring | Live human proctoring |
|---|---|---|
| Who watches the feed | Software analyses webcam and microphone input continuously during the attempt. | A trained proctor watches a small group in real time and can intervene live. |
| Scale per exam window | High. SPPU ran 2,000+ simultaneous sessions; NFTI processed 60,000 sessions over four months. | Low. Each proctor typically covers a handful of candidates at once. |
| Cost at volume | Lowest when reviewers focus on flagged cases only, not every session. | Highest. Headcount scales linearly with candidate count. |
| False positives | Higher for ambiguous context (family walking behind, poor lighting). Needs human review. | Lower for intent judgement, but fatigue and inconsistency rise over long shifts. |
| Data handling | Event-based logs and stills; ProctorLink stores artefacts on your Moodle server. | Often streams video to vendor cloud unless configured for on-premise retention. |
| Best fit | Frequent quizzes, entrance grids, fellowship programmes, and distributed cohorts. | Regulated finals where accreditors require synchronous human oversight. |
AI proctoring should not force students into a separate vendor portal. With ProctorLink, administrators enable monitoring per quiz inside Moodle, and reviewers work from the same LMS they already use.

AI proctoring is no longer experimental. These are deployment patterns from ProctorLink customers:
Across these deployments, ProctorLink has supported more than one million proctored exam sessions (see published case studies and methodology note below).
Institutions evaluating proctoring tools often look for independent feedback outside vendor case studies. ProctorLink is listed on G2, where Moodle administrators and training teams share verified product reviews.
Read ProctorLink reviews on G2 →Deployment statistics and product behaviour described in this guide link to the sources below.
Evaluating AI proctoring for your next exam cycle? These pages cover implementation, pricing, and deployment evidence.
30-minute session mapped to your LMS setup, exam calendar, and cohort size.
Subscription tiers for steady exam cycles and credit packs for seasonal peaks.
SPPU, RT-MSSU, and NFTI: numbers, timelines, and what broke before it worked.
quizaccess_quizproctoring plugin. Typical go-live in one to two business days.
Concurrency, faculty review workflows, and integrity at entrance-exam scale.
AI proctoring for credential programmes without physical test centres.
ProctorLink runs AI proctoring inside Moodle, keeps flagged evidence on your servers, and leaves outcomes to your faculty.