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 builds 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 when a clean span is available, and checks the writing you submit against the facts you accept.

PlotLens is purpose-built for Story Bible tracking. It doesn’t just store your world details — it checks them against your manuscript when you run a check. When your writing may contradict an accepted fact, PlotLens flags it with a citation to the original source when a clean span is available. 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, events listed by document, with citations back to the passage that established the fact when a clean span is available. You review and accept what it proposes; the bible is not a thing you type from scratch.

What you get:

• A queryable Story Bible. Search by character, by location, by event, by relationship. “What did I establish about the Hollow?” returns passages that touched the location, with the attributes the text states consolidated and provenance when a clean span is available. “Has Anna ever met Catherine?” returns the relationship graph and the scenes that established it.
• Manuscript Check. Run a check on a new chapter and PlotLens compares it with the facts you accepted. Possible contradictions show up with citations to the earlier passage that established the conflicting fact, when a clean span is available. Checks run from the Word add-in, from the Scrivener Companion app (beta), or on files you upload.
• Events by document. Events PlotLens finds are listed for the document they came from, and you can add or edit your own. The order within a document is not the order of the story, so story chronology is something you record.
• Character knowledge. When the text gives enough evidence, what each character has been told is kept separate from what’s narratively true. A character lying in dialogue isn’t a contradiction. A character knowing something they haven’t been told may be 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, passages that mentioned the order surface along with the attributes extraction found, and you can click a cited fact to land on the source sentence. The lookup gets shorter; check anything that matters against the passage itself.

The second is the enforcement workflow. You’re drafting chapter eighteen and you just wrote a sentence that contradicts something canonical without realizing it. A check you run flags the sentence with a citation to the conflicting passage when a clean span is available. You see both side by side. You decide: fix the new sentence, record the new state as a new version of the fact, or mark the contradiction as deliberate (a character lying, an unreliable narrator, a misdirection). Coverage depends on what extraction found, so a clean check is not a guarantee.

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, change it deliberately. See pricing for tier details; compare PlotLens to World Anvil, Plottr, and Campfire for adjacent tools in the Story Bible category.