A beat sheet is not a scene list

A beat sheet and a scene list look identical on the page. One is a list of promises, and the other is a record of what those promises cost to keep.

Both are numbered one-line records, both are written as lists, so software tends to store them the same way: a row with a title, a note, and somewhere to hang everything else. That is where the trouble starts, because the extra fields are not inert. A cast list on a beat is a claim nothing reads yet. A location is worse: in screenplay grammar a location change is a scene boundary, so a beat that moves somewhere else has quietly become a scene. The plan has started drafting itself.

A beat sheet earns its keep by staying thin. Its lines are written fast, one after another, before any of them is a scene, and what each line records is a promise: this must happen. A promise does not have a location yet, or a cast, or a rating for how much it hurts. Those arrive when the scene does, and not before, because they are answers and the beat sheet is only questions.

A scene list is the other half of the trade. It records what the promises cost: which scenes now exist, how long each runs, what the page count has become. Two numbers, planned and written, never quite equal, and the gap between them is the work.

The shapes match by accident of typography. On a page, everything is a line of text, so a list of promises and a list of scenes are hard to tell apart from a screenshot. In a file they are different things, and the difference is what each one refuses to hold.

So the test for a planning record is not how much it holds. It is how much it declines to. Six fields on a beat is an invitation to fill them, and the filling is drafting done at the wrong altitude, in a place nothing reads. The blank fields are the instrument.

Keep the beat thin and the scene list honest, and the two stay useful in different ways. Blur them and the plan becomes a draft nobody meant to write.