Scene
A scene is a unit of continuous action in one location at one point in time — the moment place or time changes, a new scene begins.
What this is about
Scene numbers are the coordinates a production navigates by. The breakdown lists needs per scene, the stripboard schedules scenes, the slate carries the scene number, the editor sorts dailies by it. That is why renumbering after a rewrite is handled so carefully — added scenes become 12A instead of shifting everything below them. In planning conversations the scene is also the unit of ambition: a day is described as three script scenes, and everyone can weigh what that means.
A term only helps when everyone on set means the same thing by it — so what follows is how it is used, not a dictionary definition.
What runs differently here
Where this differs from the general case:
- Scene and shot are different sizes: a scene usually contains several shots.
- INT or EXT, location and DAY or NIGHT in the slug line define the scene for planning.
- Inserted scenes get letter suffixes like 12A so every department keeps its numbers.
With TillyGen
TillyGen structures a project by scenes: breakdown, shot list and schedule all hang off the same scene spine.
Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.
Frequently asked
When does a new scene start?
When location or time changes. Two people walking from the kitchen into the garden is two scenes on paper, even if the camera follows them in one shot.
How long does it take to get started with TillyGen?
A first project takes under an hour to set up. There is no configuration phase in which templates and fields have to be defined before the tool produces anything.
Can the results be exported?
Yes — as PDF for the crew, CSV for downstream systems and through the API for anything automated. The plan stays the source; the exports are views of it.