Storyboards and shot lists: the picture and the checklist

Two different questions

A storyboard is a visual plan — a frame drawn for each intended shot, sequenced so the director and the client can read the scene before it exists: blocking, composition, and how the cuts will flow. It answers 'will this scene work as filmmaking?' and it earns its keep in prep, in pitch meetings, and on any sequence where the geometry matters — action, effects, complex camera moves.

A shot list is the operational counterpart: a line for every shot to capture, with size, angle, movement, lens and the equipment each implies. It answers 'what must the unit actually get today?' and it's the document the assistant directors, camera and lighting departments build the day around.

Coverage is the logic that binds them

Underneath both documents sits coverage: the master that establishes the scene, the coverage angles that let it be cut, the inserts and cutaways that protect the edit. A storyboard shows the shots the scene is designed around; a shot list must additionally carry the unglamorous shots the edit will quietly need — reaction holds, clean plates, the matching cutaway that saves a broken match cut.

The failure mode of skipping the list is a wrapped scene that can't be assembled; the failure mode of skipping the board is a scene that assembles and doesn't work. Productions with both rarely have either problem, and the two documents cross-check each other: every boarded shot on the list, and every listed shot earning its place against the design.

• •Board: how the scene reads — composition, blocking, cut flow.
• •List: what the unit captures — size, lens, movement, equipment.
• •Coverage sits under both: design shots plus the shots the edit needs.

Drift, and the cost of it

Both documents are built against a version of the script, and scripts change — pages are revised, scenes are combined, a location is lost and the scene is redesigned for its replacement. When the board and the list don't move with the script, the unit ends up working from one document, the client approved another, and the edit discovers the third. By shoot day three of any change, the disagreements are expensive.

The operational defense is to treat both as living, versioned artifacts tied to the scene data — a revision to a scene flags the board frames and list shots that reference it, rather than trusting someone to remember which scenes were touched.

From the page to the day

Both documents eventually feed the same downstream consumers: the schedule takes its per-scene workload estimate partly from shot counts; the call sheet's scene schedule reflects what the unit intends to capture; and the director's review of the day checks what was got against what was listed. A shot list that feeds the stripboard makes the day's plan realistic in both directions — enough time listed to shoot what's listed.

On the day, the list becomes the working checklist: shots struck as captured, holds noted, anything abandoned recorded rather than forgotten, so the wrap conversation about a scene is grounded in the same document everyone started from.

How Clarice handles this

Clarice keeps both on the project: a storyboard canvas where frames are drawn or attached per scene and sequenced, and a shot list where every shot carries its scene, size, lens, movement, notes and done state. Shots reference the scenes the schedule was built from, so revisions flag the work that references them.

Shot counts roll into the scheduling and daily-reporting surfaces, and the day's captured shots reconcile against the plan on the production day sheet — so 'did we get the day' is a query against the list, not a conversation from memory.