Add Narrative Intelligence to Final Draft

Final Draft watching is not open yet, and nothing on this page should be read as saying otherwise. The Companion ships Final Draft support, but the rollout unlocks Scrivener first, so adding an .fdx file to the Companion is still blocked server-side. The steps above describe the setup once that stage opens — not a workflow available today.

What works right now is the direct path: export your screenplay to .fountain and upload it to PlotLens. Screenplay format is parsed natively, so scene headings, character cues, and action versus dialogue are all distinguished rather than flattened into prose, and the Story Bible you get is the same Story Bible the Companion would build.

Everything downstream of getting the text into PlotLens is unaffected by the wait. Extraction returns characters, locations, events, items, organizations and concepts with source attestations; auto-derived facts arrive pending with the snippet they came from, so you accept or reject each one; batch validation sweeps whole documents and returns findings with a severity, a conflict type, a citation and a suggested fix. Spot Check will take a pasted excerpt of up to roughly two thousand words with no project documents required, free on every tier and outside the monthly quota — which makes it the cheapest way to check one revised passage while an integration is still closed.

Two Companion limits will still apply when Final Draft watching does open. The Companion never writes to a source file — no in-place comments, no applied fixes, no annotation of your .fdx — and Final Draft navigation is file-level rather than scene-level: there is no scene deep link, so opening a finding hands the .fdx to your operating system and you select the scene yourself. There is also no project-wide report in the Companion; a full pass means exporting and uploading to the web app.