A KDP upload is the end of the process, not the editing process
Amazon KDP gives authors a direct path to ebook and print distribution, but a file that uploads is not automatically a book readers will trust. AI-assisted drafts need a human review of voice, facts, structure, rights, and reader expectations before they become a product.
Awtter gives that review a home. Import a draft, split it into Binder sections, clean mechanical residue, and keep the document, notes, research, and export settings together instead of moving between disconnected documents.
Disclose and document how AI was used
Platform policies change, so check the current KDP disclosure questions at the moment you publish. Keep a private project note describing which material was generated, which material you wrote, and which passages you substantially revised.
The Notepad view can hold project notes, source references, comments, and bookmarks while the Write view keeps section metadata and targets visible. That separation makes an honest production record easier to maintain.
Run a document quality pass before formatting
Read every section end to end. Check continuity, names, dates, citations, quotations, duplicated scenes, generic phrasing, and claims that need a primary source. AI can accelerate drafting, but it cannot take responsibility for the finished book.
Use Clean for predictable find-and-replace, paragraph cleanup, block cleanup, and reviewable presets. Use Structure and Notepad to confirm headings, research, character details, and unresolved comments before you compile.
Export, inspect, then publish
Create DOCX for an editor, EPUB for an ebook reader, PDF for proofing, TXT or Markdown for portable source, and ZIP for a complete project record. Open each file and verify front matter, back matter, chapter order, headings, and excluded notes.
When the files are ready, use Awtter's Publish workflow to keep the active compile preset and export history tied to the reviewed Binder state.