What AI Detectors Actually Measure (And Don't)

When a Teacher Gets an 80% AI Score, This Is What It Actually Found

A teacher sees a detection report saying a paper is 80% AI-generated. The reasonable assumption is that the software found something definitive: digital evidence, a database match, a hidden watermark proving machine authorship.

It found none of those things. AI detectors do not have access to hidden metadata, authorship logs, or databases of AI-generated essays. They read the text and ask a single question: how statistically predictable is this writing?

That is a useful question in some contexts. It is a terrible question for determining whether a specific student wrote a specific essay. Predictable writing is not AI writing. Formal academic writing is predictable by design.

What Perplexity Actually Means

Perplexity is a measure of how surprising the word choices in a text are. A low perplexity score means the vocabulary is standard, expected, and likely to appear in that sequence based on the model's training data. A high perplexity score means the word choices are unusual, unexpected, or unconventional.

AI text generators are designed to produce low-perplexity text because low-perplexity text reads as coherent and natural. The model selects the statistically most probable next word at each step. The result is smooth, standard, predictable prose.

Students who carefully follow academic writing rubrics also produce low-perplexity text. Rubrics that reward topic sentences, standard transitions, formal vocabulary, and clear thesis statements are essentially instructions to write in a way that minimises perplexity. The algorithm reads their compliant, rubric-following work and sees the same statistical signature it sees in AI output.

This is also why the U.S. Constitution fails AI detection tests. Its formalized, highly predictable language has been absorbed so deeply into LLM training data that detectors read it as machine-generated. If that document fails the test, a student who carefully followed a teacher's formatting rubric is also going to fail the test.

What Burstiness Actually Means

Burstiness measures sentence length variation. Human writing tends to swing widely between short punchy sentences and longer explanatory ones. The rhythm is irregular.

AI text tends toward uniformity. Sentence lengths cluster around 15 to 20 words. The rhythm is smooth and consistent. Detectors use this signature to flag AI output.

The practical problem is that many academic writing styles also produce low burstiness. A student who writes carefully structured, consistently formal sentences because they believe it will help their grade is producing the same burstiness signature as an LLM.

There is a second, darker problem. Students who want to bypass detection tools are now deliberately using AI humanizer software that introduces awkward phrasing, grammatical errors, and sentence length variation into AI-generated text. The tool makes deliberately worse writing look more human. So schools end up in a situation where carefully polished human writing gets flagged and deliberately degraded AI writing passes. That inversion is not a bug someone can fix. It is a consequence of how the system works.

The Actual Accuracy Numbers

Vendor claims and independent testing don't agree, and the gap is not minor. Here is what the research shows.

The Copyleaks result deserves specific attention. The same tool, on essentially the same text, produced completely opposite accuracy scores depending on minor modifications. That is not a tool with a small error rate. That is a tool that is fundamentally unreliable under real-world conditions where students revise, edit, and refine their writing before submission.

For a head-to-head breakdown of how the major tools compare on independent benchmarks, the Turnitin vs GPTZero vs Originality.ai comparison covers specific false positive rates, ESL bias, and bypass vulnerability per tool.

The Base Rate Problem That Makes Everything Worse

Even if a detection tool were more accurate than current evidence suggests, there is a mathematical problem with using it in most classrooms that no engineering improvement can fix.

A paper published in the International Journal for Educational Integrity in 2026 walked through the math. If a classroom has 1,000 papers and only 10% of students are actually using AI, a flagged paper has only a 47.6% probability of genuinely being AI-generated, even with a technically accurate detection tool. That drops below a coin flip.

This happens because of base rates. When most students in a class are honest, every false positive is statistically more likely than a true positive. The prevalence of actual AI use in your specific classroom determines how meaningful any given detection score is. In a class where cheating is rare, detection scores are almost noise.

This is also why the "30% AI score means 30% was written by AI" interpretation is wrong. It means 30% of sentences matched statistical patterns the tool associates with AI. The probability that those sentences were actually written by an AI depends entirely on how many students in the class are genuinely using AI. A score of 30% could represent true detection or a false positive depending on context the tool has no access to.

False Positive Probability Calculator

This tool runs the actual math for your classroom. Adjust the three sliders and see what probability a flagged paper is genuinely AI-generated. The result is the number you should be working with, not the detection score.

The Legal and Disciplinary Exposure Schools Are Not Talking About

43% of U.S. teachers in grades 6-12 used AI detection tools regularly during the 2024-2025 academic year, according to the Center for Democracy and Technology. Most of them are not aware of what they are carrying legally when they use a score to initiate disciplinary action.

Turnitin's own documentation is explicit. Its AI detection is not always accurate and should not be used as the sole basis for punitive action. That language is not a minor disclaimer. It is the vendor explicitly transferring liability to the institution and the individual teacher who treats a probabilistic score as definitive proof.

Anchoring bias compounds this. Once a teacher sees an 80% AI flag, they read the paper looking for evidence of guilt. Dr. David Grundy, Director of Digital Education at Newcastle University Business School, noted in 2025 that investigations initiated solely on an AI flag risk contaminating the entire process, violating principles of due process and natural justice. Students and parents are now contesting these accusations, and legal defense firms are actively building caseloads around AI-based academic misconduct findings.

Mark Andrew Bassett, a researcher at Charles Sturt University, put it plainly in 2026: AI detection does not safeguard academic integrity. It undermines it. The liability sits with whoever chose to treat the score as evidence.

A classroom-level detection policy that explicitly defines what a score can and cannot trigger is the cleaner path. It protects the teacher as much as it protects the student.

Turnitin's own documentation warns against using AI detection scores as sole evidence for punitive action. Schools that do so carry the liability themselves.

LMS Integration and the Automation Problem

The detection problem has a second layer most teachers don't see coming. AI detection is increasingly baked into Canvas, Schoology, and Google Classroom integrations. Many schools did not choose this. It arrived as a feature in a contract renewal.

The specific danger of automated LMS detection is not just the false positive rate. It is that many integrations run the detection check the moment a student submits, generating a flag before the classroom teacher has seen the work in any context. In some configurations, the student sees the flag first. The teacher is pulled into a disciplinary posture they did not initiate, based on a score they did not request, about a paper they have not yet read.

This strips professional discretion from the teacher entirely. A teacher who knows a student's writing history, understands the assignment context, and recognises when a formal writing style is a sign of effort rather than AI use has that judgment replaced by an algorithm. The automation bias problem is documented: once a flag appears in a gradebook or submission portal, the teacher is anchored to it even when their own reading of the paper contradicts it.

Schools that have embedded detection at the LMS level need to audit whether teachers can override or suppress flags before a student is notified. That override should be standard, not a workaround.

What Detection Tools Cannot Do

They cannot identify which specific AI tool was used. They cannot identify when the text was generated. They cannot distinguish between a student who wrote their own work and then used Grammarly for proofreading versus one who generated the entire essay with ChatGPT. They cannot account for ghostwriting, tutoring, or editing assistance that has existed long before AI.

They also cannot reliably clear a student who is innocent. A low detection score doesn't mean the work was human. It means the statistical patterns were not flagged. A student who generated AI text and then heavily edited it manually may produce a low score not because they wrote the work but because the editing introduced enough burstiness and vocabulary variation to fall below the detection threshold.

The asymmetry is the problem. These tools can wrongly accuse honest students. They can wrongly clear dishonest ones. The error doesn't run in a single direction. That makes them unreliable as a basis for any disciplinary decision, in either direction.

For how this specifically affects ESL students, the ESL Students and AI Detection Bias post covers why non-native writers are structurally more exposed to false positives. For what to use instead of a score, process verification is the evidence-based alternative that does not depend on probabilistic software.

How Administrators and Teachers Should Actually Read a Detection Report

Turnitin runs two completely separate analyses and presents them in the same report: a Similarity check and an AI Detection check. These measure different things. A high Similarity score means text was found in existing databases. A high AI score means statistical patterns resembled AI output. A paper can score high on one and zero on the other.

When a paper is flagged, the AI score is the beginning of an investigation, not its conclusion. The next step is manual review for indicators that detection software cannot assess: citations that don't exist when you look them up, a sudden shift in the student's historical writing voice, arguments that are generic and non-specific, or a thesis that doesn't reflect anything taught in the actual class.

Those human indicators are more reliable than a percentage score. A student who used AI extensively tends to produce floating, confident-sounding claims that don't connect to specific class content. The writing is often technically competent but strangely hollow. That's a more useful signal than a number from a probabilistic classifier.

Frequently Asked Questions