Multi-book series planning gets difficult when every new book starts with a fresh file, a copied character sheet, and a vague promise to check the old manuscript later. That system works until Book 3, when a side character’s eye colour changes, a supposedly dead villain appears in a tavern scene, or a political rule from the first novel quietly stops making sense.

Build one shared source of truth instead: a universe codex that holds the people, places, history, objects, and relationships that belong to the wider story world. A series can then sit inside that universe as an ordered shelf of related books. Give each book its own plot plan, character-arc focus, and manuscript. The goal is not to turn planning into bureaucracy. It is to stop recreating foundational work every time you open a new novel.

This approach suits connected standalones, trilogies, long-running detective series, romantasy sagas, and authors with more than one series set in the same world. A universe can contain whole series and standalone books; a series by itself is simply the reading-order container.

Start Multi-Book Series Planning With Two Separate Layers

The most useful distinction is simple: separate universe truth from book-specific story.

Universe truth is information that remains relevant beyond one manuscript, whether it appears in a series or in a standalone novel from the same setting. Book-specific story is the material that changes because this particular novel has its own protagonist, problem, and ending.

Put lasting shared information in the universe codex

Your shared codex should include details you do not want to rewrite, duplicate, or hunt down later. Typical entries include:

  • Recurring characters and their physical descriptions, roles, secrets, family ties, and current status
  • Places such as towns, kingdoms, ships, schools, neighbourhoods, and businesses
  • Groups including clans, police departments, magical orders, corporations, and rival factions
  • Important objects, technologies, creatures, or magical systems
  • Lore notes covering history, rules, terminology, calendars, religion, geography, and social customs

Do not try to document every fact about your fictional world before drafting. Add entries when the information becomes useful, likely to recur, or easy to contradict. A café visited once by an unnamed protagonist does not need a codex entry. The café that becomes the meeting point for three books probably does.

Think beyond one shelf when necessary. If you write a detective series and later publish a standalone about the detective’s former partner, both books may need the same city, police department, and history. That is universe material, even if the books are not in the same series.

Keep each book’s active story plan inside that book

Each novel still needs its own working material. Keep these elements at the book level:

  • The premise, central question, and ending promise for that volume
  • Scene and chapter plans
  • The protagonist’s emotional arc for this book
  • Book-specific suspects, victims, love interests, antagonists, or settings
  • Revision notes, beta-reader comments, launch dates, and KDP metadata

For example, in a six-book cozy mystery series, the detective, her bakery, the town, and the sheriff belong in the universe codex. The poisoned judge, the annual pie contest, the killer’s motive, and the clues belong in Book 4.

This boundary prevents two opposite problems: a sprawling codex full of disposable plot notes, and a book outline that has to explain the whole world from scratch.

Build a Shared Codex Around What Readers Can Notice

A good codex is designed for continuity checks, not for showing off how much research you have done. Record details that can affect reader trust, plot logic, or future scenes.

Characters: track identity, change, and availability

Create a character entry as soon as someone has a name, a recurring role, or a meaningful connection to the protagonist. Use a consistent set of details, such as:

  • Full name, aliases, age range, pronouns, and appearance markers
  • Story role and first appearance
  • Wants, fears, strengths, blind spots, and secrets
  • Voice notes: speech habits, education level, favourite phrases, or mannerisms
  • Current location, affiliation, relationship status, and whether they are alive

“Alive” sounds obvious, but it is one of the highest-value continuity fields in a long series. Also note situations that are nearly as final: imprisoned, missing, estranged, retired, transformed, or publicly believed dead.

In Pendrilo, character entries have a Deceased setting with a note for when and how the character died. When that entry is shared with a universe, the marker follows it into every member book. That gives you a visible warning in later books without relying on memory.

Do not lock characters into static labels. A series character should have a stable core and a changing state. Detective Mara Venn may always be observant and impatient, but her relationship with her brother, rank in the department, and willingness to bend rules can move from book to book.

Places: record rules, not just scenery

For a recurring location, capture the details that create story constraints. A city entry might note its population, political structure, climate, travel time from other places, dangerous districts, and who controls it. A spaceship might include crew capacity, fuel limits, deck layout, and which systems are unreliable.

In fantasy and science fiction, make a short “what cannot happen here” note. If magic cannot work across saltwater, write it down. If travel between planets takes eleven days, write it down. Constraints are often more important than descriptions because they stop accidental shortcuts later.

Relationships: treat them as changing facts

Most series errors are not about eye colour. They are about emotional continuity. Readers notice when former enemies trust each other too quickly, when a breakup has no aftermath, or when siblings forget a major betrayal.

Track relationships as connections between codex entries, then attach a brief status note and the book where it last changed. For example:

  • Elian and Sora: former partners; professional trust restored in Book 2; romantic tension unresolved
  • Mara and Chief Bell: mentor and subordinate; strained after the Book 3 cover-up
  • The Ash Court and the River Guild: trade alliance; secretly preparing for conflict

When both connected entries are shared with the universe, their relationship can appear across the universe too. That is useful for a political alliance, family connection, or old rivalry that matters in several series. A relationship involving a private book-only entry remains useful locally without cluttering every other book.

Create a Series Spine Before You Outline Every Book

You do not need a chapter-by-chapter plan for seven future books. You do need a series spine: a lightweight map of what changes across the full run.

Start with four questions:

  1. What larger problem, mystery, threat, or transformation connects the books?
  2. What does the protagonist, ensemble, or world look like at the beginning and at the end?
  3. Which revelations must arrive early, middle, and late for the series to feel intentional?
  4. What must each individual book resolve so readers are satisfied?

Write one or two paragraphs for the series premise, then sketch a row for each planned book. Include the lead viewpoint, primary external conflict, internal shift, major series development, and ending status.

A five-book fantasy series might look like this:

  • Book 1: A reluctant heir stops a local coup and learns the royal line was falsified.
  • Book 2: She seeks an ally across the sea, loses public support, and discovers the empire caused the original falsification.
  • Book 3: Civil war forces her to choose between legitimacy and reform.
  • Book 4: A failed treaty reveals the empire’s invasion timetable.
  • Book 5: She unites rival regions, defeats the invasion, and replaces the system that created the succession crisis.

The details will change. That is normal. The spine exists to reveal gaps: three books with the same emotional lesson, a villain who disappears for too long, or a final conflict that has not been seeded.

Leave room for discovery. A useful rule is to plan the next book in detail, the following book at a medium level, and later books at a high level. Update the spine after every completed draft rather than treating an old outline as law.

Use Universe Boundaries to Avoid Rebuilding the World

When you begin a new volume, do not duplicate the prior book’s character files and lore notes. Create the book, place it in the appropriate series if it belongs in one, and connect that series or standalone book to the wider universe when shared world material is needed.

In Pendrilo, a Universe groups related series and standalone books under one header and gives them access to a shared codex. A series remains an ordered shelf inside that structure. A standalone book can also join a universe directly.

When you move existing books into a universe, Pendrilo asks whether their current codex entries should be shared. Accepting makes those entries available to every member book. Declining keeps them private to the original book, which is useful when an early draft contains tentative characters or material you have not decided is canon.

After that, new codex entries created in a member book are shared with the universe automatically. You can still make an individual entry private to its book later, or share older private entries one at a time or all at once. That gives you a practical middle ground between copying everything and exposing every rough idea too early.

The practical benefit is that a correction happens once. If you decide the harbour district is called Low Quay rather than East Quay, update the shared place entry. You are not left wondering which of five copied documents still has the old name.

Give every book a short “entry brief” at the top of its outline. It should answer:

  • Where does this book begin in the series timeline?
  • Which shared characters have a major role here?
  • What changed in the previous book that must affect this one?
  • Which codex entries might need updating by the final chapter?

That final question matters. A book changes the universe. When Book 2 ends, update the shared facts: a building burned down, two characters reconciled, a new ruler took power, a magical artifact was destroyed. Do this during your post-draft wrap-up, not six months later when you begin the sequel.

Run a Continuity Review at Three Specific Points

Continuity is easiest to manage as a repeatable check rather than a heroic reread before publication. Schedule it at three moments.

Before drafting: review only the relevant entries

Read the series spine, your book entry brief, and the codex pages for major characters, settings, and relationships. You do not need to study every minor character in the universe. Limit your review to the material that will appear on the page.

Make a small continuity watch list for facts likely to cause trouble: injuries, pregnancy timelines, travel distances, titles, unresolved promises, deaths, and age-sensitive details. Put these in a note beside your outline.

At the midpoint: check cause and effect

When you reach roughly the middle of the draft, look for consequences that have gone missing. If Book 1 ended with the heroine exposing a corrupt mayor, what changed in the town? If a main character lost an arm, have you written scenes as if they have two functioning hands?

This check is about more than factual accuracy. It protects plot causality. Major events should alter relationships, resources, risks, and choices in later books.

Before sending to readers: audit reader-facing details

Do one focused pass for names, descriptions, timeline references, relationship status, geography, and recurring rules. Search your manuscript for each major character and location. Compare uncertain details with the codex rather than trusting memory.

Then send selected chapters to beta readers who know the series. Ask targeted questions instead of the vague “Did you spot any issues?” Try: “Did anything contradict Book 1?” “Does the friendship between Mara and Bell feel consistent?” “Were any rules of the magic system unclear?”

Pendrilo’s private beta-reader share links can cover all chapters or a selected chapter list, and readers do not need an account. If you allow comments on the share, they can leave notes on a selected passage or on the chapter generally, giving you focused feedback on a continuity-sensitive reveal without sending a full-manuscript draft.

Keep the Codex Useful, Not Perfect

The danger of a shared universe codex is overbuilding it. If maintaining the reference material becomes a second job, you will avoid it, and it will stop being reliable.

Use a few simple rules:

  • Write facts in plain language, with enough context to understand them six months later.
  • Mark uncertain ideas as tentative rather than presenting them as established canon.
  • Record the book and chapter where a major fact was confirmed or changed.
  • Delete or archive abandoned ideas instead of letting them masquerade as canon.
  • Update the codex after each draft and after substantial revisions.

A short entry with accurate, current information is better than a beautiful profile written before the character has appeared in a scene. Your codex should serve the manuscript, not compete with it.

If you are still setting up your series workflow, Pendrilo’s free publishing tools can help with later production estimates, including page count and paperback spine calculations. New accounts can start a seven-day, one-book trial with up to 3,000 cumulative manuscript words; multi-book workflows require paid access. When you are ready to test the process with a current manuscript, you can create a Pendrilo account.

Keep the model simple: use a series to set reading order, use a universe when books need shared world information, and review only the codex entries that matter to the book in front of you.