Keeping a series consistent across books

Series contradict themselves for one structural reason: the facts of the world were never stored separately from the telling of them. When the only record of a character’s age is the sentence in book one that mentions it, book three has no way to check. The fix is a reference that holds facts in the world’s own terms, updated once per draft.

The three things that drift

Ages and dates

The most common failure, and the most avoidable. It happens because writers track two different quantities in two different places: elapsed time in the narrative, and character ages in the cast list. They fall out of step at the first time skip.

Store one thing instead: a birth date in the world’s own calendar. Every age is then computed, never recorded. If your world has no calendar, invent one to the level of “year 412 of the Compact”. You do not need months.

Distance and travel time

Journey lengths get set by pacing. The crossing takes six days in book one because the chapter needed six days of conversation, and a fortnight in book three because the plot needed a delay.

Store distances between places once, as a property of the pair, plus a travel rate. Then every journey length is derived. It is unglamorous, and it heads off a lot of reader complaints.

Who knows what

The hardest to track and the most damaging when wrong, because it is usually invisible to you and obvious to a reader. A character reacting to news they were told two books ago reads as a continuity error even when the fact itself is right.

Record knowledge as a dated event: who learned what, when, from whom. Give it an entry of its own rather than a field on the character.

What a series bible has that a story bible does not

A story bible serves one writer on one book. A series bible has to survive being handed to a co-author, an editor, or eventually an adaptation team. That adds three requirements.

Canon status on every entry. Settled, provisional, or abandoned. One writer on one book can hold this in their head. Two people cannot.

In-world dates, not chapter references. “Before the siege” survives a restructure. “In chapter nine” does not, and you will restructure.

An export you can hand over. Check this before you commit, not after. Obsidian stores plain Markdown on your own disk, which makes it trivially portable. Among hosted tools, vvd offers API access on its Pro plan at $10.75 per month, and World Anvil and Kanka both support exports. (Verified 22 September 2026.)

The update pass

The discipline matters more than the tool, and it is one habit: at the end of each draft, before you start the next book, reconcile the bible against what you actually wrote.

Not continuously. Continuous updating sounds responsible and fails in practice, because mid-draft you are inventing faster than you are recording, and stopping to file things breaks the writing. One pass, at a natural boundary, catches nearly everything.

The pass has four steps:

1. Read your own bible end to end, rather than the book.
2. Mark every provisional entry the draft has now settled.
3. Add the entities the draft invented that are not yet recorded.
4. Note every contradiction you find and decide which version is canon, now, while you still remember why.

Step four is the one people skip. An unresolved contradiction does not stay neutral; it gets picked arbitrarily by whichever book you write next.

The test before you draft

Before starting the next book, answer these from the bible alone:

• How old is each surviving viewpoint character, in the world’s calendar, on page one?
• How long does it take to travel between the two places this book moves between?
• What does each viewpoint character currently believe about the central secret?

If you cannot answer all three without opening a previous book, the bible is incomplete. Now, before you have written eighty thousand words on top of the gap, is the cheapest moment you will get to fix it.

Frequently asked

How do professional authors keep long series consistent?

Almost universally by maintaining a reference that is separate from the manuscript and updated at the end of each draft rather than continuously. The discipline is the update pass, not the tool.

What causes most series continuity errors?

Timelines and travel. Ages drift because the writer tracks years elapsed in one book and character ages in another; distances drift because journey lengths are set by pacing rather than by geography. Both are fixed by storing in-world dates and inter-place distances once, explicitly.

Should I re-read the earlier books before drafting the next one?

Re-read your own bible, not the books. If the bible cannot replace the re-read, it is incomplete, and finding that out before you draft is the cheapest time to find out.

Do I need different software for a series than for one novel?

The requirements change more than the tools do. A series needs canon status per entry, in-world dates rather than chapter references, and export you can hand to someone else. Several tools do all three; a folder of documents does none.