B-roll shot list template
B-roll is not the material left over after the main work. It is the material that makes the main work cuttable.
What this is about
The difference to a normal shot list is the starting point. A scene shot list begins with the script and sorts by setup; a b-roll list begins with the problems the edit already knows it will have — a jump cut to hide, an interview that needs air, a location the viewer has never seen, a transition between two days. Framed that way, the list stops being a wish for atmosphere and becomes an inventory with a purpose per line. It is also the list that gets shot in the gaps, which is exactly why it has to be written down: nobody improvises coverage well at 17:50.
A template is the starting point, not the goal: once it has been filled in by hand twice, it is worth asking whether the document should come out of the plan instead.
What runs differently here
Where this differs from the general case:
- A purpose column stating what each shot solves in the edit — covering a cut, establishing a place, carrying a voice-over, bridging two scenes
- Duration guidance per shot, because a cutaway held for two seconds is unusable where the cut needs six and a slow move needs longer still
- Grouping by location and time of day rather than by topic, since b-roll is gathered opportunistically wherever the unit already stands
- A note on movement and stability per shot: handheld atmosphere and a locked-off insert are not interchangeable when the edit wants either
- Sound recorded with the image where it exists — room tone, machines, footsteps — marked per shot, because silent b-roll needs paid library sound later
Step by step
This order gets you there fastest:
- Go through the planned edit structure and note every place where the cut will need something that is not the main action.
- Turn each of those places into a shot with a stated purpose, so no line on the list exists only because the image sounds nice.
- Add the establishing images the viewer needs to understand where they are, including the exterior nobody thinks of until the assembly.
- Set a minimum duration per shot and tell the camera team, because the usable take is almost always the one that ran longer than felt necessary.
- Cluster the list by location and time of day and slot the clusters into the schedule where the unit is already standing there.
- Record room tone and relevant sound at each location and mark on the list which shots came with usable audio.
- Tick off items during the shoot and review the open ones before leaving a location for the last time.
Common pitfalls
What most often goes wrong in practice:
- Shots collected without a purpose, producing an hour of attractive material that solves none of the problems the assembly actually has
- Cutaways held too briefly, so the only usable ones are the takes where the operator forgot to stop
- Leaving b-roll to the end of the day, when the light has changed and the location is being struck around the camera
- No room tone, which turns every b-roll sequence into a sound design task that nobody scheduled
With TillyGen
TillyGen holds the planned edit structure alongside the shot list, so the coverage a sequence will need appears as its own entries in the day it can actually be shot.
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
How much b-roll is enough?
Count the problems, not the minutes. Every cut you intend to cover, every voice-over passage and every location change needs at least one usable option, and one option is not a plan for a passage that runs a minute.
How does this differ from the normal shot list?
The scene shot list works from the script and is sorted by setup for shooting efficiency. The b-roll list works backwards from the edit and is sorted by location, because it is gathered wherever the unit already happens to be.
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.