How to Build a Story Bible for a Long Web Serial (And Why You Need One)

A story bible is your single source of truth for everything that has happened, exists, or matters in your story. It is the document you check before writing a chapter to remind yourself what the protagonist's current stats are. It is the document you check after writing a chapter to update what just changed.

The term comes from television production, where a 'show bible' tracks every character, every world rule, and every plot thread across multiple seasons of writing. Web serials are essentially long-running TV shows, and they need the same tool.

Most new web serial writers can hold their entire story in their head for the first 25 chapters or so. They remember every character name, every magic rule, every location. Around chapter 30, the cracks start to appear. The character whose name was Aldric in chapter 12 becomes Aldrich in chapter 31. The 'cooldown' on the protagonist's signature ability that was 30 seconds in chapter 18 becomes 5 minutes in chapter 35. The merchant the protagonist met in chapter 20 has somehow forgotten that they already had a conversation in chapter 14.

Readers catch every single one of these mistakes. Royal Road's comment culture is unforgiving. A single committed reader will go back through your story, find the contradiction, and post a 200-word comment listing every retcon. This drags your average rating down. A lower average rating can cut your visibility in Royal Road's rankings, which in turn slows follower growth and Patreon income.

The story bible exists to prevent this. It is a defensive document. The work you put into maintaining it is paid back in fewer retcon comments.

The minimum viable story bible tracks five categories.

Characters — name, age, physical description, current stats (if LitRPG), key abilities, current relationships, and a one-sentence summary of their role in the story.

Relationships — for each pair of important characters, what is the current state of their relationship? Allies? Romantic? Enemies? When did this state last change?

Locations — name, brief description, who lives or rules there, and what major events have happened there.

World rules — for each magic system, technology, or universal mechanic, what are the rules? What are the limits? What are the consequences for breaking them?

Timeline — a chapter-by-chapter (or event-by-event) record of major plot events, especially those that other characters can reference later.

Progression-heavy stories (LitRPG, Cultivation) need a sixth category: progression tracking — every level, skill, item, rank and stat change for the main characters, with the chapter number it changed.

The manual approach is a Google Doc or a Scrivener document with sections for each category. You update it manually after each chapter. This works for the first 30 chapters. After that, the maintenance burden becomes real — you are spending 15–30 minutes per chapter updating the bible, on top of your writing time. Most writers stop doing it. The bible goes stale. The contradictions begin.

The automated approach uses an AI tool to read the chapters you have already written and build the bible from them. PlotWrite does this with its Story brain: it reads your chapters on your own AI, proposes new characters, places, items and stat changes, and waits for your approval in the Inbox before anything is added. You write the story; PlotWrite remembers it.

The time savings compound. A writer maintaining a manual bible can spend a large share of their writing time on upkeep over a long serial. A Story brain cuts that down to quick reviews of what was proposed.

For the habits that hold a serial together past chapter 300, see How to keep a 500-chapter web serial consistent. For tracking LitRPG numbers specifically, see How to track LitRPG stats.

The most valuable part of a maintained story bible is the ability to check a new chapter against it and catch contradictions before publishing. This is called a Continuity Pass in traditional editing, and a Canon check in PlotWrite.

The check looks for: stat inconsistencies (the MC had STR 47 in chapter 30, why is it STR 50 in chapter 31 with no level-up?), character name spelling drift (Aldric vs Aldrich), timeline gaps (the journey from City A to City B took 3 days in chapter 20, why does it take 1 day in chapter 35?), and forgotten relationships (the merchant has met the MC twice already, why are they introduced again?).

A quick check before publishing each chapter helps you catch many of the issues that would otherwise become 1-star comments. PlotWrite's canon check shows both conflicting quotes side by side and offers a one-click fix that you preview as a diff first. Start your free trial →

PlotWrite reads the chapters you have written and proposes pages for:

• Characters (with a one-line description and details like gender)
• Places (with type and significance)
• Relationships between characters, shown with [[links]], a graph and a timeline
• World rules (magic systems, technology, universal laws)
• Progression details for LitRPG/Progression Fantasy stories (skills, items, ranks, status changes), timed by chapter so a stat sheet can show any character as of chapter N

Nothing is added until you approve it in the Inbox, and you can edit any page by hand. After 50 chapters, you have a detailed searchable Story brain without typing it all yourself. Using it does not put prose in your chapters, so it counts as back-office help under Royal Road's AI policy (see /royal-road-ai-policy).

This is the entire reason PlotWrite exists. Manual bible maintenance is the silent killer of long web serials, and a Story brain lets you keep writing instead of organizing. Start your free 7-day trial →