A useful shot list starts with the edit.
List the deliverables, identify the moments each cut needs, specify the coverage, group it into practical setups and review the order against actual constraints. StudioBinder, Shot Lister and Storyflow are useful candidates for different parts of that process. The right choice is the source the client, crew and editor can actually use.
A video brief can contain several different films.
A narrative scene usually begins with dramatic action that the camera must express. A commissioned video brief may instead contain several outputs: a website film, a short interview, vertical extracts, a demonstration and still frames. Each output needs a clear purpose and a usable combination of picture and sound. “Capture content” does not tell the camera operator which moment the final edit depends on.
Write the expected files before choosing individual shots. Identify format, intended destination, approximate editorial scope and any required message or product action. Resolve vague plurals such as “social clips” with the person responsible for the deliverables. The number and duration should come from the engagement and the audience need, not a universal production template.
Then ask which moments the cut cannot work without. A product explanation may require a readable action, a result and the relevant qualification. An interview needs the answer and pictures that support it. A brand film may need people, process and place. These moments supply the reason for the coverage rather than an arbitrary list of attractive angles.
A-roll and B-roll serve the explanation together.
A-roll often carries the main action or spoken argument. B-roll can illustrate a claim, establish context or make a spoken edit visually coherent. These labels describe editorial roles, not importance. A close-up showing the essential product behavior may be the most important shot even if it sits under narration.
For each must-have moment, identify the sound or action carrying it and the supporting pictures needed. “General B-roll” is too vague when the interview discusses a specific process. Plan the real object, person or step the editor will need to show, and check whether that subject will still be available after the interview.
Test six handoffs in the same project.
From brief to draft.
Bring the same representative brief or script to each candidate. Check whether its first structure preserves the required deliverables and source context. An AI-generated list can help surface possibilities, but the director still needs to review physical feasibility, continuity, factual claims and what the editor actually requires.
From intent to shot specifications.
Record the subject and action, framing, movement, sound and relevant technical constraints. Choose columns the crew will use. StudioBinder’s documented technical choices and script-linked structure, Shot Lister’s customizable categories and Storyflow’s connected planning route are different starting points. Inspect the actual required plan and editable source.
From words to frames.
A reference can clarify composition or lighting, but it needs a reason: what should be carried into the shot and what should not? Identify whether an image is a target frame, a mood reference or a storyboard. Keep the shot ID connected to the reference and preserve source context when sharing.
From coverage to shooting order.
Group related work into setups, enter estimates and place fixed windows. Compare how the candidate handles reordering and changes. A minute total is arithmetic based on entered assumptions. The source cannot infer access, talent availability or an unrecorded relight simply because it has a schedule view.
From preparation to sign-off.
Give the client the relevant creative decisions and give the crew the practical coverage and order. Test the actual recipient link. Comments are useful feedback, but the team should define how the selected version and approval are recorded. One person should maintain the source when a requested change affects several shots.
From the plan to the set.
Test the actual device, connectivity and reading format expected on the day. Identify who records completion, missing coverage and changes. A planned shot becoming “done” should mean something agreed: recorded, reviewed or selected for the editor are different states.
These are editorial decision tests based on current public primary documents, not authenticated vendor trials or a numerical ranking. A product may serve more than one stage. The trial should demonstrate the handoffs required by your production rather than reward the longest feature list.
Seven steps from deliverables to the crew.
Write the outputs and their purpose.
Give each required cut an identifiable name and destination. Record the orientation and any specific material the client expects. If one interview must support both a complete answer and several short extracts, identify those separate editorial jobs before recording.
Identify the non-negotiable moments.
Write the actions, statements or details each output needs. Connect a moment to the deliverable it supports. Ask what would make that moment unusable: an unreadable label, an absent person, a noisy answer or a missing demonstration step. These risks guide the coverage and preparation.
Pair the core with its support.
For each spoken or action-led moment, list the pictures and sound needed around it. An interview claim about assembling a product needs the relevant process, not unrelated room decoration. An event speech may need audience context and a reliable audio route. Review these relationships with the editor when possible.
Specify the shot in practical language.
Use a recognizable subject and observable action: “Technician locks the wheel and checks the brake lever” is more actionable than “cinematic workshop.” Add framing, movement, audio and technical detail where it affects production. Keep the on-set summary readable and preserve longer explanation in notes.
Group by the setup that actually changes.
A setup can involve camera position, lighting, sound arrangement, background or required talent. Several shots may share it. Record the setup cost separately from the time for individual shots when that helps the crew understand the estimate. Do not count a shared lighting change again for every close-up, and do not omit it entirely.
Place the constraints before optimizing the order.
Talent availability, venue access, daylight, event timing and equipment can determine what moves. Put those constraints into the plan, then reduce unnecessary location and lighting changes where practical. Review the resulting order with the person responsible for running the day. A convenient visual sequence is not automatically the best shooting sequence.
Agree priorities and hand over the current version.
Define a small priority system in terms the team understands. Essential coverage should be distinguishable from useful extras. Ask the client and crew to review the actual version before the shoot while changes are still practical. On set, record completed and missing material and carry the marked source to the editor at wrap.
Columns should answer a crew member’s question.
Practical source fields| Field | Question it answers | Useful example |
|---|
| Shot ID | Which planned piece are we discussing? | W-04, retained through reordering |
| Subject and action | What must be visible? | Technician releases brake after checking cable |
| Framing and movement | How should the action read? | Close detail, locked position |
| Audio | Which sound does the edit need? | Demonstration explanation plus tool sound |
| Deliverable | Which cut depends on it? | Main repair explainer and vertical excerpt |
| Orientation | Which destination must remain usable? | Horizontal source plus separately reviewed vertical framing |
| Setup | Which work can share preparation? | Workbench side light, camera near tool rack |
| Estimate | What assumption is in the order? | Entered prep and shot minutes, reviewed by crew |
| Priority | What survives if time changes? | Essential demonstration step |
| Status and notes | What happened and what remains? | Recorded; insert still needed for revised explanation |
Lens, frame rate, talent, props and source references can also matter. Add them where they affect the work. A slow-motion intention, for example, needs a production decision before recording rather than a vague request after the shoot. Avoid giving every small production a large table of unused technical fields.
The workbench below preserves its own explicit fields, including item kind, shot, scene, deliverable, setup, description, framing, movement, audio, priority, entered minutes, completion and full notes. Use notes for additional context and export the full source. Its CSV is a documented interchange source, not a promise that every vendor accepts the same schema.
Four starting lists for different shoots.
An interview.
Begin with the primary spoken coverage and its audio arrangement. If a second angle serves the edit, define its role and relationship to the primary view. Include the room or environment sound required for the intended audio edit, then identify the actual objects and actions discussed in the answers.
Plan supporting pictures while the subject and location are still available. A person explaining a repair should be seen performing the relevant action, not simply walking through a room. Capture the beginning, action and result with usable edit boundaries. Review the final list against the questions being asked rather than prescribing a fixed quantity of B-roll.
A product or brand film.
List the product behavior, details and context the audience needs to understand. Include any required hero view, but do not let it displace essential demonstration coverage. A brand story may also require the people, process and place that support its claim.
Identify product condition, continuity, readable labeling and any technical shot needs. If the concept includes slow motion or a moving close-up, confirm that the equipment, light and action support it. Treat the generated storyboard as a proposal and test whether the actual product can perform what it depicts.
Vertical social material.
Write the purpose of each short piece and the visual information it must retain. Test face placement, hand actions, product details and the planned title or caption treatment in the actual vertical frame. A horizontal view with a centered face may still lose the object or explanatory gesture.
Batch shots that share a practical setup when it helps, but keep the individual deliverables clear. A single performance may supply several versions only if each preserves a coherent thought. Record the selected wording and orientation requirement so the editor does not have to guess why the take was captured.
An event.
Use the current run of show and access arrangement as constraints. Identify the non-repeatable moments, camera positions and actual sound route. An event cannot be rearranged like a staged product demonstration. Required sponsor material or contractual coverage should be explicitly named and prioritized.
Plan where the crew must be before the moment begins. Check whether one camera can realistically cover two simultaneous jobs. Update the list when the program changes, and record missed material honestly. Context, reactions and details help the edit, but they do not replace an essential event moment that was never recorded.
Order the day and preserve enough coverage.
Distinguish story order from shooting order.
The final cut may begin outside, move to an interview and finish on a product detail. The efficient shooting order may group the interview and details under one light before going outside during the relevant window. Preserve stable shot IDs so reordering the day does not erase the relationship to the edit.
Review the order against talent, access, equipment and sound. Include preparation, moves, breaks and other required non-shot activity. The local workbench makes setup and break items explicit and totals entered minutes. It does not create a call sheet, optimize constraints or simulate the changing set.
Use priority to make a decision under pressure.
A priority should explain what the edit loses if the shot is omitted. Essential coverage supports a required action or claim; useful coverage strengthens the piece; optional coverage can be cut if circumstances change. Discuss this distinction before the day so the crew does not protect an attractive extra while losing the needed demonstration.
When time changes, review the remaining essential moments, dependencies and available subjects. Reducing the estimated minutes without changing the work does not create time. Revise the actual plan and communicate the decision through the responsible person.
Capture an editable action, not a collection of sizes.
Different shot sizes and an insert can help express context, action and detail. They are possibilities to examine rather than a universal requirement to shoot every moment three times. Ask whether the viewer can understand where the action occurs, what happens and why it matters. Choose coverage that supports that explanation.
Leave usable beginnings and endings around actions according to the editor’s needs. Check eyelines, screen direction and continuity when moving between views. For an interview, identify the points where the editor may need supporting pictures and capture relevant real material. The required quantity depends on the answer, edit style and available source, not a fixed B-roll-to-interview ratio.
Review horizontal and vertical requirements separately.
If both orientations matter, inspect the actual intended crops or capture separate framings where necessary. Preserve the subject, object and action in each. Test the planned captions and interface overlays for the destination, since an otherwise usable picture may leave no readable place for the words.
Mark which shots support both versions and which need separate treatment. This makes the editor’s choice explicit and helps the crew see what cannot be recovered later by cropping.
A worked shoot for a bicycle repair studio.
Consider a fictional independent bicycle workshop producing a main service explainer, a mechanic interview and several vertical demonstrations. The audience needs to understand what a brake check includes before booking. This is an original planning example, not a claim about a tested client production or a standard one-day output quota.
Connect the deliverables to real moments.
The main explainer needs an introduction, inspection, adjustment and a clear result. The interview supplies the mechanic’s explanation of why the check matters. The vertical pieces answer smaller questions, such as what the lever check shows. The client identifies the actual service scope and the claims that require careful wording.
The director lists the required moments and supporting pictures. A close-up of the lever action should show the relevant relationship between hand and mechanism. A tool detail may be useful context, but it cannot substitute for the actual check. The editor reviews the intended structure before the list becomes final.
Group the work into practical setups.
One setup covers the mechanic’s interview with its controlled sound. Another covers workbench actions and details. An exterior view depends on access and light. The crew enters preparation and shot estimates and checks when the mechanic and the actual bicycle are available.
Stable shot IDs connect the demonstration to its deliverable even when the order changes. A setup item makes the preparation assumption visible. A break item records required non-shot time. The list can then be read as both coverage and a manual day order without pretending every item is a camera shot.
Respond to a client change before the shoot.
The client asks to remove a claim suggesting every brake problem can be corrected by adjustment. The writer changes the spoken explanation, the director checks the related demonstration and the editor revises the intended short extract. A previous approval of the old wording should not silently cover the new version.
The shot list now identifies the narrower claim and the exact action needed to illustrate it. The client reviews the actual selected wording and references. The crew receives the revised source, not a message saying only that “the script changed.”
Run the manual order and preserve the result.
The operator imports the actual source CSV into the workbench, inspects every row and enters the intended start clock. Reordering a setup or shot changes the sequential arithmetic from entered minutes. The projected finish is an estimate, not a live tracking result or a guarantee that the production fits.
At wrap, the owner marks recorded coverage and notes the missing insert. The editor receives the full notes, stable identifiers and actual media source through the team’s handoff route. Completion in the tool does not prove that every take is usable; the editor still reviews the recorded result and any change from the plan.
Compare the solo route and the crew route.
A solo operator may need an editable list, references and a clear mobile or printed view. A crew of three to five may also need synchronized updates, distinct responsibilities and reviewer access. The required plan depends on those roles rather than the head count alone.
Check current official pricing and account entitlements for StudioBinder, Shot Lister and Storyflow. Identify which person edits, who only reads and which collaboration route the production requires. Confirm platform, locale, billing period and checkout before budgeting.
Shot Lister’s current page distinguishes optional Pro and Studio subscriptions and different crew-sync offerings. StudioBinder’s production project and Storyflow’s canvas are different purchasing contexts. A headline amount should not be multiplied into an invented equivalent crew package. Check the actual required features and supported collaborator arrangement.
Free access also needs a workflow test. Storyflow’s invited collaboration is distinct from its upcoming standalone Free route. A free app download does not establish that all storyboards or synchronization features are included. A simple spreadsheet may be enough when the team mainly needs a maintained source and a printed handoff.
Other ways to hold the source.
Google Sheets or Excel can work for a readable shared grid when the team already maintains one. Notion is a candidate when briefs and connected database pages already live there. Celtx is worth examining when screenplay or audiovisual-script context is central. Check current product and plan behavior rather than assuming a general writing tool lacks shot planning or AI.
A paper list can be useful on a small shoot if changes and source ownership are clear. A visual reference board can help communicate frames while another record holds the order. The important relationship is which source is current and how a changed shot reaches everyone who needs it.
Choose the category that matches the failure.
Try StudioBinder when the shot intent and production workflow need to stay connected. Try Shot Lister when the on-set order and current timing are the central problem. Try Storyflow when the brief, visual references and early draft are fragmented. If the main requirement is a specific offline set workflow, client sign-off record or live schedule behavior, verify that requirement directly before choosing a canvas.
Five mistakes and a practical pre-shoot check.
Starting with attractive angles instead of deliverables.
Identify the actual cuts and required moments first. A beautiful shot can be optional while an ordinary readable action is essential. Connect each item to its job in the edit.
Recording the interview without supporting pictures.
Map the likely answers to actual objects and actions. Plan that coverage while the subject and location are available. General room shots rarely solve every explanatory gap.
Waiting until the set for the client’s first review.
Show the relevant creative decisions and claims early enough for practical changes. Identify the version and requested response. A comment on an old reference is not necessarily approval of the final plan.
Leaving priority implicit.
State which coverage the required cut depends on and which can be dropped. Review that choice with the responsible people before the schedule changes under pressure.
Separating the list, frames and order without explaining their relationship.
Connect stable IDs and current source links. One person should maintain consistency when a shot changes. Several tools can coexist, but the crew should not have to guess which copy is authoritative.
Before the next shoot.
Confirm the deliverables and their orientations, required moments, actual subjects and assets, audio needs, setup assumptions, access and talent windows, entered estimates, priorities and recipient access. Open the crew handoff on the intended device. Identify who records changes and who carries the marked source to the editor. Keep the production’s permissions, logistics and safety arrangements in the appropriate real workflow; the shot-list arithmetic does not replace them.
Questions before the crew arrives.
How do I make a shot list for a video shoot?
Start with the required deliverables and the moments each edit needs. Specify the core and supporting coverage, practical setup and entered time assumptions. Place fixed constraints, agree priorities and share the current version for review. Record the result on set and carry the marked source to the editor.
What should the list include?
Use stable shot IDs, a clear subject and action, relevant framing and movement, audio, deliverable, orientation, setup, entered estimate, priority and status. Add source references, talent, props or technical details when they affect the work. Preserve longer explanations in full notes rather than making the on-set list unreadable.
Which app is best?
Test StudioBinder for connected production planning, Shot Lister for a day-running workflow and Storyflow for a visual brief and draft context. These are starting matches based on current documentation. The best fit depends on required access, devices, references and schedule behavior, not a universal score.
Should I choose StudioBinder or Storyflow?
Compare the actual relationship between your script, references, coverage and production records. StudioBinder documents structured shot specifications and production handoffs; Storyflow presents a connected visual planning route. Run a representative revision and test the client and crew views. Verify the exact required feature and plan before choosing.
Is Shot Lister useful for a video shoot?
It is a candidate when the shot-by-shot order and on-set timing are the central job. Its documented Live Mode and estimate behavior differ from a static preparation list. Test the actual device, offline route and collaboration arrangement your crew will use. A download alone does not establish that all required features are included.
Can AI make the list from a brief?
It can propose coverage from supplied context. The director and crew still need to check deliverables, physical feasibility, availability, continuity, audio and entered estimates. A fluent list may invent a location or miss the essential action. Review the proposal before treating it as a production commitment.
How many shots should I plan?
Plan enough to express the required moments and give the editor usable options within the real production constraints. There is no universal count. Review each shot’s role, identify essential coverage and distinguish optional extras. A longer list is not evidence that the edit will be clearer.
How should the shooting order work?
Place immovable windows first, then consider location, setup changes, subject availability and practical preparation. Preserve stable IDs when reordering. Include required non-shot activity and review the order with the person running the day. Story order and shooting order often differ.
How much B-roll does an interview need?
Map the expected answers to real objects and actions the viewer should see. Capture usable edit boundaries and enough relevant material for the intended structure. A fixed ratio or number of seconds cannot decide this for every interview. Consult the editor and protect access to the subject and location while recording support.
How is a shot list different from a storyboard?
A shot list records the planned coverage and practical specifications. A storyboard visualizes a selected frame or sequence. They can support one another when stable IDs and current versions connect them. A reference frame should explain its role rather than silently becoming a mandatory composition.
Can I use Google Sheets or Notion?
Yes, if the team can maintain the source, read the practical fields and find the current references. Test sharing and the expected on-set format. A general source can be enough for a small production; use a specialized route when an observed scheduling, permission or workflow requirement needs it.
How should vertical shots be planned?
Identify the actual destination and inspect its frame, relevant overlays and caption treatment. Protect the important face, object and action or plan a separate take where needed. Do not assume centering a horizontal subject guarantees a useful vertical crop. Mark which deliverables each shot supports.
How should an event list work?
Follow the current run of show and the practical access arrangement. Identify non-repeatable moments, camera positions and sound sources, and check simultaneous coverage needs. Update the source when the event program changes. A staged-shoot order cannot move a real event moment.
Is Storyflow free?
Current pricing distinguishes invited collaboration from standalone access. Invited collaborators can have a free route while the standalone Free plan remains upcoming. Check the current account arrangement and required capabilities rather than treating those routes as equivalent.
Can a client view the plan without an account?
Storyflow describes sharing routes, but test the actual current link and required content as the client will receive it. Reading and commenting can have different access requirements. The same practical recipient test applies to other vendors. Identify which version the client saw and what decision is being requested.
Does the workbench run the set automatically?
No. It holds an editable manual order, totals entered minutes and exports full source and handoff notes. It does not optimize constraints, track live production timing, edit media or generate a call sheet. Reordering changes the arithmetic; the crew must still review whether the order is practical.