Maintain a style record that explains intentional exceptions and where they apply. Give editors and AI tools that context, review proposed corrections against it, and keep each exception narrow enough that it does not excuse unrelated errors elsewhere in the manuscript.
Distinguish an intentional choice from an inconsistency
A manuscript may deliberately preserve a character's unusual phrase, an archival spelling in a quotation, or a specific capitalization for an invented institution. An automated check may flag those forms as inconsistent even when they are correct for their purpose. The author needs a record that explains why they remain.
Do not declare every recurring error a style choice after it is discovered. Establish the intended effect and the evidence or authorial decision supporting it. A genuine exception should be explainable to another editor, while an accidental inconsistency should still be corrected. The distinction protects deliberate voice without turning the style sheet into a list of unchecked preferences.
Record the scope of each exception
For each approved exception, note the exact form, its ordinary alternative, the reason, and the contexts where it applies. A spelling used inside a historical quotation may not belong in the author's explanatory prose. A character's particular expression may be appropriate in dialogue but not in narration from another viewpoint.
Include a representative example from the manuscript. That makes the rule easier to apply than a bare instruction to preserve unusual language. Keep the scope narrow enough to identify inappropriate matches. An exception that applies everywhere without a reason may hide the very inconsistency the editorial process is meant to resolve.
Connect factual exceptions with their sources
When an exception reproduces source material, retain the relevant source record and the passage being followed. This helps the reviewer distinguish faithful reproduction from a transcription mistake. Do not assume that unusual wording is historically accurate simply because it sounds old or appears in an AI-generated draft.
Review any explanation added around the source as the author's own prose. It may need modern, consistent wording even when the quoted material preserves another form. KDP's content guidance leaves responsibility for the published material and its rights with the publisher; a style exception is an editorial decision, not evidence that source use is accurate or permitted.
Provide exceptions with the editing assignment
Give human editors and AI-assisted tools the relevant style decisions before they propose changes. Explain whether the task is to identify unexpected variants, improve clarity outside the exception, or review the exception's consistency. A generic request to standardize all wording can work against the author's intended voice.
Inspect returned changes rather than assuming the supplied instructions were followed. Automated replacements can erase a deliberate form, while a tool may also invent additional exceptions by imitating a character's speech elsewhere. Compare the edited passages with the recorded scope and accept only changes that preserve the intended distinctions.
Review exceptions when the context changes
A decision can become obsolete when a scene changes viewpoint, a quotation is removed, or an invented organization is renamed. Mark affected exceptions for review as part of that revision. Otherwise, an old style record can cause editors to preserve wording that no longer serves a purpose in the current manuscript.
Keep the history of a retired exception without leaving it active in the current editing brief. Record why it changed and which passages were reviewed. This supports future revisions while preventing old decisions from returning through a reused prompt, template, or contributor handoff. The active style record should describe the book being produced now.
Check the final manuscript for both kinds of error
Before export approval, search for the approved exceptional forms and their likely alternatives. Review occurrences in context. Confirm that deliberate wording remains where intended and that the standard form is used where the exception does not apply. A simple count of matches cannot establish that either group is correct.
Inspect headings, captions, and other text outside the main narrative as well. These areas can be missed by a chapter-focused edit or produced through a different workflow. Save the final style decisions with the approved manuscript so the next edition begins with a usable explanation of its language choices rather than a mystery about which apparent errors were intentional.
Frequently asked questions
Clear answers for this publishing decision.
Should every unusual phrase become a style exception?
No. Record an exception when it serves a clear purpose and has an approved scope. Correct accidental inconsistencies instead of preserving them merely because they recur.
Can a quotation’s spelling be used throughout the surrounding prose?
Only if that broader choice is separately intended and justified. A form preserved inside source material does not automatically establish the style for the author’s narration or explanation.
What should happen when an exception is no longer needed?
Retire it from the active editing brief, retain its history, and review affected passages. This prevents a later editor or reused AI prompt from restoring an obsolete choice.
How do I get from an idea and a brief to an editable manuscript I can finish?
Write the brief first, generate a structure you can edit, then draft and revise the manuscript in reviewable sections so one change never overwrites work you already approved.
Start a book project from a brief