A style guide turns repeated choices into decisions
A book style guide is a short, living record of the choices that make a manuscript feel consistent. It can cover voice, spelling, capitalization, punctuation, names, timelines, formatting, citations, and the terms a reader should see throughout the book. The guide is useful for fiction, nonfiction, memoir, workbooks, and any project that moves through more than one editorial pass.
Without a style guide, authors and editors solve the same small questions repeatedly. Is the term capitalized? Should a number be written as a word? Is the narrator formal in this chapter? Does a character use an em dash or a comma? Recording the answer once makes later work faster and makes a change intentional instead of accidental.
Start with the book's purpose and reader
Before listing punctuation rules, write down what the book is trying to do and who it is trying to help or entertain. A literary novel, a practical guide, a memoir, and a technical workbook may all use different levels of formality, explanation, and repetition. The style guide should protect that purpose rather than force every project into the same house style.
Capture the audience, genre or category, point of view, tense, level of technical language, and the desired reading experience. Note whether the prose should feel conversational, authoritative, intimate, playful, restrained, or instructional. These decisions give an editor a reason behind the rules, which is more useful than a list of preferences with no context.
Describe the voice without flattening it
Voice guidance should be specific enough to help and flexible enough to leave room for real writing. Instead of saying make it sound good, describe the traits the manuscript should keep: short or winding sentences, direct address or third person, concrete examples, dry humor, lyrical imagery, or a calm explanatory pace. Include a short passage that represents the intended voice when a collaborator needs a reference.
Also record what the style guide must not erase. A character may speak differently from the narrator. A memoir may shift register when the subject becomes painful. A nonfiction example may use a deliberately informal phrase. Consistency is not the same as sameness. The guide should identify meaningful variation so an editing pass does not polish away the qualities that make the book recognizable.
Record spelling, capitalization, and terminology
Make a dedicated list for words that are likely to drift. Include preferred spellings, variant forms, product or organization names, recurring technical terms, hyphenation, capitalization, and words that the project uses in a special way. This list is especially valuable for long books, series fiction, client projects, and nonfiction that introduces a vocabulary readers must learn.
For each important term, record the preferred form and any forms to avoid. If a term changes depending on context, explain the difference rather than creating a rule that is too broad. Add names of people, places, programs, methods, and fictional objects as they become stable. Search and Saved Views in Awtter can help collect repeated terms while the style guide remains the place for the final decision.
Set punctuation and number conventions
Choose the conventions that editors will use for quotation marks, dialogue punctuation, em dashes, ellipses, semicolons, parentheses, spaces, and abbreviations. You do not need to defend every choice in the guide. You do need to state the choice clearly enough that a second person can apply it without guessing. If a genre convention matters, note it beside the rule.
Numbers deserve their own section because they appear in dates, measurements, ages, percentages, chapter references, money, and lists. Record when numbers are written as words, when numerals are preferred, how ranges are shown, and how units are formatted. Add exceptions for tables, headings, or technical material. A compact rule with examples is easier to use than a paragraph of abstract grammar terms.
Track names, timelines, and continuity
A style guide can also act as a continuity sheet. For fiction, track character names, nicknames, ages, relationships, locations, invented terms, objects, and facts that must remain stable. For nonfiction, track the names of sources, organizations, case studies, dates, definitions, and claims that recur across chapters. Add a note when a change is deliberate so the next editor does not treat it as an error.
Keep continuity records close to the manuscript but separate from reader-facing prose. In Awtter, Binder sections, synopsis fields, Notepad records, and linked research assets give you places to store these decisions without placing production notes inside the exported book. The goal is a single working context where an editor can verify a detail while the final export includes only the material meant for readers.
Define structural and formatting rules
Document how the book treats headings, subheadings, parts, chapter numbers, scene breaks, lists, quotations, tables, captions, footnotes, references, and appendices. Explain which elements are structural and which are decorative. A heading should communicate hierarchy; a row of blank lines should not be the only thing telling an editor that a new section begins.
Include the source structure and the final-format expectations separately. A manuscript may use a clear Binder order and semantic heading levels even when a print layout later changes the visual design. This distinction keeps the source flexible and gives the formatter reliable information. It also reduces the chance that manual spacing, repeated symbols, or temporary page-break tricks will survive into an ebook or a new edition.
Separate house style from author voice
Some decisions belong to the project or publisher, while others belong to the author or narrator. House style may define spelling, serial commas, heading capitalization, citation format, or product names. Voice may define sentence rhythm, preferred metaphors, dialogue patterns, or the level of directness. Label these categories so a collaborator knows which rules are firm and which choices deserve discussion.
When rules conflict, use the book's purpose as the tie-breaker. A clean house-style decision is not automatically correct if it makes a character sound unlike themselves or makes a technical explanation less clear. Record exceptions with a reason and an example. That small explanation prevents a later cleanup pass from “fixing” a purposeful choice simply because it looks unusual in isolation.
Make research and citation rules visible
For nonfiction, a style guide should explain how evidence appears in the manuscript. Record the citation system, source naming, quotation treatment, dates, links, bibliography order, and how to handle missing or disputed information. If the book uses interviews, permissions, public data, or adapted material, note what needs verification before publication. The guide cannot replace fact checking, but it can make the work visible.
Mark uncertainty instead of quietly normalizing it. A question such as confirm this statistic or check the spelling of this organization is more useful than a polished sentence that hides an unresolved source problem. Keep the evidence and the prose connected in the project, then decide explicitly what belongs in the reader-facing export.
Use the guide during AI-assisted cleanup
AI-assisted cleanup can make a style guide more valuable, not less. A cleanup pass may normalize punctuation, remove repeated scaffolding, or suggest consistent terminology, but it should not be allowed to invent a house style or flatten deliberate variation. Give the tool a bounded rule, inspect the proposed changes, and compare the result with the guide before applying a broad replacement.
Awtter supports a reviewable workflow for this kind of work: search across the project, preview cleanup candidates, use whole-word or match-case controls where they matter, and preserve a snapshot before a large change. The author remains responsible for deciding whether a suggested consistency change is correct. A style guide supplies the decision; it should never become an excuse to skip judgment.
Share the guide with every collaborator
Send the style guide with an editor, proofreader, formatter, ghostwriter, or co-author before the person begins a major pass. Explain which sections are settled, which are provisional, and where questions should be recorded. A collaborator who sees the reasoning behind a rule can make better local decisions and surface a real exception instead of silently creating a second standard.
Keep one current version of the guide attached to the project. If the guide travels as an email attachment, a downloaded file, and a note in several tools, it can drift just like the manuscript. Use a clear version name or date, and update the project record when a decision changes. The guide should reduce coordination cost, not create another document whose status nobody can identify.
Apply decisions in a controlled revision loop
A style guide becomes useful when it is tested against real pages. Start with a sample from the opening, middle, and end of the book. Apply the rules, note the places where they are unclear, and revise the guide before running a project-wide pass. This prevents a vague rule from multiplying across hundreds of pages and gives collaborators a shared example to discuss.
After an accepted change, update the guide and the manuscript together. Save a snapshot, record the decision, search for related uses, and review the surrounding context before exporting a new version. Awtter helps keep this loop connected through Binder structure, notes, search, saved views, and project history. The result is not just a cleaner draft; it is a record of why the draft is consistent.
Verify the guide against final exports
The last style check belongs in the files readers will receive. Review the title page, contents, chapter headings, body text, lists, quotations, references, links, and back matter in the appropriate formats. A DOCX, PDF, and EPUB may render differently, but the spelling, terminology, order, and inclusion decisions should agree. A style guide that works only in the editor is not finished.
Keep the reviewed source, the final guide, and the export package together with their version identity. If a late correction changes a term, heading, or front-matter page, repeat the affected checks instead of assuming the exported files are still current. A concise style guide pays off at every stage: it makes editing faster, collaboration clearer, cleanup safer, and the final book easier to trust.