You Got Coverage Notes. Now What?

The dangerous moment in a writer's process isn't receiving hard notes — it's the week after, when the rewrite starts. Notes handled badly produce committee drafts: scripts sanded smooth of both flaws and voice. Notes handled well produce second reads that score a tier higher. The difference is a discipline, and it's learnable.

Separate diagnosis from prescription

Every note has two parts, usually fused: what's wrong and what to do about it. "Act two drags — maybe add a subplot for the sister" contains one reliable claim and one stranger's first guess. Readers are almost never wrong about where they disengaged, got confused, or stopped believing — that's data about an experience they actually had. They are routinely wrong about fixes, because the fix requires knowing your intent, and only you hold that.

Rule: accept diagnoses gratefully, treat prescriptions as optional brainstorms. When multiple reads flag the same location with different fixes, the location is certainly real and every proposed fix is probably wrong — yours will be better.

Triage before touching the draft

Sort every note into three piles. Structural — problems in the script's spine: a soft midpoint, a late inciting incident, a passive protagonist. These get fixed first, at the beat-sheet level, because they invalidate scene-level work. Scene-level — a flat confrontation, an unearned reveal, exposition dumps. Fixed second. Polish — dialogue tightening, format cleanup. Fixed last, and never first, no matter how tempting the easy wins are. Polishing a structurally broken draft is detailing a car with a cracked engine block.

Then find the root note: surface complaints often share one cause. "Protagonist unlikeable," "middle drags," and "climax unearned" are frequently a single want-and-stakes problem casting three shadows. Fixing causes collapses whole pages of notes at once.

Protect the spine

Before rewriting, write one sentence: what this script is for — the thing that made you write it. Tape it up. Every note gets tested against it: notes that serve the spine get implemented; notes that would trade the spine for smoothness get consciously set aside. Passing on a note on purpose is a professional act. Drifting from your script's point because a stranger was briefly confused is not.

The stopping problem

Note-chasing has no natural end — every draft can generate new notes forever. Use convergence as your stop signal: when successive reads flag different, smaller things each time, you're improving; when the same structural note survives three drafts, stop drafting and rethink the beat sheet instead. And when reads come back with only polish-pile notes, the script is done enough to work — send it.

This loop is the entire design of our system: a scored read, specific notes, your rewrite, then a second read to prove the gap closed. The goal of running it twice is a measurable jump in your scores, and the thing that makes that possible is the discipline, not the brilliance of any single note.