How to Keep a Writing Audit Trail (Before You Need One)

The single most useful thing in an AI accusation is a record of the writing happening. Not an argument, not a character reference — a timeline showing a document being built.

The problem is that this evidence cannot be created afterwards. By the time someone questions your work, the window has closed: anything you produce at that point was produced under suspicion, and it looks it.

So this is a guide to habits rather than to defence. All of it is cheap, none of it changes how you write, and if you never need it you have lost nothing but a few settings changes.

What a good audit trail actually shows

It helps to know what you are trying to demonstrate, because it is not "I typed this."

What persuades is evidence of process — the shape of composition happening over time. A paragraph appearing, being deleted, returning in different words. An outline that does not match the final structure. A section written on Tuesday and rewritten on Thursday. A sentence that was wrong before it was right.

Generated text has none of that shape. It arrives whole, in one action, already finished. That difference is far more legible than any statistical score, and it is why a version history usually ends these disputes quickly.

The corollary matters: a clean record is a weak record. A document that appeared in three large pastes with no revision looks the same whether you wrote it elsewhere or generated it. Messiness is the evidence.

Draft where history is recorded automatically

The foundation. Everything else is optional.

Google Docs keeps granular, timestamped revision history by default, indefinitely, with no configuration. It is the strongest artefact most people can produce and it costs nothing. File → Version history → See version history shows the timeline, and you can name versions at milestones to make it readable.

Microsoft Word keeps version history only when the file lives in OneDrive or SharePoint. A Word file saved to your local disk has essentially no history — each save overwrites the last. If you use Word, save to OneDrive.

Notion, Dropbox Paper, and most collaborative editors keep history, usually with a retention limit on free plans. Check what yours is.

Scrivener, Ulysses, and Obsidian keep snapshots or file history, but often only when configured. Turn it on now rather than discovering the setting later.

Plain text files on your own disk keep nothing. If you write in a local editor, you need one of the backup approaches below.

If you take one action from this article: draft your next substantial piece in Google Docs.

Do not paste in your finished work

This is the habit that quietly destroys the evidence, and it catches people who did nothing wrong.

If you write a document in one application and paste the finished result into another for submission, the receiving document's history shows a large block of text appearing in a single action. That is precisely the signature of pasted generated output. Your careful three-week process is invisible, because it happened somewhere the record does not reach.

Two fixes. Either draft directly in the document you will submit, or, if you must move text, paste it in sections as you write them rather than all at once at the end. Neither costs anything.

The same applies to composing in a chat interface. Even if every word is yours, drafting inside ChatGPT or Claude and pasting the result out creates a record that is impossible to explain favourably. Write in a document; use the model for questions if you use it at all.

Keep the material around the writing

Version history shows composition. Supporting material shows engagement with the subject, which is the second half of a convincing account.

Notes. Any form — a notebook, a text file, an app. Dated, messy, and not written for an audience. Notes that contain abandoned ideas and things you later decided were wrong are more persuasive than tidy ones, because nobody fabricates a bad idea.

Sources. The PDFs in your downloads folder with their timestamps. Your library database history. Highlights in a Kindle book. Browser history from the days you were working. These establish that you actually read the things you cited.

Outlines. Especially outlines that differ from the finished piece. A structure you abandoned is evidence of thinking.

Messages. A paragraph you sent to a friend asking whether it made sense. A question to a supervisor. An email to yourself at midnight. These are timestamped by a third party, which makes them harder to dispute than anything on your own machine.

Your own false starts. The opening you wrote and hated. Keep it.

None of this requires organising. It requires not deleting.

Write things down in your first language

Specific to anyone working in a second language, and genuinely powerful.

If you outline in your first language, take notes in it, or search in it, that material is close to unforgeable evidence of authentic composition. Generated English text does not come with a Bengali or Portuguese or Arabic outline behind it. It is also just a good way to think.

This matters more for this group than for anyone else, because detectors flag second-language writing at substantially higher rates for reasons unrelated to tool use — the mechanism is in why AI detectors fail non-native English speakers. If you are in that group, the audit trail is worth more to you than to most people.

Record your reasoning while you have it

The most underrated habit, and it takes two minutes.

When you finish a working session, write a few lines somewhere dated: what you worked on, what order you tackled it in, what you found difficult, what you cut and why, what you are unsure about.

This does two things. It creates a contemporaneous record, which is worth far more than a reconstruction. And it means that if you are asked to discuss the work months later, you can — because the reasoning is written down rather than half-remembered.

The ability to talk about your own decisions is usually what ends these conversations. Someone who wrote a piece can say why section three exists and what they nearly cut. Someone who generated it cannot, because there was never a decision to recall. A short working log preserves that ability past the point where memory fades.

If you do use AI assistance, log it

Not optional if you want the record to hold up.

Keep a note of what tool you used, for what, and on which sections. "Used Grammarly for the whole document. Asked Claude to suggest a better structure for section 2 on the 14th; rewrote it myself afterwards. Ran the introduction through a rewriting tool for rhythm."

The reason is practical rather than moral. Partial use disclosed precisely is defensible almost everywhere. A denial that later unravels is treated far more seriously than the original use at every institution — the cover-up is the thing that ends careers. A log means you never have to reconstruct what you did under pressure, which is when people misremember and get caught out.

It also lets you check your use against your institution's actual policy while you can still change course. Our guides to academic integrity and when to disclose cover where the lines fall.

Back it up

History is only useful if it survives.

Cloud-based editors handle this for you. If you draft locally, the cheapest approach is a folder that syncs automatically — Dropbox, OneDrive, iCloud — which gives you file versioning as a side effect. Writers comfortable with git get an excellent audit trail almost free, since each commit is a timestamped, immutable snapshot with a message explaining what changed.

Whatever you use, check that history is actually being retained rather than just files being mirrored. Some sync setups keep only the current version.

What this is not

Two clarifications, because this advice gets taken too far.

This is not about writing defensively. Do not add errors, avoid tools that help you, or roughen prose you worked hard to make clean. Detectors penalise clear writing, and the correct response to a broken measurement is not to write worse. Keep records, then write as well as you can.

This is not paranoia. Most people never need any of it. But the cost is close to zero — draft in Google Docs, don't paste in finished work, keep your notes — and the cost of not having it, in the cases where it matters, is very high.

If you are already in the situation and reading this too late, the sequence for what to preserve and what to say is in falsely accused of using AI. Start by not editing the document.