The short answer
Maintain Continuity Across a Book Series
Maintain continuity with a source-backed series bible organized around canon and changing state. After each volume, record the final condition of characters, relationships, locations, institutions, objects, rules and unresolved story promises. Before outlining the next book, create an entry packet from that exit state. Cite the manuscript source for important facts so memory can be checked instead of trusted blindly.
Record consequences, not summaries
A plot summary tells you what happened. A continuity record tells you what the event changed and what later books must respect. The distinction matters because a memorable climax may leave dozens of less memorable constraints: a bridge is gone, a title has changed hands, an oath has become public and a character no longer has access to an institution.
For each major event, write the before state, event, immediate outcome, durable consequence and source location. This transforms the bible from an encyclopedia into an operational memory.
Separate levels of authority
Published text, an approved manuscript, a working draft and a future possibility do not have equal authority. Mixing them creates false contradictions and accidental canon. A concept mentioned in a planning meeting should not constrain Book III as if readers already encountered it.
Use simple status labels. Published canon can be changed only through a deliberate repair. Approved but unpublished material may be revised with dependency checks. Draft material is provisional. Ideas remain possibilities until selected.
- Published: visible to readers and highest authority.
- Approved: accepted for the current production but not yet released.
- Draft: present in working text and subject to revision.
- Proposed: an option with no canon authority.
- Rejected: retained only to prevent accidental reuse.
Create book exit and entry packets
At the end of each volume, capture the story world at rest: who is alive, missing or injured; which relationships changed; what the public believes; where crucial objects are; which institutions gained or lost power; and which promises remain open.
Before planning the next volume, convert that exit packet into entry conditions. Add the elapsed time and ask how recovery, travel, politics, grief, resources and rumor would realistically develop during the gap. A time jump is not permission to reset the system.
- Freeze the final manuscript version used as the source.
- Extract durable facts and changes with chapter references.
- List open promises, mysteries, debts and explicit plans.
- Advance every changing state across the inter-book gap.
- Approve the next book's entry packet before outlining new events.
Audit the series at decision points
Continuity checks are most valuable before a dependency multiplies. Audit when approving a volume outline, after a major canon change and before publication. Checking only at the end turns small questions into expensive rewrites.
Assign an owner to each disputed fact and record the ruling. A series bible with unresolved contradictions hidden inside it is not a source of truth; it is a second manuscript to interpret.
Original narrative example
Example: the world cannot silently reset
Before
Book I ends with the western floodgate destroyed and the harbor district evacuated. Book II opens six months later with merchants using the same route and no reference to repairs or displacement.
What is not working
The sequel remembers the dramatic event but not its state changes. The city behaves as though the climax were temporary scenery.
Revision
The Book I exit packet records the destroyed gate, contaminated warehouses, emergency council powers and three displaced neighborhoods. Book II opens with a costly temporary channel, political conflict over reconstruction and altered smuggling routes that directly affect the new plot.
Diagnostic
Common mistake: one enormous series document
A single file can become difficult to query and easy to contradict. Important facts disappear among biographies, lore, ideas and discarded plans.
A more useful correction
Use connected registers for canon, timeline, world state, character knowledge, objects and promises. Link them with stable IDs and source references.
Put it into practice
Minimum viable series bible
- Canon register with authority status and manuscript evidence.
- Master timeline with event order and elapsed durations.
- Volume exit packets and the next volume's entry conditions.
- Character, relationship, location and object state trackers.
- Open-promise ledger for mysteries, foreshadowing and obligations.