Revision Is a Decision: What a Second Pass Shows About Taking Notes
He took the notes that moved the structure. One note stayed exactly where it was. Here’s what both choices look like.
Most writers get notes or coverage once. Rarely do they go back to the same well after revising their script, which means they never find out what the other side of those first notes looks like. This case study is different. It follows a single script through two rounds of dev|cut.™ coverage, about two months apart, and shows what revision looks like when it’s treated as a series of decisions rather than a mere compliance exercise.
The script is a coming-of-age crime dramedy by writer-director JD Marshall, who kindly agreed to let us walk through both passes. The first version we saw received a coverage verdict of Targeted Development and sat at 148 pages. That’s a lot. But hey, page count isn’t the be-all and end-all of a script. Ask Tarantino.
The second pass of the script came back at a far tighter 120 pages with a coverage verdict of Final Polish. Twenty-eight pages out, and coverage clearly stating the script has leveled up.
Sure, the cut is the headline. But the decisions are the story.
Your script doesn’t get better just because its length is closer to “industry standard.” So the question is: how did JD cut 28 pages yet manage to add quality and craft?
What he took. The first pass of coverage named two structural problems:
- The draft ran well past the classic feature band (90–120 pages).
- The story engine didn’t properly engage until around the midpoint, because the first half gathered material instead of building on it.
Both notes are the hard kind, because answering them means removing pages a writer loves.
The 28 pages came out of exactly the stretch the coverage had pointed to: the front half. In the revised version, the engine starts turning by the end of the first act. Boom! And because a cut that size is where rewrites usually do their damage, the second pass went looking for casualties. Surprisingly, it found none. JD is talented, but even the best writers can miss things and create problems when scrapping almost a fifth of their script. JD didn’t. The strengths named in the first read were all intact, along with the three moments I’d asked him to protect when I did my side of the read. Nothing earned was lost.
A couple of notes landed only partially, which is normal. A subplot note produced a re-weighting rather than a reduction. A loose thread now resolves on the page instead of offscreen, which is great, though not yet as emphatically as the coverage called for. But remember folks, coverage… notes… reader input… it’s all to be taken as suggestion, not dogma. We’ll get into that below.
What stayed. One note didn’t move at all: the first coverage gave a central character note, that the lead sits at the center of the story without truly making a choice that costs him something. The second pass left it exactly as written.
That might sound like bad news. It isn’t. The coverage didn’t change its mind, still naming that note as the one still open and saying so plainly. But it doesn’t treat holding it as a failure either. dev|cut. coverage is analysis and suggested revision, not a ruling, and a writer is free to decide whether a note fits the story they’re telling. Whether a note is held on purpose or simply not reached yet, a second pass treats it the same way: it makes the state of the draft visible. Everything else is closed, while one item remains open. The writer can see exactly what’s left, and exactly what a change could look like. It’s up to them to decide whether it’s worth making for their script.
What it shows. Three things worth taking from a revision like this.
First, protect what’s working before you cut. The safest 28 pages are the ones you take after you’ve already identified what needs to survive.
Second, a note you hold doesn’t disappear. It becomes the whole conversation. Once the structural notes were closed, the one remaining note was the only thing left to discuss, and that’s clarity, not punishment.
Third, a second pass is a clear way to find out which notes you’re really holding onto. If you’re weighing a note you’re unsure about, our piece on how to handle a note you disagree with is a good companion to this one.
Revision isn’t obedience, and it isn’t resistance. It’s knowing, note by note, which is which, and being able to see the result on the page.
Thank you to JD Marshall for letting us share his process.
Want a read this specific on your own script? See pricing.
[Soon] The story continues…
— Brian Hanford, Writer & Founder, dev|cut.™
devcut.io