Story Bible Tracker for Complex Stories

A Story Bible tracker records what’s true in a fictional world — and a useful one verifies new writing against that record instead of trusting the writer to remember to check. PlotLens tracks your Story Bible by extracting it directly from the manuscript: characters, locations, events, objects, and world rules, each with a citation to the sentence that established it, checked in real time as you write.

PlotLens is purpose-built for Story Bible tracking. It doesn’t just store your world details — it checks them against your manuscript in real time. When your writing contradicts established facts, PlotLens flags it immediately with a citation to the original source. No more searching through notes to verify a detail you established three hundred pages ago.

What a Story Bible is, and why “tracking” is the wrong verb

The eye color you wrote in chapter four is canonical. The magic-system rule a character explains in chapter eleven is canonical. The fact that a town was destroyed in book one is canonical. Your Story Bible is the set of established facts that future scenes are accountable to — and the larger your story, the more of it there is.

“Tracking” is the word the market uses, but it’s slightly off. You don’t track a Story Bible — those facts already exist in the manuscript, by virtue of being in the text. What you do is query it (to remember what’s true), check new writing against it (to catch contradictions), and evolve it (when you intentionally change established facts in a retcon). The right verb depends on the moment in the workflow.

Tools that frame the job as “tracking” tend to be note-taking applications: a place to type the facts so you don’t forget them. The problem is the moment your manuscript changes, the notes are wrong. The bible is wrong. What’s true is whatever the text says, and any tool that lets the Story Bible drift away from the text is a tool you can’t fully trust.

How PlotLens approaches a Story Bible

PlotLens treats your manuscript as the source of truth. The Story Bible is derived from the text — entities extracted, attributes recorded, relationships mapped, timeline events placed, all with sentence-level citations back to the passage that established each fact. The bible isn’t a thing you maintain. It’s a view over your manuscript.

What you get:

• A queryable Story Bible. Search by character, by location, by event, by relationship. “What did I establish about the Hollow?” returns every passage that touched the location, with the canonical attributes consolidated and provenance to each. “Has Anna ever met Catherine?” returns the relationship graph and the scenes that established it.
• Real-time Manuscript Check. Write a new chapter and PlotLens compares every sentence against the Story Bible. Contradictions show up inline with citations to the earlier passage that established the conflicting fact.
• Time-indexed state. What was true at chapter twelve of book one is queryable independently of the current state. For serialized fiction this is non-negotiable — the reader’s experience depends on it.
• Character knowledge as a first-class concept. What each character has been told is tracked separately from what’s narratively true. A character lying in dialogue isn’t a contradiction. A character knowing something they haven’t been told is one. The belief-vs-fact model is what makes this tractable for the validator.
• Per-writer attribution. On team plans, every Story Bible change is recorded with the writer who made it. Useful for writers’ rooms where the room needs to know who introduced a rule and when.

The two workflows Story Bible tracking serves

The first is the reference workflow. You’re drafting chapter eighteen and you need to remember exactly what you said about the Order of the Wakeful Sky in chapter six of book one. Today that’s an exercise in searching your manuscript, scrolling, second-guessing, and sometimes giving up and guessing. With PlotLens, you type “Order of the Wakeful Sky” into Story Bible search, every passage that mentioned the order surfaces with the consolidated attributes (when founded, who leads it, what its rules are, who it’s antagonistic toward), and you can click any fact to land on the source sentence. The lookup that took ten minutes takes ten seconds.

The second is the enforcement workflow. You’re drafting chapter eighteen and you just wrote a sentence that contradicts something canonical without realizing it. The validator highlights the sentence with a citation to the conflicting passage. You see both side by side. You decide: fix the new sentence, accept the new state as a retcon, or mark the contradiction as deliberate (a character lying, an unreliable narrator, a misdirection). The error doesn’t ship.

Most writers describe a third workflow over time, which is the trust workflow: knowing that the system has your back means you can draft faster, take more risks with what you establish, and stop holding the entire manuscript in your head as a defense against contradiction. That’s the part that’s hardest to advertise but the most valuable in practice.

Story Bible tracking is the infrastructure of complex storytelling. If you write novels, screenplays, serialized TV, or game narrative, the same primitive applies: derive a Story Bible from the text, check new writing against it, evolve it deliberately. See pricing for tier details; compare PlotLens to World Anvil, Plottr, and Campfire for adjacent tools in the Story Bible category.