Start with the document you actually have
An AI-assisted document may be a chat export, a collection of files, or a long document with repeated attempts. Begin by identifying the source of truth and the sections that are real book content rather than prompts, options, or process notes.
Awtter's Import workflow accepts pasted text or files, detects section boundaries, and lets you review what will be added to the Binder before it becomes part of the project.
Edit in layers
Developmental editing checks the promise and structure of the book. Copy editing checks clarity, consistency, and style. Proofreading checks the final files. Running these passes in order is more reliable than asking one tool to make every decision at once.
Use Structure for the outline, Write for section targets and status, and Notepad for synopsis, research, characters, locations, comments, and footnotes.
Format the book for its destination
An ebook needs flexible reflow and tested navigation. Print needs page geometry, readable typography, and reliable front matter. An editor may prefer DOCX, while a client may need a portable Markdown or TXT package.
Awtter's compile presets keep the selected formats, inclusions, page breaks, and table-of-contents settings in one reusable configuration.
Build a proof and recovery loop
Generate the files, inspect them on the devices your readers use, fix the source, and export again. Keep snapshots and backups before major imports, cleanups, or formatting changes.
This review-first loop is slower than pressing a single generate button and much faster than repairing a public upload with missing chapters or exposed notes.