Static Facts, Changing Stories: How to Keep Your Story Bible Useful
August 2026 · By Derrick Houger
Tell me if this problem is familiar: You are making progress on your draft when you realize you need to flesh out some history relevant to one of your characters. You pause where you are, open your favorite story bible or character-building workspace, and jot down the details you have just worked out.
Sometimes you are deciding basic reference facts about them: their birthday, birthplace, family relationships, or the name of their first pet. Other details may be less static, such as their favorite food, the person they are dating at the beginning of the story, or the reason they dislike one of their classmates.
Or maybe you write out a longer piece of their history, like the story of how they had their first kiss on the banks of the Potomac after sneaking away from their friends with their crush.
After recording those details, you return to your manuscript. It is a good system, and it provides a useful record of your thinking about the character.
When you begin writing, you probably have some picture of who your character is as a person. Maybe you have already written a detailed history for them. Or maybe you are letting their history and personality develop as you write.
If you design a character before drafting and follow that plan closely, their profile can remain a durable source of truth. But if you write like me, you get to know your characters through the process of writing them. Who they are near the end of a draft may be drastically different from who they were at the beginning.
Some of that difference is character development inside the story. Some of it comes from discovering that your original idea of the character no longer works and revising it.
That creates an interesting set of problems when static information in a document is connected to a changing story. A traditional character profile is being asked to answer several questions at once:
- What is canonically true about this person?
- What happened to them in the past?
- What is true about them at this particular point in the manuscript?
- What did I once plan to be true before changing my mind?
Why Character Profiles Contradict Themselves
Character sheets almost inevitably contain a mixture of reference facts and mutable properties.
I suspect many authors design their characters, either formally or informally, around the state in which they enter the narrative. They may also have some broad plans for how those characters will develop over the course of the manuscript.
That works until the profile begins accumulating facts that are all true, but at different points in the story.
Say a character begins the story with a close friend whom they trust completely. During the story, that friend betrays them in some substantive way and destroys that trust. Later in the manuscript, the two reconcile and begin repairing the relationship.
That short outline could imply dozens of changing states, both internal and external to the characters. What they believe about each other changes. What they know changes. Their willingness to speak honestly changes. Even the meaning of an otherwise ordinary interaction may depend on whether it happens before the betrayal, during the estrangement, or after the reconciliation.
A character profile could accurately say that they trust their friend, distrust their friend, and have begun trusting their friend again. None of those statements is necessarily wrong. They only appear contradictory when they are flattened into one document without any indication of when each one is true.
Not Every Character Detail Relates to Time in the Same Way
There are four broad categories tied to the questions a traditional character sheet is asked to answer:
- Reference facts: Information treated as canonically true and not inherently tied to a particular scene.
- Historical events: Things that happened to the character at a particular point in their history.
- Changing story state: Information that is true during one part of the story but may change later.
- Replaced authorial decisions: Ideas that were once part of your plan but are no longer canon.
The first three categories can all remain true at the same time. They simply relate to the story differently. Replaced authorial decisions are something else. They reflect changes you made to the story rather than changes that happened inside it.
Say you have a simple fact about a character: Karina gets a slice of pizza every Tuesday after work.
Several events in your manuscript could change that routine:
- The pizza place closes.
- Karina develops lactose intolerance.
- A coworker she dislikes begins going to the same restaurant at the same time, so she starts avoiding it.
- She simply gets tired of pizza and decides that Tuesday is now cheesesteak night.
Any one of those events could end Karina’s routine. The fact that she used to stop for pizza every Tuesday remains part of her history, but it is no longer true after the scene in which the routine changes.
There is another possibility, though.
Suppose that while drafting, you decide Karina has always had a severe intolerance to dairy and would never have established a weekly pizza routine in the first place. You now need to revise the earlier scenes in which she gets pizza, along with any reference material built around that routine.
That is not a change in Karina’s story state. Karina did not stop eating pizza because something happened to her. You changed your mind about who Karina has always been.
The old routine is not an earlier stage of her character development. It is an abandoned authorial decision.
Decide What to Replace and What to Preserve
The distinction matters because not every change should be recorded in the same way.
If Karina stops eating pizza because the restaurant closes in Chapter 8, you probably want to preserve both states. Before Chapter 8, she has a weekly pizza routine. After Chapter 8, she does not.
If you decide during revision that the pizza routine never made sense for Karina, preserving it alongside her current profile may create more confusion than useful history. In that case, you should revise the profile and any affected scenes so that the current version of the character remains internally consistent.
You might still preserve a note explaining why you made the revision, especially if the decision affected several scenes. But the abandoned fact should not appear beside the current one as though both remain part of the story.
A useful question is:
Did this change happen to the character, or did I change my mind about the character?
If the change happened to the character, preserve the transition. If you changed your mind about the character, update the current canon and revise the affected material.
Give Changing Information a Location in the Story
Once you determine that something is a genuine change in story state, give it an anchor in the manuscript.
That anchor might be:
- A scene or chapter
- A date in the story’s timeline
- The passage in which the change occurs
- A brief description of the state before and after the change
The important thing is that the note gives you enough information to reconstruct what happened and why.
You may feel completely confident that you will remember why a relationship changed or why a character abandoned an old routine. Six months later, after adding more characters, moving scenes around, and revising several story threads, that confidence may be gone.
A reference back to the manuscript gives you somewhere authoritative to look. It also helps distinguish a deliberate change from an accidental contradiction.
A Simple System You Can Use in Any Writing Tool
One possible system for organizing a character might include:
- A reference profile containing current canon and basic details
- An event or history record for things that happened to the character
- A scene-linked change log for evolving story state
- An optional revision log for abandoned ideas worth remembering
You can build that system with separate documents, headings in one large document, a spreadsheet, index cards, or whatever other writing tool works for you. The particular tool matters less than separating information that serves different purposes.
The amount of structure should also depend on the character and the story.
A central character with a complicated emotional arc may need a detailed profile, a substantial history, and numerous scene-linked changes. In a romance-driven story, the relationship itself may deserve its own page or change log rather than being treated as a property belonging to either character individually.
A minor character may need only a few reference facts and no dedicated history at all.
The goal is not to create the same collection of documents for every person in the manuscript. It is to preserve enough context for each character that your notes continue helping rather than creating another source of confusion.
How Scriptri Separates These Kinds of Information
Scriptri approaches this problem by giving different kinds of information different places to live instead of asking one character profile to do everything.
Entity Profiles provide a place for structured reference facts about characters, locations, objects, and other important parts of a story. Lore Pages provide room for longer histories and worldbuilding material, while the Glossary can be used to define project-specific terms and connect them back to the manuscript.
Scriptri also brings together related information such as timeline events, locations, scene appearances, notes, and manuscript context. That makes it easier to find relevant material without forcing every detail into a single profile.
Topics and scene-linked state notes are intended for the more difficult problem of changing story state. They preserve the history of a thread while surfacing the most recent relevant information at a particular point in the manuscript. Instead of replacing an old relationship state, belief, or concern, you can record where it changed and still see how it developed.
These workflows are not rigid. A minor character may need nothing more than a simple profile. A central relationship might accumulate a long thread of changes across the manuscript. You can use the parts that serve your story and ignore the ones that do not.
The goal is not to make authors maintain more records. It is to prevent a record from becoming misleading because it treats one version of a character as though it were true everywhere in the story.
A useful story bible should not only tell you who a character is. It should help you understand who they are at this point in the story, and how they got there.
A story bible that keeps facts, history, and story state separate
Scriptri gives reference facts, longer history, and changing story state different places to live: Entity Profiles, Lore Pages, and scene-linked state notes. No account required, and your manuscript stays in your browser.
Try Scriptri freeAll articles