Skip to content

Narrative Intelligence features — built for writers.

PlotLens builds a story bible from the manuscript you already have — then checks new pages against it and flags contradictions with sources, so you can fix what breaks before readers do. You write. We keep the continuity.

Your cast, mapped automatically.

PlotLens reads your manuscript and identifies characters, locations, events, and objects — then links the ways they're referenced throughout. "The detective", "Harrison", and "he" in the same paragraph? PlotLens knows they're the same person.

  • Characters with names, aliases, and all their defining traits
  • Locations tied to the scenes that happen inside them
  • Events linked to the people and places involved
  • Objects that carry history and significance across chapters
Story BibleSample project · 2 facts · 2 held
SarahCharacter · Greyhaven
  • Scar on left cheek, aches in the cold Ch. 3, p. 47
  • Burned the letter without opening it Ch. 6
Sarah ↔ James · held for reviewCh. 3 puts them in the same scene; no sentence states a relationship.
Sarah ↔ Vera · held for reviewNo sentence states a relationship.

What's true — and what a character only thinks is true.

PlotLens is a guide, not a judge. It distinguishes established fact from what a character believes, suspects, or has been told — then surfaces potential contradictions so you can decide what to do with them. When a character is wrong about the world, that's not an error: it's a plot point.

  • Continuity guidance catches inconsistencies as you write — real-time validation on Plus and above
  • Character-level belief tracking separates knowledge from fact
  • Add your own facts to define what's allowed in your world
  • Severity levels distinguish continuity issues from intentional choices
Manuscript checkSample project · 3 lines checked · 1 open query
Draft, Ch. 14 · checked against the Story Bible

Sarah could still recite the letter's last lineQuery A.

James waited outside the precinct, his hands in his pockets.

The rain had not let up since morning.

Query AKnowledge conflict

How does Sarah know the letter's last line? Ch. 6 says she never opened it.

Canon, Ch. 6

Sarah burned the letter without opening it.

When we flag a break, you can open the source.

Manuscript Check findings point back to the draft line and the Story Bible evidence behind the conflict — so you verify, not trust a summary. Items without a clean span stay in review, not dressed up as cited proof.

  • Chapter and paragraph citations when a supporting span is available
  • Full attestation trail shows how facts were derived
  • Unquoted or span-failed items stay in review — not dressed up as cited proof
  • See competing evidence when facts conflict across documents
Source to factSample project · 2 cited · 1 held · 1 open query
Greyhaven · Ch. 3, p. 47

Sarah · Characterscar on her left cheek ached in the coldCh. 3, p. 47 · verbatimStory Bible: 2 facts · 2 held for review pulled her coat tighter as the wind cut across the square. The scar on her left cheek ached in the cold — it always did when the weather turned. James · Characterleaning against the iron railing of Greyhaven BridgeCh. 3, p. 47 · verbatim3 items held for review was already there, leaning against the iron railing of Greyhaven Bridge · Locationiron railing of Greyhaven BridgeCh. 3, p. 47 · verbatim, pretending to read.

Sarah · scar on left cheek, aches in the coldCh. 3, p. 47 · “scar on her left cheek ached in the cold”
Greyhaven Bridge · has an iron railingCh. 3, p. 47 · “iron railing of Greyhaven Bridge”
Sarah ↔ James · held for reviewThe passage puts them in the same place; no sentence states a relationship or a plan to meet.
Draft, Ch. 19

Sarah turned the brass key in the lockQuery A.

Query AObject continuity

Sarah uses the brass key in Ch. 19. Ch. 11 says it went into the harbor. Which is right?

Canon, Ch. 11

She dropped the brass key into the harbor and watched it sink.

Your story's timeline, always in order.

PlotLens tracks when events happen in your story's world — and also the order in which you revealed them. If a character references something that hasn't happened yet, PlotLens can flag it against the Story Bible.

  • Story-world chronology separate from narrative reveal order
  • Catch impossible sequences — "Tuesday after Thursday" errors
  • Flashbacks and flash-forwards tracked without confusion
  • Timeline consistency across a whole series, not just one book
Story timelineSample project · Ashenmoor · 1 open query
  1. Winter, year 1
    The Battle of AshenmoorCh. 3, p. 47 · Event
  2. Spring, year 1
    Treaty signed at Kestrel FordCh. 8, p. 142 · Event
  3. Spring, year 1?
    The Battle of Ashenmoor (draft)Draft, Ch. 20, p. 310 · Event

    The battle raged through the spring rainsQuery A

Query ATimeline conflict

Which season was the battle? Ch. 3 places it at the first snow.

Canon, Ch. 3, p. 47

The battle broke on the first snow of winter.

Ask your manuscript anything.

Hybrid search blends exact matches with semantic ranking, so natural-language queries can pull up the right passages, story elements, and your Story Bible even when the wording differs. Your Story Bible is the set of facts your story has established — what readers call canon.

  • Semantic ranking surfaces related passages even when the query words do not match exactly
  • Filter results down to story elements, documents, or your Story Bible as you narrow the search
  • Results include the passage context that explains why each hit matched
  • Useful for fact-checking, not just navigation
SearchSample project · 3 results
who has a reason to betray the king?
  • VeraCharacter

    The throne had been promised to Vera’s family before the coup.

    Ch. 12, p. 203
  • MarcusCharacter

    Marcus had been sending sealed reports north for months.

    Ch. 18, p. 291
  • JamesCharacter

    James had never sworn an oath to the crown.

    Ch. 9, p. 156

Your whole team, working from the same Story Bible.

When multiple writers share a project, PlotLens keeps them consistent. See who validated a fact, who introduced a character detail, and when. Disagreements surface as flags, not surprises in the final draft.

  • Shared projects so every writer sees the same established facts
  • Attribution on every edit — who wrote what, and when
  • Role-based access keeps established facts safe from accidental edits
  • Real-time updates when a teammate validates or flags something
Greyhaven · activitySample project · 3 writers
  • Query A

    Query raised on Marco's Ch. 19: Sarah turns the brass key in a lock, but Ch. 11 has her drop it into the harbor.

    Manuscript check · just now
  • Jeremy checked Ch. 15 against the Story Bible. No open queries.

    Manuscript check · 2 min ago
  • Alicia marked the brass key fact from Ch. 11 as critical.

    Story Bible · 8 min ago
  • Marco uploaded Chapter 19 draft.

    Documents · 14 min ago

See what PlotLens finds in your manuscript.

Start free — no credit card required.

No credit card required. Manuscripts stay private.