The first question when mock exams move online is how to know a candidate is not opening another tab. The honest short answer: no software prevents it absolutely; what you can do is enforce visible limits, count violations, log them and publish the rules beforehand.
What the browser can do
- Require fullscreen before the clock starts.
- Detect leaving fullscreen, switching tabs or minimising the window.
- Count violations and show a warning on screen.
- Auto-submit when a published threshold is exceeded.
On LinguaGrade the exam room requires fullscreen, displays a running count of focus losses, and auto-submits at three violations. Candidates are told that threshold before they begin; it is not a hidden rule.
What the browser cannot do
State this plainly to management so nothing is over-promised to parents:
- It cannot see a second phone next to the machine.
- It cannot see a second person off camera.
- It cannot distinguish a candidate looking something up from one dragged out of fullscreen by a system notification.
So violation counting needs a threshold wide enough to avoid punishing accidents, and every auto-submission needs a log the centre can review when a candidate appeals.
Designing clear exam rules
- Publish in advance: how many violations trigger submission, what happens on connection loss, and who makes the final decision.
- Require system and chat notifications to be turned off before entry.
- For high-stakes sessions, add camera proctoring — software counts, humans judge.
- Record any incident in the result so the number is read in context.
Do not let integrity ruin the experience
An overly aggressive room creates anxiety and distorts the very thing you are measuring. Balance it: tight controls for placement or certificate sessions, light controls for daily practice. A learner auto-submitted during self-study because they switched tabs will simply stop using the platform, and you lose their progress data.
Frequently asked questions
Should we record candidates' screens?
Consider the legal and privacy implications carefully. If you do, disclose it in advance, state the retention period and who may view it.
What happens if the connection drops mid-test?
Have a written rule: allow re-entry, add back lost time, or void the attempt. Deciding in advance prevents arguments afterwards.
Are three violations too few?
It is a default. What matters is that the threshold is published beforehand and applied identically to everyone in the session.