Accused of using AI? Your Google Doc already has the proof.

Why detectors get it wrong

AI detectors read the final text and estimate how predictable it is. Clear, well-structured writing, the kind teachers ask for, is exactly what they mistake for machine output. Non-native English writers, students who follow templates closely, and anyone who edits heavily toward polished prose get flagged more often. None of that is proof of anything, and most universities now tell instructors not to rely on a detector score alone.

The problem is that a score is easy to produce and hard to argue with. "I didn't use AI" is a claim. What you need is a record.

The record you already have: revision history

Every Google Doc keeps a complete history of edits, stamped to the second. Google's built-in version history view only shows snapshots. Checked4AI reads the same data and turns it into a character-by-character replay of the whole writing process: the first messy sentence, the paragraph you deleted, the citation you went back to fix, the three sessions across two evenings.

A document written by a person looks like a person wrote it. Text pasted from ChatGPT arrives in one or two large blocks with almost no edits afterward. The difference is obvious inside ten seconds of playback, and it doesn't depend on anyone's opinion of your prose style.

How to prove you wrote it, step by step

1. Install the free Checked4AI Chrome extension and sign in with the Google account that owns the document.
2. Open the Google Doc you're being asked about. Don't edit it first; the history is already there and anything you add now will only appear at the end.
3. Click the Checked4AI button in the Docs toolbar. The revision history syncs and the viewer opens in a new tab.
4. Read your Natural Typing score. A score in the 70–100% range means the history is consistent with organic drafting: normal delete ratio, varied keystroke timing, little pasted text.
5. Open the session timeline and note when you wrote each section. Dates and times are the part instructors find most persuasive.
6. Export the replay as a video (Pro) or screen-record the playback, and send it along with a short, calm note explaining what it shows.

What to say to your instructor

Keep it factual. A message that works: "I understand the detector flagged my essay. I wrote it in Google Docs and the full revision history is available. Here is a replay of the document being written, with timestamps for each session. I'm happy to walk through it with you or share the document so you can view the history directly."

Offering to share the original document is important. Your instructor can install Checked4AI themselves, open your doc, and see the same replay. That's stronger than any file you send, because they generate it independently.

What the replay will and won't show

• It shows drafting. Typing, pausing, deleting, rewriting and moving text are all visible, in order, with timing.
• It shows pastes. Text pasted from anywhere, including your own notes, appears as a single instant insertion. If you drafted in another app and pasted into Docs, the replay will show a paste, and you should explain that up front.
• It doesn't prove where pasted text came from. A paste is a paste. The case for authorship comes from the editing that surrounds it.
• It only covers Google Docs. If you wrote in Word, Pages or Notion, there is no Google revision history to replay. Those apps have their own version tools, but they are far less granular.

Protect yourself on the next assignment

Draft in Google Docs from the first word, in the document you'll submit. Avoid writing elsewhere and pasting in. If you use AI for brainstorming or feedback, keep that in a separate doc and type your own sentences into the essay. The history then tells the whole story on its own, and you never have to argue with a percentage again. See our guide to replaying revision history for how the replay works in detail.