ExamGuard verifies who enters an examination hall, and keeps a record of every decision it helps produce. This page explains the whole flow — from setting up the examination to ending the session — without technical jargon.
The short version: the system compares a live camera image with an enrolled reference photo, checks that a real person is present, and hands anything it is not sure about to a human. Every step leaves a trace.
1. The examination is created
Examination staff create a session with the subject, date, time, semester, department, exam hall, and seats. Students who are registered for that examination appear in the system with their seat allocation.
Nothing about the student is guessed — the record comes from the institution's own registration data.
2. A reference photo is enrolled for each candidate
Before exam day, staff enroll one clear face photo for each candidate from the dashboard. This photo becomes the candidate's reference face.
The reference photo is what the camera will compare against at the hall door. It can be replaced at any time if a better photo is available.
3. The invigilator is assigned
Each examination session is assigned to an invigilator. Only that invigilator (and administrators) can manage the session, run verification, and view its results.
4. The session is started
On exam day, the invigilator starts the session. The session moves from Not Started to In Progress, and it can only be started once — a second attempt is refused instead of creating a duplicate.
5. The candidate checks in on camera
At the hall, the candidate sits in front of the camera and a live image is captured. Two separate checks run on that image:
Face Similarity (identity check)
Compares the live camera image with the enrolled reference photo and produces a similarity score. The score is a comparison of the two faces — it is not a percentage chance of being the right person.
Live-Person Check (liveness check)
Checks that a real person is in front of the camera, rather than a printed photo or a video replayed on a screen. This check is independent of the identity check.
6. Evidence is collected
Both results — identity and liveness — are stored together as an evidence package with the images, scores, and timestamps used for that attempt.
The evidence package is what a reviewer (or an auditor later) can look at. Nothing about the attempt is judged without evidence being kept.
7. A decision is made — or held for a human
The decision engine evaluates the evidence against fixed, server-side thresholds:
- Clear identity match and passing liveness — entry is granted (MATCH).
- Identity clearly does not match — entry is denied (NO_MATCH).
- Scores land in an uncertain middle range — the result is INCONCLUSIVE. An uncertain result never silently becomes a pass or a fail.
8. Uncertain cases go to a person
When a check-in comes back INCONCLUSIVE, the invigilator reviews it. The review panel shows the reference photo, the captured image, the identity and liveness results side by side, and why the automatic decision was inconclusive.
The invigilator then records a decision — Check In (the candidate may enter) or Check Out (the candidate may not enter) — and gives a reason. The system records who decided, when, and why.
The AI never makes the final call on an uncertain case. Human review is always available.
9. Attendance and the audit trail are recorded
Every granted entry, denied entry, and manual review decision is written to the attendance record and to an append-only audit trail of events.
Corrections are appended, not overwritten — the original history stays intact, so any decision can be traced back to its evidence.
10. The exam runs, then the session is ended
While the session is in progress, the invigilator can monitor candidates and their verification history. When the examination finishes, the invigilator ends the session.
The session moves to Completed, the end time is recorded, and the record stays available for review and reporting. Ending a session asks for confirmation first, so it cannot happen by accident.
What ExamGuard does not do
- It does not decide who enters on its own — uncertain cases are always referred to the invigilator.
- It does not quietly discard results it dislikes — denied and inconclusive attempts stay on the record with their evidence.
- It does not let one person do everything — candidates, invigilators, and administrators each have their own role and permissions.
Where to go next
Questions about how your data is handled are covered in the Privacy Policy. Terms of use are in the Terms & Conditions.