Study
Show Your Writing Process With Annotated Drafts
The best evidence that you wrote something is the mess you made on the way. Kept drafts, marked-up sources and a short note about what changed turn that mess into a record a teacher can read in five minutes.
Writers have always produced drafts, notes and crossed-out paragraphs; what has changed is that those leftovers now matter. When a teacher is unsure how a piece of work was produced, the fairest thing anyone can look at is the process, and a student who kept it can answer the question in minutes. This page shows how to keep a process record without extra work, and how to mark it so the important changes are obvious to someone reading it for the first time.
In short
To show your writing process, keep version history on, save one dated draft per writing session, keep the sources you read with your highlights, and write a five-sentence process note. Then highlight what changed between your first and final drafts, so a teacher can see the work grow in your own hands.
What to keep while you write
| Keep | Why it matters | Effort |
|---|---|---|
| Version history in your editor | Shows the work growing over days, with dates, in small steps | None: turn it on and leave it |
| The sources you read, with your highlights | Shows you read what you cite and what you took from it | Low: highlight as you read anyway |
| Your outline or plan | Shows the structure came from you before the prose did | Low |
| One saved draft per writing session | Lets a reader compare two moments of the work side by side | Low: save a copy with the date in the file name |
| A short process note | Tells the reader what changed and why, in your words | Ten minutes at the end |
Online editors keep a history of changes automatically; desktop word processors can keep previous versions when files are saved to a cloud folder. Check your editor's help pages once so you know where the history lives. On paper, date each draft at the top and keep them in a folder.
Marking your drafts in three passes
Highlight what changed between two drafts
Put your first full draft next to the final one. In yellow, mark every passage in the final version that is new or was substantially rewritten. Real revision is uneven: some paragraphs stay almost identical, a few are rebuilt, and an argument or example often arrives late. That unevenness is exactly what a reader expects to see.
Link each source claim to its source
In a second colour, mark each sentence that depends on something you read. In your saved copy of the source, highlight the passage it depends on. For web sources, a highlight link from the link generator takes your teacher straight to the sentence you used.
Write a process note of five sentences
What was your first idea, and what changed it? Which source mattered most? What did you cut, and why? Which part was hardest? Did any tool help, and with what? The last question is the one teachers most want answered; writing an honest disclosure of tool help shows how to phrase it.
A worked example: one paragraph, three sessions, marked
Here is a paragraph from an imagined school essay on the bicycle, saved at the end of three writing sessions. The texts are short so the marks are easy to see; the pattern is the same in a full essay.
| Session | Text saved | Marks and record |
|---|---|---|
| Monday | Bicycles became popular in the 1890s because they were cheaper than horses and women could use them too. | First draft. The outline beside it says: cost, women, safety bicycle? |
| Wednesday | Bicycles spread quickly in the 1890s. They were cheaper to keep than a horse, and the new safety bicycle, with two equal wheels and a chain drive, was easier to ride than the high-wheeled models before it. Women in particular took them up. | The safety bicycle arrives after Tuesday's reading. The student's copy of a museum page has "two equal wheels and a chain drive" highlighted, with a highlight link saved. |
| Friday (final) | The safety bicycle, with two equal wheels and a chain drive, spread quickly in the 1890s because it was easier to ride than the high-wheeled models that came before it and far cheaper to keep than a horse. Writers of the time noticed that women took it up in large numbers, and the illustrated magazines of the decade are full of them. | Yellow on the rebuilt first sentence: the argument now leads with ease of riding. Green on "writers of the time noticed": a source claim, linked to a highlighted passage in a magazine archive. Process note line: "I started with cost; the museum page moved the argument to ease of riding." |
What the record shows is ordinary and therefore convincing: an idea that changed after reading, a source that can be opened at the exact passage, and a final sentence that is better than the first because of both. Nothing about it needed extra effort beyond saving a copy on three days and highlighting while reading.
What a teacher sees when they read it
A teacher reading a marked record looks for the same things they look for in a conversation about the work: an idea developing over time, sources that were really read, and choices the writer can explain. Our page on a fair authorship review using highlights describes that review from the teacher's side. Students who hand in a record like this rarely need the conversation at all, and when they do, it is short, because the evidence is already on the table.
The record also protects against the weakest kind of evidence. Automated writing checks can flag human work, especially from writers using English as an additional language, and a style that happens to be plain or formulaic can look suspicious to a hurried reader. A dated trail of drafts is much harder to argue with than any score or impression.
How to prove you did not use AI: the record that shows it
Strictly, nobody can prove a negative, and you should not have to. What you can do is show a positive record of how the work was made, which is far more persuasive than any claim about what you did not do. The checklist below is that record. Every line is something a teacher can open and see for themselves.
| Check | Where it lives | What a reader sees |
|---|---|---|
| Version history switched on | Google Docs: File, then Version history. Microsoft Word: the Version History command under the file name, which works only for files saved in OneDrive or SharePoint | Timed edits accumulating over days, with small changes rather than one large paste |
| One dated draft per session | A copy saved with the date in the file name, or a photo of each paper draft | Two moments of the same page, side by side |
| Sources with your highlights and notes | The PDF or web highlights, exported into a file you keep | That the sources were read and what you took from each |
| A highlight link per source claim | In the margin of your marked final draft, or in the process note | One click opens the source at the passage you used |
| A five-sentence process note | At the end of the final draft or on a cover sheet | What changed, why, and what any tool did |
| A marked comparison of first and final drafts | Your own copy of the final draft, with the changed passages in yellow | The revision at a glance, without reading both drafts in full |
The record is also the natural end point of the reading side of this site. Highlights made while reading become a dated export of your highlights and notes, and that export sits next to your drafts as one file. The guides on turning highlights into a record of work cover the reading half; this page covers the writing half. A teacher who receives both rarely needs to ask anything at all.
Pitfalls that weaken the record
- Drafting in a chat window or a notes app and pasting into the editor. The history then shows one large paste, which is exactly what you do not want it to show. Draft in the document itself.
- Saving the final draft over the first. Use Save a copy, or rely on version history, so the earlier moment survives.
- Highlighting a source without a note. A highlight alone shows you saw a passage; a note in your own words shows you understood it.
- Writing the process note last minute in vague terms. "I edited it a lot" tells a reader nothing. Name the idea that changed and the source that changed it.
- Cleaning up the folder. Deleted false starts and crossed-out paragraphs are evidence of thinking. Keep them.
Habits that make the record better
- Write in one place. Drafting in several apps and pasting the result together erases the history. If you must move text, keep the older file.
- Make your notes in your own words. Notes built from highlights, as in turning highlights into notes you use, show your understanding directly.
- Do not clean up the history. Deleted false starts and awkward first sentences are part of the evidence. Leave them.
- Share, do not attach, when you can. A view-only share of the document with its history is more convincing than a folder of exported files.
None of this needs special software, and all of it helps the writing as well as the record: a marked comparison of two drafts is also the fastest way to see whether your revision actually improved the argument. The rest of the pages on highlighting for study cover the reading side of the same skills.
Common questions
How can I prove I wrote my essay myself?
Keep version history on, save dated drafts, keep the sources you read with your highlights, and write a short note on what changed and why. A marked comparison of your first and final drafts shows the work growing.
Does version history show when text was pasted in?
Most editors record each change with a time, so a large block appearing at once is visible, as is a steady build-up of small edits. That is why writing in one document helps.
What should a process note include?
Your first idea and what changed it, the source that mattered most, what you cut, the hardest part, and any tool that helped and how. Five honest sentences are enough.
Should I keep drafts on paper too?
Yes, if you draft on paper. Date each page and keep them together; a photo of each draft is a good backup.
Is a process record useful if nobody asks for it?
It is still the quickest way to review your own revision, and it costs almost nothing to keep. When a question does come up, it answers it immediately.
What if I did not keep my drafts?
Start the record now. Check whether your editor kept version history without you asking (Google Docs does for files in Drive; Word does for files in OneDrive). Gather the sources you read and mark the passages you used. Write the process note from memory, honestly, and offer to talk the work through. A partial record is still far better than none.
Sources
- Google Docs Editors Help: Find what's changed in a file (version history)
- UK Quality Assurance Agency for Higher Education: Academic integrity resources
- Liang, W. et al. (2023). Study of detector bias against non-native English writers, Patterns 4(7). Preprint arXiv:2304.02819
- Microsoft Support: View previous versions of Office files (Version History works for files in OneDrive or SharePoint)