Integrity vs. Surveillance: Is Your Proctoring Tool Monitoring Learners or Surveilling Them?

There is a difference between monitoring and surveillance. Most programs running online assessments haven’t thought carefully about which one they’re actually doing, and that gap is where trust starts to erode.

Monitoring confirms that the right person completed the assessment, stayed engaged, and followed the rules. Surveillance collects everything it can, flags anything it doesn’t recognize, and leaves the program to sort out what any of it means.

One produces a defensible result. The other produces liability.

If your proctoring tool accesses the file system of a personal device, stores recordings your team will never review, or generates hundreds of automated flags with no human judgment behind them, it’s not monitoring. It’s surveillance. And your learners know the difference.

What monitoring is actually supposed to do

Every program administering online assessments has the same core need: confirm identity, verify participation, and produce a result that holds up to scrutiny.

That’s it.

You’re not trying to catalog everything that happens in a candidate’s home. You’re not trying to build a behavioral profile. You’re trying to answer three questions:

1. Was this the right person?
2. Did they complete the assessment under appropriate conditions?
3. Can you stand behind the result if it’s challenged?

A well-designed proctoring approach answers all three. An over-engineered one tries to answer questions nobody asked, and in doing so, creates new problems. More data. More noise. More privacy exposure. And a test-taking experience that generates complaints before a single result is issued

Where surveillance starts

Privacy-first proctoring is not a softer version of security. It’s a more precise one.

It starts with a design principle: collect only what is necessary to confirm identity and verify engagement. Nothing beyond that scope. No recordings stored by default. No system-level device access. No behavioral data used outside the bounds of the specific assessment.

In practice, that looks like this:

No downloads or extensions. The assessment runs in a browser. No software installs, no hidden permissions, no access to personal files or background applications. A test taker can sit the exam on any device without IT involvement or configuration.

Proportionate data collection. Every feature and every data point collected should have a clear answer to the question: why does this make the result more defensible? If the answer is “it doesn’t,” it shouldn’t be collected. Surveillance produces volume. Monitoring produces clarity.

Data minimization by design. The only data collected is what’s needed to produce a defensible result: identity verification, participation confirmation, and a reviewable record of any flagged behavior. Sensitive data, including ID images, is deleted within 24 hours.

Compliance built in, not bolted on. GDPR, PIPEDA, FERPA, and SOC2 compliance aren’t checkbox items. They reflect a commitment to proportionate data collection, the kind of approach that holds up when regulators or institutional counsel start asking questions.

Human review is what makes the result defensible

Here’s what automated flags can’t tell you: whether a behavior was actually a problem.

An algorithm can detect that a second face appeared in the frame. It cannot tell you that the second face belongs to a child who walked in, not an accomplice. It can flag an unusual eye movement pattern. It cannot determine whether that pattern indicates academic dishonesty or a medical accommodation. It can detect a background sound. It cannot decide whether that sound matters.

Those determinations require a person.

At Integrity Advocate, every flagged session is reviewed by a trained human reviewer before any outcome is issued. Not as a premium tier. Not as an add-on. As the standard, at every price point.

That’s the difference between a defensible result and an automated flag you have to explain to a grievance committee.

Programs that rely on automated proctoring alone are producing outcomes they cannot fully stand behind. When a result is challenged, and eventually one will be, “the algorithm flagged it” is not a sufficient answer. A documented, human-reviewed decision is.

The question your program should be asking

Before your next contract renewal or platform evaluation, ask this: what does your current proctoring tool collect, and who reviews it before a result is issued?

If the answer is “a lot” and “no one,” that’s the surveillance model. It may feel thorough. It isn’t defensible.

Privacy-first online proctoring isn’t about doing less. It’s about doing exactly what’s necessary, with human judgment behind every decision that matters. That’s what produces results your program can stand behind. It’s what earns trust from your learners. And it’s what holds up when the stakes are highest.

Integrity doesn’t require surveillance. It requires precision.