Falsely accused of using AI? What to do, step by step

The short version

An accusation feels like a verdict, but it usually starts as a question. Your instructor saw something that worried them, often a detector score, and has to ask about it. The best answer is the story of how you wrote the paper, told calmly and backed by your drafts and notes. Keep everything, take a breath, and aim for a conversation. Your instructor wants to get this right too.

Why this happens

AI detectors read finished prose and estimate how likely it is to be machine-generated. They are wrong often enough that the numbers are public. Stanford researchers (Liang and colleagues, Patterns, 2023) found detectors flagged 61.3 percent of TOEFL essays by non-native English writers. Common Sense Media (2024) found 20 percent of Black teens reported being falsely accused, against 7 percent of white teens. Turnitin’s own false positives page states a document-level rate under 1 percent, which on a large campus is still hundreds of papers a term. A March 2026 report in Nouse found neurodivergent students disproportionately flagged. If you write cleanly, formally, or in a second language, a detector is more likely to misread your work. That is worth mentioning, calmly, when you talk.

Source: Liang et al., Patterns, 2023; Common Sense Media, 2024; turnitin.com false positives page; Nouse, March 2026; checked 2026-09-08.

The steps, in order

1. Reply briefly and politely. You do not need to answer everything at once. Say that you received the message, that you wrote the paper, and that you would like to meet and show how it came together. If you need a few hours to calm down first, take them.
2. Gather how you wrote it. Every draft with its file timestamps, your outline and notes, annotated sources, the version history of the document, and anything from a writing center visit. If your course used a recording editor, ask your instructor to look at your session. The evidence page explains what each kind of material shows.
3. Ask what prompted the concern. Politely ask which passages or which part of the paper worried them, and which course or school policy applies. Knowing the passages lets you show the draft or the notes behind each one.
4. Walk through the paper together. Thesis, structure, why each source is there, the paragraph you struggled with, what you would change now. Offer to answer questions about it, or to write a short response on the same topic while they watch. If you wrote the paper, this part is easier than it sounds.
5. Be open about any help you did use. A tutor, a spell checker, Grammarly, a friend who read a draft. Say what it was and what it did. Instructors can work with an honest account.
6. If the conversation does not settle it. Every school has a next step, usually an academic integrity office or a committee that reviews the case. Ask how it works and what the timelines are, and check whether you may bring a support person. A student advocacy office or ombuds can explain the process if it is unfamiliar.

What the cases so far say

A few of these disagreements have ended up in court. They are worth knowing about mainly as a reminder of why a clear record and an early conversation matter. In Newby v. Adelphi University (New York Supreme Court, Nassau County, 2026 NY Slip Op 26021, early 2026) a student’s paper was flagged by Turnitin at 100 percent while Grammarly and ZeroGPT read it as human. The court found the finding “without valid basis” and ordered the record expunged.

Other cases have turned on whether the school followed its own process. Doe v. University of Michigan (February 2026) was disability-related. Rignol v. Yale involves a GPTZero flag and is pending. Yang v. University of Minnesota (February 2026) went the other way: the expulsion was affirmed. Kato v. Palo Alto Unified School District, filed in federal court on May 5, 2026 over a Turnitin 76 percent flag, came with a 1,162-page packet including Google Docs revision history. All of these took months. The simpler path, for you and for your instructor, is the one on this page: show the work early and talk it through. The case list keeps the dates.

Source: Justia (Newby); N.D. Cal. docket (Kato); GradPilot tracker (Doe, Rignol, Yang); checked 2026-09-08.

What a writing record adds, and what it cannot

Some courses now have students write inside an editor that records the session, such as EssayGuard: every keystroke, revision, pause and paste, with server-side timestamps. A record like that shows what a Google Docs history cannot: whether a passage was typed or pasted, how long the pauses were, which sentences were rewritten and in what order the argument formed. If your course used one, it usually answers the question quickly for both of you. Be honest about the limit too. A record shows how text entered the editor, not whether the ideas were yours. It is evidence for a conversation, and it is not something you can make after the fact.

What not to do

• Do not delete, rename, or clean up any file. An incomplete record is fine; an edited one is not.
• Do not lead with screenshots from other detectors. A disagreement between tools says the score is uncertain, but it says nothing about who wrote the paper. Your drafts and your explanation do.
• Do not use a humanizer or an auto-typer to create a history. It turns a false accusation into a true one.
• Do not post about your instructor or share their messages publicly. It makes the conversation harder for everyone.
• Do not skip the meeting because it feels unfair. The meeting is where this gets resolved.

A note on advice

Nothing here is legal advice, and every school handles this differently. Read your course and school policy before you reply. Then ask your instructor for the meeting, bring what you have, and explain the paper the way you would explain it to a friend. That conversation is what every step above is meant to get you.