Story Bible Template for Novel Writers: AI-Ready Guide

Story Bible Template for Novel Writers

A good story bible template does not need to look polished. It needs to be findable, current, and specific enough to stop your novel from contradicting itself three chapters later.

If your notes are scattered across chats, character sheets, drafts, and worldbuilding files, a story bible gives the project one reliable center: premise, style, cast and relationship state, world rules, timeline, open threads, and chapter changes. It should make the next scene easier to draft, not become a second novel you have to maintain.

For writers using AI for long-form fiction writing, long context does not remove the need for editorial judgment. The model still needs the right facts: what happened, what must not change, and what each character knows now. Below you’ll find a copy-paste story bible template, filled examples for hidden rules and relationship tension, and a practical way to turn the bible into AI chapter context.

📘 What Is a Story Bible?

A story bible is the reference you check when the draft starts contradicting itself. It records the facts that must stay consistent: premise, character arcs, relationship states, world rules, timeline, factions, open threads, and chapter-by-chapter changes.

The best story bibles do not answer every lore question. They answer the questions most likely to break later chapters: what changed, who knows it, which promise is still open, and what rule the next scene cannot violate. Character bibles, worldbuilding bibles, and lorebooks can help too; the difference is easier to see once the working template is in front of you.

🧩 Copy-Paste Story Bible Template

Copy the template, then cut it down. If you are starting from zero, fill only the fields your next chapter actually needs: premise and reader promise, style notes, current cast or relationship state, world rule limits, timeline, open threads, and chapter state changes. Add the rest when the draft gives you a reason. A useful story bible starts small enough that you will actually update it.

1. Core Premise and Reader Promise

Working Title:

One-Sentence Premise:

Main Dramatic Question:

Genre:

Reader Promise:
- Emotional experience, trope pleasure, and what the story should not become:

If the reader promise changes, update this before you revise scenes. A draft can absorb a new subplot more easily than a broken promise about what kind of book this is.

2. Genre, Tone, and Style Notes

Genre and Subgenre:

Tone Words:

Prose Style:
- Sentence rhythm:
- Dialogue style:
- POV distance:

Keep style notes plain enough to use while drafting: “close third, clipped dialogue under stress, sensory detail through touch.”

3. Main Cast and Relationship States

Character Name:
Role in Story:
External Goal:
Private Want:
Fear or Wound:
False Belief:
Arc Direction:
Current Emotional State:
Current Knowledge:
Voice Notes:
Physical Anchors:
Relationship States:
Copy one unit for each important relationship.

Relationship: [Character A] ↔ [Character B]
Current Dynamic:
Trust Level:
Unresolved Issue:
Last Major Shift:
Current Block:
Next Allowed Shift:

Relationship: [Character A] ↔ [Character C]
Current Dynamic:
Trust Level:
Unresolved Issue:
Last Major Shift:
Current Block:
Next Allowed Shift:

Do Not Forget:

In long fiction, current relationship state usually saves more scenes than another paragraph of backstory. Treat each relationship as a repeatable unit: copy the block once for every bond that can change the next chapter, then track the last shift, the block still in place, and the next move the story has earned.

4. World Rules, Locations, and Systems

World Overview:

Public Rules:
- What ordinary people believe is true:
- Who believes the public rule:

Hidden Rules:
- What is actually true, but not widely known:
- Who knows the hidden rule:
- When the reader learns the truth:

Limits and Costs:
- What magic / technology / social power cannot do:
- Using it costs:

Major Locations / Factions:
- Name:
- Function in story:
- Who controls it:
- What changed there:

If a rule cannot change a choice, reveal, cost, or consequence, it probably belongs in your worldbuilding archive. The common mistake is preserving lore history while forgetting the limit that controls the next scene.

5. Timeline and Continuity Log

Story Start Date or Season:

Age / Time-Sensitive Details:

Travel Times:

Injuries, Damage, and Physical Continuity:

Promises Already Made to Reader:
- Emotional promise:
- Mystery or reveal promise:
- Physical continuity promise:
- Relationship payoff promise:

A reader promise can be a visible injury that should still hurt tomorrow, or a reveal the opening chapter trained the reader to expect. Keep both where you can find them.

6. Plot Threads, Secrets, and Unresolved Questions

Open Plot Threads:
- Thread:
- Introduced in chapter:
- Current status:
- Who cares about it:
- Planned payoff:

Secrets:
- Secret:
- Who knows:
- Who suspects:
- Who is wrong:
- Reader knowledge:
- Reveal timing:

Unresolved Questions:
- Question:
- Why it matters:
- Latest clue or complication:

Readers forgive mystery. They notice neglect. The “who is wrong” field matters because AI often smooths misunderstandings unless you tell it which false belief must stay alive.

7. Chapter Index and Current Story State

After each chapter, record what changed, not the whole plot. A short state change is more useful than a polished recap.

Chapter Number:
POV Character:
Setting:
Time Passed:
Scene Purpose:
What Changes in This Chapter:
- Character state:
- Relationship state:
- World knowledge:
- Plot thread status:
- Physical continuity:
New Facts Added to Story Bible:

For example: Mara now knows Jun lied, the fever cure failed, the council deadline moved to dawn, and the knife wound still limits her grip. The next chapter has to obey those facts.

8. AI Drafting Notes

Core Context the AI Must Know:
- Pull 6-8 scene-relevant facts, not the whole story bible.

Current Chapter Goal:

Must Preserve:
- Character voice:
- Relationship tension:
- World rule:
- Timeline detail:
- Unresolved secret:

Do Not Resolve Yet:

Do Not Mention Yet:

Useful Prior Chapter Facts:

--- After Drafting ---
Revision Check After Drafting:
- Did the scene contradict the story bible?
- Did any character know something too early?
- Did the scene resolve tension before the planned payoff?
- Did the tone match the reader promise?
- Did it forget an injury, object, clue, or deadline?

Treat this as a scene packet, not a memory dump. Pull only the facts that can change the next scene: current goal, relationship state, relevant rule, recent change, and reveal boundary.

The template is ready. The next step is keeping it beside the draft, not in a separate window you have to rebuild every session. Start with one small context pack: current scene goal, relationship state, rule limit, recent change, and what the next chapter must not reveal.

In SeaBell, that context pack becomes the opening brief for a chapter drafting session. Bring it in, choose the model, and draft from there.

✨ Story Bible Example: A Fantasy Novel Setup

Here is a condensed story bible example showing how a fantasy draft can separate public truth, hidden truth, character knowledge, and reader knowledge without turning the bible into a lore encyclopedia.

Core Premise

Working Title: The Glass Orchard
One-Sentence Premise: A disgraced mapmaker must guide a prince through a forest of living glass to find the queen's missing heart before the kingdom's memories shatter.
Genre: Adult fantasy with mystery and court intrigue
Reader Promise: Elegant danger, secrets inside old magic, a slow trust arc between two wounded allies
Tone: Lyrical but controlled; tense, not grimdark
Main Dramatic Question: Can Liora save a kingdom that punished her for telling the truth?

Magic Rule Tracking

Public Rule:
The Glass Orchard preserves memories. Anyone who touches a glass fruit can relive a lost moment.

Hidden Rule:
The Orchard does not preserve memories. It feeds on them, copies them, and returns a polished version that removes guilt.

Limit / Cost:
Every use removes one uncomfortable truth from the user. The loss feels like relief, so most people do not notice.

Who Believes the Public Rule:
Most of the court, the common pilgrims, and Prince Cael at the start of the journey.

Who Knows the Hidden Rule:
Lord Veyr knows the Orchard consumes guilt. The queen knew enough to hide her heart there for a reason.

Protagonist Knowledge:
Liora knows the Orchard changes maps and paths. She does not yet know it changes memory.

Antagonist Knowledge:
Lord Veyr understands the Orchard's cost and has used it to keep the court obedient.

Reader Knowledge:
By chapter 4, the reader sees that witnesses remember the same event in slightly prettier versions. The full rule is not confirmed until chapter 9.

Do Not Reveal Yet:
The queen willingly hid her heart in the Orchard to remember her crimes without being controlled by them.

Cast Snapshot

Liora Vale
Role: Protagonist; former royal mapmaker
External Goal: Find the queen's heart and restore her name
Private Want: To be believed without begging
Fear: That her talent only brings ruin
Arc Direction: From defensive truth-teller to leader who chooses when truth needs mercy
Current Knowledge: Knows the royal maps are lying; does not know why
Voice Notes: Precise, dry humor, notices angles and distances

Prince Cael
Role: Reluctant ally and heir
External Goal: Recover his mother before the council declares him unfit
Private Want: To stop being measured against a saintly version of the queen
Fear: That he will be easier to control than she was
Relationship State with Liora: Suspicious alliance; respects her skill, resents her bluntness
Do Not Resolve Yet: He should not apologize fully before chapter 8

Lord Veyr
Role: Antagonist; keeper of the Orchard treaty
Public Face: Calm regent protecting the kingdom from panic
Hidden Agenda: Keep the court dependent on edited memories
Knowledge Advantage: Understands the Orchard's cost and has used it for years

Chapter State Change Example

Chapter 6
POV: Liora
Setting: Eastern edge of the Glass Orchard
Time Passed: One night after the council hearing
Scene Purpose: Force Liora and Cael to trust each other under pressure
What Changes:
- Liora learns the Orchard reacts to spoken lies.
- Cael sees a memory of his mother that contradicts the official story.
- Relationship state shifts from hostile cooperation to cautious reliance.
- Reader now suspects the queen was not kidnapped by an enemy faction.
Story Bible Updates:
- Add spoken lies to World Rules / Hidden Rules.
- Move Cael's knowledge from official story to first doubt.
- Update Liora and Cael's relationship state.
- Add Liora's hand injury to continuity log.
Do Not Forget:
- Liora's left hand is cut by glass; keep bandaged through chapter 8.
- Cael still does not know Veyr arranged the false border attack.

What This Example Does Not Include

Notice what the bible does not do: it does not explain the full history of the Orchard. It tracks the facts that control scenes: who can lie, who knows the cost, what the reader suspects, and which reveal must wait. The queen’s hidden choice also supports the reader promise: old magic is dangerous because it edits guilt, not because it throws brighter sparks.

💞 Romance and Web Novel Example: Relationship State Tracking

Relationship-state tracking matters in romance, romantasy, fanfiction, and web novels because tension changes faster than backstory. The practical question is not “Do they love each other?” It is “What are they willing to admit right now?” “Enemies to lovers” is not enough guidance for chapter 22.

Pairing: Mara / Jun
Trope: Rival healers forced to run the same plague ward
Current Stage: Trust in crisis, attraction acknowledged privately, no confession yet
Public Dynamic: Polite professional rivalry
Private Dynamic: Protective, easily hurt, afraid to need each other
Last Major Shift: Jun covered for Mara's illegal treatment choice in chapter 18
Current Block: Mara thinks Jun acted from guilt, not loyalty
Next Allowed Shift: Jun chooses Mara's method in front of the council, risking his license
Do Not Resolve Yet: No full confession before the quarantine breach
AI Warning: Do not write them as openly affectionate yet. Keep care visible through action, not direct declarations.

This note stops an AI draft from jumping to the payoff too early. In serialized fiction, the couple can move closer in behavior before the confession moves closer on the timeline.

🗂️ Story Bible vs. Character Bible vs. Worldbuilding Bible vs. Lorebook

The names overlap, which is why writers often keep several documents that repeat each other. Separate them by job instead, then let only the active, scene-relevant facts return to the story bible.

The practical rule: archives can be large, but the story bible should stay current. A lorebook can retrieve the Silver Court when the name appears; the story bible should track whether the protagonist still misunderstands what the Silver Court really wants. Move only the facts that can affect the next scene back into it.

🔄 How to Keep Your Story Bible Useful While Drafting

Start small: premise, cast, core world rules, and first plot threads. Leave room for discovery. A story bible should protect the draft from chaos, not punish you for changing your mind.

Retire stale notes early. If a subplot is cut, mark it as removed. Old notes confuse both writers and AI systems because they keep competing with the current version of the story.

The fastest way to ruin a story bible is to treat it like a second novel. Keep the prose plain. Future-you is looking for facts, not atmosphere.

After each chapter, update only changed facts: a relationship shift, a secret moving from hidden to suspected, a wound, an object, a promise, a clue, or a deadline.

Use short labels. “Mara trusts Jun professionally but not emotionally” is more useful during drafting than three polished paragraphs of history.

Make the story bible part of your drafting rhythm: open it before a difficult scene, update it after a chapter, and check it before revising a reveal. That is the practical answer to how to make a story bible: build the smallest reference that protects the next chapter, remove what no longer applies, then let the draft tell you what else deserves a field.

🤖 How to Use a Story Bible With AI

Do not paste a giant story bible into every prompt and hope the model notices the right details. Long inputs still run through token limits, and they can bury the signal. In AI writing workflows, the common failures are ordinary: the model reconciles a couple too early, leaks a hidden rule, forgets a wound, or corrects a false belief the scene still needs.

Before drafting: turn story facts into a short context pack

Weak prompt: “Use my story bible and write chapter 12.” That asks the model to decide what matters, which is exactly where continuity mistakes begin.

Better context pack:

Chapter 12 Context Pack
Premise: A disgraced mapmaker and reluctant prince are searching the Glass Orchard for the queen's missing heart.
Current Scene Goal: Liora must negotiate with the Orchard's blind gardener without revealing that Cael carries royal blood.
Current Relationship State: Liora and Cael trust each other under pressure but still avoid emotional honesty.
World Rule to Preserve: The Orchard reacts to spoken lies and quietly edits painful memories.
Character Knowledge: Liora suspects memory magic; Cael does not know Veyr caused the border attack.
Recent Change: Liora's left hand is cut and should affect how she handles tools.
Do Not Reveal: The queen hid her own heart.
Style: Close third, tense, lyrical but not ornate. Keep dialogue restrained.

That pack gives the scene the facts that matter now, without burying them inside a sprawling reference file.

After drafting: update what changed

Before asking for the next scene, add the latest state changes in one or two plain sentences. Do not paste the whole story bible again; tell the model what just moved.

For example: “Liora cut her left hand, Cael saw a false memory of his mother, and their relationship shifted from hostile cooperation to cautious reliance. In the next chapter, Liora should still struggle with tools, and Cael should trust her under pressure without becoming emotionally open yet.” That update gives the next prompt the changes it must obey.

During revision: check contradictions without surrendering judgment

Use AI for a second pass after drafting: ask it to look for knowledge leaks, premature payoff, contradicted rules, forgotten injuries or objects, broken deadlines, and plot threads resolved too early. Treat the output as an assistant pass, not canon. AI can flag a possible contradiction, but the writer still decides whether the draft is wrong, the bible is outdated, or the story has genuinely changed.

🌊 Where SeaBell Fits Into Story Bible Workflows

Once the story bible is useful, the next challenge is keeping it close to the actual writing. Many writers build a solid reference document, draft somewhere else, prompt an AI model in another window, and track revisions in a third place. The gaps show up quickly: the prompt misses the latest wound, the draft forgets the relationship stage, and the revision pass treats a secret as public knowledge.

SeaBell fits after the story bible has done its job: when you need to carry the current chapter pack into drafting instead of rebuilding the prompt from scattered notes. Bring over the current goal, relationship state, rule limit, recent change, and do-not-reveal note, then draft or revise with those facts close at hand.

In practice, open the session with your chapter context pack, choose the model that fits the scene, including a long-context AI model when the chapter needs more background, and draft from the facts the chapter must obey. Using the examples above as a guide: when a scene depends on restrained dialogue, keep the relationship block and “do not resolve yet” note visible. When a scene tests a hidden rule, bring over the rule, who knows it, and when the reader is allowed to learn it.

That is the right level of handoff: not the whole archive, not a vague “remember everything,” but the specific context the next chapter must obey.

That does not make SeaBell a magic memory solution, and it does not replace judgment. It keeps the working notes nearer to the chapter, the prompt, and the revision pass, where continuity usually breaks.

Build your story context, choose the model that fits the scene, and draft your next chapter in SeaBell’s AI fiction writing workflow.

❓ FAQ

What is a story bible?

A story bible is a working reference for a story’s continuity: premise, cast, rules, timeline, relationship states, open threads, secrets, and chapter changes. It helps you keep later scenes consistent while the draft evolves.

What should be included in a story bible template?

Include the fields that protect the next draft: premise, reader promise, cast state, relationship state, world rules and limits, timeline, open threads, secrets, chapter changes, and AI context notes if you draft with AI.

What is the difference between a story bible and a character bible?

A story bible tracks the whole story’s continuity. A character bible tracks a person’s voice, history, wounds, habits, and emotional triggers. If that layer gets complex, keep it in a dedicated novel character card system, then move only scene-critical facts into the story bible.

What is the difference between a story bible and a lorebook?

A lorebook is usually built for retrieval inside an AI writing tool. It can define people, places, factions, or rules. A story bible is broader: it tracks what has changed, who knows what, and what the next chapter must preserve.

Do I need a story bible before writing a novel?

No. Some writers discover the story as they draft. Start a light story bible when chapter two introduces facts you need chapter three to remember.

How detailed should a story bible be?

If you do not use a note while drafting or revising, it probably does not need to be in the active bible yet. Keep the archive elsewhere and keep the working bible current.

How often should I update my story bible?

Update it after a chapter changes the story state. You do not need to summarize every scene; record new knowledge, relationship shifts, injuries, objects, deadlines, clues, and promises that later chapters must honor.

Can I use a story bible with AI writing tools?

Yes. Keep the full story bible as your reference, then create a short context pack for each chapter or scene: current goal, relationship tension, relevant rule, recent change, and anything the AI must not reveal yet.

📝 Final Thought

A story bible is not proof that you planned perfectly. It keeps the story honest while it changes. Start with the smallest useful version: premise and reader promise, style notes, current cast or relationship state, world rule limits, open threads, and chapter state changes. That is enough to make the next scene less fragile—and enough to keep the reference alive instead of abandoned.