What Makes a Good Shot List (and Why Templates Fall Short)

Search for a shot list and you will find a hundred templates: a blank grid with columns for scene, shot, size, angle, lens, and a description waiting to be filled. The grid is not the hard part. A good shot list is not the one with the most rows filled in. It is the one where every shot can say why it is there.

This is about what separates a shot list that helps from one that just exists, and why a blank template is the wrong place to start.

What a shot list is actually for

A shot list does three jobs. It records the decisions you made about how to tell the scene. It communicates those decisions to the people who execute them, your DP, your AD, your crew. And it gives you a reference on the day, so the plan survives contact with a busy set. All three jobs are about intent. A list that captures specs but not intent does the first job badly and the others not at all.

The fields that matter, and the ones that mislead

The executional columns are real and necessary: size, angle, movement, lens, a rough length. A crew needs them. But on their own they describe a shot without explaining it. "MS, eye level, 50mm, static" tells the camera team what to build and tells you nothing about whether the shot should exist.

The fields that make a list good are the ones most templates leave out: what beat the shot serves, and why this treatment and not another. A shot that carries its purpose can be defended, cut, or improved on purpose. A shot that is only specs can only be executed.

Why templates fall short

A blank template has a quiet bias: it invites you to fill it. Rows want occupants, columns want entries, and before long you have a tidy table of shots nobody decided to need. The template has no notion of the beat a shot serves, so it cannot tell you that two of your setups are covering the same moment. It does not get shorter when the scene calls for less. It treats a five-shot scene and a fifteen-shot scene as the same task: fill the grid.

A template is a container. It holds a considered list and a thoughtless one equally well, which is the problem. The thinking has to come from somewhere else.

What a good list looks like

It is usually shorter than you expect. Every shot can name the beat it belongs to. The moment the scene turns on gets its own treatment instead of being buried in a master. A DP or AD can read it once and understand the intent, not just the specs. And it survives a change to the script: when a line moves or a beat is cut, you can see which shots are affected and which are not.

The common failure modes

Over-listing, where coverage anxiety produces a shot for every possible angle and the list becomes a wish rather than a plan. Specs without reasons, where every row is technically complete and none of them is justified. And a list divorced from the script, a freestanding table that no longer connects to the scene it came from, so nobody can tell why a row is there or what happens to it when the writing changes.

Where Decoupa fits

A good shot list is a record of decisions, and that is what Decoupa is built to produce. It turns your screenplay into a first-pass list you shape by hand, with every shot tied to the beat it serves and a short line on why this size and this angle. The reasoning sits next to the shot, and the list stays connected to the script it came from, so it never becomes a grid you fill for its own sake. You are the director; the list just keeps your decisions in view. See how it works