Break down a script

A breakdown converts a script from prose into countable elements. Everything downstream — schedule, budget, call sheet — consumes this inventory.

What this is about

Feature productions break scripts down by reflex; corporate and commercial shoots skip it because the script is short — and then discover on set that scene four needs a second laptop, a branded mug and an actor who wrapped an hour ago. The breakdown is deliberately uncreative work: scene by scene, which cast, which props, which wardrobe, which special kit, interior or exterior, day or night. That inventory is what scheduling sorts, what budgeting prices and what the call sheet distributes. The shorter the shoot, the less slack exists to absorb a missing element, which is the argument for doing the breakdown precisely when it feels unnecessary.

The order matters more than the tools. Skip a step and you usually notice two steps later — by which point the fix costs several times as much.

What runs differently here

In planning terms, that means:

  • Scene numbers are infrastructure: once schedule and lists reference them, renumbering breaks every downstream document.
  • INT/EXT and DAY/NIGHT flags drive scheduling harder than anything else in the text.
  • Scripts hide elements in verbs — 'she signs the contract' quietly requires a contract, a pen and a table that reads on camera.
  • Page eighths as an effort proxy work as a starting point, corrected for known heavy lifts like stunts, VFX or choreography.

Step by step

This order gets you there fastest:

  1. Lock the script version first, then number every scene and freeze the numbering. A breakdown of a moving script is work you will do twice.
  2. Flag each scene INT or EXT and DAY or NIGHT. These four values sort the entire schedule later, so resolve every ambiguous case now.
  3. Read slowly and extract elements per scene into categories: cast, extras, props, wardrobe, vehicles, special equipment, sound needs. The verbs hide half of them.
  4. Estimate effort per scene — page eighths are the classic proxy — and correct for the known heavy lifts: choreography, kids, animals, VFX plates.
  5. Note dependencies across scenes: same actor pairing, same set dressing state, continuity of weather, wardrobe or time of day.
  6. Compile per-location and per-cast summaries from the sheet. These summaries, not the script, are what scheduling actually consumes.
  7. Walk the breakdown through with the director and production together, because 'we will solve that on set' items are exactly what this document exists to catch.

Common pitfalls

What most often goes wrong in practice:

  • Breaking down an unlocked script version — every rewrite invalidates the sheet quietly.
  • Skipping the breakdown on 'simple' corporate shoots, where a single missing prop has no slack to hide in.
  • Extracting only the obvious elements and trusting that wardrobe and set dressing 'will be handled'.

With TillyGen

TillyGen's breakdown lives in the same system as shotlist and schedule, so an added scene updates the plan instead of five separate documents.

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

Do corporate videos without a classic script need a breakdown?

Yes, in lighter form: interview blocks, b-roll situations and demo actions each get elements, people and flags. The format shrinks; the inventory logic stays.

What are script eighths?

A page divided into eight parts, used as a rough effort measure per scene. An eighth of a page of dialogue and an eighth of a car chase are not equal — the measure starts the conversation, it does not end it.

When in pre-production does the breakdown happen?

Directly after script lock and before scheduling, because the schedule is built from the breakdown's sorted elements — not from the script itself.

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.