No Camera for Tests, Full Proctoring for Exams: Here's Why It Matters

⚡ Quick Answer Assessments need no monitoring. Tests need browser lockdown and session logs — no camera. Exams need full camera proctoring, AI monitoring, and identity verification. Applying the same security level to every evaluation is wasteful, invasive, and counterproductive. Here's why matching proctoring to assessment type is the most important decision in online exam design.

The Problem With One-Size-Fits-All Proctoring

Most institutions approach online exam security the same way — turn everything on for every evaluation.

Weekly quiz? Full proctoring. Practice test? Webcam on. Diagnostic pre-test? Browser lockdown. Formative assessment? Identity verification.

This approach creates four serious problems:

1. Student anxiety spikes unnecessarily Research consistently shows that proctoring increases exam anxiety. The mere presence of proctoring technology can significantly reduce the inclination to cheat — but it also creates psychological pressure on honest students. Applying that pressure to a low-stakes weekly quiz does nothing for integrity and measurable harm to learning outcomes.

2. False positives multiply AI monitoring is criticised for being excessively punitive — averaging 57 flags per exam. When every evaluation is fully monitored, administrators are buried in alerts — most of them meaningless. Alert fatigue sets in, and genuine integrity issues in high-stakes exams get missed in the noise.

3. Students are surveilled when they shouldn't be A formative assessment is designed to identify gaps in learning — its value depends on students engaging honestly without fear. Heavy surveillance changes student behaviour in ways that corrupt the diagnostic signal the assessment was designed to create.

4. Resources are wasted The global online exam proctoring market was valued at $836 million in 2023 and is expected to reach $1.99 billion by 2029. Institutions paying per-exam proctoring fees for every quiz and assignment are spending budget on security that adds no value.

The solution is not more proctoring — it is the right proctoring for the right evaluation type.

The Three-Level Framework

Every evaluation your institution runs falls into one of three security levels:

Level 1 — No Proctoring: Assessments

What this covers: Diagnostic assessments, formative quizzes, peer reviews, homework, portfolio submissions, self-assessments, classroom participation tracking.

Why no proctoring is needed: Assessments at this level are designed to inform teaching and support learning — not to certify achievement. The consequences of a student getting one wrong or looking something up are low. The purpose is to identify gaps, not to enforce compliance.

Applying proctoring to formative assessments is like using a security scanner at a school library. The risk doesn't justify the friction — and the friction actively harms the purpose.

What to use instead:

• Access control (login required, one response per student)
• Time-window restrictions (open for 48 hours, not indefinitely)
• Auto-grading for instant feedback
• Session logging for administrative records

MonitorExam configuration: No proctoring layer — use AssessME for auto-grading and instant performance reports.

Level 2 — No Camera: Tests

What this covers: Unit tests, chapter tests, weekly assessments, mid-term tests, mock exams, practice papers, skill checks.

Why no camera — but browser lockdown is needed: Tests carry real stakes — they contribute to grades, inform progression decisions, and are used to evaluate whether a student is ready to advance. But they are not the final word. Students can retake them. They cover a unit, not an entire course.

The primary cheating risk in a test is not identity fraud — it's tab switching to look up answers, copy-pasting from notes, or using a second device. These are behaviours that browser lockdown and session logging detect without any camera feed.

A camera adds friction, bandwidth cost, and anxiety — but catches very little that browser monitoring doesn't already catch at this stakes level.

What to use:

• Browser lockdown — prevents tab switching, copy-paste, screen sharing
• Session logs — every event timestamped
• Timer enforcement — auto-submission when time expires
• Tab switch detection — flagged and logged

What not to use:

• Webcam monitoring — disproportionate to stakes
• Identity verification — not required for periodic unit tests
• Full AI behaviour analysis — overkill for low-to-medium stakes

MonitorExam configuration: Camera-optional mode — browser lockdown + session logs + tab switch detection. No webcam required.

Level 3 — Full Camera Proctoring: Exams

What this covers: Final exams, semester exams, entrance exams, professional certifications, board exams, competitive selection tests, high-stakes assessments.

Why full camera proctoring is essential: Exams are high-stakes, often final, and produce credentials or results that are relied upon by employers, institutions, and regulators. The consequences of a compromised result extend beyond the individual student — they affect everyone competing for the same outcome and undermine the value of the credential.

At this level, every layer of security is justified:

• Identity verification — confirms the right person is sitting the exam before a single question is answered
• Webcam monitoring — tracks face presence, detects multiple people, flags environmental anomalies
• Browser lockdown — blocks tab switching, copy-paste, screen sharing, and application switching
• AI behaviour analysis — monitors timing patterns, eye movement, unusual activity throughout the session
• Real-time alerts — notifies the teacher or proctor immediately when suspicious behaviour is detected
• CredScore integrity report — a complete, timestamped audit trail generated at submission

This is the level where the Haishan Yang case at the University of Minnesota becomes relevant — a high-stakes PhD preliminary exam with no proctoring, no session data, no objective record of what happened. The entire misconduct case collapsed into competing interpretations because the right security level wasn't applied to the right exam type.

MonitorExam configuration: Full proctoring — FIDO2 passkey identity verification + webcam monitoring + browser lockdown + AI behaviour analysis + CredScore report + teacher dashboard.

Not sure which security level fits your exams?
MonitorExam configures automatically to your assessment type —
no camera for tests, full proctoring for exams, nothing for
assessments. Same platform, three levels, zero friction.
See how it works in 30 minutes →

Why Camera-Optional for Tests Is Not a Security Compromise

Why Camera-Optional for Tests Is Not a Security Compromise

The most common pushback to this framework is: "But what if a student cheats on a test and there's no webcam to catch them?"

The answer is that webcam monitoring is not the primary detection mechanism for test-level cheating. Here's why:

The most common forms of cheating on a unit test are:

• Opening a new tab to search for answers — caught by tab switch detection
• Copy-pasting questions into ChatGPT — caught by copy-paste blocking
• Using a phone alongside the laptop — partially caught by environment monitoring, but a camera adds marginal value
• Collaborating with another student via messaging — caught by unusual timing patterns

A webcam primarily catches:

• Someone else sitting the exam (identity fraud)
• Consulting physical notes on a desk
• Looking away frequently

For a unit test contributing 10% to a final grade, identity fraud is not the primary risk. For a final exam determining whether a student graduates, it absolutely is.

Camera monitoring should be deployed where it adds the most security value — not universally to reduce administrative effort.

The Student Experience Argument

There is a second reason the three-level framework matters beyond security: student wellbeing.

Proctoring technology has the ability to pause or end the online exam if the rules are not followed, catch students in irrelevant activities, and flag suspicious conduct in real time. When a student knows all of this is happening during a weekly quiz, their cognitive load increases significantly — leaving less capacity for the actual thinking the quiz is designed to assess.

MonitorExam's calm exam design philosophy is built on this insight: security should be invisible to students who are not cheating. Browser lockdown for a test runs silently in the background. The student experiences a normal exam interface — not a surveillance apparatus.

Full camera proctoring for a final exam sends a different, appropriate signal: this matters, it is being taken seriously, and the result will be credible. That signal has value. Diluting it by applying the same intensity to every evaluation destroys it.

How This Applies in Practice

Common Mistakes Institutions Make

Mistake 1 — Using Google Forms for final exams Google Forms has no browser lockdown, no tab detection, no identity verification, and no session logging. It is an appropriate tool for assessments and tests — not exams. Read: Can teachers detect cheating on Google Forms?

Mistake 2 — Using full proctoring for everything Applying camera monitoring to weekly quizzes creates anxiety, burns budget, and trains students to associate learning activities with surveillance — changing the culture of assessment in ways that are hard to reverse.

Mistake 3 — Using no proctoring for high-stakes exams The Haishan Yang case is the clearest illustration. A final exam without session data creates an institution that cannot defend its own integrity decisions when challenged.

Mistake 4 — Not telling students which level applies Students should know before every evaluation what level of monitoring applies and why. Transparency reduces anxiety, builds trust, and signals that the institution's security choices are intentional — not arbitrary.

How MonitorExam Supports All Three Levels

MonitorExam is the only proctoring platform designed with adaptive security levels as a core feature — not an add-on.

All three levels run on the same platform — no switching tools, no separate contracts, no IT team required. A teacher can configure a weekly test with browser lockdown and a final exam with full camera proctoring from the same dashboard.

Frequently Asked Questions

Do tests need proctoring? Tests need browser lockdown and session logging — no camera required. Camera monitoring is disproportionate to the stakes of a periodic unit test and adds friction without proportionate security value.

Do assessments need proctoring? No — formative assessments, diagnostic quizzes, and homework assignments do not need proctoring. Their purpose is to support learning, not certify achievement. Access control and time limits are sufficient.

When does an exam need camera proctoring? Any exam that produces a grade, certification, or credential relied upon by a third party — university, employer, or regulator — requires full camera proctoring with identity verification.

Is camera-optional proctoring secure enough for a mid-term test? Yes — browser lockdown, tab switch detection, and session logging catch the primary cheating risks at mid-term level. Camera monitoring adds marginal value for a test that is not the final determination of a student's achievement.

What is the difference between browser lockdown and full proctoring? Browser lockdown restricts what a student can access during the exam — no other tabs, no copy-paste, no external applications. Full proctoring adds webcam monitoring, identity verification, AI behaviour analysis, and a complete integrity report on top of browser lockdown.

Set the Right Security Level for Every Exam

MonitorExam adapts to your evaluation type — no camera for tests, full proctoring for exams, nothing for assessments. One platform, three security levels, zero friction for students who aren't cheating.

Book an Institution Demo

Try MonitorExam Free