Make an Editorial Style Sheet for a Series Bible

A style sheet for a series bible is a short list of the document's own settled language: how the recurring names are spelled, which forms belong in dialogue and which in descriptive prose, and which variations are decisions rather than mistakes. You build it from the bible in front of you. You do not import a house rulebook from somewhere else and impose it on a manuscript that has already made most of these choices.

Three limits are worth stating once, so they don't have to be repeated in every section. The sheet does not settle story. It does not restyle pages. It does not level out the way characters talk.

What it produces is small: a one-page reference and a bounded copy pass. You search for the variants the sheet knows about, read each hit inside its sentence, correct only the occurrences the sheet covers, and leave everything else alone.

Separate a wording inconsistency from a story disagreement

Start by sorting the problem in front of you, because two conflicts that look similar need opposite responses.

One page of a bible calls the town Kestrel Point. A later page calls it Kestral Point. Nothing about the series changes depending on which is right. The town is still the same size, the harbor still freezes the same way, Cal is still a dockhand. This is a wording problem, and the manuscript itself usually contains the answer: a location list, a character list, a synopsis heading, or a note from the writer that states the form the document intends to use.

Now a different conflict. Suppose one character note describes a woman as Cal's sister, and another describes her as his crewmate. Picking one silently would be a mistake, and it wouldn't be a copy edit. Either statement could be the true one, or both could be true at once, and only the person who owns the story can say which. That goes to the responsible writer as a question. Until it comes back, neither phrasing gets standardized, because standardizing is a way of deciding.

Two habits are worth adopting here. The first is refusing recency as authority. A name misspelled four times in the second half of the document does not outvote the location list that spells it correctly, and the newest line is not automatically the right one. Authority comes from where the manuscript states its intent, plus any decision the writer has actually authorized. Frequency is a supporting signal at best, and when the body of the text contradicts a list consistently, that's a question rather than a vote.

The second habit is keeping adjacent problems out of this list. Typeface, point size, indents, heading treatments and paragraph styles live in the authoring document where they are applied; a language list is the wrong place to record that scene numbers are bold. Conversely, the fact that the ferry stops running in November is continuity, not usage. If the bible says November in one place and December in another, that is not a copy pass. It is the same kind of question as the sister who might also be a crewmate.

The rest of this article deals with the first kind of problem.

Capture preferred forms with enough context to use them

Collect the things that repeat: character and place names, spellings, diacritics, pronouns where the bible supplies them, invented terms with no real-world counterpart, and a small number of capitalization and punctuation choices that recur often enough to matter. The last category is smaller than people expect. Two or three entries are usually enough — how the bible refers to its own episodes, say, whether it writes "Episode 3" or "Ep. 3" or "3.02" — and it is nowhere near a full style manual. A bible does not need a position on the Oxford comma unless the Oxford comma is genuinely unsettled in the text.

Here is an invented sample, made up for this article and drawn from no client document. Ten short passages from a fictional bible draft.

1. Series overview, opening line: "Kestrel Point is a working harbor of about four thousand people, and everything in it depends on the water."
2. Series overview, third paragraph: "Kestrel point has never been a rich town and has never been an empty one."
3. Location list: "Kestrel Point — town and harbor. North Quay — the working pier, west side of the channel."
4. Character list: "Cal Ferris, 40s, dockhand. Ten years on the north quay; speaks when there's something to say."
5. Character list: "Harbormaster Ivo Reyn, 60s, twenty-two years in the post. The harbormaster's office is the third door on the North Quay."
6. Dialogue sample, Cal, scene 4: "Nothing comes into the Point without somebody signing for it."
7. Descriptive prose: "Past the breakwater the point drops away in a shelf of black rock, and the water there is never warm."
8. Logistics paragraph: "The ferry to Kestral Point runs twice a day until November. After that the Harbormaster decides whether the channel opens at all."
9. Synopsis line: "Every winter the fleet hauls out for a week, and after the Long Haul the yard goes quiet until spring."
10. Dialogue sample, Cal, scene 11: "It's a long haul to April, and the ferry money runs out before that."

An entry needs four things to be usable an hour from now: the preferred form, where that form comes from, where it applies, and what exception it carries. Kept to that, the sample yields five entries.

Where the practice comes from is worth being honest about. Book editors have kept lists like this for a long time, and the Chartered Institute of Editing and Proofreading publishes a working account of it by a practicing editor, describing how language conventions, names and consistency decisions get recorded for everyone who will edit and typeset the text, and how the sheet gets adjusted for the way it is actually used (ciep.uk/resource/fiction-style-sheets.html). That is a UK book-editing method. Adapting it to a series bible is a choice, not a requirement, and nobody is enforcing a US television version of it. What transfers is the habit: write the decision down, say where it came from, and keep the list where the next person can find it.

Protect intentional variants and leave genuine questions open

Two of the sample's entries earn their place by not smoothing something over.

Same string, different job. Passage 6 has Cal saying "the Point" as shorthand for the town he lives in. Passage 7 has prose saying "the point" about a shelf of black rock. A search for the string finds both. Treating them as one inconsistency would produce a bible in which a headland has been renamed after a town, or a dockhand has started talking like a survey.

Same string, undecided job. Passage 9 capitalizes "the Long Haul" as though it names something — an annual week when the fleet comes out of the water. Passage 10 uses "a long haul" as the ordinary phrase it is, about the distance to April. Two readings fit: either the series has a named event that passage 10 happens to echo, or passage 9 is a capitalized idiom and therefore an error. Only the writer knows whether the Long Haul exists in the story world. So the entry carries a question mark, the reason for the question, and a name next to it.

A third case doesn't arise in this sample, but it belongs to the same logic when it does: Supplied, not inferred. If a character note states a character's pronouns, that statement goes into the entry as supplied. If no note states them, the sheet stays silent rather than reasoning from a name, a relationship label, or how someone is described in an adjacent paragraph. This is not a formatting preference. A description of someone as "his wife" or "the receptionist" tells you about a sentence, not about how that person should be referred to in the document, and the copy editor is the wrong person to settle it. Send the question to the writer.

The same logic sets the conditions for variants that are genuinely allowed. Dialogue can use a nickname where prose can't. Descriptive prose can use an ordinary noun, lowercase, where a heading means the name of a place. A quoted document inside a bible — a newspaper clipping, a formal notice, a letter read on screen — may carry its own conventions, and those belong to the quote rather than to the bible around it. Write the condition, not just the form. "Capitalized in dialogue" is usable; "capitalize where it feels like a name" is not.

Apply the sheet to a sample before the whole bible

Run the pass on the ten passages before touching the rest. A case-insensitive search for "point" returns six hits and three different treatments, which is exactly why nobody should be running a global replace on it.

Correct

• Passage 2: "Kestrel point" → "Kestrel Point." The location list states the name; the lowercase second element is a slip.
• Passage 4: "the north quay" → "the North Quay." In this bible there is one working pier and the location list names it; the sentence is about that pier, not about a direction.
• Passage 8: "Kestral Point" → "Kestrel Point." A misspelling, not a variant.
• Passage 8: "the Harbormaster decides" → "the harbormaster decides." The character list capitalizes the title directly before a name and lowercases it standing alone, and this occurrence stands alone.

Keep

• Passage 6: "the Point" in Cal's dialogue. Intentional, and the sheet says whose dialogue it belongs to.
• Passage 7: "the point" in prose, meaning the headland. Different referent, different word.
• Passage 10: "a long haul," the ordinary phrase, pending the question about passage 9.

Ask

• Passage 9: is "the Long Haul" a named event in the series, or is it the same idiom with a stray capital? The answer decides whether the entry becomes a proper noun with a scope, or a correction, or nothing at all. It does not get settled in the sheet.

Then recheck the corrected passages next to the ones you left alone, because the value of a copy pass is in the difference. A pass that leaves every variant in place has done nothing; one that removes all of them has done damage.

Notice how shallow the reasoning behind one of those corrections is, and how deep behind another. Passage 2 is mechanical. Passage 8's title correction rests on a pattern the manuscript itself established in passage 5 — and if the writer preferred the capital everywhere, the pattern changes and three passages follow it, not the other way around. That is why the sheet records a decision rather than a law.

When an authorized decision changes

Two weeks later, the writer sends a note. A real working harbor elsewhere uses the town's name and the series can't share it. The town becomes Kestrel Bight in every formal mention. The same note adds that Cal and the other waterfront characters keep calling it the Point, because that is what people who live there have always called it and the maps changing is part of the story.

That one authorized decision touches four passages and two entries, and the entries and the text move together:

• The first entry becomes Kestrel Bight, sourced to the writer's note, and passages 1, 2, 3 and 8 all change. The earlier correction to "Kestrel Point" is superseded rather than wrong; what preserves the work is the log line, not the corrected string.
• The second entry stays as the Point, and its note gets stronger: retained by decision, not a residual form of the old name.
• "Kestral" now has no home anywhere in the document. The retired variant stays in the change history so that nobody re-adds it as a correction, and a search for "Kestrel Point" should now return nothing.
• A dated line at the top of the sheet records the change and who authorized it: Rev 4 — town renamed Kestrel Bight (writer's note). Supersedes Kestrel Point. Dialogue nickname "the Point" retained by the same note.

Without that line, the next editor finds "Kestrel Point" in an older file, assumes the newer file has a typo, and restores a name the series no longer uses — or, worse, decides the capitalized nickname in Cal's mouth must be a leftover and fixes it.

What the finished sheet holds is modest and checkable: five entries, four corrections, three deliberate non-corrections, one dated change, and one question still open with the writer's name on it. The Long Haul sits there with its question mark. That isn't an unfinished sheet — that's the part of the sheet that's working, and the same is true of every entry nobody has answered yet. The judgment worth developing is knowing which of the three treatments a given variation deserves, and having the record show why.

Frequently asked questions

When a series bible spells a town two ways, how do I decide whether to standardize it or ask the writer?

Treat it as a wording problem if nothing about the story changes—the town is still the same size, the harbor still freezes the same way, Cal is still a dockhand. Look for the form the manuscript itself states in a location list, character list, synopsis heading, or writer’s note. Refuse recency as authority: a misspelling repeated four times does not outvote a correct list, and the newest line is not automatically right. If the body of the text contradicts a list consistently, that is a question rather than a vote.

What four things does a usable style-sheet entry need?

The preferred form, where that form comes from, where it applies, and what exception or note it carries. In the sample, 'Kestrel Point' is sourced to the location list and overview line 1 and applies to prose, headings, synopses, and dialogue that speaks the full name; 'the Point' applies only in Cal’s dialogue, capitalized, and is not the headland; 'North Quay' applies to any mention of the pier; 'Harbormaster' is capitalized directly before a name and lowercase standing alone; 'the Long Haul' has no source yet and is an open question for the writer.

Why does the sheet keep some variants instead of correcting every occurrence?

Because the same string can have different jobs. In the sample, 'the Point' in Cal’s dialogue is shorthand for the town he lives in, while 'the point' in prose is a shelf of black rock. Correcting them as one inconsistency would rename a headland after a town or make a dockhand talk like a survey. A second case is the same string with an undecided job: 'the Long Haul' may name an annual event, while 'a long haul' is the ordinary phrase about the distance to April. The sheet writes the condition, not just the form.

What happens when the writer authorizes a rename or change?

The entries and the text move together. If the writer renames the town to Kestrel Bight, the first entry changes source to the writer’s note, passages 1, 2, 3, and 8 change, and the earlier correction to 'Kestrel Point' is superseded rather than wrong. The 'the Point' entry stays and its note gets stronger: retained by decision, not a residual form. The retired variant stays in the change history so nobody re-adds it, and a dated line records the change and who authorized it. Without that line, the next editor may assume the newer file has a typo and restore a name the series no longer uses.

Further reading

• The Deck, Pilot, and Bible Describe Different Shows. Reconcile the Package — If the disagreement turns out to be about the show rather than the spelling, this shows how to separate gaps from conflicts and route the choice to its owner.