Story Bible Software That Builds Itself

Story bible software keeps a structured record of a story’s established facts — characters, locations, timelines, relationships, and world rules — so a writer can verify any established fact without rereading the manuscript. PlotLens is story bible software that builds the bible itself: it reads your manuscript and proposes your Story Bible with a citation when a clean span is available. Re-run extraction on a new draft to refresh it.

Your Story Bible is the set of facts your story has established — what readers call canon.

Traditional story bible tools require you to manually enter every character, location, and plot point. PlotLens takes the opposite approach: it reads your manuscript and proposes the Story Bible from the text itself. What it finds depends on what the manuscript states, so review the result rather than treating it as complete.

What story bible software actually has to do

A story bible has one job: be the answer to “what’s true in this story, and where did we establish it?” Everything else — the categories, the templates, the tag taxonomies — is secondary. If the answer to that question lives in a tool, the tool is doing its job. If the answer lives partly in a spreadsheet, partly in a Scrivener folder, partly in a Notion page someone updated in 2023, the tool isn’t.

That sounds simple until you try it across a 400-page manuscript with 40 named characters, three timelines, and a magic system whose rules change between the prologue and chapter twenty. Most “story bible software” on the market is really form-builder software with a fiction-flavored template — fields for eye color, hometown, motivation. The fields are right. The problem is that you fill them in by hand, you forget half of them, and the moment your manuscript changes, the bible is wrong and you don’t know which entry to update.

The bible that stays accurate is the one that’s derived from the manuscript, not the one that’s maintained alongside it.

How PlotLens approaches story bible generation

PlotLens reads your manuscript — .docx, .pdf, .rtf, .odt, .md, .epub, .txt, and Final Draft .fdx or Fountain files — and extracts entities: characters with their aliases and traits, locations, events, objects, organizations, and concepts, from which it proposes facts and world rules for you to accept. An entry links back to the sentence in your manuscript where the fact was established when a clean span is available. Where a cited entry exists, click on a character’s eye color and you land on the passage that set it.

The extraction layer is the AI work. The bible itself is structured data — searchable and exportable as JSON, CSV, or Markdown. You browse it like a database. A check you run on the next chapter compares it against the facts you accepted and flags sentences that may contradict what your earlier draft established.

A few specifics that matter once you’ve used the tool for a week:

• Aliases are linked. “Detective Morrow,” “Anna,” “Morrow,” and “Anna Morrow” can resolve to one character, as can nicknames and titles. Ambiguous identities still need your review.
• Relationships are typed. Anna is Lewis’s partner; Lewis is Catherine’s ex-husband. The bible records the links between characters, not just the characters, when the text states them.
• Belief is separate from fact. When the manuscript gives enough evidence, what a character has been told is kept apart from what’s narratively true. For mystery, dramatic-irony romance, and unreliable-narrator stories, that distinction matters; the output is a review lead, not a guarantee.
• Provenance. Facts point to the sentence that established them when a clean span is available. Items without one are not shown as cited, and there are no paraphrased AI summaries to take on trust.

Where it fits in a working writer’s day

A novelist drafting book three of a series uploads books one and two on day one. PlotLens reads them in the background and proposes a Story Bible of the characters, locations, rules, and events it finds. When the writer drafts a new chapter in Word, the add-in can check the passage and flag a sentence that may contradict an accepted fact; in Scrivener the Companion app (beta) syncs each scene when you save it, and you run a check when you want one. For Google Docs, export to .docx and upload until the add-on is published. “Anna’s eyes are described as green; book one chapter four established hazel.” The writer fixes it, accepts the new fact, or marks the change as deliberate, and either way makes the choice consciously.

A writers’ room building season four of a show uploads the bibles for seasons one through three. On team plans, writers in the room can each check drafts against a shared Story Bible, and a check can surface where one writer’s outline may contradict an already-aired episode before the script goes to table read. The writers’ rooms surface of the product is what this workflow lives in.

A studio’s narrative team with a large cast and years of accumulated lore can use the same approach: propose the bible from the source material, check new writing against the facts they accept, and re-run extraction as the story evolves.

Free story-bible templates

Not ready to install anything yet? Start with the focused Story Bible facts-and-rules template for established facts, world rules, relationships, events, and source passages. It works in the browser without signup and exports to PDF or Markdown. For deeper character development fields, use the separate character bible template. Both stand alone even if you never use the software.

If you write novels, screenplays, or game narrative, the same primitive applies: the story bible is derived from the manuscript, not maintained beside it. Compare PlotLens to Novelcrafter or World Anvil for adjacent points in the category, or see current pricing — the free tier covers a single project so you can try the extraction on a manuscript you’ve already written before committing to a plan.