Skip to main content
If some violations in a proctoring report have no evidence, the attempt most often reached its evidence limit. The other causes are below.

​
Understanding Violations vs. Evidence

Violation

An event that AutoProctor detects as anomalous. For example, no face detected on the camera feed, or the candidate switching to a different tab.

Evidence

Supporting documentation of the violation. For example, a photo of the camera feed when no face was detected, or a screenshot of the tab the candidate visited.
The Trust Score is calculated based on the type, frequency, and duration of violations. Evidence files are provided in the proctoring report so you can review what happened during the test.

​
Three Reasons for Missing Evidence

​
1. Evidence Limit Reached (Most Common)

Each attempt can save only a set number of evidence files for each type of event. A long or eventful test can use them all up. See Evidence Limits for the numbers.
The Trust Score depends on violations, not on whether evidence is stored. All violations are tracked and affect the Trust Score even when evidence files are not available for viewing.

​
2. Device or Internet Issues

The candidate’s device or internet connection may have prevented the screenshot from being captured or transmitted to AutoProctor’s servers. This is common when candidates experience brief connectivity drops during the test.

​
3. Test Proctoring Settings

The test administrator may have disabled evidence storage through the test’s proctoring configuration. Check your proctoring settings to confirm that evidence recording is enabled.

​
Evidence Limits

What happens at the limit: once the files for an event type are used up, AutoProctor still records each new violation. For its evidence, it randomly either replaces an earlier file or skips the new one. This keeps a mix of evidence from early and late in the test.
Tests on the AutoProctor website use the first column. The second applies only if your developers embed AutoProctor with SDK v5. The common pool is one set of 50 files for no face, multiple faces, noise, phone and multiple monitors together. Every file one of them uses leaves fewer for the others. Monitoring stops after 6 hours on the AutoProctor website and SDK v4, and after 5 hours on SDK v5. Nothing is captured after that.