Writing & MediaFree
Producer Notes Response and Page Tracker
River resolves every note onto the scenes it actually lands on, then totals what the whole set does to your page count.
Halberd Lane Pictures sent Ines Calloway-Osei 23 notes on Dry Lightning, a 118-page draft in 61 scenes. Six of the 23 name a scene number. Seventeen name no location at all: a thread, a quality, or in one case the whole script. Resolved against the draft, those 23 notes land on 53 of the 61 scenes and 89.2% of the page count. Nothing in the notes document says that, and it is the first thing the writer needed to know.
Doing all 23 as written adds 22.5 pages and cuts 15.0, so the draft goes to 125.5. The delivery mandate is 105. One note of the 23 says the script is long and it names no figure, so 20.5 pages have to come out of scenes nobody mentioned. The eight scenes no note touches hold 12.75 of them. Cut every one and the draft is still 7.75 pages over, which is a conversation to have before the rewrite rather than after it.
Page one for this query is about the conversation: step away before you answer, find the note behind the note, pick your battles. Final Draft's version gets closest by telling writers to track the ripple effects of each solution across the script, then leaves it there. None of them produces a number. This does: which scenes each note reaches, what the set costs in pages, and which pairs of notes cannot both be done. Then you choose, one note at a time.
A note that names no scene still lands on scenes
Four pairs in this set cannot both be satisfied. One is visible on the page: N-20 cuts the flash-forward, N-22 asks to open on the fire, and the flash-forward is the fire. The other three only appear after resolution. Two of the seven sister scenes sit inside the first act, so the 5.0 pages N-03 adds land in the act N-01 wants 4.5 pages shorter. You can still do both. You cannot do both and keep the act length.
The scenes carrying the most notes are mostly not the scenes anybody named. Scene 34, the spillway at night, takes five notes and is named once. Six more carry three notes or more and appear in no note at all: scenes 4, 14, 18, 38, 41 and 56. Those six are where a rewrite opens, and no amount of rereading the notes document produces the list. It comes out of the join, the same way a book's revision order does.
Runtime moves too. At the ratio measured across 2,520 produced scripts, where a page runs about 55 seconds rather than a minute, 118 pages is 107.3 minutes and 125.5 is 114.1. The one-page-one-minute rule would have said 118 and been 10.7 minutes out. The 89.2% figure is scope, not credit: the guild's own manual is explicit that contribution cannot be settled by counting pages. It is still the number that tells you whether you were asked for a polish.
How it works
Send the notes
The notes document exactly as it arrived. Bad phrasing is the input, so do not tidy it.
Send the draft
The current draft with its scene numbers, plus the page count you have been told to deliver.
Resolve every note
Each note lands on scenes, named or not, and each landing is priced in pages.
Choose per note
Options arrive with their page cost and the conflicts named. You decide, and nothing gets rewritten here.
What you get
- Every note resolved onto the scenes it lands on, whether or not it names one
- Pages added and pages cut per note, totalled against the page count you must deliver
- The pairs of notes that cannot both be done, with the arithmetic that proves it
- Scenes ranked by how many notes reach them, so the busiest one is not a guess
- Runtime before and after at the measured page rate, not the one-page-one-minute rule
- The share of your page count the note set touches, before you agree to anything
- Two or three options for each note, each one carrying its own page cost
- One register row per note: the scenes, the page delta, your decision and the reason
Common questions
Half the notes do not name anything. Is that a problem?
It is the normal case and it is why the resolution pass exists. Seventeen of Dry Lightning's 23 named no location. A note about theme still has scenes where the theme is carried, and those are findable from the draft. You get the scene list back, not a guess at what the producer meant. An editorial letter on a book resolves against chapters the same way.
Does it rewrite the scenes for me?
No, and that is deliberate. This run ends at the decision. Each note comes back with two or three options and the page cost of each, and you pick. Writing the replacement scene is a separate job, and the scene writer is where that starts once you know which scenes are moving.
What if I want to push back on a note?
The arithmetic is the pushback. Saying the ending needs more room is an opinion; saying N-11 adds 3.5 pages to a draft already 13 over the mandate is a fact the room can act on. Every note keeps a row whether you take it or not, and the row records the reason, which is what the next set of notes gets read against.
I have no page mandate. Does the arithmetic still work?
Yes, it just changes what the total is measured against. Without a mandate the net figure stands on its own: this set adds 7.5 pages, and a draft going up when everyone in the room thinks it is coming down is worth naming early. If you have a target runtime instead, the page rate converts it.
The notes came out of a meeting, not a document.
Send your own transcript of them, in whatever shape you took it down. The resolution pass runs the same way, and a rough note is often more honest about what was said than a tidied one. Where a note is genuinely ambiguous it comes back with both readings and the scene list each one implies.
Can it tell me the structural problem behind the notes?
It tells you where the notes cluster, which is usually the same thing. Six scenes drew three notes or more without being named once, and a cluster like that is a structural signal rather than six separate fixes. Whether the spine holds is a different pass, and the scene register and beat sheet is where that gets checked.
These are development notes, not production notes.
Different document, same resolution. Coverage arrives as a rating grid and a recommendation rather than as instructions, so the coverage read handles that shape and cites the scenes behind every rating. Notes from a company that has already committed to making the film go through this one, because the page count is a contractual number.
Producer Notes Response and Page Tracker
Fill in the form and your workspace opens with the work already underway.