How to Break Down a Script, Step by Step

Breaking down a script means going through it page by page and flagging every physical thing each scene needs to shoot, then organizing those flags into a document your department heads can actually plan against. It's the first real production task on any project, and it's the foundation everything else — the schedule, the budget, the call sheets — gets built on. If you're new to the concept entirely, start with what a script breakdown actually is; this post is the how-to.

There's no shortcut around doing this carefully. A missed prop or an uncounted extra on page 40 turns into a scramble on set. Here's the process, start to finish.

Step 1: Read the script once for story, no marking

Before you tag anything, read the whole script straight through like an audience member. Don't highlight, don't take notes beyond stray thoughts. You're building a mental map of the story — who's in it, where it goes, what the tone is, whether it's a bottle episode in one apartment or something that jumps continents. This matters because breakdown decisions later (is that a "day player" or a "featured extra," is that gunshot a stunt or a sound effect) go faster and more accurately when you already understand the scene's context instead of parsing it cold.

Step 2: Do a line-by-line pass, scene by scene

Now go back to page one and work through the script scene by scene, line by line, tagging every breakdown element as you hit it. The standard categories, in the order most breakdown sheets list them, are:

Cast — any speaking or named character in the scene
Extras / background — non-speaking bodies (a crowd, diners, commuters)
Stunts — falls, fights, car hits, anything requiring a coordinator
Vehicles — cars, bikes, boats, anything that drives, floats, or flies on camera
Animals — pets, livestock, wildlife, and their wranglers
Special effects — practical effects: squibs, rain, fire, breakaway glass
Props — anything an actor picks up, carries, or uses
Wardrobe — anything notable beyond a character's everyday look (uniforms, costumes, a torn shirt)
Makeup / hair — special makeup effects, wounds, aging, wigs
Set dressing — anything that lives in the space but nobody touches (furniture, signage, dressing on a wall)
Sound effects — anything requiring a specific recorded or sourced sound
Music — a song playing in scene, a character singing, a needle-drop
Special equipment — cranes, underwater rigs, drones, anything beyond your standard camera package
Security / other — permits, police presence, crowd control, anything logistical the scene triggers

Go element by element, not category by category — read the scene once for cast, once for props, and you'll burn a full day on a feature. Instead, work down the page and flag everything you see in a single pass per scene, then double-check against the category list before moving on.

Step 3: Mark it on paper, or tag it digitally

Traditionally this pass happens with a stack of highlighters, one color per category, run down the physical page — a pink line under a prop, a green line under wardrobe, and so on. If you want the actual color-to-category standard, that's covered in full in our breakdown color guide; we won't repeat it here.

The paper method works, but it doesn't scale past a short or a small feature without becoming a filing problem — you end up with a script binder full of marked pages that someone then has to manually retype into a spreadsheet. Doing this digitally against an imported script file skips that retyping step entirely: you highlight or click a piece of text, tag it as a category, and the tag is attached to the scene and the script permanently. Production Slate works this way — you import a script (we support both major screenplay file formats, see Final Draft vs. Fountain if you're not sure which one you're using), then tag elements directly against the on-screen text instead of marking a printed page. The tags live with the scene from day one, so there's no second pass to transcribe anything.

Step 4: Turn marked scenes into per-scene breakdown sheets

Once a scene is fully tagged — cast, props, wardrobe, everything — that scene's tags get pulled into a breakdown sheet: one page (physical or digital) per scene, listing every element by category along with the scene's heading, location, time of day, and page length. This is the document a department head actually reads. A wardrobe supervisor doesn't want to read your whole script; they want the fifteen breakdown sheets that mention wardrobe, in order.

We won't rebuild the sheet format here — there's a full breakdown sheet layout, with every field explained, in our breakdown sheet template post. Use that as your reference for what a finished sheet should contain.

Step 5: Roll the sheets into a one-liner and a schedule

With every scene broken down, you have what you need to build a one-liner schedule — a single-line-per-scene summary showing scene number, set, cast, and page count — and from there a full stripboard. The breakdown is what makes the stripboard possible: you can't group scenes by location or cast availability if you don't already know which scenes need which people and things. Page counts, incidentally, are usually tracked in eighths rather than whole pages; if that's unfamiliar, see what an eighth of a page is.

A worked mini-example

Say scene 14 reads: INT. DINER - NIGHT. MARA (30s, waitress) pours coffee for JOEL, who sets his revolver on the counter. A radio plays softly. Behind them, three late-night regulars sit at the counter.

Tagged out, that scene produces:

Cast: Mara, Joel
Extras: 3 background diners
Props: coffee pot, revolver (non-firing prop)
Set dressing: diner counter, radio
Sound: radio music (needle-drop or library cue - flag for music clearance)
Wardrobe: Mara's waitress uniform

That's six category flags off three sentences of script — which is normal. A single scene routinely touches four to eight categories once you're actually looking line by line instead of skimming for the obvious ones (here, most people catch the revolver and miss the radio cue until someone asks who's clearing the music).

Breaking down a script inside Production Slate

Production Slate is built so the breakdown, the one-liner, and the stripboard are the same data set instead of three separate documents you keep re-syncing by hand. Tag elements straight against your imported script, and those tags flow into scene records your schedule and budget already read from. See how it works on the script breakdown feature page.