Tomorrowish

How scene numbers survive script revisions

Locking, A and B scenes, OMITTED, and how to check that a new revision kept the numbers everyone else is working from.

Why the numbers matter

Once a script goes into prep, its scene numbers stop being the writer's and become everybody's. The schedule, the breakdown sheets, the Day out of Days, the call sheets, the budget, the script supervisor's notes and the editor's bins all point at scenes by number. If scene 34 quietly becomes scene 35, every one of those documents is now wrong in a way nobody can see.

That is why scripts are locked: from a set point (usually when the production starts sending out revisions), scene numbers and page numbers are frozen. The script still changes; the numbers do not.

The rules of a locked script

A cut scene stays
The heading is replaced by OMITTED and the number stays in place: 34 OMITTED. Anyone reading the list sees that 34 was removed on purpose, not lost. Two scenes combined usually means one keeps its number and the other becomes OMITTED.
A new scene takes a letter
A scene added between 12 and 13 is 12A, the next one 12B. A scene added before scene 1 is commonly A1. Splitting scene 12 in two gives 12 and 12A. Many productions skip the letters I and O, because they read like 1 and 0.
A moved scene keeps its number
If scene 40 now plays before scene 20, it is still 40. The running order changes; the number does not.
Changes are marked
Changed lines get an asterisk in the right margin, and revised pages go out on coloured paper in a set sequence. A common order starts white, blue, pink, yellow, green, goldenrod; each production publishes its own.

Before the lock: renumbering is normal

Writers' drafts are often renumbered from 1 every time. That is fine until someone has to carry notes, a schedule or a breakdown from one draft to the next: insert a scene on page 3 and every number after it moves by one. Comparing the two drafts by number then looks like a rewrite of the whole script, when only one scene was added.

Scene Number Lineage lines the two drafts up in running order first, the way a text diff does, so that case shows as one new scene and a run of renumbered ones. It then matches scenes that left their place by their heading (and by their text, when you give it the script files), and leaves the genuinely unclear ones for you.

Checking a revision before it goes out

  • No locked number changed. Every scene in the last revision is under the same number in the new one, or is OMITTED.
  • Every cut kept its OMITTED line. A number that simply vanished is the most common slip, and it reads as a gap.
  • New scenes are lettered, in order. No plain number appears inside the locked range, letters run without holes (12A, 12C with no 12B is worth a question), and nothing sits out of order.
  • No number was used twice. Duplicates usually come from two people inserting the same 12A.
  • Headings that changed are deliberate. A set or a DAY to NIGHT change under an unchanged number moves the schedule.

Paste both scene lists (or open both scripts) in Scene Number Lineage with "a locked revision" selected, and it lists each of these, then writes the renumbering memo for the departments: old to new, omitted, new, headings changed.

Getting a scene list out of a script

You do not have to type one. Open the script itself: a PDF exported from your writing app (it needs a text layer, so not a scan), a Final Draft .fdx or a .fountain file. The scene numbers and headings are read from it in your browser. A scene report or a scheduling export pasted from a spreadsheet works too, as long as each row has the scene number and the heading.

Nothing you open is uploaded: the tool runs in the page, and the page is not allowed to make network requests.

Open the tool

Breaking the script down for the schedule? Scene Sheets makes breakdown sheets, element lists and a Day out of Days from the same file.