Why every document needs a cleanup gate
A document can look finished in the editor and still fail in export. Hidden notes may be included, headings may not generate navigation, blank sections may create empty pages, and copied chat material may expose prompts or role labels. A cleanup gate catches these problems before the file reaches an editor, client, retailer, or reader.
The gate should be repeatable rather than dependent on memory. Use a written checklist, mark each section ready, and keep the final review tied to a known snapshot or version. If the source changes after approval, run the relevant checks again.
Confirm scope, order, and completeness
Review the Binder or outline from top to bottom. Confirm front matter, parts, chapters, scenes, references, and back matter are present and correctly ordered. Look for accidental duplicates, empty sections, temporary titles, missing chapter numbers, and content stored in the wrong folder.
Check include-in-export settings for every section. Private research, prompts, comments, synopses, and production notes should remain available to the author without entering the reader's file. Conversely, verify that no real chapter is excluded.
Search for AI chat and drafting residue
Search the whole project for User, Assistant, ChatGPT, Claude, Gemini, would you like me to continue, here is the revised version, placeholder text, and any phrases common to your generation workflow. Use whole-word and case controls to reduce false positives, then inspect every result in context.
Also search for Markdown fences, repeated asterisks, raw URLs, TODO markers, bracketed instructions, and comments pasted into body text. A previewable cleanup preset can speed this work, but a final project-wide search confirms that the preset covered every source variation.
Check language, facts, and continuity
Read for duplicate paragraphs, repeated conclusions, abrupt transitions, inconsistent terminology, and sentences that promise content the document never provides. Confirm names, dates, capitalization, abbreviations, and point of view. In fiction, track character details, timeline, setting, and unresolved plot commitments.
Verify facts, quotations, citations, links, and permissions using appropriate sources. Resolve every comment that affects accuracy or reader understanding. If a question must remain open, state the limitation honestly instead of leaving an unsupported claim.
Audit headings and paragraph formatting
Use real title and heading styles in a logical hierarchy. Confirm chapter titles are consistent and subordinate headings do not jump levels. Check lists, quotations, code, footnotes, scene breaks, and text messages for intentional styles rather than manual spaces or pasted browser formatting.
Choose a paragraph convention and use it consistently: first-line indents, spacing between paragraphs, or the requirements of a specific template. Remove extra blank lines, tabs used as margins, doubled spaces, orphan punctuation, and inconsistent quotation marks only after confirming they are not deliberate.
Review metadata and accessibility
Confirm the document title, author name, language, description, keywords, identifiers, and any publisher information. Metadata should match the cover, retailer listing, and file. Remove test values and old project names that may have survived from a template.
Use meaningful heading order, descriptive links, alt text for informative images, readable contrast in fixed-layout output, and clear table structure. Accessibility is easier to preserve when the source uses semantic styles instead of visual workarounds.
Export every required format from the same source
Generate DOCX for collaboration, EPUB for reflowable reading, PDF for fixed proofing, and TXT or Markdown when portable source is required. Use a named compile preset so section selection, breaks, and metadata remain consistent across revisions.
Awtter supports unlimited exports from the reviewed project, which makes iterative proofing practical. Keep file names clear and avoid overwriting the last approved package until the replacement passes inspection.
Open and inspect the actual files
Use Word's navigation pane, an EPUB reader, and a PDF viewer to inspect the outputs. Test navigation, links, page breaks, lists, italics, scene breaks, headers, footers, and the beginning and end of every included section. Search exported files for known labels and placeholders.
Save the final project backup beside the approved exports and record the release date. The checklist is complete only when the files readers will receive have been opened and reviewed, not when the export button reports success.
Ask a second person to perform a short cold read when the document is important or public. Give them the exported file rather than the editor view and ask them to report unclear navigation, missing context, obvious placeholders, inconsistent terms, and visual distractions. A reader who did not build the project is more likely to notice assumptions the author has stopped seeing. Capture each correction in the source document, regenerate every affected format, and update the release record. This final independent pass turns the checklist from a private memory aid into a repeatable quality-control process. Note who reviewed the file, which format they saw, and when their corrections were incorporated. Retain that evidence securely with the approved release package.