For most of the last decade, the default answer to online exam integrity was the same: lock the browser down. Disable copy and paste, block other applications, take over the desktop for the duration of the exam. It was a reasonable-sounding solution to a real problem, and hundreds of institutions adopted it without much debate.
That consensus is breaking. Across higher education, IT departments, disability services offices, and faculty governance bodies are independently arriving at the same conclusion: lockdown browsers create more problems than they solve. Here is what is actually driving institutions away from the lockdown model, and what they are moving toward instead.
The accessibility problem lockdown browsers created
Lockdown browsers were built to control a narrow, standard environment: a recent laptop, a mainstream operating system, and no assistive technology running in the background. Students who fall outside that assumption are the ones who pay for it. Screen readers get disabled mid-exam. Speech-to-text tools lose their permissions. Switch-access and eye-tracking devices, which route input through system-level processes that a lockdown browser is specifically designed to block, simply stop working.
Disability services offices have become the front line for this problem, fielding exam-day emergencies that have nothing to do with academic performance and everything to do with software conflicts. Chromebooks, common in many student populations, frequently cannot run lockdown browsers at all. A tool meant to protect exam integrity ends up deciding, in practice, who gets to take the exam smoothly and who does not.
Student backlash became an institutional risk
Students noticed. Petitions against lockdown proctoring tools circulated on campuses nationwide, student government resolutions calling for their removal are no longer rare, and in 2021 the University of Illinois announced it would drop Proctorio after sustained pushback. The complaints cluster around a few consistent themes: software that demands broad system access, monitoring that continues after the exam submits, and appeals processes that offer no real way to contest an automated flag.
For an institution, that pattern of complaints is not just a support burden. It shows up in course evaluations, in enrollment decisions for online programs, and in the kind of public incidents that make their way into student newspapers and local press. Assessment integrity software was supposed to protect institutional reputation. Increasingly, it has become a source of reputational risk instead.
Faculty senates started passing resolutions
Faculty governance has weighed in too. Faculty assemblies and senates have formally pushed back on invasive proctoring tools, citing equity, data privacy, and pedagogical value; the University of Colorado Boulder's faculty assembly memorandum on Proctorio is a representative example. Faculty who once deferred to their institution's IT recommendation on proctoring software are now asking harder questions: What data does this tool collect? Where does it go? What happens to a student who is flagged by an algorithm no one on campus can fully explain?
Those questions are difficult to answer when the underlying system is a black box. That difficulty, more than any single incident, is what has turned faculty governance from a rubber stamp into a real obstacle for lockdown vendors.
What is replacing the lockdown model
The alternative gaining traction is not less oversight. It is differently structured oversight, built on consent and evidence rather than control and suspicion. Instead of seizing the student machine, a consent-based platform asks the student to share what an assessment requires, the same way they would share their screen on a video call, and captures that as one stream of evidence for a human reviewer. See how consent-based monitoring compares to browser lockdown for a closer technical look at the difference.
The other shift is in how flags get handled. Lockdown-era tools often wired an algorithmic suspicion score directly to a consequence, up to and including automatically ending an exam. Evidence-based platforms route flags to a human reviewer instead, with timestamped video and context attached, so a flag becomes the start of a documented review rather than an automatic accusation. That distinction is what actually holds up when a result is appealed. You can see the full workflow, from exam launch to human decision, on the how it works page.
What this means for your institution
If your institution is still running a lockdown browser, the pressure to change is unlikely to ease. Accessibility complaints will keep landing on the same desks. Faculty senates will keep asking for documentation the vendor cannot provide. And students, who have more visibility into each other's exam experiences than any single office does, will keep comparing notes.
The institutions moving fastest are not abandoning oversight. They are replacing a control-based model with an evidence-based one that their accessibility office, their faculty senate, and their conduct process can all actually stand behind. For a closer look at what that looks like specifically for a university, community college, or online program, see Nigel's higher education solution, or read the Trust Center for how evidence is captured, stored, and governed.