How to Use a Story Bible for Fiction Writing

A story bible is a central reference document that keeps characters, timelines, locations, world rules, relationships and plot facts consistent throughout a novel or series. It gives the writer one reliable place to check what has already been established before planning a new chapter or revising an existing scene.

This becomes especially important when writing with AI. An AI tool may help generate character profiles, chapter plans and scene drafts, but it does not automatically remember every detail from a long project. Without an updated reference document, ages may change, injuries may disappear, characters may know information they never learned and invented rules may contradict earlier chapters.

This guide explains how to use a story bible from the first idea to the final continuity review. You will learn what to include, how to organize the information, when to update it and how to provide the right context when working in AI Story Studio.

What Is a Story Bible?

A story bible is a structured collection of facts about a fictional project. It may be a document, spreadsheet, database, notebook or collection of connected files.

Its purpose is not to contain every sentence of the manuscript. It should preserve the information needed to understand and maintain the story.

A basic story bible may include:

• the premise,
• genre and tone,
• theme,
• character profiles,
• relationships,
• worldbuilding rules,
• important locations,
• the story timeline,
• the main plot outline,
• chapter summaries,
• continuity notes,
• unresolved questions,
• style guidelines.

A useful principle is:

The manuscript contains the story.

The story bible contains the facts needed to keep that story consistent.

Why Writers Need a Story Bible

Long-form fiction creates hundreds of details. Even a relatively simple novel may include several timelines, changing relationships, hidden information, recurring objects and events remembered differently by different characters.

Without a central reference, common problems include:

• changing character ages,
• contradictory physical descriptions,
• impossible travel times,
• forgotten injuries,
• objects appearing in the wrong location,
• characters knowing secrets too early,
• world rules changing to solve a scene,
• repeated discoveries,
• unresolved promises,
• subplots disappearing without explanation.

A story bible does not prevent every mistake, but it makes inconsistencies easier to detect and correct.

Why a Story Bible Matters When Writing with AI

AI works best when it receives clear, relevant and current context. If you ask it to write a chapter without providing the necessary facts, it may fill the gaps with plausible but incorrect details.

For example:

Established fact:
Mara broke her left wrist in Chapter 6 and cannot use it normally for three weeks.

Prompt without continuity context:
Write a scene in which Mara climbs through a maintenance shaft.

Possible inconsistency:
The generated scene shows her pulling her full body weight with both hands.

Improved context:
Mara’s left wrist is in a rigid brace. She cannot grip or support weight with that hand. The scene must account for this limitation.

The story bible gives you the information required to create better prompts and evaluate generated text.

Story Bible, Outline and Continuity Tracker

These tools overlap, but they perform different jobs.

Story bible

Stores the major facts and rules of the project.

Plot outline

Explains what is planned to happen and why.

Continuity tracker

Records changes that occur while the story is being written.

Chapter summaries

Describe what actually happened in completed chapters.

They can be maintained separately or as sections of one larger system.

Story-bible fact:
Daniel has never met Elian before the story begins.

Outline plan:
Daniel confronts Elian in Chapter 18.

Chapter-summary update:
Daniel first sees Elian during the council hearing in Chapter 11 but does not speak to him.

Continuity note:
The Chapter 18 confrontation is their first direct conversation, not their first sight of each other.

1. Begin with the Core Story Brief

The first section should summarize the project in a compact form.

Include:

• working title,
• genre,
• target audience,
• tone,
• premise,
• central conflict,
• main thematic question,
• planned ending,
• approximate length.

Example:

Working title:
The Erased Archive

Genre:
Science-fiction mystery thriller

Tone:
Restrained, tense, investigative and emotionally intimate

Premise:
In a city where legal identity can be edited, archivist Mara Vale discovers that her missing brother was deliberately removed from public records.

Central conflict:
Mara must expose the archive without revealing protected witnesses whose lives depend on secrecy.

Thematic question:
When does protection become control?

Planned ending:
Mara transfers authority over each identity record to the person it belongs to.

Approximate length:
90,000 words

This brief helps AI understand the overall direction before generating detailed material.

2. Record the Story’s Non-Negotiable Elements

Some ideas define the identity of the project and should not change accidentally.

These may include:

• the central dilemma,
• the planned ending,
• the protagonist’s primary motivation,
• a crucial world rule,
• the identity of the antagonist,
• the intended narrative perspective,
• the emotional tone.

Non-negotiable elements:
- Mara’s brother chose to enter the identity-removal system.
- Mara does not receive a complete explanation from him.
- The archive protects real people as well as enabling abuse.
- Elian sincerely believes centralized control prevents harm.
- The final solution must preserve personal choice.
- The novel uses close third-person narration.

Marking these elements prevents later suggestions from quietly changing the entire story.

3. Create Detailed Character Profiles

Each important character should have a practical profile containing facts that influence the story.

Useful fields include:

• full name,
• age,
• role,
• physical description,
• personality,
• external goal,
• motivation,
• fear,
• internal need,
• protective strategy,
• skills,
• limitations,
• important relationships,
• secrets,
• speech habits,
• planned development.

Example:

Name:
Mara Vale

Age:
Thirty-four

Role:
Senior municipal archivist and protagonist

Physical description:
Short dark hair, grey eyes, narrow scar below the right jaw, formal clothing in muted colors

External goal:
Recover the original identity record of her missing brother

Motivation:
Prove that he did not abandon the family without explanation

Fear:
Trusting another person will cause another irreversible loss

Internal need:
Accept that protecting people does not give her the right to decide for them

Protective strategy:
Limits information and completes important tasks alone

Skills:
Archival law, pattern recognition, procedural knowledge and careful planning

Limitations:
Poor improvisation under emotional pressure, damaged left wrist after Chapter 6

Speech style:
Precise, restrained and reluctant to answer personal questions

Development:
Moves from controlling information to respecting informed choice

4. Separate Stable Facts from Changing Facts

Some character information remains stable. Other information changes throughout the story.

Stable facts

• date of birth,
• family history,
• basic appearance,
• education,
• established skills,
• events that happened before the novel.

Changing facts

• injuries,
• current location,
• knowledge,
• alliances,
• emotional state,
• public status,
• access to resources,
• beliefs affected by the plot.

Do not overwrite a changing fact without recording when and why it changed.

Stable fact:
Daniel is an encryption specialist.

Changing fact:
He loses legal access to government networks in Chapter 10.

Later update:
He regains limited access under witness supervision in Chapter 23.

5. Build a Relationship Map

A relationship section should explain more than whether two characters are friends or enemies.

Track:

• shared history,
• what each person wants from the other,
• trust level,
• power balance,
• shared values,
• conflicting values,
• secrets,
• boundaries,
• important turning points,
• final relationship state.

Relationship:
Mara and Daniel

Starting connection:
Former colleagues with strong professional respect

Mara wants:
Technical help without surrendering control

Daniel wants:
Complete information about his daughter

Shared value:
Protecting vulnerable people

Conflict:
Privacy versus transparency

Starting trust:
High practical trust, low emotional trust

Power balance:
Mara controls institutional access. Daniel controls the decoding technology.

Major change:
Daniel publishes a protected record without permission.

Repair:
He returns the remaining data and accepts new conditions.

Final state:
Equal partners who still disagree about public disclosure

Use the guide How to Build Relationships Between Characters to develop connections that influence the plot.

6. Document the World Rules

World rules explain what is possible, impossible, legal, dangerous or culturally accepted.

Depending on the genre, track:

• political systems,
• social hierarchy,
• technology,
• magic,
• religion,
• economics,
• communication,
• transportation,
• law,
• education,
• medicine,
• customs and taboos.

A good rule should include consequences and limits.

Weak rule:

Identity records can be changed.

Stronger rule:

Legal identity records can be amended only by certified archivists using two independent authorization keys.

An emergency deletion removes public access but preserves a sealed internal copy.

Restoring a deleted identity requires the original biometric signature or a court order.

Illegal restoration creates an automatic security report.

Specific rules create usable conflict and prevent convenient solutions.

7. Record the Limits of Technology or Magic

Restrictions are as important as abilities.

Archive technology can:
- alter public identity records,
- create protected aliases,
- hide a person from ordinary searches,
- record every authorized change.

Archive technology cannot:
- erase private memories,
- change physical evidence,
- remove unofficial copies,
- restore a record without authorization,
- identify why a legal request was submitted.

When AI suggests a solution, compare it against these limits before accepting it.

8. Create Location Profiles

Important locations should have stable physical and functional details.

Include:

• name,
• purpose,
• layout,
• atmosphere,
• entrances and exits,
• security,
• distance from other places,
• important objects,
• events that occurred there.

Location:
Central Identity Archive

Purpose:
Stores current, historical and protected identity records

Layout:
Public reading room above three restricted storage levels

Main access:
Street entrance, staff elevator and maintenance tunnel

Security:
Biometric doors, rotating access codes and automatic request logging

Important areas:
Public terminal hall, legal records chamber, witness vault and authorization room

Travel time:
Twenty minutes from Mara’s apartment by tram

Continuity note:
The maintenance tunnel can be entered only from the western service yard.

A location profile prevents rooms, distances and security systems from changing between scenes.

9. Build a Master Timeline

The timeline should show when major events occur before and during the novel.

Track:

• dates,
• time of day,
• event duration,
• travel time,
• deadlines,
• character ages,
• historical events,
• overlapping scenes.

Five years before the novel:
Mara and Daniel recover records after the archive fire.

Fourteen months before the novel:
Mara’s brother disappears.

Day 1, 08:20:
Mara finds the damaged identity request.

Day 1, 19:00:
Daniel begins decoding the record.

Day 2, 01:15:
The unauthorized request triggers an alert.

Day 2, 09:00:
Elian opens an internal investigation.

Day 3:
Mara’s access is suspended.

A timeline is especially important in mysteries, thrillers and stories with several viewpoint characters.

10. Track Character Knowledge

A character should not react to information they have not received.

Create a knowledge table or list showing:

• the fact,
• who knows it,
• how they learned it,
• when they learned it,
• what they believe it means,
• whether their interpretation is correct.

Fact:
Lena is inside the witness-protection archive.

Mara:
Learns this in Chapter 7 by reading the sealed index.

Daniel:
Learns this in Chapter 8 when Mara confirms the name.

Elian:
Already knows because he approved the protection request.

The reader:
Sees the name when Mara opens the index.

Incorrect interpretation:
Daniel assumes Lena was forced into the system.

Later correction:
Lena entered voluntarily but did not understand the permanent restrictions.

11. Track Secrets Separately

Secrets affect suspense, motivation and relationships. Record who knows each secret and what would happen if it were revealed.

Secret:
Daniel copied the archive access key.

Known by:
Daniel and the reader

Hidden from:
Mara and Elian

Reason for secrecy:
Daniel wants independent access to Lena’s file.

Potential consequence:
The copied key allows Elian to trace the investigation to Daniel.

Planned revelation:
Mara discovers the copy after the witness location is exposed.

This prevents secrets from being forgotten or exposed without consequences.

12. Record Important Objects

Recurring objects often create continuity problems.

Track:

• description,
• owner,
• current location,
• condition,
• special function,
• who has handled it,
• when it changes hands.

Object:
Western archive access key

Initial owner:
Mara

Chapter 8:
Mara gives it to Daniel temporarily.

Chapter 9:
Daniel copies the key and returns the original.

Chapter 13:
The original is confiscated during Mara’s suspension.

Chapter 24:
The copied version becomes the only remaining way to enter the western terminal.

13. Maintain a Plot Overview

The story bible should include the current version of the main plot.

Record:

• opening situation,
• inciting event,
• first commitment,
• early progress,
• midpoint,
• major setback,
• climactic choice,
• resolution.

Opening:
Mara discovers a damaged identity request signed by her missing brother.

Commitment:
She steals an authorization key and asks Daniel to decode the request.

Early progress:
They prove that protected records were deliberately altered.

Midpoint:
Mara learns that her brother requested his own removal.

Major setback:
Her secrecy causes Daniel to act on incomplete information, exposing witnesses.

Climax:
Mara must choose who will control the archive.

Resolution:
She transfers each record to its owner and accepts that some answers will remain hidden.

Update this section when structural changes are approved.

14. Add Chapter Summaries

After drafting a chapter, create a short factual summary of what actually happened.

A useful summary contains:

• viewpoint,
• location and time,
• goal,
• main events,
• decision,
• consequence,
• new information,
• relationship changes,
• continuity updates.

Chapter 8 summary

Viewpoint:
Mara

Location:
Daniel’s workshop

Goal:
Convince Daniel to decode the protected index

Events:
Daniel refuses until Mara discusses Lena. Mara confirms that Lena appears in the archive but withholds the record number.

Decision:
Mara chooses partial disclosure.

Consequence:
Daniel agrees to help but secretly copies the access key.

New information:
Lena entered the archive under voluntary-protection status.

Relationship change:
Practical cooperation continues. Emotional trust decreases.

Continuity:
Daniel now possesses a copied western access key.

Chapter summaries are easier to provide to AI than entire manuscripts.

15. Separate Planned Events from Completed Events

A planned outline may change during drafting. Do not treat a future idea as something that has already happened.

Use clear labels:

PLANNED:
Daniel will confront Elian during the council hearing.

DRAFTED:
Daniel attends the hearing but does not speak.

REVISED PLAN:
Their first direct confrontation moves to Chapter 18.

CONFIRMED CANON:
Daniel sees Elian for the first time in Chapter 11 and speaks to him for the first time in Chapter 18.

This distinction prevents outdated plans from conflicting with the manuscript.

16. Mark Canon Status

Not every idea in the story bible needs to be final.

Use statuses such as:

• confirmed,
• drafted,
• planned,
• possible,
• rejected,
• needs research.

Confirmed:
Mara’s brother entered the archive voluntarily.

Possible:
He entered to protect Mara from an investigation.

Rejected:
Elian secretly replaced Mara’s brother.

Needs research:
Legal procedures for restoring an erased civil identity.

This helps you avoid treating brainstorming material as established fact.

17. Track Open Questions

A story bible should also record what has not been decided.

Open questions:
- Why did Mara’s brother believe disappearing was necessary?
- Who first gave Elian emergency authority?
- What evidence proves the archive manipulated consent?
- Which witness chooses public disclosure?
- What professional consequences will Mara face after the climax?

Open questions guide future planning and prevent important problems from being forgotten.

18. Keep a Decision Log

When you make a major creative decision, record why.

Decision:
The brother entered the archive voluntarily.

Reason:
This makes Mara confront the difference between love and control.

Rejected alternative:
Elian erased him without consent.

Reason for rejection:
That version makes the moral conflict too simple and removes the brother’s agency.

A decision log is useful when revisiting the project after a long break or considering major revisions.

19. Add a Style Guide

The story bible can preserve narrative consistency as well as factual continuity.

Include:

• point of view,
• tense,
• narrative distance,
• sentence rhythm,
• description level,
• dialogue approach,
• humor level,
• metaphor preferences,
• words or habits to avoid.

Point of view:
Close third person limited to the current chapter character

Tense:
Past

Tone:
Restrained, tense and observant

Description:
Specific sensory details connected to the viewpoint character’s profession

Dialogue:
Concise, goal-driven and dependent on subtext

Avoid:
Excessive rhetorical questions, generic emotional labels, repeated descriptions of breathing and dramatic summaries of obvious feelings

20. Create a Character Voice Guide

Important characters should not sound interchangeable.

Mara:
Precise vocabulary, short answers, avoids emotional labels, corrects inaccurate terminology

Daniel:
Uses humor under moderate pressure, asks direct personal questions, becomes formal when angry

Elian:
Calm and courteous, reframes threats as administrative necessity, rarely raises his voice

Lena:
Speaks concretely, rejects euphemisms, frequently asks who has the authority to decide

Provide the relevant voice notes when asking AI to draft dialogue.

21. Include Research Notes Carefully

Separate verified facts from unconfirmed AI suggestions.

A useful format is:

Research topic:
Legal identity restoration

Verified information:
[Add confirmed notes and sources.]

Unverified possibility:
A court may issue a temporary identity order.

Questions to confirm:
- Which authority could issue the order?
- What evidence would be required?
- Would the process be public?

Do not add an AI-generated factual claim to the confirmed section until it has been checked.

22. Create Genre-Specific Sections

Different genres require different continuity systems.

Mystery

• clues,
• suspects,
• alibis,
• false interpretations,
• investigator knowledge,
• reveal order.

Fantasy

• magic rules,
• cultures,
• political factions,
• geography,
• languages,
• travel time,
• historical events.

Science fiction

• technology limits,
• scientific assumptions,
• social consequences,
• terminology,
• political systems,
• communication delays.

Romance

• relationship stages,
• trust,
• boundaries,
• important disclosures,
• independent goals,
• emotional turning points.

Thriller

• deadlines,
• antagonist activity,
• resources,
• surveillance,
• travel,
• escalation,
• information exposure.

23. Keep the Story Bible Searchable

A large reference document becomes less useful when information is difficult to find.

Use:

• clear headings,
• consistent character names,
• dates in one format,
• short factual entries,
• tables or lists for recurring data,
• links between related sections,
• tags or labels for status.

Avoid hiding important facts inside long paragraphs.

24. Use Version Control

Major revisions may make old information incorrect. Keep a record of significant versions.

Version 1:
Mara’s brother was erased without consent.

Version 2:
He entered the archive voluntarily to protect Mara.

Current version:
He entered voluntarily but received incomplete information about the consequences.

Mark the current version clearly and archive outdated material instead of leaving contradictory notes together.

25. Update the Story Bible After Every Chapter

Do not wait until the end of the novel.

After drafting a chapter, update:

• the timeline,
• character locations,
• knowledge,
• injuries,
• relationships,
• object ownership,
• promises,
• secrets,
• open questions,
• the chapter summary.

A short update after every chapter is easier than reconstructing the entire novel later.

26. Provide Only Relevant Story-Bible Context to AI

More context is not always better. Sending the entire story bible for every task can distract the model from the current scene.

For a dialogue scene, provide:

• the two character profiles,
• their relationship status,
• current goals,
• relevant secrets,
• voice notes,
• the immediate situation.

For a continuity check, provide:

• the timeline,
• chapter summaries,
• character knowledge,
• object tracking,
• world rules.

For a chapter plan, provide:

• the current plot position,
• the previous chapter summary,
• required future events,
• character goals,
• subplots,
• continuity constraints.

27. Use a Context Packet for Each Scene

A context packet is a compact selection from the story bible prepared for one task.

SCENE CONTEXT

Viewpoint:
Mara

Location:
Daniel’s workshop, Day 2 at 19:00

Immediate goal:
Convince Daniel to decode the witness list

Relevant character facts:
Mara avoids personal disclosure and currently has a damaged left wrist.

Relationship status:
High professional trust, low emotional trust.

Daniel knows:
Mara found a protected family record.

Daniel does not know:
Lena’s name appears in the archive.

Required event:
Mara confirms Lena’s presence but hides the document number.

Continuity:
Daniel must copy the western access key before the scene ends.

Style:
Close third-person past tense, restrained prose, no access to Daniel’s private thoughts.

This gives AI the information needed without overwhelming the task.

28. Ask AI to Identify Missing Information

Before generating a chapter or scene, ask what information is absent.

Review this context packet before writing.

List any missing facts that could affect:
- character motivation,
- continuity,
- setting,
- timeline,
- relationship logic,
- point of view,
- the required ending.

Do not draft the scene yet.

This can reveal gaps before they become inconsistencies.

29. Use the Story Bible for Revision

The reference document is valuable after drafting as well as before it.

During revision, compare the manuscript against:

• character motivations,
• world rules,
• timeline,
• knowledge states,
• relationship development,
• object locations,
• planned themes,
• unresolved questions.

Mark whether the manuscript or the bible should change. The reference document is a tool, not a law. A stronger scene may justify revising an earlier plan.

30. Archive Outdated Information

Deleting old ideas completely can make later decisions difficult to understand. Move them to an archive section instead.

ARCHIVED IDEA

Old plan:
Elian is secretly responsible for the brother’s disappearance.

Reason removed:
It reduces the brother’s agency and simplifies the thematic conflict.

Possible reuse:
Elian may have concealed the long-term consequences without forcing the original decision.

This keeps the active story bible clean while preserving useful development history.

Complete Story Bible Example

Project overview

Title:
The Erased Archive

Genre:
Science-fiction mystery thriller

Premise:
An archivist discovers that her missing brother entered a system capable of removing legal identity.

Central conflict:
Exposing the archive may endanger the witnesses it protects.

Theme:
Protection, consent and control

Narration:
Close third person with Mara as the primary viewpoint

Ending:
Each person receives authority over their own record.

Protagonist

Name:
Mara Vale

Goal:
Recover her brother’s original record

Motivation:
Understand why he disappeared

Fear:
Trust will lead to another loss

Protective strategy:
Controls information

Internal need:
Respect other people’s choices

Current status after Chapter 8:
Suspicion from archive security, damaged left wrist, reduced trust with Daniel

Antagonist

Name:
Elian Voss

Role:
Director of the Central Identity Archive

Goal:
Obtain permanent authority over protected identity records

Worldview:
Dangerous information must be controlled by responsible institutions

Advantage:
Legal authority, institutional access and public credibility

Blind spot:
He assumes independent choice always creates chaos

World rule

Identity deletion:
Removes public records but preserves a sealed internal copy.

Required authorization:
Two certified keys and a verified biometric signature.

Restoration:
Requires the original signature or a court order.

Automatic consequence:
Every unauthorized restoration attempt creates a security report.

Current timeline

Day 1:
Mara finds the damaged request and contacts Daniel.

Day 2:
They decode the protected index and trigger a security alert.

Day 3:
Mara is suspended.

Day 4:
Daniel begins an independent search.

Day 5:
The first protected witness is exposed.

Open questions

- Why did the brother choose removal?
- What information did Elian hide from him?
- Which witness will agree to testify?
- How will Mara obtain the second authorization key?
- What will happen to the archive after control is transferred?

Why this story bible works

It stores stable facts, current changes, world rules, plot direction and unresolved questions. It is compact enough to use during planning but detailed enough to prevent major contradictions.

Universal Prompt for Creating a Story Bible

Create a complete story bible for this fiction project:

Working title:
[Insert title.]

Premise:
[Insert premise.]

Genre and tone:
[Insert genre and tone.]

Target length:
[Insert length.]

Current outline:
[Insert outline.]

Characters:
[Insert available character information.]

Develop:
1. A concise project overview.
2. The central external conflict.
3. The central internal conflict.
4. The main thematic question.
5. Non-negotiable story elements.
6. Detailed profiles for all major characters.
7. Stable and changing facts for each character.
8. A relationship map.
9. World rules and limitations.
10. Important location profiles.
11. A master timeline.
12. Character-knowledge tracking.
13. A secrets tracker.
14. Important-object tracking.
15. The main plot overview.
16. Subplot summaries.
17. Planned chapter turning points.
18. Open questions.
19. A decision log.
20. A style and character-voice guide.
21. Research topics requiring verification.
22. A list of continuity facts to update after every chapter.

Separate confirmed facts, planned ideas, possible ideas and unresolved questions. Do not invent facts that contradict the supplied material.

Prompt for Creating Character Entries

Create story-bible entries for these characters:

[Insert character information.]

For each character provide:
- full name,
- age,
- role,
- physical description,
- personality,
- external goal,
- motivation,
- fear,
- internal need,
- protective strategy,
- skills,
- limitations,
- important relationships,
- secrets,
- speech habits,
- planned development,
- stable facts,
- changing facts,
- current status.

Flag missing information instead of inventing essential facts without explanation.

Prompt for Building a World-Rules Section

Create a structured world-rules section for this story:

Premise:
[Insert premise.]

Genre:
[Insert genre.]

Existing world information:
[Insert notes.]

Organize:
- government,
- law,
- social structure,
- technology or magic,
- communication,
- transportation,
- economy,
- medicine,
- education,
- religion,
- customs,
- important historical events.

For every important system explain:
1. What it can do.
2. What it cannot do.
3. Who controls it.
4. What it costs.
5. What consequences follow misuse.
6. How it affects ordinary people.
7. How it influences the main plot.

Identify contradictions and unanswered questions.

Prompt for Creating a Timeline

Create a master timeline from these notes and chapter summaries:

[Insert material.]

For every event provide:
- date,
- time if known,
- location,
- characters present,
- duration,
- cause,
- consequence,
- related secrets,
- continuity notes.

Separate:
- historical events,
- events before the novel,
- current-story events,
- planned future events.

Flag impossible timing, inconsistent ages, unrealistic travel and overlapping events involving the same character.

Prompt for Tracking Character Knowledge

Create a character-knowledge tracker:

Story facts and secrets:
[Insert facts.]

Chapter summaries:
[Insert summaries.]

For every important fact track:
- which characters know it,
- how they learned it,
- when they learned it,
- what they believe it means,
- whether their interpretation is correct,
- who is deliberately hiding it,
- when it should be revealed.

Flag scenes where a character appears to know information they never received.

Prompt for Updating a Story Bible After a Chapter

Update the story bible after this chapter:

Current story-bible information:
[Insert relevant sections.]

New chapter:
[Insert chapter or detailed summary.]

Update:
- timeline,
- character locations,
- injuries and physical condition,
- knowledge,
- secrets,
- relationships,
- promises,
- object ownership,
- world rules used,
- subplot progress,
- unresolved questions,
- character development,
- chapter summary.

Separate new confirmed facts from interpretations and possible future developments. Flag contradictions with earlier canon.

Prompt for Creating a Scene Context Packet

Create a compact scene context packet from this story bible:

Story-bible material:
[Insert relevant sections.]

Planned scene:
[Insert scene plan.]

Include only:
- viewpoint,
- time and location,
- immediate goal,
- obstacle,
- relevant character facts,
- relationship status,
- current knowledge,
- secrets affecting the scene,
- world rules used,
- continuity constraints,
- required event,
- required ending,
- style requirements,
- information that must remain hidden.

Keep the packet concise enough to use in a scene-drafting prompt.

Prompt for Auditing a Story Bible

Perform a complete story-bible audit:

[Insert story bible.]

Check:
1. Project overview.
2. Character facts.
3. Character development.
4. Relationships.
5. World rules.
6. Locations.
7. Timeline.
8. Character knowledge.
9. Secrets.
10. Important objects.
11. Plot structure.
12. Subplots.
13. Chapter summaries.
14. Open questions.
15. Style guide.
16. Canon status.

Flag:
- contradictions,
- duplicate entries,
- outdated plans,
- missing motivations,
- impossible timing,
- changing world rules,
- characters knowing information too early,
- unresolved objects or promises,
- subplots without conclusions,
- planned events treated as completed,
- unverified research presented as fact.

Rank the problems and recommend the smallest effective corrections.

Prompt for Checking a Manuscript Against the Story Bible

Compare this manuscript section against the story bible:

Story bible:
[Insert relevant material.]

Manuscript section:
[Insert text.]

Check:
- character appearance,
- age,
- injuries,
- goals,
- motivation,
- voice,
- relationship status,
- current knowledge,
- location,
- timeline,
- important objects,
- world rules,
- point of view,
- unresolved promises.

List every confirmed inconsistency. Distinguish factual contradictions from creative choices that may simply require updating the story bible.

Practical Workflow for Using a Story Bible

Stage 1: create the project overview

Record the premise, genre, theme, conflict and planned ending.

Stage 2: build character and relationship profiles

Document goals, fears, limitations, secrets and changing connections.

Stage 3: define world rules and locations

Explain limits, costs and practical consequences.

Stage 4: create the timeline

Track historical events, current events and deadlines.

Stage 5: add the plot outline

Record the major structural turns and planned subplots.

Stage 6: begin drafting

Create compact context packets for individual chapters and scenes.

Stage 7: update after every chapter

Add factual summaries and record all important changes.

Stage 8: mark canon status

Separate confirmed material from plans, possibilities and rejected ideas.

Stage 9: run regular continuity checks

Compare new chapters against the current reference.

Stage 10: revise the bible with the manuscript

When a creative change improves the story, update the active canon.

Common Story-Bible Mistakes

Recording too much irrelevant detail

Prioritize information that affects character, plot, setting, continuity or tone.

Failing to update the document

An outdated story bible can create more confusion than no story bible at all.

Mixing confirmed facts with possible ideas

Use clear canon labels.

Keeping planned events after the manuscript changes

Update or archive old versions.

Writing long paragraphs that are difficult to search

Use short entries, headings, tables and consistent labels.

Sending the entire story bible for every AI task

Create a focused context packet containing only relevant information.

Allowing AI to invent missing canon silently

Ask it to identify missing information before drafting.

Ignoring character knowledge

Track who knows each important fact and when they learned it.

Forgetting objects, injuries and promises

Maintain separate changing-fact trackers.

Treating the story bible as unchangeable

Update it when the manuscript discovers a stronger direction.

How Story Bibles Change Across Project Types

Standalone novel

Focus on current continuity, the complete plot, character development and the final resolution.

Novel series

Add long-term development, recurring locations, historical events, unresolved series questions and changes between books.

Shared fictional universe

Track canon ownership, overlapping timelines, shared rules, recurring organizations and contradictions between projects.

Multiple-viewpoint novel

Emphasize chronology, location, character knowledge and distinct narrative voices.

Mystery series

Separate case-specific clues from permanent character and setting information.

Fantasy series

Expand geography, history, cultures, political factions, languages and magic-system development.

Connect the Story Bible to Other Writing Skills

Use How to Write a Novel with AI to integrate your story bible into the complete writing process.

Use How to Plan Chapters with AI to turn your structural notes into a chapter-by-chapter roadmap.

Use How to Create Fictional Characters with AI to develop consistent character profiles.

Use How to Build Relationships Between Characters to track trust, power, conflict and relationship turning points.

Use a Story Bible in AI Story Studio

Before working in AI Story Studio, prepare a compact version of your story bible.

Begin with:

• the premise,
• genre and tone,
• main characters,
• central conflict,
• world rules,
• major plot points,
• planned ending,
• current timeline,
• important continuity facts,
• style requirements.

For each task, provide only the relevant sections. After generating or revising a chapter, update the reference with confirmed changes before moving forward.

Story Bible Checklist

• Does the project overview match the current story?
• Are non-negotiable elements clearly marked?
• Does every important character have a complete profile?
• Are stable and changing facts separated?
• Are relationships tracked through goals, trust and conflict?
• Are world rules specific and limited?
• Do locations have consistent layouts and travel times?
• Is the timeline current?
• Is character knowledge tracked?
• Are secrets assigned to the correct characters?
• Are important objects and injuries monitored?
• Does the plot overview match the latest outline?
• Are completed chapters summarized?
• Are planned and completed events separated?
• Is canon status clear?
• Are open questions recorded?
• Does the style guide describe the intended voice?
• Are research notes marked as verified or unverified?
• Are outdated versions archived?
• Is the story bible updated after every chapter?

Frequently Asked Questions

What is a story bible?

It is a central reference containing the important facts, rules, characters, relationships, timeline and continuity information for a fictional project.

When should I create a story bible?

You can begin during early planning and expand it as the project develops. It does not need to be complete before drafting starts.

How detailed should a story bible be?

It should contain enough detail to answer important continuity questions without becoming a copy of the entire manuscript.

Should chapter summaries be included?

Yes. Short factual summaries make it easier to track what actually happened and provide accurate context to AI.

How often should it be updated?

Update it after every completed chapter and after every major structural decision.

Can the story bible change?

Yes. It should reflect the strongest current version of the story. Archive outdated information instead of mixing it with active canon.

What is the difference between a story bible and an outline?

An outline describes planned events. A story bible stores the wider system of characters, rules, relationships, timelines and confirmed facts.

Can AI create a story bible?

AI can organize supplied information, identify missing fields and create a useful structure, but the writer must approve facts and resolve contradictions.

Should I give AI the entire story bible?

Usually not. Provide a focused context packet containing only the sections relevant to the current task.

How does a story bible help revision?

It provides a reference for checking character behavior, world rules, timelines, knowledge, objects, relationships and unresolved promises.

Final Thoughts

Learning how to use a story bible means creating a reliable source of truth for a growing fictional project. The document should preserve important facts without becoming so large and disorganized that it is difficult to use.

Begin with the premise, characters, relationships, world rules and major plot points. Add a timeline, knowledge tracker, chapter summaries and continuity notes as the manuscript develops. Clearly separate confirmed canon from plans, possibilities and rejected ideas.

When working with AI, create a focused context packet for each task and update the story bible after every important change. Open AI Story Studio, organize your project and give every new chapter a consistent foundation.