Every writer has that tool. The one they’ve used for years. The one where the keyboard shortcuts are muscle memory, the layout feels like home, and even the quirks are endearing at this point. You didn’t arrive at your writing tool by accident — you tried others, you compared, you chose. And now someone’s asking you to copy-paste your manuscript into a browser tab to check for continuity errors.

No thanks.

We built PlotLens integrations on a simple principle: your writing tool is yours. We’re not here to replace it, compete with it, or ask you to leave it. PlotLens comes to you.

Here’s what that looks like for the tools writers actually use.

Microsoft Word: Story Intelligence in the Task Pane

Aria writes a seven-book urban fantasy series. 140-plus named characters, three magic systems, a timeline spanning twelve centuries. She writes in Word because her publisher requires .docx deliverables, and honestly, because she’s been writing in Word since college. There’s a printed spreadsheet of character attributes taped to her monitor. It’s dog-eared. Some of the entries are wrong.

The PlotLens Word add-in lives in the task pane — that sidebar on the right side of the document that you’ve probably used for spell-check or the thesaurus. When Aria writes a scene, the sidebar shows the entities relevant to the current paragraph: the characters present, the location details, the timeline markers. She doesn’t have to ask for it. It’s just there, updating as she writes.

The part she actually loves, though, is the squiggly underlines.

When PlotLens detects an inconsistency — a character’s eye color contradicting an earlier book, a location described with the wrong street name, a timeline that doesn’t add up — it marks the text with a blue wavy underline. Hover over it and you get the finding: what the established canon says, where it was established, and how confidence is scored. It feels like spell-check, but for your story.

Aria doesn’t have to switch windows. She doesn’t have to copy text into a browser. She writes, PlotLens watches, and the printed spreadsheet is starting to collect dust.

Google Docs: Validation Your Co-Writers Don’t Have to Learn

Marcus co-writes a TV series with two partners. They use Google Docs because real-time collaboration is non-negotiable — they’re often in the same document simultaneously, arguing about dialogue through cursor proximity and comment threads. It works. They’re not switching.

The problem is that Marcus is the continuity person. He’s the one who remembers that Detective Reyes drives a 2019 Civic, not a 2021, and that the precinct is on Ashland Avenue, not Ashland Street. He used to spend thirty minutes twice a week copying script pages into PlotLens, running validation, then manually pasting findings back as Google Docs comments. His co-writers thought he was just meticulous. He was, but he had help.

The PlotLens Google Workspace add-on eliminated the ritual. Now validation runs from the sidebar without leaving the document. But here’s the part that matters for Marcus’s situation: findings appear as native Google Docs comments, threaded right alongside the text. His co-writers see a comment that says “Reyes drives a 2019 Honda Civic, not 2021 — established in S02E03, scene 14.” They don’t need to know where it came from. They don’t need a PlotLens account. They just see a comment, fix the line, and resolve the thread.

Marcus’s co-writers still haven’t learned PlotLens. They don’t need to. The validation results speak their language — Google Docs comments — and the continuity conversation happens where it always has: in the margins.

Scrivener: Your Binder Is Sacred

Elena writes literary fiction in Scrivener. She has opinions about her binder hierarchy. Strong ones. Her novel is organized into four parts, each with nested chapter folders, each containing scene documents, research notes, and character sketches filed exactly where she wants them. She uses the corkboard view for structural planning and the compile feature for manuscript output. This system took her months to build. It is not a suggestion.

Scrivener doesn’t have a plugin ecosystem. There’s no sidebar to inject, no add-in marketplace to browse. Elena knows this. She chose Scrivener anyway, because its organizational tools are unmatched for the kind of complex, non-linear narrative she writes — a 400-page novel with an unreliable narrator and a timeline that deliberately folds back on itself.

The PlotLens companion app works differently. It runs alongside Scrivener, watching the project file on disk. When Elena saves — which Scrivener does automatically — the companion app detects the change, reads the updated project structure, and syncs with PlotLens. It understands the binder hierarchy. It knows the difference between manuscript text and research notes. It respects the distinction between “Draft” and “Trash.”

Validation results appear in the companion app window, organized by Elena’s own scene and chapter structure. She can see them side-by-side with Scrivener, or check them during a break. Her workflow stays exactly the same: write in Scrivener, organize in Scrivener, compile in Scrivener. PlotLens is the quiet second opinion she consults when she’s ready, not an interruption that demands attention mid-sentence.

Her binder hierarchy remains untouched. As it should be.

Final Draft: PlotLens Speaks Screenplay

James writes feature screenplays in Final Draft. His world is scene headings, character cues, dialogue blocks, and action lines. Screenplay format isn’t a preference — it’s an industry standard enforced by every production company, agency, and studio he works with. The structure matters. INT. PRECINCT - NIGHT means something different from EXT. PRECINCT - NIGHT, and a character cue that reads DETECTIVE REYES must be consistent across 120 pages or someone in production will notice.

Final Draft’s .fdx files are XML under the hood, but the application has no plugin system. Like Scrivener, it’s a closed environment. James is fine with that. He needs Final Draft to format his screenplay correctly and stay out of the way.

The PlotLens companion app watches his .fdx files and — this is the part that matters — actually understands screenplay structure. It doesn’t treat a screenplay like a generic text document. It parses scene headings as location markers. It treats character cues as authoritative name references, so if James accidentally types DET. REYES in one scene and DETECTIVE REYES in another, PlotLens flags it. Dialogue is attributed to the correct character. Action lines are parsed for physical descriptions and continuity details.

When James opens the companion app, he sees validation results organized by scene, using the same heading format he wrote. INT. REYES APARTMENT - MORNING has two findings. EXT. COURTHOUSE - DAY has one. It speaks his language.

He doesn’t have to export a PDF. He doesn’t have to explain screenplay format to a tool that thinks everything is prose. PlotLens already knows.

The Principle

There’s a reason writers get attached to their tools. Writing is a craft that depends on rhythm, comfort, and trust. The tool you write in becomes part of the process — invisible when it’s working, infuriating when it isn’t. Asking a writer to leave that environment for continuity checking is like asking a carpenter to put down their hammer and walk to a different room every time they need to check a measurement.

PlotLens doesn’t ask you to come to us. We come to you — as a task pane in Word, a comment thread in Google Docs, a companion window next to Scrivener, a screenplay-aware watcher for Final Draft. Your tool, your workflow, your rhythm. We just make sure the story holds together.

Write where you write. We’ll be there.