A storyboard shows what a shot looks like. A shot list is the document that gets it filmed: the ordered, numbered list a first AD calls out on set, a DP checks against, and a script supervisor uses to confirm coverage before the company moves on. Skip it and a scene gets "covered" in whatever order felt natural on the day, which is how crews end up re-lighting a setup they already struck.
Here's how to build one that a crew can actually run on.
Start From Coverage, Not Inspiration
The instinct is to list shots in the order they occur to you while reading the scene. That's how you end up with a shot list that looks complete on paper and leaves a gap in the edit. Work scene by scene from a fixed checklist instead:
The master. One shot that covers the whole scene, wide enough to hold every actor and every piece of blocking. If nothing else survives the day, the master lets an editor cut something together.
Coverage on each speaking character. Medium or close, matched in scale to whoever they're talking to. This is what most of the scene will actually be cut from.
Reaction shots. The character not speaking is usually doing more storytelling than the one who is. Don't assume the master captured a reaction well enough to hold on.
Inserts. A hand reaching for something, a phone screen, a door lock turning. Small, but frequently the shot that saves a scene in the edit when a performance take has a flaw everywhere else.
The button. However the scene ends, on what image, on whose face, in what shot scale. Decide before the day, not after four takes of the master.
Working the checklist scene by scene is slower than free-associating a list, but it's the difference between a shot list and a wish list.
Group by Setup, Not by Story Order
A screenplay is chronological. A shot list should not be. Once you know every shot a scene needs, the next pass is grouping them by camera position and lighting setup, not by the order they'll appear on screen.
If three shots across two scenes share a lens, a light, and roughly the same camera position, shoot them back to back regardless of which scene they belong to. Every setup change costs time that doesn't appear in a script page count, and a shot list organized by story beat instead of by setup is quietly asking the crew to relight the same corner of a room three times in one day.
This is also where a shot list earns its place over a shooting script alone: it's the layer that turns "what happens in the story" into "what the crew does, in what order, to get it."
Specify What the Crew Actually Needs
A shot list entry that just says "Sarah reacts" is not useful on set. Every line needs enough information that a first AD can call it and a camera operator can frame it without asking a follow-up question:
- Shot scale: wide, medium, close, insert.
- Camera movement: static, pan, handheld, dolly.
- Lens or approximate focal length, if the DP works that way.
- What's in frame: which characters, which part of the set, what's foreground versus background.
- Duration or action beat: what has to happen inside the shot before it's a take, not just a frame.
None of this needs to be exhaustive prose. A shot list is read at a glance between setups, not studied. Short, specific lines beat detailed ones that take longer to parse than the shot takes to light.
Number Every Shot, and Never Renumber
Every shot gets a number the moment it's added to the list, and that number is permanent. A scene supervisor, a DIT, and an editor all refer to takes by shot number, and a shot list that gets renumbered mid-production breaks every piece of paperwork that referenced the old numbers, including camera reports and sound logs that have already been filed.
Add shots during production under a new number, not by inserting into the existing sequence. If shot 14 turns out to need a companion insert that wasn't planned, it becomes 14A, not a renumbered 15 that shifts every shot after it.
Build It From the Scene Breakdown, Not From Scratch
A shot list isn't independent of the rest of prep; it's downstream of the scene breakdown. The breakdown already tells you every character, location, and prop in a scene. The shot list is where that information turns into camera decisions: which of those characters get coverage, in what order the elements appear on screen, what's in frame when.
In plotwell, the shot list lives next to the scene breakdown and the storyboard rather than as a separate document assembled by hand. Pull a scene's breakdown in, and the cast, location, and element data is already there instead of retyped. Attach panels from the storyboard to each shot line so the list carries the visual reference along with the technical one, and a first AD calling shot 14 is looking at the same frame the director boarded, not reconstructing it from a text description.
A shot list built this way stays in sync with the rest of prep automatically. One built in a separate spreadsheet drifts the moment a scene gets revised, and nobody notices until the AD is calling a shot for a character who got cut from the scene two drafts ago.
