Blog / Research
Falsely Accused of Using AI: The Full Checklist Nobody Publishes in One Place
Falsely accused of using AI? We read the six student-facing advice pages that currently rank for that question and coded each one against ten concrete defence actions. The best of them covers six. The three actions that get omitted most are the three that cost nothing. Here is the merged checklist — what to do today, how to prove you wrote it, and why the detector flagged you in the first place.
TL;DR
Stop editing the file, export your version history, and ask in writing what the accusation is based on before you answer it. Don’t confess to make the meeting end. We coded the six advice pages ranking for this query against ten defence actions: mean coverage 5.0 out of 10, best page 6. Tool vendors document the evidence half (8 of 9 items), law firms document the rights half (8 of 12) — three pages per group, so a pattern rather than a rate, but nobody publishes both. The full grid is below. On why you were flagged: our May 2026 test of 861 verified human-written sentences returned 13.8% classified AI or mixed by GPTZero. That is sentence-level and deliberately the hard case; GPTZero states ≤1% at document level. Both can be true. Neither makes a score proof.
If you were accused today, do these five things first
Before anything else, and before you reply to the email:
- Stop editing the document. Its revision history is your best evidence and every further edit muddies the timeline. Duplicate it if you need to keep working.
- Export what you already have. Version history, dated drafts, outlines, notes, the sources you read, messages where you discussed the assignment.
- Ask, in writing, what the accusation is based on. Which tool, what score, which passages, and what the written policy says about how that score may be used.
- Read your institution’s academic-integrity procedure before any meeting, so you know whether this is an informal chat or step one of a formal process, and whether you may bring an advisor.
- Do not confess to end the discomfort. This is the one that ruins cases. An admission is permanent; an unresolved accusation is not.
That list is not novel advice. What is novel is that you would have had to read six different pages to assemble it — which is what we did.
The words people will use at you
| Term | What it actually means | How it gets used |
|---|---|---|
| AI detector | A statistical classifier that estimates the probability text was machine-generated | Quoted as a verdict, sold as a screening aid |
| False positive | Human-written text the classifier labels as AI | Acknowledged in vendor documentation, absent from the marketing page |
| Perplexity | How surprising each next word is to a language model. Low = predictable = machine-ish | One of the two numbers behind most “AI score” gauges |
| Burstiness | Variance in sentence length and complexity. Humans vary; models don’t | The other number. Penalises consistent, well-edited prose |
| AI indicator / AI writing report | Turnitin’s percentage estimate of AI-written text in a submission | An institutional setting; whether your instructor sees it isn’t up to you |
| Academic-integrity process | Your institution’s written procedure for handling alleged misconduct | The document that defines your actual rights. Most students never read it |
We coded every advice page that ranks. None is complete.
On 12 August 2026 we pulled the live US search results for the four things a falsely-accused person actually types — falsely accused of using ai, accused of using ai, how to prove i didn’t use ai, and what to do if accused of using ai.[1] We took every student-facing advice page in the top ten, read it, and marked YES or NO against ten concrete defence actions. Six pages qualified. Here is every mark — all six pages are linked in the sources, so you can check the coding against the originals.[9]
| Page | Action 1 — don’t admit under pressure | Action 2 — ask for the specific evidence | Action 3 — version or revision history | Action 4 — drafts, outlines, notes, sources | Action 5 — timestamped process evidence | Action 6 — cite the false-positive evidence | Action 7 — offer to demonstrate knowledge | Action 8 — read the written policy | Action 9 — bring an advisor | Action 10 — keep it in writing | Total out of 10 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| GPTZeroDetector vendor | No | Yes | Yes | Yes | Yes | No | No | Yes | Yes | No | 6 |
| LLFLaw firm | No | Yes | Yes | No | No | Yes | Yes | Yes | Yes | No | 6 |
| NMLLPLaw firm | No | Yes | Yes | Yes | No | Yes | No | Yes | Yes | No | 6 |
| LyteWriterWriting-tool vendor | No | Yes | Yes | Yes | Yes | Yes | No | No | No | No | 5 |
| Tully RinckeyLaw firm | Yes | No | No | No | No | No | No | Yes | Yes | Yes | 4 |
| Winston AIDetector vendor | No | No | Yes | Yes | No | Yes | No | No | No | No | 3 |
| Pages advising itof 6 | 1 | 4 | 5 | 4 | 2 | 4 | 1 | 4 | 4 | 1 | 30 / 60 |
ToHuman, 12 August 2026. Six student-facing advice pages from the top ten organic results across four queries, each coded YES (✓) or NO (·) against the ten actions numbered above — the same ten, with full descriptions, are listed in the checklist below.[9] Mean coverage 5.0, median 5.5, 30 of 60 possible marks. Reddit and Quora threads, video results, faculty-facing guides and journal articles were excluded from the coding. Every coded page is linked in source [9]; a YES requires the page to advise the action explicitly, not to imply it.
Two things fall out of that table. The first is that the complete checklist does not exist on any page you are likely to land on — the best score is 6 of 10, and half the grid is empty. The second is that the gaps are not random — they track who is paying for the page. The three tool vendors cover 8 of 9 evidence-mechanics marks (actions 3–5) and 2 of 12 procedural-rights marks (actions 1, 8–10). The three law firms invert it exactly: 3 of 9 on evidence, 8 of 12 on rights. Each publisher documents the half of your problem its product solves. That said — three pages per group. Read the split as a pattern in what currently ranks, not as a measured rate for either industry.
And the three least-covered actions across all six pages — advised by exactly one page each — are don’t admit under pressure, offer to demonstrate your knowledge of the work, and keep the exchange in writing. None of those requires buying anything. That is probably the explanation.
It also explains why a Reddit thread, not a university page, holds the #1 organic slot on both the main query and what to do if accused of using ai. People ask peers because the institutions that run these processes mostly don’t publish this side of them.
How do you protect yourself against AI accusations? — r/college
Source: r/college — the #1 organic result for what to do if accused of using ai, US, 12 August 2026.
The merged checklist
Ten actions, with how many of the six ranking pages advise each one:
| Action | What it means in practice | Pages advising it |
|---|---|---|
| 1. Don’t admit under pressure | Ask for time before responding. “I’d like to review the assignment and my drafts before we discuss this” is a complete answer | 1 / 6 |
| 2. Ask for the specific evidence | Which tool, what score, which passages, what the policy permits that score to be used for | 4 / 6 |
| 3. Version / revision history | Google Docs File › Version history; Microsoft 365 Version History. Export or screenshot it before you touch the file again | 5 / 6 |
| 4. Drafts, outlines, notes, sources | Dated files, annotated PDFs, library or browser history, photos of handwritten notes | 4 / 6 |
| 5. Timestamped process evidence | Edit replays and keystroke records, where your tooling captured them. Powerful when it exists; can’t be created afterwards | 2 / 6 |
| 6. Cite the false-positive evidence | Bring the research, not an opinion about detectors. Sources below | 4 / 6 |
| 7. Offer to demonstrate knowledge | Talk through your argument, explain a choice on page three, write a comparable passage under observation. Often the most persuasive thing you can do | 1 / 6 |
| 8. Read the written policy | Find the academic-integrity procedure. Note the appeal deadline — it is usually short and it starts running immediately | 4 / 6 |
| 9. Bring an advisor | Student ombudsman, advocacy office, students’ union, or counsel if the stakes justify it. Many policies grant this and don’t advertise it | 4 / 6 |
| 10. Keep it in writing | After any verbal meeting, email a short summary of what was said and agreed. It creates a record you’ll want later | 1 / 6 |
Why the detector flagged writing you actually wrote
Detectors don’t recognise machines. They score statistical properties — how predictable each next word is, and how much your sentence lengths vary. Writing that is clean, consistent and well-edited scores the same way machine output does, because those are the same properties.
We measured this ourselves. In May 2026 we ran 861 verified human-written sentences — drawn from pre-LLM PubMed abstracts, Wikipedia, ESL learner writing and news journalism — through GPTZero’s v2 API, one sentence at a time. 13.8% came back classified as AI or mixed.[2] Worst hit: professionally edited news prose at 19.8%, and writing by people learning English at 16.0%.
The honest caveat, which matters if you plan to quote this in a meeting: that is not the number GPTZero publishes, and it isn’t measuring the same thing. GPTZero states a false-positive rate of no more than 1% at document level.[3] We tested at sentence level, which is deliberately the harder case — a short span gives the classifier far less signal. Both figures can be true simultaneously. Cite ours as what it is: a sentence-level worst case, on text nobody disputes was human-written. Our full write-up of AI-detection false positives has the wider measurement picture, and the 861-sentence study publishes the raw data.
Two external findings are worth having with you. Liang and colleagues at Stanford showed that GPT detectors are biased against non-native English writers, misclassifying a majority of TOEFL essays by non-native speakers while classifying comparable native-speaker writing almost perfectly.[4] Weber-Wulff and colleagues tested a range of detection tools and concluded they are neither accurate nor reliable.[5] If English is your second language, that first paper belongs in your file — we covered it in detail in our piece on AI detectors and non-native English speakers.
What your rights actually are
They are whatever your institution’s written procedure says they are, which is why step four exists. But there are patterns worth knowing before you read it.
Almost every published policy treats a detector score as an indicator, not as proof. Turnitin’s own guidance is explicit that the percentage should not be the sole basis for a misconduct decision, and that short documents score less reliably — which is why very low percentages are suppressed rather than shown.[6] Some institutions went further and switched the indicator off: Vanderbilt University and the University of Alabama at Birmingham each published their reasoning for disabling Turnitin’s AI detection.[7] We tracked the wider institutional picture in universities banning AI detection, and what the Turnitin number does and doesn’t mean in our Turnitin AI detection explainer.
Three practical rights to look for specifically: whether you may bring an advisor or support person to a meeting; what the appeal route and its deadline are; and whether you are entitled to see the evidence in writing before you respond. If the policy grants these and the process skips them, that is itself grounds for appeal.
Protecting yourself from the next one
The fix is boring and it works: write somewhere that keeps a history. Draft in Google Docs or Microsoft 365 rather than pasting a finished piece in at the end. Keep outlines and dated notes. If you research in a browser, don’t clear that history before a deadline. None of this changes your writing — it just means the timeline exists if anyone ever asks.
One honest note about tools like ours, because this page would be dishonest without it. ToHuman is not a defence against a false accusation, and running your own writing through a rewriter before submission is a bad idea: it replaces text you can account for with text you can’t. Where a humanizer legitimately fits is the other case — you did use AI assistance somewhere in a workflow that permits it, and the draft doesn’t sound like you. Then rewriting it into your own register is editing, not evasion.
We make no claim that any rewrite will change a detector’s verdict; the classifier belongs to somebody else and gets retrained without notice, which is the argument we made at length on our GPTZero bypass page. If you want to see what the rewrite does, the tool on the homepage is free for 2,500 humanized words a month with no card.
One last number, and it is not flattering to our own category. The five US queries we measured for help proving you didn’t use AI come to about 360 searches a month between them. AI humanizer gets about 823,000.[8] That is roughly 2,300 times more demand for changing the text than for defending the person who wrote it — and the supply has followed the demand, which is what the census above is really measuring.
Frequently asked questions
What to do if falsely accused of using AI?
Do four things before you reply to anything. Stop editing the file, so its revision history freezes where it was when you submitted. Export the evidence you already have — version history, drafts, notes, sources, browser history for the research. Ask, in writing, for the specific basis of the accusation: which tool produced it, what score it returned, which passages were flagged, and what the written policy says about how that score may be used. Then find your institution's academic-integrity procedure and read it before the meeting, so you know whether this is an informal conversation or the first step of a formal process, and whether you are entitled to bring an advisor. What you should not do is confess to end the discomfort. An admission closes the case permanently, and the discomfort of an unresolved accusation is temporary.
How can I prove I didn't use AI?
You prove it with process, not with prose. The strongest artefact is the document's own revision history — Google Docs File > Version history and Microsoft 365 Version History both record timestamped edits you cannot fabricate after the fact, and a real document shows dozens of sessions with false starts and deletions rather than one paste. After that: dated drafts and outlines, annotated sources, the browser or library history from your research, messages where you discussed the assignment, and handwritten notes photographed with their timestamps. The other half of proving it is demonstrating you understand the work — offering to talk through your argument, explain a choice you made on page three, or write a comparable passage under observation. Only one of the six ranking advice pages we read suggests that, and it is the thing an instructor is usually most persuaded by.
What happens if a teacher accuses you of using AI?
It depends entirely on your institution, which is why reading the written policy is step one rather than step five. Typically it starts with an informal conversation, where the instructor raises a detector score or a suspicion and asks you to explain. If it is not resolved there, it escalates to a formal academic-integrity referral: a written allegation, a hearing or panel of some kind, a decision, and an appeal route. Most published policies state that a detector percentage is an indicator, not proof — Turnitin's own guidance says the score should not be the sole basis for a misconduct decision, and Vanderbilt and the University of Alabama at Birmingham each disabled Turnitin's AI indicator entirely and published their reasoning. In practice the outcome usually turns on what evidence of your process you can produce and whether you can discuss the work convincingly.
I was flagged for AI when I didn't use it. What should I do?
Being flagged is not the same as being accused, and it is much more common than the vendor numbers suggest. When we ran 861 verified human-written sentences through GPTZero one sentence at a time in May 2026, 13.8% came back classified as AI or mixed — highest on clean, professionally edited news prose at 19.8% and on writing by people learning English at 16.0%. That is not the same measurement GPTZero publishes: it states a false-positive rate of no more than 1% at document level, and we tested at sentence level, which is deliberately the harder case. Both numbers can be true at once. Practically: preserve your version history immediately, ask what the flag is based on and what it means procedurally, and do not rewrite the flagged text hoping the number drops — editing the file after the fact damages the best evidence you have.
If you’re in this right now
Work the checklist in order, starting with the file you must stop editing. The evidence you need almost certainly already exists; the mistake most people make is destroying it in a panic, or agreeing to something in a meeting they walked into unprepared. Nothing on this page requires a purchase, and the parts that matter most are the free ones nobody else wrote down.
Sources
- DataForSEO — live Google organic SERPs, US (location 2840), English, depth 10, retrieved 2026-08-12, for falsely accused of using ai, accused of using ai, how to prove i didnt use ai, what to do if accused of using ai and ai detector false positive. dataforseo.com/apis/serp-api
- ToHuman — We ran 861 human sentences through GPTZero. 13.8% were flagged AI. (May 2026, raw CSV published).
- GPTZero — how our AI detector works, including the stated ≤1% document-level false-positive rate. gptzero.me/technology
- Liang, Yuksekgonul, Mao, Wu & Zou (2023). GPT detectors are biased against non-native English writers. Patterns 4(7), 100779. doi.org/10.1016/j.patter.2023.100779
- Weber-Wulff et al. (2023). Testing of detection tools for AI-generated text. International Journal for Educational Integrity. doi.org/10.1007/s40979-023-00146-z
- Turnitin — Understanding false positives within our AI writing detection capabilities, turnitin.com; and Using the AI Writing Report, guides.turnitin.com.
- Vanderbilt University — Guidance on AI detection and why we’re disabling Turnitin’s AI detector, vanderbilt.edu; University of Alabama at Birmingham — Ending the gen-AI detection war: turning off Turnitin’s AI detection, uab.edu.
- DataForSEO — Google Ads bulk search volume, US (2840), English, retrieved 2026-08-12: ai humanizer 823,000/mo; falsely accused of using ai 110; accused of using ai 110; how to prove i didnt use ai 90; what to do if accused of using ai 40; accused of using chatgpt 10.
- The six coded pages: GPTZero, LLF, NMLLP, LyteWriter, Tully Rinckey, Winston AI.
Methodology. The coverage census was run on 12 August 2026. We pulled live DataForSEO organic SERPs (US 2840, English, depth 10, tag w33-thu-falsely-accused) for four accusation queries plus one detector-error query, took every student-facing advice page appearing in the top ten, and coded each page YES/NO on ten defence actions defined in advance; a YES requires the page to advise the action explicitly, not to imply it. Reddit and Quora threads, video and social results, faculty-facing guides and journal articles were excluded from coding, leaving n = 6. Small n and single-coder judgement are the obvious limits: six pages is a census of what currently ranks, not a sample of published advice in general, and every YES/NO is one reader’s call. The complete six-by-ten coding is published above, mark by mark, and all six coded pages are linked in source [9], so every YES and NO can be checked against the original. One method change is worth disclosing: we had planned to code accusation threads collected from Reddit at scale, but Reddit’s search endpoint now refuses unauthenticated requests, so the SERP census replaced that plan mid-run. Detector figures come from ToHuman’s May 2026 study: 861 sentences from four verified pre-LLM human corpora submitted individually to GPTZero’s v2 endpoint (model 2026-05-11-base); sentence-level rates are higher than document-level rates by construction and are labelled as such wherever they appear. This page is general information about a process, not legal advice.
Published August 12, 2026 by the ToHuman team.