Your Drafts Are Your Defence: Building an Authorship Trail Before Anyone Asks
Being told your own essay ‘looks like AI’ is a strange experience. You know you wrote it. You remember the late-night paragraph you rewrote four times and the source you nearly gave up on. But the email from a tutor or module leader lands, and suddenly you are scrabbling through old files trying to remember what you did three weeks ago. The answer is not to write a panicked defence at midnight. It is to build a quiet, boring evidence folder while you work — and to know how to present it calmly if anyone asks.
An evidence folder is not a loophole
Let’s be clear about the point. This is not about ‘beating’ an AI detector, and it is not a cover story for work you didn’t do. It is a record of authorship: the drafts, notes, sources and conversations that show how your argument grew. UK universities rightly expect students to work with integrity. If you used AI in a way your policy allows — for brainstorming, checking grammar, or planning — say so. The folder is there to support honest work, not to disguise dishonest work.
Save the messy middle
Most students save the final file and nothing else. That is exactly when the panic starts. Keep the awkward middle: the outline with three crossed-out thesis statements, the paragraph you pasted into a separate doc and rewrote, the version where you changed your mind about the conclusion. If you draft in Google Docs or Word, version history is your friend. Take dated screenshots or export page history where the platform allows, and keep the original document files rather than only PDFs. A folder of drafts with dates tells a more convincing story than a single polished file.
Keep a source trail you can follow
Detectors are not the only thing that can make writing look ‘generic’. Weak referencing can do it too. Keep your reading notes in a way that links claims to sources: author, page number, a short quotation, and the database or library record. If you use Zotero, Mendeley or EndNote, export a copy of your library at the end of the project. If you use library search, keep the search terms and dates in a simple notes file. Do not dump whole articles into your notes; keep the citation and the bit you actually used. That trail is useful for your bibliography, and it is useful if someone asks how you got from a source to a sentence.
Put tutor conversations in writing
After a meeting with your tutor or supervisor, send a short follow-up. ‘To confirm, we agreed the argument should focus on X, and I’ll send a draft by Friday.’ It takes two minutes and creates a neutral record. Save feedback emails, Turnitin receipts, extension approvals and any messages about the brief. If you had a verbal conversation that mattered, make a note of the date and what was agreed. You don’t need to record anyone secretly; a polite follow-up email is enough.
A five-minute folder structure
Create one folder for each module or project. Inside, use simple subfolders: 01_brief, 02_outline, 03_drafts, 04_sources, 05_feedback, 06_final. Add a one-page README or index that lists the main files and dates. Name drafts with dates: essay1_draft_2026-10-03.docx. It is not glamorous. That is the point. When you are stressed, you want a folder that explains itself.
If the email lands
First, read your university’s academic integrity policy and the email properly. Ask which part of the work has been flagged and which tool was used. Many detectors produce a probability score, not a verdict, and false positives do happen. Ask for a meeting rather than firing back a long defence. Then assemble a short evidence index: a table with the date, the file, and what it shows. Offer to share the folder; don’t attach fifty files to your first reply.
Contact your student union advice service or the university’s academic integrity office if you are unsure of the process. They can explain what the panel will ask and what support you are entitled to.
Present it without sounding defensive
Lead with a timeline, not a speech. ‘Here is my outline from 2 October, my draft from 9 October, and the feedback email from my tutor on 10 October.’ Show two or three strong pieces of evidence, not everything you own. If you used AI for permitted planning or proofreading, say what you used and when, and point to the policy that allowed it. If you did not use AI at all, say that plainly. Avoid claiming that detectors are ‘always wrong’; the stronger point is that your own process is documented.
What not to put in the folder
Do not backdate files, invent notes, edit metadata or delete drafts after you have been flagged. That turns a misunderstanding into a misconduct issue. Do not ask a friend to write a retrospective ‘study journal’ for you. Do not submit a folder that includes other people’s work or personal data you do not need. Keep it relevant, dated and honest.
The calm version of events
A false AI flag is stressful, but it is not proof of anything. Your best defence is the ordinary evidence of how you work: the messy outline, the source notes, the tutor email, the draft that changed direction. Build that folder as you go. If the email never comes, you have lost five minutes. If it does, you will have something far better than panic: a calm, factual record of your own writing.
