Scene Numbers Explained (A-Scenes, Omitted Scenes, Locked Scripts)

Scene Numbers Explained (A-Scenes, Omitted Scenes, Locked Scripts)

Scene numbers are the fixed reference ID every department uses for a scene once a script is locked for production. They stay stable through revisions on purpose: if scene 24 could quietly become scene 26 between drafts, every call sheet, breakdown sheet, and camera report referencing "scene 24" would suddenly point at the wrong thing. So instead of renumbering, production scripts insert A-scenes (24A) and mark cut scenes as OMITTED, leaving the original numbers untouched for the life of the shoot.

If you've only worked from a spec script or an early draft, this can look strange the first time you see it — gaps in the sequence, letters tacked onto numbers, "OMITTED" sitting where a scene used to be. It's not a mistake. It's the whole system working as designed.

The 50-word definition

Scene numbers are the fixed identifiers assigned to each scene when a screenplay locks for production. They don't change once assigned — new scenes get inserted as lettered A-scenes (24A) and cut scenes are marked OMITTED rather than deleted, so every department can reference "scene 24" and mean the same thing throughout the shoot.

Why numbering only happens at lock

A spec script or an early draft usually has no scene numbers at all, or numbers that are still moving with every pass. That's fine at that stage — nobody outside the writer's room is building paperwork off it yet.

The moment a script is locked for production, that changes. The script supervisor is now logging takes against specific scenes. The 1st AD is building a one-liner schedule and a stripboard with a strip per scene. Sound and camera are labeling media by scene and take. Props and art are tracking what's needed scene-by-scene off the breakdown sheet. Every one of those systems needs scene 24 to mean the exact same thing on day one of prep and on the last day of the shoot.

If the script got renumbered every time a scene was added or cut, that shared reference would break constantly. Departments that hadn't seen the latest draft would be labeling footage, sides, and reports against numbers that no longer matched. So production scripts adopt a rule: once numbers are assigned, they don't move. Everything after that is handled with insertions and omissions instead of a fresh count.

A-scenes: adding a scene without renumbering

Say the script locks with scenes running 22, 23, 24, 25, 26 in order. Two weeks into prep, the director wants a short scene between 24 and 25. Renumbering everything from 25 onward would touch every department's paperwork that's already in circulation — call sheets, the DOOD, camera logs, the stripboard. Nobody wants that this deep into prep.

Instead, the new scene becomes 24A. It sits physically between 24 and 25 in the script and on the breakdown sheet, and it gets its own row everywhere scenes are tracked — its own strip on the stripboard, its own line on the day out of days, its own slate. If a second scene gets added in the same gap later, it becomes 24B, and so on. The original sequence never shifts.

OMITTED: cutting a scene without deleting the number

Cuts work the same way in reverse. If scene 26 gets cut after lock, it doesn't just vanish from later drafts — the number is retired, not deleted or reused. Later revisions show it as "26 OMITTED" both in the script and on the one-liner or breakdown sheet.

This matters more than it sounds like it should. If scene 26 simply disappeared with no trace, anyone flipping through the revised script would have no way to tell the difference between "this scene was cut on purpose" and "a page is missing" or "I'm holding an out-of-date draft." Marking it OMITTED closes that question immediately — everyone can see it was an intentional call, not an error, and no future scene will ever reuse the number 26.

Locked pages and revisions

Once a script locks and scenes are numbered, further changes go through revision pages — new pages printed on colored paper (blue, pink, yellow, and so on down the standard order) so everyone can tell at a glance which pages are current. That's a big enough topic on its own that it deserves separate treatment, but the piece that matters here is: revision pages can change dialogue or action within a scene, but the scene number and page numbering stay fixed. A page can go from white to blue to pink and still be "page 42, scene 24" the whole way through.

FDX vs. Fountain: a quick note

How you get scene numbers onto the page differs by screenwriting format. Final Draft's FDX format has scene numbering built in — turn it on and it auto-numbers every scene, and those numbers carry through the file. Fountain, being a plain-text format, doesn't natively track scene numbers the same way; numbers typically get assigned when the script comes into production software, or added manually by whoever's prepping the shooting draft. Neither approach is wrong, but if you're deciding which format to write in, it's worth understanding the tradeoffs — see our full Final Draft vs. Fountain comparison rather than sorting it out here.

Production Slate reads scene numbers from either format on import and keeps them exactly as assigned — including A-scenes and OMITTED markers — instead of forcing a renumber onto your script.

Worked example

Here's what a locked scene sequence looks like after one insertion and one cut, exactly as it would read on a one-liner or breakdown sheet:

Scene 22   INT. WAREHOUSE - NIGHT
Scene 23   EXT. WAREHOUSE - PARKING LOT - NIGHT
Scene 24   INT. WAREHOUSE - OFFICE - NIGHT
Scene 24A  INT. WAREHOUSE - HALLWAY - NIGHT       (added after lock)
Scene 25   EXT. HIGHWAY - NIGHT
Scene 26   OMITTED                                 (cut after lock)
Scene 27   INT. MOTEL ROOM - NIGHT

Notice the sequence still reads 22 through 27 in order — nothing was renumbered. 24A slots in cleanly where the new scene lives, and 26 stays visible as a deliberate gap rather than disappearing. Anyone picking up this page for the first time, on day one or day forty of the shoot, can reconstruct exactly what happened without asking a single question.

This same numbering also does double duty on the breakdown sheet, where it sits next to each scene's page count in eighths — scene number and eighths are the two columns everyone reads first when they're scanning for how long a day is going to run.

Keep scene numbers intact from script to schedule

Scene numbers are the thread that ties your script, breakdown, one-liner, and stripboard together — lose that thread and every downstream document stops agreeing with itself. Production Slate's script import reads FDX and Fountain files, preserves scene numbers exactly as locked (A-scenes, OMITTED markers, and all), and carries them straight through to your breakdown and scheduling tools. Import a locked script and see it for yourself.