Read the manuscript once. Catch what three reads would miss.

How editors use PlotLens

PlotLens has no editor-specific mode, and this page does not pretend otherwise. What it has is a Story Bible that is built from the manuscript itself and a Manuscript Check that reports against it — which is the work an editorial continuity pass is made of. Here is that pass, step by step, in the features that exist today.

1. 1

   Give each author their own project

   A project is one story world. It owns its own documents, story elements, established facts, timeline and Manuscript Check sessions, and deleting it cascades to all of them — so one author's Story Bible can never surface inside another author's checks. Plus covers ten projects; Pro and above are unlimited under fair use.

2. 2

   Upload the manuscript in the format the author sent it

   PlotLens parses .txt, .md, .docx, .pdf, .rtf, .odt, .epub and .fountain. It does not read legacy .doc, and a scanned PDF needs OCR before it carries any text to extract. You can queue up to twenty files in one batch upload; three transfer in parallel.

3. 3

   Read the Story Bible PlotLens derived, and reject what is wrong

   Extraction runs rule-based gazetteers, then spaCy NER, then an LLM pass, and returns six entity types: characters, locations, events, items, organizations and concepts. Entity attributes become attribute rules, relationships above 0.5 confidence become relationship rules, and described concepts become world rules. Auto-derived rules land as pending with the source snippet attached, so you accept or reject each one rather than inheriting a machine's guess.

4. 4

   Mark what the manuscript means to be false

   A rule carries an epistemic status, and the status changes what the validator does with it. Rumour, speculation and unreliable-POV rules are downgraded to low severity; lies, dreams and red herrings are excluded from validation entirely; a retcon validates normally and supersedes the fact it replaces. This is how a deliberate unreliable narrator stops generating findings you would otherwise have to dismiss one at a time.

5. 5

   Run the pass and work the findings

   Batch validation takes the documents you select and returns findings asynchronously, each with a severity, a conflict type, a citation and a suggested fix. Severities are Error for a direct contradiction, Warning where the text is ambiguous, and Info for a note. Every finding is unresolved, resolved or acknowledged, so a second pass shows you what moved.

6. 6

   Check a single passage without touching the project

   Spot Check takes a pasted excerpt of up to roughly two thousand words and reports against the Story Bible in two to eighty seconds, with no project documents required. It is free on every tier, forever, and never counts against a monthly quota — so a query about one paragraph costs nothing.