ExamLense

Platform

Every part of a defensible online exam

Identity settled before the paper opens, detection while it is open, and a human decision afterwards with the evidence attached. Here is how each piece works.

Identity verification

Settle who the candidate is before the paper opens

Authentication is not identity proofing. However a candidate signed in, the identity check still runs: an ID document, a live selfie, and a name matched against the roster you supplied.

  • The name is read from the ID document automatically. Adding a new country card is a configuration change, not a new integration
  • The name is fuzzy matched against the candidate record and the institution roster, so spelling and ordering differences do not fail an honest candidate
  • The live selfie is matched to the document photo at a high, configurable similarity threshold
  • A failed match goes to a manual review queue. Nobody is silently hard blocked from an exam they are entitled to sit

In-exam proctoring

Watch at the depth the exam actually warrants

Three tiers exist so an institution can buy the level of scrutiny an exam justifies rather than paying for maximum surveillance on every quiz. All three verify identity, watch for a face, lock the browser, and catch an extra display or a prohibited assistant. What changes is how much is captured and kept.

  • Identity verification with guided capture before the exam opens
  • A live face check at the moment the exam starts
  • Face presence monitoring for the whole session
  • Camera integrity checks that catch a frozen, covered or fabricated feed
  • Fullscreen lockdown, with tab-switch and focus-loss detection
  • Additional-display detection
  • Prohibited AI extension detection
  • An append-only record of every flag and decision

Lite

Identity and face monitoring, with nothing recorded

A verified, browser-locked exam with the candidate watched throughout, and no screen capture and no recording at all. The right choice for high-volume, cost-sensitive assessment: aptitude tests, recruitment screening, and routine coursework.

  • Face presence is checked continuously and identity is re-confirmed periodically through the session
  • Nothing visual is retained: the checks happen and the frames go
  • The lightest bandwidth demand of the three, which is what makes it usable on a constrained campus

Locked browser extension: optional

Pro

Continuous recording, room scans and live intervention

The complete set. Continuous webcam and desktop recording, room and desk scans before the exam, an optional second camera from the candidate’s phone, speaker detection on the audio, and monitors who can step into a live session. Required where the evidentiary chain has to be complete.

  • Both feeds record continuously, so a reviewer can jump straight to the moment a flag was raised
  • Guided room and desk scans establish the environment before the paper opens, and a monitor can ask for a rescan at any point
  • The candidate’s phone can act as a second camera for a side view of hands and desk, which is far more available than a second webcam in our markets
  • Speaker detection on the audio flags sustained dialogue, which is what coaching sounds like
  • Monitors can message a candidate in their own language, approve a scan, or pause a session, and an alert fires if a Pro exam starts with nobody watching

Locked browser extension: required

SecureBrowser

A locked browser that proves it is still locked

SecureBrowser is a browser extension that confines the candidate to the exam window. The important part is the second half: it proves to us that it is genuinely running, rather than being taken at its word.

  • New tabs close, and navigation away from the exam is blocked
  • Clipboard, downloads, and printing are disabled for the session
  • It proves it is running continuously, and lockdown status is confirmed on our side. A client claiming to be locked is not evidence that it is
  • Optional on Lite, recommended on Standard, required on Pro
  • Because it is optional on two tiers, the exam itself also detects an additional display, a duplicate window, and prohibited AI extensions without it

Review Console

A person decides, with the evidence in front of them

Flags and risk scores are inputs to a human decision, never a verdict. Risky sessions are promoted into review cases and land in a queue with the evidence attached.

  • A live monitoring grid for sessions in progress, updating as the exam runs
  • An evidence timeline that puts every flag beside the moment it occurred
  • Dismiss, confirm a violation, or escalate, with the reasoning recorded
  • High-stakes exams can require a second reviewer to agree before a violation stands
  • Reviewers cannot alter exams, rules, or licences, and administrators cannot overturn a review decision

Exam delivery

The server is the referee

The candidate machine is not trusted with anything that matters. Timing, scoring, and licence consumption are all decided server side, which is what makes a result defensible.

  • The countdown runs on our side. A candidate who changes their own clock changes nothing
  • Answers auto-save as the candidate works, so a crash costs seconds rather than a paper
  • Disconnection is a pause with a configurable grace period, not a failure
  • Force submit at zero, and a licence consumed in a single atomic step so a pool cannot be oversold
  • Exam rules are versioned, and the version in force is stamped onto the session and never mutated afterwards

Integrations

Launches from the system your institution already runs

Candidates never create ExamLense accounts. They arrive through one of three routes, and all three end in a short-lived token scoped to a single exam.

  • LTI 1.3, which every major LMS supports, so the launch, the roster sync and the grade return all work out of the box
  • Single sign-on from your own identity provider
  • Passwordless: an invitation link plus a one-time code by email or SMS
  • Staff sign in separately, with multi-factor authentication

Two modes that are not tiers

Verification on its own, and screens without a camera

Both are configurations of the same session rather than separate products, so they behave the same way and are bought the same way.

Identity only

The candidate verifies and the session ends. For enrolment, credential checks, and pre-screening where no examination follows.

Screen monitoring only

Desktop evidence with no camera at all. For workplace compliance testing where camera monitoring would be disproportionate, and for candidates whose accommodation excludes camera use.

A sitting, end to end

What a candidate actually goes through

See the whole chain on one of your own exams

We will run a sitting end to end, including a deliberate flag, so you can see exactly what a reviewer would be looking at when they make the call.