That's the opening line of a Reddit post from a public health student at the University at Buffalo. He submitted an assignment he completed entirely on his own — no ChatGPT, no Claude, no Copilot. Turnitin's AI detector flagged it as "likely AI-generated." The university opened an academic dishonesty investigation based solely on that score.
He's not alone. Across the US, UK, Australia, and Canada, students are being accused of AI cheating based on scores from tools that the universities themselves know are unreliable. And the numbers tell a story that the detection companies don't want you to hear.
Turnitin says its AI detector has less than a 1% false positive rate. That sounds reassuring. But here's what that actually means.
Vanderbilt University submitted 75,000 papers to Turnitin in 2022. Even at the 1% rate Turnitin claims, roughly 750 of those papers would have been incorrectly flagged as AI-written. That's 750 students facing accusations they didn't earn.
After testing the tool, Vanderbilt disabled Turnitin's AI detection entirely. Their reasoning: even at the rate Turnitin claims, the absolute number of wrongly accused students was unacceptable.
The University of Iowa went further. Their Office of Teaching, Learning, and Technology explicitly advises faculty to "refrain from using AI detectors on student work due to the inherent inaccuracies." Vanderbilt, MIT, and the University of Pittsburgh have published similar guidance.
But independent testing suggests the real false positive rate is higher than vendors admit. The RAID Benchmark — the largest independent evaluation of AI detectors — found that when researchers constrained the false positive rate below 1%, most detectors became ineffective at catching AI text. The high accuracy numbers detectors advertise only hold when they're allowed to misclassify a significant percentage of human writing.
GPTZero, one of the most popular detectors, has a false positive rate around 9% according to Stanford NLP Group testing. ZeroGPT: 14.7%. At a university processing 50,000 papers per semester, a 5% false positive rate means 2,500 innocent students wrongly flagged. Every semester. With no automated appeals process.
Here's where it gets ugly. AI detectors don't just produce random errors — they systematically disadvantage certain groups.
A 2023 Stanford study found that popular AI detectors flagged essays by non-native English speakers as AI-generated up to 61% of the time. Compare that to under 5% for native speakers. The detectors weren't detecting AI. They were detecting formal, grammatically consistent writing — the kind that ESL students produce when they're carefully following the rules they were taught.
The reason is mechanical. Non-native writers use a more restricted vocabulary. They repeat sentence structures they know are correct. They rely on formal connectors taught in language courses. These are exactly the patterns that raise AI detection scores.
AI detectors don't distinguish between "AI-generated" and "formally constrained human writing." They measure linguistic patterns, and those patterns appear in both. A student who writes carefully and formally gets flagged. A student who writes sloppily gets a pass.
This isn't a minor edge case. The bias is baked into the math. When detectors are trained on patterns common in LLM output, and LLMs are trained on millions of academic papers, the resulting statistical models catch anyone who writes like — well, like a good student. The tools are essentially punishing people for having learned the conventions of academic prose.
The fundamental problem is that AI detectors are trying to solve an impossible problem.
These tools work by analyzing statistical patterns — sentence length variation, vocabulary diversity, word-by-word predictability. They measure something called "perplexity" (how surprising each next word is) and "burstiness" (whether the writing varies naturally). The assumption is that AI text is more predictable than human writing.
That assumption is shaky and getting shakier. AI models have gotten better at generating varied, less predictable output. Meanwhile, human writers trained on formal conventions produce text that looks statistically "AI-like." The gap has narrowed to the point where the scanners are essentially guessing.
Academic writing is almost designed to trigger detection. Academic prose favors structural consistency: clear topic sentences, uniform paragraph lengths, predictable transitions. It favors formal vocabulary. It hedges. It avoids first-person voice and strong opinions. Every one of these conventions pushes the statistical profile toward what detectors flag.
This puts good academic writers in a bind. The habits their training rewards are the habits detectors penalize. There's no fix short of deliberately un-learning conventions — which is not something most writers should do just to appease a statistical tool.
The situation gets worse when you consider that AI models are now being trained on more diverse, less formal data. A 2026 literature review found that most detection tools perform only slightly better than chance in real-world conditions. Accuracy declines sharply with sophisticated, edited, or patterned texts. One controlled study found that both human and AI detectors identified AI text at rates barely above 50%.
The student at the University at Buffalo started a petition. He wants his university to stop using Turnitin's AI detection until due process protections are in place. "Once flagged, there is no real mechanism for appeal," he wrote. "The burden of proof falls entirely on the student, and in most cases, no additional evidence is required from the university."
This is the core of the problem. A score from Turnitin is treated as evidence, but the tool's methodology is a black box. Turnitin gives no detailed information as to how it determines if a piece of writing is AI-generated. They say their tool "looks for patterns common in AI writing," but they don't explain what those patterns are or how the scoring works.
The burden of proof inversion is the real scandal. In any other context, if a university accused a student of cheating, the institution would need to present evidence — witness statements, documented irregularities, clear signs of misconduct. With AI detection, the evidence is a percentage generated by an algorithm that the student cannot inspect, the university cannot verify, and the detection company will not fully disclose.
Australian Catholic University reported nearly 6,000 alleged cheating cases in 2024, with about 90% relating to AI use. That's 6,000 students subjected to integrity proceedings, many based on scores from tools with documented false positive rates. Even if only a fraction of those cases were wrongly initiated, that's hundreds of students whose academic records were affected by a tool that may not work.
The numbers tell you where universities actually stand. The California State University system spent $1.1 million on Turnitin in 2025. Turnitin charges universities anywhere from $1.79 to $6.50 per student for the same service. The AI detection add-on costs extra.
Universities keep paying because switching costs are too high. They know the tools are imperfect. They know the false positive rates are real. But they don't have a better option, and the alternative — not having any detection at all — feels worse.
As one researcher put it: "No detection company has published a peer-reviewed false-positive rate, because those numbers would raise hard questions about the product category."
The detection industry has a perverse incentive problem. Detection companies make money when universities buy their tools. Universities buy their tools because they need to show they're doing something about AI cheating. Detection companies have no financial incentive to publish accurate false positive rates, because those numbers would undermine their sales pitch. The whole system runs on plausible deniability.
Some universities are starting to push back. SUNY Buffalo's current RFP for plagiarism detection tools doesn't mention Turnitin by name — a sign they're open to alternatives. But switching is expensive, and the alternatives face the same fundamental limitations.
If AI detectors don't work, what does? The most effective approach combines several methods. Get a writing baseline early in the semester — have students submit a personal, low-stakes writing sample so you know their authentic voice. If something feels off, submit the suspicious work to an AI tool and ask it to rewrite. AI often lazily rewrites its own work by substituting synonyms without changing the core meaning. Human text gets reshaped more dramatically.
Request a rewrite in person. Ask students to explain their thinking. Check whether the writing matches the student's usual style across assignments. Look for factual errors that signal hallucination. These methods aren't perfect either, but they require human judgment — which is exactly what a statistical scanner can't replace.
Some universities are shifting toward process-based assessment — oral exams, in-class writing, draft submission requirements. Others are designing assignments that AI can't easily complete: personal reflections, local case studies, hands-on projects that require domain-specific knowledge.
The uncomfortable truth is that there's no technological fix for a trust problem. Universities adopted AI detectors because they needed a scalable way to enforce AI policies. But the tools they bought don't deliver on that promise, and the students paying the price are the ones who played by the rules.
The detection industry is in a strange position. It's selling a product that its own customers are increasingly abandoning. Over 50 universities have banned or disabled these tools. The ones still using them know they're flawed but can't figure out what else to do.
None of the alternative solutions scale the way a detection tool does. That's the real problem. Universities need to process hundreds of thousands of assignments across thousands of courses. AI detection promised to automate the enforcement of AI policies. It was always too good to be true.
A black-box algorithm, known to produce false positives, is being used as de facto evidence in high-stakes academic processes. That should bother all of us — not just the students getting flagged. When we let a statistical tool decide whether someone cheated, we've already lost something important about how education is supposed to work.