← Back to blog

Style Consistency Check: A Manuscript Guide for Authors

October 20, 2026
Style Consistency Check: A Manuscript Guide for Authors

A style consistency check confirms that your book treats the same thing the same way every time: spelling, capitalization, hyphenation, numbers, names, headings and layout. Do it in three passes. Build a style sheet while you draft, run a copyedit-level read against it, then test the typeset files, because typesetting introduces its own inconsistencies.

This guide walks through each pass, shows what to look for, and explains where software helps and where it should stay out of your prose.

Alhora
Keep Your Book’s Formatting Consistent
Alhora helps authors prepare professionally typeset eBooks and print editions, with real-time validation against publishing standards.
Explore Alhora

Key takeaways

  • Consistency is not correctness. A deliberate choice, such as dialect spelling, is valid if you apply it the same way everywhere. The same choice used sporadically is an error.
  • Start a style sheet in the first draft, not at the copyedit. It is the reference every later check runs against.
  • Check content, mechanics and layout separately. Spelling and names are one problem; rivers, hyphen ladders and heading hierarchy are another.
  • For a series, keep one master style sheet and consult it for every book.
  • Test the exported EPUB and print PDF, not only the source file. Reading systems reflow text differently.

Table of Contents

What a style consistency check covers

The term sounds narrow, but it spans three layers.

Mechanics. Spelling variants, capitalization, hyphenation, punctuation, number style, abbreviations. Professional guidance describes this as the core of the copyedit stage, which focuses on technical errors and internal consistency and is distinct from substantive line editing.

Internal logic. Character traits, timelines, place descriptions, invented terms. A character whose eyes change color between chapters is a consistency error, even though no spelling rule is broken.

Formatting. Heading hierarchy, paragraph indentation, scene-break treatment, table styling, running heads. These are the errors a reader sees before reading a word.

Three manuscript consistency-check layers

The MLA's style guidance frames consistency as a matter of reader trust: a work's treatment of words, names and titles stays uniform, which reduces ambiguity. You do not need a university press to benefit from that. A reader who meets "e-mail" on page 12 and "email" on page 212 does not consciously object. They simply start to trust the book a little less.

Consistency is not the same as correctness

Before you run any check, decide what counts as a mistake.

Practitioners distinguish the two this way: a non-standard punctuation habit or intentional dialect spelling can be part of an author's voice. Applied consistently, it is a style decision. Appearing here and there, it is a defect.

This matters for fiction in particular. Say your narrator never uses the serial comma in dialogue tags, or your fantasy world spells "grey" in one kingdom and "gray" in another on purpose. A blunt checker flags both. You need a record that says these are intentional, which is exactly what a style sheet provides.

Also keep the purpose in view. The University of Chicago Press has long made the point that editorial rules are not rock-ribbed law: consistency serves clarity, and common sense wins when a rule would make the text harder to read.

Pass 1: Build a style sheet while you draft

A style sheet is a separate document that records the decisions specific to your book. Editors use it to keep a manuscript or an entire series consistent, and it is not static: it grows as the project does. Editors who build it during drafting avoid time-consuming backtracking and settle conflicts before they harden into the manuscript.

Start with these entries:

  1. Base references. Your dictionary and style guide (for US fiction, typically Merriam-Webster and the Chicago Manual of Style).
  2. Spelling choices. Variants you use, such as "okay" or "OK", "toward" or "towards".
  3. Hyphenation and compounds. Words you hyphenate and words you close up.
  4. Capitalization. Titles of rank, invented terms, brand names, directions.
  5. Numbers. When you spell out and when you use numerals; how you write times, ages and dates.
  6. Punctuation conventions. Em dash spacing, ellipsis style, serial comma, how you render text messages and thoughts.
  7. Character and place details. Names with spellings, ages, physical traits, relationships, geography.
  8. Timeline points. Dates and durations that other scenes depend on.
  9. Intentional exceptions. Anything a checker or editor might flag that you want kept.

Update it the moment you decide something new. A sheet written after the fact only documents the inconsistencies you already have.

Series: one master sheet

For a series, keep a master sheet of canon details: eye color, internal geography, historical timelines. Unlike a general style guide, it has to be consulted by everyone on the project so terminology in Book 1 matches Book 10. The risk is silent drift: a spelling or a detail changes slightly each volume and nobody notices until a reader writes in.

A practical setup:

  • One master sheet, plus a short per-book addendum for new characters and places.
  • A change log with the book and chapter where each decision was made.
  • A rule that you open the sheet before drafting a new book, not after.

Pass 2: Check the manuscript against the sheet

The copyedit-level read is where you apply the sheet. Read linearly rather than jumping between sections, since copyediting protects correctness and consistency after the larger edit is stable. Do not run this pass while you are still moving scenes around. You will check text you later cut.

A working order

  1. Find and replace for known variants. Search for each pair on your sheet ("okay/OK", "e-mail/email") and confirm one survives.
  2. Names and terms. Search every character, place and invented term. Look for near-misses: "Marguerite" and "Margerite", "Thornfield" and "Thorn Field".
  3. Numbers and dates. Scan for numerals in prose and spelled-out numbers in the same context.
  4. Capitalization of titles and ranks. "the Captain" versus "the captain" is the classic fantasy and military-fiction drift.
  5. Punctuation habits. Ellipses, dashes, quotation marks (straight versus curly is a frequent leftover from pasting between apps).
  6. Headings and scene breaks. Same treatment for every chapter opening and every break.
  7. Continuity. Walk the timeline and the character facts from the sheet. Check weather, day of the week, injuries, and who knows what.

Where AI belongs in this pass

A checker is good at the repetitive part: surfacing every instance of a variant, flagging mismatched numbers or a heading that skips a level. It should flag, and you should decide. In Alhora, the proofreading engine works that way: it points out issues but never writes or alters your creative content. Your sentences stay yours. That is a deliberate boundary, and it is the one we recommend for any tool you let near a manuscript.

Pass 3: Check what typesetting changes

This is the pass most authors skip. A manuscript can be perfectly consistent in Word and still look inconsistent once it is laid out, because layout creates new problems.

Rivers, ladders and bad breaks

The MLA Style Center describes rivers, hyphen ladders and bad line breaks as typesetting-stage problems. A river is a run of conspicuous gaps lining up across successive lines. A ladder is a stack of consecutive lines ending in hyphens. Authors rarely catch them because they appear only after justification and hyphenation are applied to a specific page size.

What to inspect in a print proof:

  • Justified paragraphs with wide word gaps that stack into rivers.
  • Three or more consecutive hyphenated line endings.
  • Widows and orphans: a single line stranded at the top or bottom of a page.
  • Chapter openings: same drop cap, same first-line treatment, same space above the title.
  • Trim, bleed and gutter: margins that hold on every page, including the inner edge near the binding.

Reading systems do not agree

EPUB files reflow. The same file can look different on an e-ink device and in a phone app, because rendering engines interpret CSS differently. Professional formatting practice involves testing in more than one reading system rather than trusting the source view. For store-specific advice, see our guides on Kobo EPUB formatting and preflighting EPUB 3.3 for Google Play Books. Drop caps are a common offender, and we cover them in making drop caps work in EPUB.

Metadata is part of consistency

The title on the cover, the title page, the retailer listing and the ISBN record should match exactly. A subtitle that differs between the file and the store listing creates real problems at upload. Our book metadata guide covers the fields to settle before you publish.

Accessibility belongs in the check

Consistency in an ebook includes structure that assistive technology can read. Accessible publishing guidance expects semantic heading hierarchies, descriptive alt text for informative images, and link text that makes sense out of context. Decorative images should be marked as such rather than given filler descriptions. The same guidance points to tools such as EPUBCheck and Ace by DAISY for technical validation, and notes that accessibility metadata must be present in the EPUB package.

A quick structural checklist:

  • One H1-level title per document, with headings that descend in order and never skip levels.
  • Alt text on every informative image; none on decorative ones.
  • Link text that says where the link goes.
  • Accessibility metadata declared in the package.

For the full walk-through, use our EPUB accessibility checklist and the guide to testing the package for WCAG compliance. If you produce educational or children's titles, a related read is this publishing workbook for children's book authors, which pairs well with an accessibility-first approach.

A sample consistency audit

Here is how the three passes fit together for a 90,000-word novel, as a worked schedule rather than a promise of timing.

StageWhat you checkReferenceOutput
DraftingDecisions as they ariseStyle sheetLiving sheet
Revision completeSpelling, names, numbers, capitalizationStyle sheetCleaned manuscript
Continuity readTimeline, traits, geographyMaster sheetFix list
Typeset proofRivers, ladders, widows, trim and gutterPrint proofLayout corrections
EPUB testReflow, headings, alt text, metadataEPUB validators, two reading systemsPassing package

Run the stages in order. Fixing a layout problem before the text is final means redoing it when the text changes.

Our perspective

We build Alhora for authors who want a professional finish without handing over their words, so we think about consistency from both ends.

First, the checks authors do by hand are mostly the wrong size of job. Searching for "okay" against "OK" across 300 pages is mechanical, and mechanical work belongs to software. Deciding that your narrator says "okay" is a creative decision, and it belongs to you. That is why our AI assistant, Inkia, checks and operates but can never write a word.

Second, a manuscript is not finished when the text is. Many consistency problems appear only at layout: hyphenation, justification, widows and orphans, trim and gutter. We built a typesetting engine and real-time validation against publishing standards into the same studio as the manuscript, so you see these problems while you can still fix them, instead of after an upload is rejected.

Our perspective — overview diagram

Third, series are where drift hurts most. Alongside the book, Alhora has a World and continuity desk, and batch series formatting applies the same design decisions across every volume. Keep the style sheet next to the book and the book next to the sheet.

Our advice, in one line: decide your style early, write it down, and let tools find the exceptions while you make the calls.

— James

Run the layout and file checks in Alhora

Alhora is book-formatting and typesetting software for Mac, Windows, Linux and ChromeOS. It handles automatic typography (justification, hyphenation, widows and orphans, drop caps, custom fonts), trim, bleed and gutter checks, a proof simulator, series batch formatting, and accessible EPUB export that is gated by an audit. Pricing is a £99 one-off license. If you want to see how it compares with other options first, read our guide to choosing book formatting software, or go straight to Alhora.

FAQ

What is a style consistency check?

It is a review that confirms your manuscript applies the same conventions throughout: spelling, hyphenation, capitalization, numbers, names, headings and layout. Editors usually do it at the copyedit stage, before typesetting. Authors can do a first version themselves with a style sheet.

What is formatting consistency?

It means every element of the same type looks the same: chapter openings, headings, scene breaks, block quotes, paragraph indents. In an ebook it also means structure is consistent underneath, such as heading levels that descend in order. Check it on the exported files, because layout can change what the source file showed.

How do I identify my writing style for a style sheet?

Read a few chapters and list the choices you make repeatedly: serial comma or not, how you write numbers, how you punctuate dialogue, which spellings you prefer. Record each one, along with any deliberate oddities. Those entries become your sheet, and anything that breaks them is a candidate for correction.

Can AI check consistency without changing my writing?

Yes, if the tool is built to flag rather than rewrite. A checker can list every variant spelling or mismatched number, and you accept or reject each one. Alhora's AI proofreading engine works this way: it flags issues and never writes or alters creative content.

Sources