首頁 / ShortFling 部落格 / Writing
本文目前僅提供英文版。閱讀英文版 →
WritingAccused of Using AI? How to Prove You Wrote Your Story
The accusation you cannot disprove with a score
A common complaint from writers in 2026 goes like this: someone runs your story through an AI detector, posts the percentage, and suddenly you are the one who has to prove a negative. A higher detector score in your favour does not settle it, because the other side can always say the tool missed something.
The most useful case study of how to get out of that position comes from one of the biggest literary disputes of the year. It shows that what actually cleared a writer was not software, but an ordinary paper trail. This post explains that case and turns it into a checklist. Whether detectors themselves can be trusted is a separate question, covered in Can AI detectors prove a novel was AI-written?
What happened at the Commonwealth Short Story Prize
In May 2026, shortly after the Commonwealth Foundation announced its regional winners, readers and commentators online accused several of the winning stories of being AI-generated. The most prominent target was “The Serpent in the Grove” by Jamir Nazir, the Caribbean regional winner from Trinidad and Tobago. Granta, which had published the winning stories for more than a decade, stepped back from the partnership, citing editorial integrity.
On June 22, 2026, the Foundation’s Director-General, Razmi Farook, published the result of a month-long review. The Foundation said it had not used AI detection tools, citing concerns about artistic ownership and consent around unpublished work, and noted that such tools “cannot provide conclusive evidence on their own.” Instead, it held detailed discussions with every regional winner about their creative process and examined “working drafts, time-stamped documents and notes.” It concluded that AI was not used to write the winning stories. Nazir went on to win the overall prize at the end of June.
In an interview with the Trinidad Express published July 6, Nazir explained the polish that critics had read as machine-made. He said neuropathy means he can no longer type, so he dictates with speech-to-text on his phone and then revises a few lines at a time on the small screen. The fallout was not over: the Foundation later postponed the opening of the 2027 prize until January 2027 to review its rules and processes.
Why process evidence works when detectors don’t
A finished text can only show what it looks like. A process record shows how it came to exist: the abandoned opening, the scene you moved, the note to yourself about a character’s motive, the date each version was saved. Faking months of uneven, messy development is much harder than producing one clean file, which is why the Foundation treated drafts and timestamps as meaningful.
It also protects writers whose style happens to look “too smooth.” Nazir’s case is a reminder that dictation, accessibility tools, or a habit of heavy line editing can all produce prose that some readers find suspicious. Your process is the explanation, so it is worth keeping proof of it.
A practical record-keeping checklist
Keep dated drafts, not just the final file. If you write in Google Docs, version history already records who changed the file and when; you can open it from the “Last edit” link and give important milestones a name, such as “first full draft” or “after beta readers.” Google’s help pages note that deleting version history is permanent, so leave it alone. If you write in a local app, save a new copy at each major stage instead of overwriting one file.
Keep your notes and outlines. Character sheets, plot outlines, research links, and scribbled scene ideas are exactly the kind of “notes” the Commonwealth review looked at. A photo of a notebook page is fine.
Keep raw material from your method. If you dictate, keep the unedited transcripts or voice memos. If you get feedback, keep the beta-reader comments or critique-partner emails that show what changed and why.
Be honest about any AI you did use. If you used a tool for brainstorming or line edits, keep that record too and be ready to describe it plainly. Many platform rules distinguish assistance from generation, as our comparison of fiction platforms’ AI rules shows, and a clear account of what the tool did is far more convincing than a blanket denial that later turns out to be incomplete.
Store copies somewhere you control. A backup on your own drive or cloud account means your evidence does not depend on any single website staying online or keeping its edit history.
If you are accused anyway
Respond once, calmly, and to the people who actually decide: the contest organiser, the publisher, or the platform’s moderators. Offer to show your process privately rather than posting unpublished drafts in public, which can expose work you may want to sell later. Avoid posting your own detector screenshots as a rebuttal; it invites a battle of percentages that nobody wins.
Some authors are also looking at formal human-authorship labels from writers’ organisations; we look at one of them in the Authors Guild’s Human Authored certification explained. A label can help, but the drafts behind it are still what carries weight if someone challenges you.
Writing on ShortFling
ShortFling’s /write studio includes an AI editor that helps with outlining, drafting and revision, free within a daily allowance. It is a writing tool, not a proof-of-authorship system, so we suggest keeping your own dated drafts and notes outside the platform before you publish, especially for work you might enter in contests or sell elsewhere.
Every published story requires a creator agreement confirming the work is your own original work and that all characters are adults. Pressing publish submits the story for review, and it goes public in the fiction library only after approval. If an accusation ever turns into a formal dispute, this is an overview, not legal advice.
FAQ
Can an AI detector score prove I wrote my story?
Not on its own. In the 2026 Commonwealth Short Story Prize review, the Commonwealth Foundation said detection tools can be useful indicators but cannot provide conclusive evidence, and it relied on drafts, time-stamped documents, notes and interviews instead.
What evidence should I keep to show I wrote my own work?
Dated drafts or version history, outlines and notes, dictation transcripts or voice memos if you dictate, feedback from readers or editors, and an honest record of any AI tools you used and what they did.
Does Google Docs keep a record of my drafts?
Yes. Google Docs version history shows who changed a file and when, and you can name important versions. Deleting version history is permanent, so keep it intact.
Does ShortFling verify that I wrote my story?
No. ShortFling requires a creator agreement confirming originality and reviews stories before they go public, but it does not issue proof of authorship. Keep your own drafts and notes.
Sources
- Commonwealth Foundation: 2026 Commonwealth Short Story Prize update (June 22, 2026 statement on drafts, timestamps and detectors) (checked 2026-10)
- Brittle Paper: Commonwealth Short Story Prize clears regional winners after month-long review (June 26, 2026) (checked 2026-10)
- Book Riot: Writer accused of AI use wins Commonwealth Prize; Granta ended partnership (July 2026) (checked 2026-10)
- Trinidad Express: Who is Jamir Nazir? Interview on dictation and neuropathy (July 6, 2026) (checked 2026-10)
- The Art Hub: Commonwealth Foundation postpones opening of 2027 prize until January 2027 (checked 2026-10)
- Google Docs Editors Help: Find what’s changed in a file (version history) (checked 2026-10)




