Formatting helps the recipient evaluate the manuscript
A manuscript does not need to look like a finished book before you submit it to an editor, agent, beta reader, or publishing partner. It does need to be readable, navigable, and clearly identified. When the file has inconsistent headings, unexplained blank pages, draft instructions, or several competing versions, the recipient has to spend attention on production questions before they can respond to the writing.
A manuscript formatting checklist creates a final quality boundary. It separates what the recipient needs in the review copy from what belongs in later typesetting or ebook production. The exact requirements vary by recipient, genre, and submission call, so follow the instructions you were given first, then use this checklist to catch avoidable problems.
Confirm the recipient's exact submission instructions
Start with the source of truth for the handoff. Check the requested file format, naming convention, page or word-count limits, contact information, synopsis or query requirements, sample length, and whether the recipient wants a complete manuscript or selected chapters. An agent's guidelines may differ from an editor's request, and a contest or residency may impose its own template.
Keep a copy of the instructions with the project notes and mark each requirement as you complete it. Do not rely on a remembered standard such as a preferred font or margin setting when the recipient has published a different rule. Formatting is only useful when it supports the actual review process.
Preserve the source before making a submission copy
Before formatting, preserve the manuscript version you intend to submit. Record the title, author name, date, word count, chapter order, and any open questions. Use a clear version label such as manuscript-submission-01 rather than overwriting a file called final. If the recipient asks for a revision later, you will know exactly what they saw.
Make formatting changes in a review copy when possible. Keep the working manuscript available for structural edits and keep the pre-submission version recoverable. A snapshot or backup is especially valuable when you are normalizing many chapters at once, removing comments, or changing the inclusion boundary for a selected sample.
Create a simple, consistent document hierarchy
A reader should be able to identify the title, author, major divisions, chapters, scenes, and supporting sections without decoding each page. Choose a consistent pattern for chapter titles and part titles. Make the difference between a chapter heading, a subsection, a scene break, and an author note visible through structure rather than a collection of one-off formatting tricks.
Do not spend the submission pass trying to imitate the finished cover, interior design, or ebook theme. A clean hierarchy is more valuable than decorative styling. Use meaningful headings, consistent text treatment, and deliberate section boundaries so the recipient can move through the manuscript quickly and understand its shape.
Standardize chapter openings and breaks
Review every chapter opening as a set. Check the title spelling, capitalization, numbering, subtitle treatment, first paragraph, and space before the text. If some chapters start with a title and others begin with a filename or a repeated header, resolve the inconsistency. For fiction, also check scene breaks and section dividers. For nonfiction, check whether exercises, examples, and callouts follow a repeatable pattern.
Look at the end of each chapter too. A chapter that ends with an accidental blank page, a duplicated heading, or a note to yourself can make a clean manuscript feel unfinished. Read the transition into the next chapter and verify that a heading has not been separated from the paragraph it introduces by a copied page break.
Check paragraphs, spacing, and emphasis
Run a mechanical pass for paragraph-level consistency. Look for extra spaces, accidental tabs, broken lines from copied PDF text, empty paragraphs used for layout, inconsistent indents, and headings that are actually ordinary body text. Also check italics, bold, quotation marks, em dashes, ellipses, and other emphasis choices that may have changed during import or copy and paste.
Use search and preview rather than a blind global replacement. A double space may be a mistake in one section but part of an intentional example in another. A bold phrase may be a heading, a character's emphasis, or a production note. Inspect representative matches, apply only a rule with a known scope, and read the affected passage afterward.
Keep front matter and back matter intentional
Decide what the recipient should see before and after the main manuscript. Depending on the handoff, that may include a title page, author name, contact details, contents, a short note, acknowledgments, references, an author bio, or selected back matter. It may not include a dedication, marketing copy, research appendix, alternate ending, or internal production checklist. The correct boundary depends on the request.
Give every included section a clear place and label. Keep private research, comments for collaborators, alternate scenes, and unresolved questions in the project but outside the submission copy. A section that is useful during writing can be distracting or confidential during review, so inclusion should be an explicit decision rather than an accidental consequence of exporting the whole file.
Remove production residue before you send
Search the manuscript for drafting and production residue: prompt language, User or Assistant labels, instructions such as expand this section, placeholder text, tracked-change remnants, comments, duplicate headings, copied page numbers, internal notes, and references to an earlier version. Read the opening, a middle chapter, and the final pages after cleanup because residue is often concentrated at boundaries.
Awtter supports reviewable cleanup, snapshots, Binder structure, and export from one project. Use a preview before applying repeated cleanup rules, then keep a recovery point in case a phrase that looked like residue is actually part of the author's voice or subject matter. The recipient should receive the manuscript, not the scaffolding used to build it.
Use a clear filename and handoff note
Choose a filename that identifies the project, author, version, and purpose without becoming a sentence. Include the requested extension and avoid a string of vague labels such as final-final-newest. If the recipient provided a naming convention, follow it exactly. Clear filenames reduce the chance that an attachment is mistaken for an older draft.
Add a short handoff note outside the manuscript when appropriate. State what is attached, the manuscript's approximate word count, the version date, and any question the recipient needs to answer. Do not bury important instructions in the first page of the book unless the recipient requested that format. A separate note keeps the reader-facing manuscript clean.
Review the manuscript like the recipient
Open the submission copy from a fresh location or a new application window, not only from the project where you created it. Confirm that the filename, title page, author name, chapter order, headings, page flow, and final page make sense to someone who has no access to your working notes. If possible, read the opening and several representative sections at the size the recipient is likely to use.
Ask a second reader to check the mechanics if the handoff matters. Give them the checklist and ask them to flag missing sections, inconsistent titles, confusing notes, or anything that looks like an unfinished draft. Their job is not to rewrite the book. It is to identify friction that the author may no longer see after living inside the document.
Export and inspect the final DOCX
If the recipient wants a DOCX, create it from the reviewed source and inspect the exported file itself. Do not assume that the version visible in the writing workspace is identical to the attachment. Check that headings, paragraph breaks, emphasis, links, special characters, and section order survived the export. Confirm that comments, hidden notes, and excluded material are not present if they should remain private.
Awtter lets authors export DOCX, PDF, EPUB, TXT, Markdown, and ZIP from the same included Binder order. Use the format that matches the request, and keep a PDF or source snapshot only when it helps your records. The important point is that the file you send should come from the same version you just reviewed.
Keep a clean record after submission
Save the submitted file, the date it was sent, the recipient, and the exact version identifier. Keep the instructions and your handoff note with that record. If the recipient responds weeks later, you can compare their comments with the manuscript they actually received instead of trying to reconstruct it from memory.
When you make the next revision, start from the canonical working source and record what changed. Do not silently replace the submission copy. A simple version history makes it easier to accept useful feedback, decline a suggestion for a documented reason, and produce a new clean file when the review stage changes.
Use the checklist as a repeatable handoff workflow
A manuscript formatting checklist is most useful when it becomes a small repeatable workflow: confirm the recipient's requirements, preserve the source, establish the hierarchy, standardize chapter boundaries, remove residue, decide what is included, export the requested format, inspect the actual file, and record the handoff. The sequence is short enough to use before every major submission.
The result does not need to look like a finished commercial book. It needs to be the correct manuscript, in the requested format, with a clear structure and no avoidable production noise. That gives editors, agents, beta readers, and collaborators the best chance to spend their time on the writing itself.