Under Optional settings on the Review step, expand Integrity checks.
The four integrity checks
Remind candidates to work independently. Shows a reminder before the assessment. This is the only one that changes what candidates see, and it is the one with the best evidence behind it: asking people to be honest, at the moment it matters, changes behaviour more reliably than watching them.
Record when candidates leave the test tab. Notes when the test tab loses focus, so you can see it on the report.
Ask candidates to use full screen. Asks. It cannot force a browser to comply and it does not try to.
Vary question order where the test supports it. Shuffles the order of questions for tests built to allow it, which makes comparing answers with someone else harder.
Where the results appear
On each candidate's report, in a Browser observations panel just above the decision. It reports, across the whole assessment:
- Mouse exits, how many times the pointer left the test area.
- Tab hidden, how many periods the test tab was not the visible one.
- Full-screen exits.
- IP changes.
- Camera enabled, which reads "not available" because there is no camera check to enable.
The panel is labelled Coverage unknown and says so in its own words: "These are browser reports, not proof of cheating. Monitoring coverage is unknown, including across reloads and unsupported devices. No report does not mean an event could not have happened. An IP change does not establish a change of location."
Read that twice before you act on anything in it. In particular, an empty panel is not evidence that nothing happened.
What a flag means
The product says it plainly on the settings panel, and it is worth repeating: checks provide context for review, and a flag alone does not show that a candidate cheated.
A candidate who left the tab may have had a message pop up, answered the door, or opened the calculator in another window. A candidate who never left the tab may have had a second device beside them. The checks tell you where to ask a question, not what the answer is.
Using the checks well
- Treat a flag as a reason to ask, in the same tone you would ask about anything else on a CV. "I noticed the test tab lost focus a few times, was something going on?" is a fair question. An accusation is not.
- Look at the whole report next to it. The every answer in order view shows time spent per question, and an unusual pattern there is more informative than a tab-focus count on its own.
- Be consistent. If you only look at the flags for candidates you already had doubts about, the flags are confirming your doubts rather than testing them.
What none of them do
They do not verify identity, they do not watch the candidate through a camera, and they do not detect a second person in the room or a search in another browser. If you need certainty about who sat the test, the answer is a supervised stage later in the process.
See can candidates cheat? for the honest version of that question.
Telling candidates about the checks
Whatever you turn on, say so. Candidates who know a check exists behave differently from candidates who find out afterwards, and the second group is entitled to be annoyed. The welcome message on the assessment is a good place for one sentence about it. See the messages candidates receive.