# How to prove you didn't use AI in Word · ScriptGrain

> Word's version history, AutoSave and Track Changes can show how a document was written. How to switch them on before you start, what they record, and what to do if your file only lives on your computer.

Canonical: https://scriptgrain.com/blog/how-to-prove-you-didnt-use-ai-in-word

# How to prove you didn't use AI in Word

*By Jack Stovell · 2026-09-29 · Guides*

The strongest evidence you can have is a record of the document growing over time. Word keeps one, but only if the file lives in OneDrive or SharePoint with AutoSave on. Set that up before you write a word, because it can't be added afterwards. Everything else in this guide is a fallback for when you haven't.

For the general case (process, consistency, live evidence), start with [how to prove you didn't use AI](https://scriptgrain.com/blog/how-to-prove-you-didnt-use-ai). This post is the Word specifics.

## The short answer

Four habits. That's it.

1. Save the file to OneDrive (or SharePoint, if it's a work file).
2. Keep AutoSave on.
3. Write in the one file, start to finish, rather than pasting in from elsewhere.
4. Keep your notes and sources, wherever they live.

Do those and you've built the record before anyone asked for it. Skip the first two and you're relying on softer evidence later. Softer isn't worthless, and I'll cover it below. But it's softer.

## Turn on the history before you write

Here's the thing about Word's history: it's a side effect of where the file lives. Version history works only for files stored in OneDrive or SharePoint in Microsoft 365. A file saved only on your own computer doesn't get it.

AutoSave is the engine underneath. It's a feature of Excel, Word and PowerPoint for Microsoft 365 subscribers, and it saves the file automatically every few seconds as you work. It's on by default when the file is stored on OneDrive, OneDrive for Business or SharePoint Online. So in most cases you don't switch anything on. You just save in the right place and check that AutoSave is still on when you start.

Check it once. Don't assume.

There's a limit to know about. With a personal Microsoft account you can retrieve the last 25 versions. With a work or school account, the number depends on how the library is configured, and that's up to whoever runs it, not you. So if you're writing something long over several weeks on a personal account, the earliest versions can eventually drop off the end. If the piece matters, save a copy at meaningful stages: after the outline, after the first full draft, after the edit. Save those under different names, in the same folder. A small chore now, a lot of proof later.

## What version history shows, and what it does not

To open it in Word for Microsoft 365, select the file's title and choose Version history. You can also go through File > Info > Version History. Select a version and it opens in a separate window. Restore brings it back, so look before you click that.

What a teacher or manager sees is the text building up in stages. A few paragraphs on one day. A restructure two days later. A rough conclusion, then a rewritten one. That's what human drafting looks like: uneven, revisited, occasionally backtracked. A paste-in of finished text looks very different. One version, or two, and the whole piece arrives at once.

That pattern is persuasive. It isn't magic.

Here's the honest limit. Version history shows when text changed. It doesn't show who typed it or how. Someone could, in principle, paste in chunks over several days, and the history would look staged too. So treat it as strong supporting evidence, not a signed confession of innocence. Its real value is that a genuine, gradual writing process leaves genuine, gradual traces.

Pair it with something you can say in person. If you can walk through why paragraph three moved, the history and the explanation back each other up. And to be fair, that combination is hard to argue with.

## Track Changes and the file's own details

Track Changes is the tool for drafts you share with a tutor or editor. You'll find it under Review > Tracking > Track Changes. Once it's on, deletions show as strikethrough, additions as underline, and different authors' changes appear in different colours.

That last detail matters. If your tutor suggests edits and you accept some and reject others, the marked-up document shows two people working on one text, each visibly distinct. It's a clean record of how a draft moved between you and someone else.

It's also useful for you. Turn it on when you start revising a finished draft and you can show exactly what you changed.

Then there's the file itself. Open File > Info and Word shows the file's properties, including when it was created and last changed, plus statistics it keeps for you such as the word count. You can't edit these automatically updated properties, which is precisely why they're worth glancing at. A file created two weeks before the deadline and last changed the night before tells a different story from one created and finished within the same few minutes.

That's all the file properties will tell you here. Don't lean on them for more than that.

## If you wrote it offline or already deleted the drafts

So the file sat on your desktop. Or you tidied up your drafts last month. Fair enough; plenty of people do exactly that, and nobody told them it would matter.

You still have options. They're just spread around.

Start with process evidence. Your notes, your outline, the sources you read, your browser history from the research sessions, earlier drafts you emailed to yourself or to a friend. None of it is as tidy as version history, but together it shows a piece of work with a beginning, a middle and some wrong turns. Gather it into one folder, in date order, before anyone asks.

Next, consistency. Your earlier writing is evidence, because people tend to write in recognisable habits: how long their sentences run, how often they reach for a comma, which connecting words they favour. You can compare the disputed piece with work you wrote before using the free [consistency checker](https://scriptgrain.com/tools/brand-voice-consistency-checker). It compares pieces by measured habits. Be clear about what that gives you: a comparison, not proof. It's useful because it turns "it doesn't sound like me" into something a person can actually look at.

Last, offer to explain or extend the work live. Ask to talk through your argument, or to write a further paragraph on the spot. It's the simplest test and often the most convincing one.

## Why a detector score is not the verdict

If your work was flagged, there's probably a number involved. Read it carefully.

A detector score is a probability from a model, not evidence of how a text was written. And the models get it wrong more often than people assume. In one Stanford study (Liang et al., Patterns, 2023), seven detectors wrongly flagged non-native English writing, TOEFL essays, as AI at 61.3% on average. Read that again. More than half.

Another study (Weber-Wulff et al., 2023, a multi-university European team) found 96% accuracy on plain human-written text but only 74% on unmodified AI-generated text. So even the better result leaves a quarter of unmodified AI text unflagged, while the same tools can still misfire on honest writers.

The same tool can post a 1% false positive rate in one test and 16% in another, because the tests used different texts and thresholds. The number depends on the conditions, not just the tool.

What does that mean for you? If your English is formal or learned, your careful, correct, slightly textbook phrasing is exactly what these models tend to misread. The fault lies with the method. The full sourced figures are on the [detector accuracy page](https://scriptgrain.com/reference/ai-detector-accuracy), and there's a longer look at [AI detectors and non-native English writers](https://scriptgrain.com/blog/ai-detectors-and-non-native-english-writers) if that's your situation.

The practical point: a score is a starting question, not a finding. Ask what else supports it.

## Questions

### Does Word show if you used AI?

No. Version history, AutoSave and the file's details record when the document changed, not how the text was produced. What Word keeps, if the file is in OneDrive or SharePoint, is that history of changes. That can show text arriving gradually or all at once, but it can't tell a reader who typed it or what tool, if any, was involved.

### Can a teacher see my version history?

Only if they can open the file itself. Sharing it from OneDrive or SharePoint may let them open its version history, depending on the access you give them. If you only submit a copy, they see the finished text. You can always open the history yourself and walk them through it.

### Does Google Docs have the same?

Google Docs keeps its own version history, and the same principle applies: a record of the document growing over time is your strongest evidence, and you need it to exist before the question arises. Write in one document, keep it in one place, and keep your notes and sources alongside it.

### What if my file was saved on my computer?

Then Word has no version history for it, because that works only for files stored in OneDrive or SharePoint. You can still check File > Info for created and last-changed dates, and lean on process evidence: notes, outline, sources, browser history, earlier drafts in email. Offering to explain or extend the work live helps too.

### Will a detector score get me in trouble?

It can start a conversation, but it shouldn't decide one. A score is a probability from a model, and the sourced studies show high error rates, especially for non-native English writers. Bring your process evidence, ask what else supports the flag, and ask to be assessed on the work and your ability to discuss it.

[More from the ScriptGrain Journal](https://scriptgrain.com/blog)