Coverage and the Script Doctor#

A professional read on your whole script — a verdict, a scorecard, and constructive notes.

Dismiss keeps the same note on the same passage from returning on a later read, even when its wording changes. The Notes buttons currently record Dismiss without a written reason. Accept and Resolve keep the decision and its date; a later read can still raise a new observation. Reopening a note from any of its scene copies undoes that dismissal for the same finding. It keeps the original decision history and leaves unrelated notes as they were. Notes already retired by a later read stay retired. Through the API or CLI, you can add your reason or explicitly rule a thread complete on purpose. Nabu keeps your words with that decision. Thread completion does not add a payoff to the script; replacing an existing thread ruling requires explicit confirmation.

When you want an honest, outside opinion on your screenplay, run Coverage on the Script Doctor page. Coverage is the film industry's word for a written assessment: a verdict on whether a script is worth making, scores on the parts of the craft, and an essay on what's working and what isn't.

Note: Coverage works on a phone, but a laptop or desktop is more comfortable for reading the report.

Note marks update after a pause in typing. Opening Notes or reloading can bring them up to date sooner.

Notes#

Below the open notes, Nit Notes · N · Show keeps the smaller observations collapsed, and any note that pushes against a choice you already made in chat. Click Show to read them or Hide to close the group. Select a row to open the same inspector and actions as any other note. These notes do not appear as marks on your script or add to the open-note count. Their scene link, Open scene action and Enter shortcut still open the selected note and its review actions in the editor. When you dismiss a focused note with D, focus moves to the nearest remaining row, or to the empty queue if no rows remain.

A suggestion shows the passage and the proposed words; Accept or Dismiss it here, as on the page. Answered suggestions stay under Answered. A suggestion whose words you have since changed says No longer matches the page. It can't be accepted; Dismiss it here.

Character Voice notes#

After you pause, Nabu checks the main characters in the scenes you just changed against what is on file for them: what they want, need, believe and fear, and how they sound. When one acts against that and nothing in the scene turns them, a Character Voice note appears on that scene. The note says whose line it was checked against — yours, Setup's, or Nabu's reading of the pages. Usually there is nothing to note. A dismissed note stays dismissed.

Uses your plan: Character Voice notes are part of the Pro plan and are charged for what each check uses.

Running a coverage report#

Open your project and click Doctor (the cross icon) in the left sidebar, then Coverage. The two rooms under Doctor are Notes and Coverage. The page is titled Script Doctor, with the subtitle Coverage of the whole script.
Click Run Coverage in the page header. Once you have a report, the button reads Re-run coverage, with when the script was last checked beside it. For a larger run, Nabu shows the estimated share of your plan first.
The button changes to Analyzing… and then Synthesizing… while Nabu reads your script. A progress bar runs across the page, and a busy line appears in the Reports rail.
When it finishes, the report appears: the verdict, the scorecard, the executive summary, then the rest of the written assessment.

Uses your plan: Coverage is part of the Pro plan. A run reads your whole script, so it can use a substantial share of your plan, varying with script length. See What uses your plan.

Tip: You don't have to wait on the page. The read runs in the background — close the tab or move to another part of your project and come back.

If the combined reading cannot be completed, the report says so and preserves the individual reader reports. An incomplete combined reading is not presented as a finished consensus.

If coverage fails, Nabu shows “We’ve been notified, please try again in a moment” with the job ID; wait a moment, then try again.

What each control does#

Run Coverage / Re-run coverage — starts the read. Greyed out (with the tooltip AI is offline) when the AI is unavailable, and while a run is already going.
Export PDF — in the inspector's This report panel after a report finishes. Saves the whole report as a PDF.
Reports rail — a list on the left showing every report you've run, each labelled by date. Click any row to view that report.

Note: If you run coverage again too soon, the button tells you when you can run it again.

Reading the verdict#

The Verdict section holds the headline: your Script call. It's one of three words, the standard industry calls:

RECOMMEND (green) — the rare top call. A script a reader would actively champion.
CONSIDER (amber) — promising, worth a serious look. This call has to be earned by both a strong idea and execution already on the page.
PASS (rose) — the default. Not the end of the road — it's where every script starts until the writing proves otherwise.

Note: The verdict is deliberately tough, the way a real development desk is tough. A great premise alone will not lift a script out of PASS if the pages aren't working yet.

In the same section you'll also see:

A Writer call — a second, more forward-looking verdict from the creative-development point of view. It reads for what the script could become, not only what's on the page today.

Reading the scorecard#

The scorecard scores the main parts of the craft, such as premise, characters, dialogue, and structure. A low score points you at what to work on next — the notes below explain why.

Reading the written notes#

The body of the report helps you revise. Use In this report in the left rail to jump between headings:

The Verdict — the headline calls at a glance.
Scorecard — the scores.
Executive Summary — the top-line read, with reader pull-quotes and their attribution beneath.
Creative Assessment — what's working and what isn't, and where the reads disagree.
Voice Distinctiveness — how each character's voice reads, where voices converge, and where they drift apart.
Technical Assessment — the market and production read.
Hot Spots — the most important specific notes, each pinned to a scene.

Linked scene references follow your draft’s current numbering and headings; saved reader text stays as written.

Who contributed to the report#

Open Who contributed to this report below the assessment to see the model that supplied each specialist analysis, reader report, adjudication and executive summary. A configured fallback is distinguished from an additional fallback used during the run. These facts are saved with the report and included in its PDF. Older reports may say that attribution is unavailable.

Good to know#

Coverage reads the script as it is right now. Run it again after revisions to see whether the scores and verdict move.
Coverage is advice about your script. Its readers assess the pages; they do not write your screenplay. The assessment can still be exported as a PDF.
A run takes a little while. The full read runs for tens of seconds to a couple of minutes. The progress bar keeps you posted.
You can ask Nisaba about past coverage. In chat, ask Nisaba what the Script Doctor said about a character, scene, or part of the craft — she reads your saved coverage reports. See Working with Nisaba.
Anyone with edit access can run it; viewers can read finished reports.

A script menu’s Get a note on this scene opens Notes on its saved answer when the read completes. This destination uses that read’s identity, including a note folded under an existing note; it does not guess the newest note in the scene. A missing or ambiguous answer says it is unavailable in the current view.