Halfway through writing your novel, you’re sitting with a scene where your protagonist returns to his childhood home. You want to describe the house: colours, the layout of the rooms, the smell. You remember mentioning this house somewhere earlier. But what exactly? And in which chapter?
You start searching. Half an hour later you have notes from three different scenes, each describing the house slightly differently. You decide to use the version from chapter 3 because it sounds best. But then you need to check whether the description in chapter 7 conflicts with that choice.
This is precisely the problem a Story Bible solves.
Where the term comes from and what it means
The term “story bible” (also series bible or show bible) comes from the television industry. Showrunners have been creating these documents for their productions for decades. Before a single episode is filmed, there exists a document describing all the characters, the world, the narrative rules and the tone.
Why? Because a TV series is a collective work. Dozens of writers, directors and actors must understand that world in the same way. The story bible is a reference point for everyone, regardless of when they joined the production.
In fiction writing, a story bible solves a slightly different problem. Not the problem of coordinating between many people, but the problem of coordinating between your current self and your self from six months ago — the one who wrote chapter 3 and knew everything about that house.
What a story bible should contain
Good story bibles differ between projects. A fantasy novel requires a different scope than a thriller set in contemporary life. But certain categories are useful in almost every case.
Character profiles. Not biographical essays, but current facts: what a character looks like, what they want in this story, what they know and don’t know at every point in the narrative, and what relationships they have with other characters. A character’s knowledge defines how they can behave. A character who in chapter 4 doesn’t know their brother is alive cannot behave as though they did.
Locations. Every important place should have a brief description: appearance, atmosphere, what is narratively significant about it. How long it takes to travel between two locations is also a fact that recurs and must stay consistent.
World rules. In fantasy this is obvious: how magic works, what the limits are, who can do what and why. But world rules exist in realistic prose too: how the company where the protagonist works operates, what the rules of their social environment are. Facts that, once established, must be consistently observed.
Threads. A list of active plot threads: which are open, which are closed, which are intentionally suspended. Without this list it’s easy to forget one or accidentally resolve it too early.
How to build a story bible while writing, not after
The most common mistake: a writer finishes a first draft and decides to “write the story bible before revisions.” This doesn’t work, because they’ve forgotten half the details and extracting them from the text is time-consuming.
A story bible only works when it’s updated in real time. Ideally after every writing session, or at the very least after every chapter.
A practical approach: don’t try to write it simultaneously with writing. Instead, after each chapter you write, spend fifteen minutes extracting the new facts from it and recording them. What new things did you learn about the world? What traits of a character were revealed? Did a new location appear? Did a thread open or close?
With this method the story bible grows organically alongside the text and is always current. The cost of maintaining it is spread across small portions rather than becoming one big task to do “someday.”
What this looks like in practice with long projects
For a novel over eighty thousand words, with a dozen or more characters and a developed world, a story bible can run to fifteen or more pages. It remains manageable.
Experienced writers often say that the story bible becomes more valuable than the text itself, because it contains knowledge that is compressed and easily searchable. Instead of hunting for the description of a house in three hundred pages of manuscript, you open the document and have it immediately.
How Vellam applies the same principle
A manual story bible works on one principle: every new scene is read with awareness of what came before. Vellam works the same way, just internally.
Each chapter is analysed with awareness of the previous ones: what is already known about the characters, which threads are open, what has happened. The feedback you receive is not a reaction to the current chapter in isolation from the rest, but a comment on the chapter as the next link in the whole text.
This doesn’t replace maintaining your own documentation if you like having full visibility into the state of your project. But if what you care about is having the analysis understand your novel rather than just a fragment of it, this is exactly where the difference comes from.
If you’re interested in maintaining consistency for specific characters within the text, read the article on character consistency in a novel. A story bible and character consistency tracking are two tools that work best together.