Module 6 · Lesson 6.4

Use Version History as Proof of Your Process

3 min read · Updated

A finished piece of writing can't prove who wrote it. The process can. Version history records how a document grew over time: when you started, how often you came back, what you added, cut and rewrote. Real writing leaves a messy trail. Pasted text arrives all at once.

Set this up before you need it. It costs nothing and takes two minutes.

Google Docs

Version history is on by default for every Google Doc.

  1. Open the document and go to File → Version history → See version history.
  2. The panel on the right lists every saved version, grouped by session. Click any one to see the document as it was, with changes highlighted.
  3. To mark a milestone, use File → Version history → Name current version, for example "Outline done" or "First full draft".

There are free browser extensions, such as Draftback, that replay a Google Doc's history keystroke by keystroke like a video. Some students share these replays when their work is questioned.

Microsoft Word

Word keeps version history when the file is saved to OneDrive or SharePoint with AutoSave turned on. Go to File → Info → Version History to see and open earlier versions. Files saved only on your computer usually don't keep this history, so save important work to the cloud from the start.

Other tools

  • Notion: page history is in the "…" menu at the top right. How far back it goes depends on your plan.
  • Apple Pages: File → Revert To → Browse All Versions, when the file is saved in iCloud.
  • Plain text and code: a Git repository gives you a complete, dated history of every change.

Habits that make your history convincing

Version history is only useful if it shows real writing. A few habits make a big difference:

  1. Start in the document. Put your first notes and outline in the same file you'll submit, rather than writing elsewhere and pasting the finished text in.
  2. Write over several sessions. Coming back to a draft over a few days creates a natural, dated trail.
  3. Keep your cut material. A "cuts" section at the bottom of the document, deleted at the end, shows the editing that went into the final version.
  4. Name versions at milestones. It takes five seconds and makes the history much easier for someone else to follow.
  5. Note where AI helped. If you used AI for a brainstorm or an outline, paste that into the document with a label. Being open about it beats having it discovered.
If you use AI to draft and then edit heavily, as this course teaches, your version history will show that too: a block of text arriving, then many rounds of changes. That's an honest record of AI-assisted writing. Whether it's acceptable depends on the rules where you're submitting it. See lesson 7.1 and lesson 7.2.

How to share it if asked

  • Share the document itself with view or comment access, so the reader can open version history themselves.
  • Or take screenshots of the history panel showing dates and sessions, plus two or three earlier versions.
  • Add a short note explaining your process: when you started, where your notes are, what tools you used.

Combined with your notes and research trail, this is the strongest evidence you can offer if you're falsely flagged.

Try this

Open the version history of the last document you worked on. How many sessions does it show? Would a stranger be able to see how the piece came together? Name the current version, and start your next piece of writing in the document from the very first note. That finishes Module 6. Module 7 covers the rules around AI writing.