Proctortrack doesn't hand down verdicts — it collects evidence and raises flags that someone else reviews. That distinction matters, because Proctortrack is more intrusive than most platforms: it monitors your whole desktop, not just your browser, and it can see things that have nothing to do with cheating.
What Proctortrack actually captures
Unlike lockdown-browser tools, Proctortrack runs a background agent on your machine. In a typical configuration it collects:
- Webcam video and room audio throughout the exam.
- Full desktop screen capture, not just the exam window — anything visible on your monitors.
- Process and application monitoring — what software is running, what windows gain focus, when.
- Network and keyboard activity metadata in some deployments.
- An environment scan at check-in: a 360-degree webcam sweep of your room, your desk, and sometimes your ID.
- Behavioral flags: faces leaving frame, multiple people, talking, gaze patterns, tab or application switches, second monitors, unauthorized processes.
Every one of those produces timestamped evidence an instructor or reviewer can replay. The system is tuned to over-flag rather than miss — which means the review step is where your actual protection lives.
What counts as cheating versus what counts as noise
A flag is a lead. Reviewers look for clusters and context: "no face detected for 40 seconds" plus audio of a second voice plus a focus switch to an unknown window is a pattern. Gaze wandering while you think, or a parent walking in, usually isn't — but only if you make the innocent explanation obvious and available.
How to avoid false flags
- Close everything before you start, including chat apps and anything running in the system tray that pings. Process monitors don't know Slack from Chrome.
- Use one monitor. A second screen is flagged as a second screen even if it shows nothing.
- Run the environment scan honestly and completely, then keep the room bare. A half-completed scan is worse than a clean one.
- Stay in frame, light your face, and don't talk through problems under your breath — audio flags are easy to produce accidentally.
- Never take calls or texts during the exam, even for family logistics.
- If something legitimate must happen (a required accessibility tool, a caregiver entering), tell your proctor before the exam, not after the flag.
If you're accused based on flags, ask for the specific timestamped evidence and respond to it concretely. Review boards dismiss far more flags than students expect once context is on the table — but vague denial helps nobody.
For organizations evaluating Proctortrack-style tools
Be clear-eyed about what full-desktop monitoring buys you in hiring rather than academia. It shifts real cost onto whoever reviews recordings and flag clusters, and it measurably depresses completion among candidates who were never going to cheat — the honest majority simply dislike surveilled assessments more than bad actors avoid them. If your integrity problem is small and your volume is large, the tool can cost more than it saves. Deciding which signal you actually need — capability evidence versus process control — before choosing monitoring depth is the useful first step. AI candidate evaluation walks through structuring assessments so scoring and integrity settings serve one defensible shortlist instead of two separate checklists.
Disclose what is recorded, in the invitation, in plain language. Full-desktop capture that a candidate discovers mid-exam becomes a trust incident regardless of what they did.
Bottom line
Proctortrack detects behaviors, not cheating: desktop-wide screen capture, process monitoring, webcam and audio flags, plus an environment scan — all reviewed by a human afterward. Close everything, run one monitor, complete the scan, stay in frame, and answer any flag with the specific timestamp and context rather than a general denial.