Revision does not end when the first export downloads
Self-publishing usually requires several export passes. Authors generate a DOCX, catch a typo, update front matter, test an EPUB, fix a chapter break, export again, and compare the new files with the previous version.
The risk is stale output: one file contains the latest chapter while another still carries an older draft. An export-safe revision loop keeps every format tied to one reviewed project source.
Start every loop with a recovery point
Before cleanup, import, batch replace, or structural changes, create a snapshot or project backup. Recovery points let authors revise aggressively because the previous state is still available if a cleanup pass removes too much or a chapter move was wrong.
Awtter combines section snapshots, project backups, and export history so cleanup and revision decisions can be traced instead of guessed later.
Check the Binder before regenerating files
A safe export starts with structure. Confirm chapter order, included sections, excluded research, Trash, front matter, back matter, title, and any notes that should remain private before compiling a new file package.
This checklist matters because export problems are often source problems. If a scene is excluded, misplaced, empty, or still in Trash, the generated DOCX, EPUB, PDF, TXT, Markdown, and ZIP files will reflect that.
Regenerate every format from the same source
Once the project is clean and ready, export the formats you actually need from the same Binder order. Do not manually update a DOCX in one tool, an EPUB in another, and a ZIP package somewhere else.
Awtter's unlimited exports make the revision loop practical: clean the source, check readiness, export, review files, revise the source, and export again until the document is ready to submit.