Become a Writer Today

Falsely Accused of Using AI? A Defense Guide for Writers

BC
By Bryan Collins
20 July 2026 · 5 min read

In April 2026, Hachette cancelled a horror novel. Not for plagiarism, not for poor sales projections, but because of an AI detector score. I have been writing and editing professionally for two decades, and I think every working writer now needs a file they hope they never open: proof they wrote their own book.

This guide covers what actually happened in the two cases every editor is now thinking about, what the published accuracy evidence says about the tools used, and the provenance checklist I recommend you start keeping today.

What happened with Shy Girl

Mia Ballard’s horror novel Shy Girl started as a self-published book, got picked up by Hachette, and was pulled before its US release. According to Slate’s April 2026 account, readers on Reddit and YouTube had raised suspicions for months, then the detection company Pangram analysed the full manuscript and flagged it as 78 percent AI-generated. After a New York Times story presented the evidence, Hachette cancelled the book.

CBC’s reporting adds the detail that matters most for the rest of us. Hachette cancelled both the US and UK releases. Ballard denied using AI to write the novel, but said it was possible an editor she had worked with on the self-published version might have. And the industry split: some accepted the accusation and Hachette’s response, while others considered the punishment prejudicial because detection software is imperfect. John Degen, president of the Writers’ Union of Canada, told CBC: “I really would have preferred to see her publisher stand up for her and stand behind the work themselves because they trusted their own process.”

Notice what decided the outcome. Not a confession, not a court, not the publisher’s own editorial process. A score.

The Commonwealth Short Story Prize case

A month later the same script ran in literary fiction. Jamir Nazir’s story “The Serpent in the Grove” won the Commonwealth Short Story Prize for the Caribbean region and was published in Granta. Then, as The Conversation reported in May 2026, screenshots circulated on X of Pangram reports claiming 100 percent of the text was AI-authored. Granta’s publisher, Sigrid Rausing, even consulted Claude, an AI chatbot, which concluded the story was “almost certainly not produced unaided by a human”. Her final position: “perhaps we will never know.”

Two things in that story deserve attention. First, no formal determination was ever made; the doubt itself became the verdict in public. Second, the Commonwealth Foundation declined to start running detectors on submissions, saying that scanning unpublished work “would raise significant concerns surrounding consent and artistic ownership” and that a prize must operate on a principle of trust.

What the accuracy evidence actually says

I keep a full evidence page on this site, with every figure linked to the study it came from: AI detector accuracy: what independent tests find. The short version:

The pattern that should worry fiction writers: the Authors Guild concluded that polished, edited prose by experienced human writers shares many characteristics with AI output. Clean writing is the false-positive profile.

The provenance checklist

None of the following requires new software. It requires the discipline of not deleting things.

  1. Draft in a tool with version history and never turn it off. Google Docs, Word with AutoSave to OneDrive, and Scrivener snapshots all keep timestamped revisions. A document that visibly grew across hundreds of editing sessions over months is close to impossible to fake and close to impossible to argue with.
  2. Keep your dated drafts as separate files. At the end of each significant revision, export a dated copy (2026-03-14-draft2.docx) to a folder you never prune. Email major drafts to yourself or a trusted reader; the email headers are independent timestamps you do not control.
  3. Keep the mess. Notebooks, outlines, character sheets, voice memos, research bookmarks, the deleted chapter that did not work. AI-generated manuscripts arrive clean. Human manuscripts trail wreckage, and the wreckage is your alibi.
  4. Preserve correspondence. Notes from beta readers, editorial letters, critique-group comments on early drafts. Third parties who watched the book evolve are witnesses, not just readers.
  5. If you use AI for anything, log it. Spell-check, a brainstorm you discarded, a synopsis draft. Keep the chat transcripts and note what was and was not used. Ballard’s account of Shy Girl, per CBC, is that an editor she hired may have introduced AI; if you hire freelance help, put an AI clause in the agreement and keep their marked-up files.
  6. Know the policies before you submit. Markets differ wildly on what is allowed and what must be disclosed. I keep a tracker of magazine and contest rules at /ai-submission-policies/, and if you publish through KDP, Amazon’s generated-versus-assisted distinction is walked through at /kdp-ai-disclosure/.

If the accusation arrives anyway

Ask, in writing, exactly which tool was used, on which text, and what score it produced. Any accuser acting in good faith can answer in one sentence. Then respond with provenance, not indignation: version history export, dated drafts, correspondence. Point to the published false-positive evidence, ideally the Authors Guild test and the benchmark page that collects it. If the stakes are contractual, as they were for Ballard, that is the point to involve an agent, an authors’ organisation such as the Authors Guild or the Society of Authors, or a lawyer, before agreeing to anything.

A score is not evidence of anything on its own. The record of your work is. Build it now, while nobody is asking.

Newsletter

The writer's edit

One practical writing tip, a new tool, and a fresh contest deadline, every Thursday. No spam, unsubscribe anytime.