AI-Assisted vs AI-Generated: What Novelists Need to Disclose

A grammar checker fixing a comma and a chatbot writing your next chapter are not the same thing, even though both involve software. The phrase you want is AI-assisted vs AI-generated, and the gap between those two ideas is wide enough to matter for your contracts, your award eligibility, and what you are asked to disclose when you publish. If you write fiction, it is worth understanding the line before someone asks you which side of it you are on.

Two terms that get blurred together

AI-assisted work means a human writes the book and uses software along the way. You might brainstorm a list of names, talk through a plot knot, ask for feedback on a scene, or clean up grammar. The choices and the sentences are yours. The tool is a helper, the way a thesaurus or a writing group is a helper.

AI-generated work means the machine produces the prose. You prompt it, and it returns paragraphs of finished writing that go into the book more or less as the model wrote them. The human role shrinks to steering and selecting.

Most working novelists who use any tools at all sit on the assisted side. The trouble is that the labels often get collapsed into one, so a writer who only used a tool for outlining can feel tarred with the same brush as someone who generated a whole novel from a single prompt. Knowing the difference lets you describe your own process honestly.

Why the line matters for AI-assisted vs AI-generated

Three separate systems care about this distinction, and they care for different reasons.

• Publishing platforms. Self-publishing services, Amazon KDP among them, generally ask authors to disclose AI-generated content while treating ordinary assistive use as nothing they need to hear about. The disclosure is usually a checkbox or a question during upload, not a public label.
• Awards and writer organizations. Many contests and professional bodies generally exclude fully AI-generated work from eligibility, while still welcoming books written by a human who used tools. The exact wording varies a lot from one organization to the next.
• Copyright. In general, copyright protects human-authored expression rather than purely machine-generated text. The book you wrote yourself is yours to protect. Passages a model produced may sit on shakier ground.

None of this is settled law or a fixed standard, and the policies move. Treat the points above as the shape of the landscape, not a rulebook, and read the current version of any policy that applies to you.

Stay in the driver's seat

The cleanest way to stay on the assistive side of the line is simple. Keep writing the actual sentences yourself. Use tools for the surrounding work, the parts that have always involved other people and other references: ideas, structure, research, feedback, proofreading.

When a model hands you finished prose and you paste it in, you have crossed into generated territory, even if you edit afterward. When a tool helps you think and you go write the scene, you have not. The test is whose words ended up on the page.

Keep notes on how you worked

If you ever need to answer a disclosure question or a publisher's query, a short record makes it painless. You do not need anything formal. A few lines per project will do.

• Which tools you used, and for what: outlining, naming, grammar, continuity checks.
• Whether any tool produced prose that went into the manuscript, and if so, where.
• The date, roughly, so you can match it to whatever policy was current at the time.

This is the same habit good researchers keep about their sources. It costs you almost nothing now and saves you a scramble later.

Tools that read your draft, not write it

Here is a useful distinction inside the assistive category. Some tools generate text. Others only read and organize what you have already written. A tool that reads your manuscript and never adds prose to it sits firmly on the assistive side, because it changes nothing about who authored the words.

Continuity tracking is the clearest example. Software that scans your draft to remember that a character's eyes were green in chapter two, then flags the moment they turn brown in chapter nine, is doing the work a sharp-eyed editor does. It is not writing your book. Everwrite's continuity copilot works this way: it reads your draft, builds a local story bible, and flags contradictions, and it never writes prose for you. It runs on Apple's on-device intelligence, so the manuscript stays on your machine rather than going to a server. That is one option among several, and the same logic applies to any tool that reads rather than writes.

Disclose when asked, and check the current rules

You do not need to announce your tools to the world. You do need to answer honestly when a platform, a contest, or a publisher asks. If you generated prose, say so where the form requests it. If you only used assistive help, ordinary disclosure rules generally do not ask anything of you, but read the specific policy to be sure.

This is guidance, not legal advice, and the policies in this area change quickly. Before you publish or enter a contest, find the current, specific guidelines for that platform or organization and follow those. The terms AI-assisted and AI-generated give you the vocabulary to read those policies clearly and describe your own work without overstating or hiding anything. That is most of the battle.