Build a Character Bible That Scales Across a Series
SOBy Scott Ohlund, FounderUpdated June 25, 202610 min readSeries Craft
A character bible that survives a long series is not a folder of notes you maintain by hand.
It is a structured record of every character (names, aliases, ages, physical traits,
relationships, arcs, and voice) extracted from the books you have actually written, then carried
forward across all of them. Build it from the prose, tie each fact to the scene it came from,
and re-check it every time you draft. The bible stays accurate because it stays tethered to the
manuscripts, not because you keep remembering.
A character bible works fine for the first two books. You hold the cast in your head, the notes
file is short, and a quick scroll answers most questions. Then comes Book 3. The cast has grown
to thirty-odd named people, half of them go by two or three names, a side character you barely
planned has become a fan favorite with a backstory readers quote at you, and the hand-kept file
has quietly fallen behind the books. You typed “green eyes” into the wiki in 2024 and
wrote “gray” into the actual scene last week. The fix is not a tidier spreadsheet. It
is a bible structured to scale, and tethered to what you actually wrote. Here is how to build one.
1
Decide what a character entry actually holds
Most bibles fail not from missing characters but from inconsistent entries. One character has a
paragraph of detail, the next has a name and nothing else, and a third has notes you wrote in two
different formats nine months apart. A bible that scales uses the same fields for everyone, so a
gap is visible at a glance.
For each named character, capture the durable facts (the ones a reader could hold you to):
Names & aliases: the canonical name plus every other thing they are called
Age & timeline anchors: birth year or age at a fixed event, not a loose number
Physical traits: eye color, height, scars, the handful of details you describe twice
Relationships: who they are to whom, and how that changes across books
Arc: where they start, what changes them, where they land
Voice: how they speak, so dialogue is recognizable without a tag
Skip the trivia that never reaches the page. Their favorite tea, their childhood pet, the
novel-planning detail that never gets described twice: none of it can contradict, so none of it
needs a record. The bible tracks what readers can catch you on, not everything you ever imagined.
2
Resolve aliases to one person before they multiply
The single biggest reason a large-cast bible breaks is the alias problem. One character can be
named four ways across a series, and if your bible lists them as four people, every later check on
that character is split four ways and half your contradictions hide in the gap.
Consider a character introduced in Book 1 and referred to across the saga as:
Book 1, ch. 2: “The boy at the forge was just Elric then,
barefoot and stubborn.”
Book 3, ch. 11: “They knelt as Lord Ashford entered, and few
remembered the forge at all.”
Book 5, ch. 1: “To the men who'd bled for him, he was only ever
the Gray Marshal.”
Elric, Lord Ashford, and the Gray Marshal are one man. If your bible carries three entries, his
eye color can drift between them and you will never see it, because nothing in the file says they
are the same person.
Pick one canonical name per character and attach every alias to it as a label, not a separate
record. Then a trait set once on Elric is the same trait the bible checks when he is called the
Gray Marshal four books later.
3
Track ages, traits, relationships, and arc on one record
A character is not a static index card. Across a six-book series they age, a scar heals or
arrives, an enemy becomes an ally, and the person on the last page is not the one on the first.
The bible has to hold both the fixed facts and the deliberate changes, and tell them apart from
accidental drift.
Ages & traits
Anchor age to a dated event, not a number. “Twenty-eight in the year of the siege”
survives a flashback; “twenty-eight” alone does not.
Relationships
Note who they are to whom and when it shifts. A sister revealed in Book 4 must not have been
a stranger in a Book 2 scene they shared.
Arc
The intended change, written down. When a trait shifts, you can check it against the arc: did
a scene earn it, or did you slip?
Intent is the whole distinction. Hazel eyes that become brown by accident is an error; a limp that
arrives after a Book 3 battle is character. The bible only protects you if it records the fixed
facts firmly enough that the unplanned changes stand out against them.
Watch the relationship that changes off the page. Two characters can be strangers in Book 1,
married in Book 4, and never shown meeting. That is not always a mistake, but it is the kind of gap
a careful reader notices, so the bible should flag it for you to decide.
4
Capture voice so dialogue stays in character
Physical traits are the obvious thing to track. Voice is the thing readers actually feel when it
slips. A character who spoke in short, clipped sentences for four books should not suddenly turn
eloquent in book five without a reason, and a comic-relief sidekick should not start sounding like
the brooding lead. When two characters' dialogue blurs, the page loses the people in it.
For each major character, record the markers that make their dialogue theirs:
Sentence rhythm: terse and blunt, or long and winding
Vocabulary and register: formal, plain, profane, archaic
Verbal tics: a phrase they overuse, a question they always ask, a thing they never say
What they avoid: the subject they deflect, the emotion they never name out loud
Captain Reyes who says “say again” and clips her sentences to four words is a different
person from the courtier Hale, who never uses one word where three will do. Write those markers
down once, and when a later draft puts Reyes's clipped lines in Hale's mouth, you have something
concrete to check against instead of a vague sense that the scene reads wrong.
5
Extract the bible from the prose, then keep it tethered
A bible you maintain by hand is a second source of truth, and the moment you write a scene without
updating it, the two diverge. By Book 3 the file describes a slightly different series than the one
on the page, and you cannot tell which is right without rereading everything. The error never lives
in the manuscript or the notes alone; it hides in the drift between them, where neither one warns you.
The durable approach inverts it: the manuscripts are the ground truth, and the bible is extracted
from them. Instead of typing entries into a separate wiki, you pull the character record out of the
prose itself, so every trait, alias, and relationship is tied to the exact scene it appears in.
Each fact carries a citation: the book, chapter, and line it came from
When the prose changes, the bible can be re-extracted instead of hand-edited
A trait that appears two different ways in two books surfaces as a conflict, not a guess
New characters from the latest draft enter the bible without you transcribing them
A bible tethered to the prose answers the question that breaks the hand-kept one: not “what
did I write in my notes,” but “what did I actually write in the book.” Those are
the same thing for two books and quietly different by the sixth.
How StoryHelm builds this from your prose
StoryHelm reads and analyzes your manuscripts; the author writes every word. It
extracts character entities straight from the prose into your Canon, the
structured single source of truth. This is Braindump in reverse: instead of you
typing a wiki by hand, StoryHelm pulls the names, aliases, ages, traits, and relationships out of
the scenes you actually wrote, each tied to the chapter it came from.
Across a series, that Canon carries forward in the shared Series Atlas, and the
Coherence Guardian flags when a character's eye color, age, or relationship
contradicts an earlier book, with the conflicting passages side by side and a severity rating. You
read the findings and make every edit yourself. The bible stays accurate because it is tethered to
the manuscripts, not to your memory.
This guide is part of the StoryHelm Learn library on series-scale continuity and craft.
StoryHelm reads and analyzes a series; the author writes every word.
A Bible That Keeps Itself Current
Stop hand-keeping a bible that falls behind your books.
Point StoryHelm at book one or all six. It reads the series, extracts every character into your canon, resolves the aliases to one person, and re-extracts as you draft, so the bible never drifts from the prose. The day before you ship a box set is the wrong day to learn a trait went gray ten chapters ago. StoryHelm flags it with the book and chapter; you keep every word.