Blog

How to Run Coding Exams Without a Lockdown Browser

Lockdown browsers were built for multiple-choice tests, not for students who need to write, compile, and run real code. Here is how to run secure coding exams without one — using a controlled, AI-free environment, live monitoring, and integrity evidence instead.

Examination Center is in early access — we're onboarding institutions through our Early Access Program. The information here describes our current platform and direction and may evolve; it is not a contractual commitment.

By the Examination Center team · Last updated: 2026-06-18

Why lockdown browsers fit coding exams poorly

Lockdown proctoring tools are designed to stop a student from opening other tabs, copying questions, or reading notes during a quiz. That model assumes the answer lives in the student's head and the only risk is looking something up. Coding exams are different. Students need an editor, a working language runtime, error messages they can read, and the freedom to run their code many times before they are done.

These tools also tend to require an install, take over the device, and sometimes record the camera or screen. That creates friction on exam day: a student on a locked-down lab machine or a personal laptop with the wrong OS can be blocked before they write a single line. For a CS department running exams across many sections and machines, every install and permission prompt is a support ticket waiting to happen.

The deeper mismatch is what you are actually trying to protect. In a coding exam, the real integrity question is not "did the student open another tab" — it is "did this student write this code, or did they paste it from an AI tool or a classmate?" A browser that locks the desktop does not answer that question.

What you actually need to protect

Before picking tools, get specific about the risks you care about in a programming assessment. Most of them fall into a short, concrete list:

• AI assistance: built-in code completion or a chat assistant writing answers for the student.
• Outside help: code pasted in from a phone, a second device, or a messaging app.
• Collaboration: two students producing suspiciously similar solutions.
• Lost work: a frozen tab, a closed laptop lid, or a crashed browser wiping an hour of effort minutes before the deadline.

A controlled, AI-free exam environment

The first move is to remove the AI advantage at the source rather than trying to police it after the fact. Run the exam in a plain editor with no built-in AI assistant and no autocomplete, identical for every student. Nobody gets a smarter editor than anyone else, and there is no "helpful" suggestion writing the answer for them.

Browser-based delivery removes the install problem entirely. Students open a link and start working — no software to push to lab machines, no driver conflicts, no admin rights needed. Examination Center runs Python directly in the browser through Pyodide (including NumPy, pandas, and Matplotlib), and compiles and runs C, C++, Fortran, and Java in a secure server sandbox. The student sees a clean editor and a Run button; the heavy lifting happens behind the scenes.

Because the environment is the same for everyone and there is no AI layer baked in, you are testing the student's own problem-solving — not their skill at prompting a model. That is the part a lockdown browser was never built to do.

Live monitoring and integrity evidence, not automated verdicts

Instead of locking down the device, you watch the exam as it happens. A live instructor dashboard shows current code, run history, and integrity signals across the room. If something looks off, a human can look closer in real time.

Those signals are exactly the ones that matter for code: paste events, large or sudden edits that do not match a normal typing pattern, and cross-student code similarity. Critically, these are shown as evidence for human review — not accusations and not a guilty/not-guilty stamp. The platform never claims to "detect AI" or hand down a verdict. An instructor reads the signal, looks at the context, and decides.

This is a fairer model than a black-box flag. A paste event might be a student moving code between two files in their own workspace. A similarity hit might be two students who both used the obvious approach. By keeping a person in the loop, you protect honest students from false positives while still catching the cases that deserve a conversation.

Protecting student work without locking the machine

One of the loudest objections to going browser-based is "what if the tab crashes?" It is a real fear: in a high-stakes exam, losing work is as damaging as cheating. The answer is not to lock the device — it is to autosave continuously and recover the session.

With autosave and session recovery, a frozen tab, a closed lid, or a closed browser does not wipe an hour of work. The student reopens the exam and their code is there. That removes a major source of exam-day panic and the appeals that follow it, and it does so without any of the heavy device control a lockdown tool imposes.

You also keep the records you need afterward. Sessions, run history, and integrity reports can be exported (JSON/CSV) for your own files and your department's review process — useful if an integrity case ever needs documentation.

Putting it together: a workflow that does not need a lockdown browser

A coding exam without a lockdown browser comes down to four design choices working together. Each one replaces a piece of what the lockdown model promised, but in a way that actually fits how students write code.

This is the model Examination Center is built around. To be clear about what it is not: it is not an autograder — it does not score work or keep a grade book, so grading stays in your normal workflow. It is not an LMS, and it does not lock, take over, or record the student's device or camera. It is a purpose-built place to run the exam itself.

If you run programming exams and the lockdown approach has been fighting you, this is worth a look. Examination Center is currently invitation-only through a free Early Access Program — you can apply for early access to try it with a real exam, or walk through the instructor demo first to see the monitoring view.

• Use an AI-free, identical editor so no one gets an unfair assist.
• Deliver it in the browser so there is nothing to install on exam day.
• Monitor live and surface integrity evidence for a human to review, instead of automating accusations.
• Autosave and recover sessions so a crash never costs a grade.

Related reading

Examination Center vs Respondus LockDown Browser · Python lab exams use case · Security and data handling · Coding exam and academic integrity glossary

Run fair coding exams

Early Access scope: up to 40 students and 1 exam. Indicative pricing only — see pricing or apply for Early Access.