How to read a session report: second monitors, virtual cameras and other harmless signals
A signal is a fact about the machine, not proof of cheating. What each of the five lines means, its harmless causes, the two levels, and how disputes work.
Each line in a session report is a fact about the machine during the interview, printed with its harmless causes. There is no score and no threshold. Read the line, check the recording at that moment, weigh it against the answers, and never base a decision on a line under dispute.
The session report is generated when the interview ends, and both sides receive the same file. It has five lines, two levels, no score and no verdict. This guide is for the recruiters and interviewers who read it and make a decision afterwards.
What the report is, and what it is not
Each line is a fact about the machine during the session: a window was hidden from screen capture, a virtual camera was in use, a second display was connected. Nothing appears on either screen during the interview. The report exists only after the session ends.
A signal is not proof of cheating. A virtual camera belongs to a streamer, a second monitor to a developer, and the report prints the harmless causes next to every line. Answer timing is used only as context for a system signal and never produces a signal by itself. Voice, gaze, posture and facial expressions are not analysed at all.
The five lines
| Line | What it reports | Common harmless causes |
|---|---|---|
| Hidden windows | Windows hidden from screen capture during the session | Recording tools and some wallpaper apps |
| Known AI copilot processes | A process from the known interview-copilot list was running | A code assistant inside an editor is a different signature and is not on the list |
| Virtual camera or audio | Video or audio arriving from a virtual device | OBS for streamers, noise suppression drivers |
| Second monitor | A second display was connected, and for how long; never its contents | Most developers work on two screens |
| Liveness | One check at the start that a live person is on camera | Not face recognition and not an ID check; never repeated during the interview |
The copilot list is published and updated weekly.
Note and attention
Signals have two levels, note and attention, and neither is a verdict. A note records a fact with its usual explanation, such as a second monitor connected for the whole session. Attention marks a line that is worth checking against the recording. There is no score to add up and no threshold that turns lines into a decision.
How to read a line
- Read the harmless causes printed next to it. Most lines end there.
- Open the recording at the moment the line refers to; the report and the recording share one timeline.
- Compare the line with the answers around it. A signal next to answers that stay the same in depth and rhythm means little. A signal next to answers that change says more, and it is still a question, not a conclusion.
- If a question remains, ask the candidate. The candidate has the same report and can explain it.
- Write the decision into the decision log with the evidence it rests on: the scorecard lines, the quotes and the timecodes.
Three examples
These are typical reports, simplified.
- Second monitor, whole session, note. A developer with two screens, answers steady throughout. Nothing to do.
- Virtual camera, whole session, note; liveness confirmed. A streamer's camera setup, and the check at the start confirmed a live person on camera. Nothing to do unless something else in the session raises a question.
- Known copilot process for six minutes in the middle of the session. Open the recording at that moment and compare the answers before, during and after. The decision stays with the interviewer, and the candidate can dispute the line within 14 days.
Disputes
Any line can be disputed within 14 days of the report, with an explanation attached. A Vettasy reviewer looks at the underlying data, only within the dispute and with every access logged. The outcome is confirmed, withdrawn or inconclusive, and both sides see it. While the dispute is open, the line cannot be grounds for rejection. Dispute outcomes and the false-positive rate are published quarterly in the Trust center.
What not to do
- Treat a line as proof. It is a fact with context.
- Reject on a note.
- Count lines and compare candidates by the total. There is no score by design.
- Base a decision on a line while its dispute is open.
Sources
- Vettasy, Verified Session, AI Notice and Trust center.
Written by the Vettasy teamVettasy is a desktop application for job interviews. Employers run structured, recorded interviews in it with verified participants. It is free for candidates. Windows and macOS.
