A practical video shot list

Make the next
shot obvious.

One row should tell the crew what to capture, how to approach it, why it matters and whether it still needs shooting. Start with twelve useful columns, then keep the list current.

Original illustration of three planned camera shots and their capture checklist

Twelve columns.
One readable decision.

A shot list is a plan of individual shots, not the screenplay or a call sheet. This compact framework combines closely related details so a small video crew can scan it quickly. Twelve is an editorial starting point, not an industry mandate; add separate technical fields in your wider production system when the job needs them.

ColumnWhat to recordFilled example
SceneThe script scene or content block.Workshop
Shot IDA stable reference that survives reordering.W-03
Action / descriptionExactly what the camera should capture.Hands lower the lamp onto the bench.
Purpose / coverageWhy the edit needs this shot.Reveal the repaired object.
Framing / angleShot size and camera relationship.Close-up, eye level.
MovementThe intended camera move.Static.
Lens / gearVerified lens and equipment requirements.Chosen macro lens; locked tripod.
Setup / locationThe setup label and actual shooting space.Bench setup, verified workshop.
PerformersWho is needed for the frame or performance.Maker’s hands.
SoundDialogue, sync sound or intended audio handling.Record clean object placement sound.
PriorityMust-have or optional, decided by the team.Must-have.
StatusThe crew’s actual capture record.Pending.

Scene and shot references, description, framing, movement, lens and equipment are established shot-list details in StudioBinder’s official guide. Purpose, priority and status make this compact template useful as an editing-coverage checklist. Keep IDs stable when shooting order changes; “captured” here is a manual status, not proof that the take is usable.

Write the action clearly.

“Close-up” describes framing, not the event. Add the gesture, object or line that must appear. An editor should be able to understand what coverage was intended from the description alone.

Group by real setup.

Put shots that share a location and lighting arrangement together when the team judges it practical. Do not assume this automatically produces the fastest schedule; actor availability, continuity and access can change the order.

Review the must-haves.

A wide context shot, an action shot and a detail can serve different editing needs. Their necessity depends on the actual brief and scene. Use the purpose field to explain the coverage rather than assigning an invented quality score.

Record the remaining work.

Use Pending, Captured or Pickup. Write why a pickup is required in the notes. The checklist reports your entries; it does not inspect footage, infer approval or verify continuity.

The best home depends
on the production.

StudioBinder: detailed production shot lists

Its documented shot-list workflow supports technical fields, reference images, scene-based lists and PDF generation. Current support notes specify JPG and PNG reference uploads. Choose it when the shot list belongs inside a broader production system. Check your required plan and import limits rather than assuming every capability is free. Current shot-list help, official film template.

Milanote: visual references beside the shots

Its shot-list guide connects scene references, individual shots, extra notes and a gear list. Choose it when the visual explanation is as important as the tabular checklist. Keep each reference’s purpose explicit and cross-check the gear against the planned shots. Official shot-list guide.

Storyflow: a draft connected to the board

The shot-list page documents AI drafting from script or scene context alongside a visual plan. Treat the output as a starting draft: check coverage, real equipment and production details before shooting. Official generator page.

That page’s broad free wording must be read against the explicit pricing availability statement checked October 5, 2026: standalone access is paid-only during early access, invited collaboration is free today, and standalone Free is announced for before the end of 2026. No signup test was performed.

This builder: a portable manual checklist

Choose the local tool below when you want a lightweight list you can edit here or in a spreadsheet. ExcelJS 4.4.0 produces an actual XLSX workbook with the twelve shot columns, full notes, frozen headers and filtering. It does not generate shot ideas, synchronize a crew or replace a call sheet.

Product capabilities are drawn from official documentation checked October 5, 2026. Recommendations are editorial judgments, not account tests or measured efficiency claims.

Plan it.
Review it.
Update it.

Start with the deliverable.

Read the brief and script. List the moments the edit must communicate, then choose shots that actually cover those moments. A template cannot decide the story for you.

Walk the setup with the crew.

Review framing, movement, lens, sound and performer requirements together. Use confirmed location details and practical access. Resolve an equipment question before turning it into a requirement.

Leave a useful capture record.

Update the status and full notes on set. A missing detail should become a named pickup, not a vague memory. Save a versioned workbook or JSON before closing this page.

A workshop demonstration

Show the space, the making action and the finished object. Give each shot a coverage purpose rather than relying on three attractive frames.

Original illustrative examples, not tested productions.

Before the crew arrives

Verify performer availability, the actual location and the equipment list. Keep addresses and personal contact details in the appropriate controlled production document, rather than a widely shared creative board.

When the order changes

Reorder the rows while retaining shot IDs. The builder does not optimize a schedule. Check continuity, light, access and performance constraints before choosing a new order.

When a take needs repeating

Mark Pickup and explain the missing action, framing, sound or performance in full notes. A status count identifies entered work; it does not judge the media.

Plan coverage that survives a changed day.

A useful video shot list connects each intended camera setup to a specific editing need. It tells the crew what action to capture, how to frame it, what sound is required and why the shot matters. It also gives the production a record of remaining work. A list of scene titles cannot do that: one scene can need several camera setups, and one setup can cover moments from several parts of the final video.

Begin with an approved brief, outline, script or storyboard. Break the material into moments the viewer needs to understand, then decide how the camera and sound will cover them. Keep references stable while changing the shooting order. Review equipment and estimates with the people who will do the work, and mark essential coverage before the day becomes difficult.

This guide explains a camera-specification template alongside the compact workbook below. It compares seven possible homes for the list and provides an independent twenty-four-shot example. The example illustrates decisions, not an average production rate. Neither a fixed shot count nor a generic number of minutes guarantees that a two-minute video can be completed in one day.

Four jobs the document must perform.

Explain coverage. Each row should name the action and the reason the edit needs it. “Close-up” is a framing instruction, not a description of what happens. “Hands close the restored instrument case” is an action. “Complete the return-to-owner sequence” explains its editing purpose.

Expose production assumptions. A lens, movement or sound instruction can imply equipment, people and time. Identify unconfirmed choices rather than presenting them as booked resources. The director’s desired move still needs a practical review by the camera team.

Support shooting order. Group work around real camera positions, lighting states and access when that is appropriate. Protect performance, continuity, daylight and sound constraints. The row order can change without changing the identity of a shot already discussed with the editor.

Record remaining work. Captured, Pending and Pickup describe entered production status. A captured frame may still have unusable sound or a continuity problem. Keep the reason for a pickup in the notes and let the responsible people assess the actual footage.

Shot list, storyboard, schedule and call sheet.

A storyboard explains planned visual relationships with drawings, images or reference frames. A shot list specifies capture requirements. A shooting schedule assembles work into time and resource blocks. A call sheet communicates the operational day. These documents inform one another but do not become interchangeable because they share a project folder.

Write the first list early enough to influence equipment and access decisions. Revise it after the technical scout and creative review. When the client removes a sequence, review the dependent shots, storyboards and schedule together. Keep the approved source linked so a later reader can understand why a row exists.

Twelve camera fields, explained.

A camera specification can use Scene, Shot ID, Size, Angle, Movement, Lens, Subject, Action, Audio, Location, Setup Group and Time Estimate. These are useful fields rather than a universal mandate. The interactive workbook combines some technical fields and adds purpose, performers, priority and status. Keep a more detailed specification in your wider production system when the job needs it.

Scene and shot identity.

The scene field links the shot to a narrative scene or content block. The shot ID identifies the individual planned setup or coverage item. A scene-letter convention such as 4A and 4B can work well, but agree the production’s convention before issuing records. Avoid IDs based only on current row position: reordering should not change the reference used in camera notes and editorial discussion.

If a shot is deleted, retain a traceable revision record rather than reusing its identifier casually. Agree how inserted shots and letter revisions are named. Readability matters on small screens and handwritten records; choose a convention the crew can distinguish consistently.

Size, angle and movement.

Size describes how much of the subject appears in the frame: wide, medium, close-up, extreme close-up or a more specific agreed label. Angle describes the camera’s relationship to the subject, such as eye level or overhead. Movement describes the planned camera behaviour, such as static, pan, tilt or a supported moving shot.

Use a small shared vocabulary, then add a reference where the labels are insufficient. “Medium” does not establish identical framing across different aspect ratios. “Push in” does not specify whether the movement is physical or an editorial crop. Make those decisions with the camera and editing teams when the difference affects the job.

Lens and equipment.

Record a lens choice when it helps the camera team prepare. Verify the intended focal length and relevant equipment rather than filling every row with an imagined technical value. The same focal length behaves differently across camera formats. A phone or one-lens production may need a simpler note about camera position and available field of view.

Keep specialist equipment decisions practical. A slider, macro lens or stabilised move has implications for access, rigging, focus and crew. If the equipment is tentative, say so. Do not let a generated shot list become an unreviewed rental order.

Subject and action.

The subject identifies who or what receives attention. The action states the event the camera needs to record. Separate “instrument case” from “owner opens the case and checks the repaired clasp.” That specificity helps the director, performer and editor agree what the shot must contain.

When a row contains several distinct actions with different framing or continuity states, consider separate rows. Conversely, one planned continuous shot can legitimately contain several beats. The useful boundary is the production decision, not a rule that every sentence automatically becomes another camera setup.

Audio and location.

Specify whether a shot needs intelligible dialogue, synchronous action sound, a separately recorded sound element, room tone or deliberately silent footage. Agree sound terminology with the recordist. A visually suitable location can be unusable for an interview when machinery or public activity starts nearby.

Location should identify the practical space relevant to production. A story setting and an actual address are different things. Keep sensitive contact and access details in the appropriate controlled document. The shot list can refer to the practical location without becoming a public address book.

Setup group and estimate.

A setup group links rows that can share a meaningful camera or lighting arrangement. A common room is not necessarily one setup: turning the camera, changing lighting or resetting a product can require another block. Review the group with the crew rather than assigning letters merely to tidy the spreadsheet.

Estimates should identify what is included. If the group’s first row includes lighting and rigging, do not count that same setup cost again for every insert. Separate additional capture and reset time from shared preparation where your schedule supports it. Then account for transitions, breaks, rehearsals and other work outside shot rows.

How those fields map to the workbook.

The builder retains Scene, Shot ID, Action/Description, Purpose/Coverage, Framing/Angle, Movement, Lens/Gear, Setup/Location, Performers, Sound, Priority and Status. Use its combined fields clearly: “Group C · bench detail” in Setup/Location and “close-up · overhead” in Framing/Angle are readable examples. Subject can be part of the action and performer information.

The builder has no numeric timing engine or automatic schedule calculation. Record reviewed timing assumptions in the full project notes or a separate schedule. Do not claim that its status counts show hours remaining. Its XLSX, JSON and Markdown outputs preserve your entered checklist; they do not optimise a shoot or analyse footage.

Build the list in seven deliberate passes.

Control the source.

Identify the brief or script revision the list uses. If the creative idea is still vague, write the audience, intended message, output format, practical locations and available production window first. Name the person who approves changes. Retain a source reference alongside the exported list.

Identify the beats.

List the moments the viewer must understand: an arrival, a problem, a demonstration, an explanation, a result and the final action. These are editorial needs rather than a required sequence. A documentary observation and a product demonstration need different planning levels. Avoid inventing a predetermined number of beats for every duration.

Choose coverage for each beat.

Decide how the edit can communicate each moment. Context, action, reaction and detail may each serve a different function. An interview may need a reliable primary angle and visual coverage for edits, but another camera is not automatically required. Discuss continuity, screen direction and the intended cut with the director and editor.

Review the technical information.

Ask the camera and sound teams to confirm relevant framing, movement, lenses, equipment and audio. Use references to clarify ambiguous instructions. Keep unconfirmed values visible. A list made by the director alone is a starting proposal, not proof that the equipment fits the location.

Assign practical setup groups.

Group work that can share meaningful preparation, then identify transitions and resets. Consider how props and performances change state. Capturing the “before” detail after the repair is complete might require a duplicate object or become impossible. Setup convenience must respect continuity.

Estimate and reorder.

Review preparation, capture and reset estimates with the crew. Compare proposed shooting orders against access, light, sound and performer availability. Keep shot IDs stable. Add non-shot work in the schedule so a pleasing row total does not conceal an unworkable day.

Mark essentials and issue the version.

Identify coverage without which the agreed edit cannot work. Mark optional work separately. Share the current list with the camera, sound and production owners, and give the client an appropriate review view. Explain which creative decisions are being approved and which practical details remain open.

A filled example: an instrument repair film.

This fictional two-minute profile follows a local instrument repairer explaining a case repair and returning the instrument to its owner. The example uses twenty-four planned shots across eight groups. The count illustrates coverage and grouping, not a promise about required shots, shooting hours or professional repair technique. The real craftsperson would approve any process shown.

The story needs an arrival, an explanation, practical action, a checked result and a handover. Interview sound is recorded while the workshop is quiet. Detailed work is captured when the craftsperson can safely demonstrate it. The exterior depends on agreed light and access. Those constraints influence shooting order before the team chooses a lens.

Group / IDAction and coverage purposeFraming / moveSound and practical note
A · 1AOwner approaches the workshop; establish arrivalWide · staticExterior ambience; confirm pedestrian access
A · 1BOwner pauses at the entrance; connect subject to placeMedium · staticNatural action; maintain case position
A · 1CHand reaches the door; bridge the cut insideInsert · staticClean door sound; match hand and sleeve
B · 2ARepairer explains the problem; primary interviewMedium · staticReviewed microphone position; quiet window
B · 2BRepairer describes the check; supplementary framingCloser view · staticSame sound plan; record complete answer
B · 2CRepairer listens to owner’s question; usable reactionMedium · staticProtect natural context; avoid misleading edit
C · 3ACase lies on bench before work; establish starting stateWide bench detail · staticDocument continuity before alteration
C · 3BRepairer indicates the clasp; show the actual issueClose-up · staticCraftsperson confirms accurate description
C · 3COwner shows how the case closes; explain the problemHand detail · staticCapture useful action sound; review reset
D · 4ARepairer prepares the bench; connect preparation to actionMedium · staticPractical safe demonstration, not staged advice
D · 4BRepairer arranges the approved items; editorial bridgeOverhead detail · staticConfirm camera placement does not obstruct work
D · 4CHands begin the agreed demonstration; introduce processClose-up · staticRecord actual action sound
E · 5ARepairer performs the approved action; essential processMedium · staticFollow craftsperson’s working constraints
E · 5BDetail makes the change visible; explain the resultClose-up · staticConfirm repeatability before requesting reset
E · 5CRepairer checks alignment; demonstrate verificationDetail · staticRetain enough action for an intelligible cut
F · 6ACase closes after the check; show completed functionBench medium · staticRecord sync closure sound
F · 6BClasp detail shows the final state; compare with 3BMatched close-up · staticUse compatible framing for before/after
F · 6CRepairer signs the agreed record; complete the processInsert · staticUse authorised fictional or cleared information
G · 7AOwner receives the case; complete the handoverTwo-person medium · staticNatural exchange with intelligible sound
G · 7BOwner checks the closure; show personal outcomeClose-up · staticMatch final case state and handling
G · 7CRepairer responds; finish the interactionReaction medium · staticMaintain screen direction
H · 8AOwner leaves with the case; resolve arrivalWide · staticReview exterior light against 1A
H · 8BWorkshop interior returns to routine; closing contextWide · staticRecord suitable room tone separately
H · 8CApproved workshop sign ends the sequence; identityDetail · staticLeave room for agreed graphic treatment

The camera team supplies verified lens and rigging choices after the scout. The producer and crew estimate each preparation block and its additional work. The example avoids invented focal lengths and generic minute allowances because those decisions depend on the actual camera, location and demonstration.

Which shots protect the edit?

The essential set includes reliable interview sound, the visible starting problem, the approved process, the checked result and the handover. A second decorative exterior angle may be optional. A readable before/after detail may be essential if the interview describes a change the viewer otherwise cannot see. Priority follows the agreed story rather than how attractive a shot sounds.

How grouping changes the day.

The narrative begins outside, but shooting can begin with the quiet interview while the location allows clean sound. Bench work follows the practical process and its irreversible changes. Exterior coverage occurs when access and light are suitable. The arrival and departure still need compatible continuity even if captured together.

Groups C through F use one bench but are not automatically one identical setup. Overhead framing, detail coverage and practical work can require changes. Conversely, shots from different story sections can share a preparation block. The crew decides the actual grouping and includes resets, rather than letting alphabetic labels manufacture efficiency.

Entering the example into the builder.

Add each planned shot with a stable ID and a concrete description. Put its narrative reason in Purpose/Coverage, its group and practical space in Setup/Location, and its sound requirement in Sound. Record reviewed timing assumptions and unresolved decisions in full notes or the production schedule. Use Must-have only after the editorial review.

Filtering to Pickup changes the visible checklist, not the export contents. Save the full JSON and workbook before closing the browser. A marked Captured row is your record of progress; inspect the footage and sound before deciding the production no longer owes that coverage.

Seven homes for the list.

Storyflow: keep source and visual planning together.

Storyflow describes an AI shot-list workflow connected to creative material. Investigate it when the main problem is converting a script or storyboard into a reviewable proposal while retaining visual context. Test the result with an actual authorised brief, then correct the proposed action, coverage and setup group.

Ask whether the generated list explains each shot’s purpose and preserves the current source reference. A plausible table can still contain unavailable equipment or redundant coverage. Treat AI output as a draft reviewed by the director, camera team and producer. Demonstrate any required live tracking, export or call-sheet handoff rather than assuming visual planning provides every on-set function.

StudioBinder: connect shot specifications and production records.

StudioBinder documents script-linked shots, specifications, setup grouping, estimates and sharing. Its relevant trial is whether the creative source and practical production records stay connected after a change. Build the same small sequence, adjust a shot and inspect the view the team receives.

Check plan access for required features and the current recipient workflow. Confirm how shot status relates to the issued schedule and other documents. A producer’s editable shot list and a client’s view-only link should be tested separately. Do not infer a feature’s access level from the existence of a free signup button.

Shot Lister: test the person running the day.

Shot Lister documents shot-level scheduling and Live Mode, with additional subscription features for collaboration and other production needs. It is worth evaluating when someone actively maintains the plan while shooting. Trial it on the real device and with the person responsible for changes.

Move a setup, record progress and inspect how the current plan appears to collaborators under the intended account arrangement. Check relevant device and sync requirements, subscription scope and source exchange. A live schedule can be useful without becoming the authority for creative approval or media quality.

Google Sheets: a transparent table with a process owner.

Google’s documentation explains sorting, filtering and filter views. A spreadsheet is a useful candidate for a straightforward shoot because the team can build explicit columns and inspect the records. Freeze the header, use consistent values and sort the complete row range so shot descriptions remain attached to their identifiers.

Use filter views when different readers need different views without changing everyone’s working display. Confirm actual sharing permissions and keep one identifiable issued revision. A flexible sheet does not establish a revision process by itself. A person still needs to maintain the source, protect essential coverage and reconcile changes.

Notion: link shots to their context.

Notion documents database views, filters, sorts and groups. A shot database can link the brief, reference material, owner and open questions in one workspace. This is useful when preproduction discussion is as important as the eventual table.

Trial the production view on a phone and the export the crew would use. Confirm that each shot has a stable identifier and that a filtered view does not hide essential work from the issued plan. Database flexibility needs an agreed schema; a beautiful page with loosely named properties can be difficult to scan while the crew waits.

Celtx: evaluate the script-to-production connection.

Celtx presents writing and production workflows. It deserves a trial when the script or audiovisual material already lives there. Follow one source revision into the shot records and confirm the relevant production feature access in the current plan.

For a brand or corporate video, examine how audiovisual structure maps to practical capture. Verify the exported or shared list the production will actually use. A convenient writing home is a reason to investigate the workflow, not proof that every required on-set record is included.

Boords: visual approval before practical capture.

Boords presents storyboard and video preproduction workflows. It is a candidate when the client or director needs to review visual sequencing. Trial how an approved frame becomes a practical capture requirement, including sound, equipment and setup information.

A storyboard frame is not automatically a fully specified shot row. Keep frame identity, approved revisions and references traceable when transferring into the shooting list. Test the current export and review route, especially when the client needs comments but should not edit production records.

Use one controlled sample for every trial.

Compare the same short sequence with the same source, essential coverage and corrections. Test stable IDs, technical clarity, setup grouping, mobile readability, revision visibility and exports. Have an outside reviewer open the actual shared result. Product documentation supports feature scope; this controlled trial establishes whether the workflow fits your team.

Cost the workflow your crew will use.

A solo creator may need a portable table and dependable backups. A director and camera operator may need source-linked review and technical discussion. A crew with an assistant director maintaining live progress may benefit from a dedicated on-set workflow. An agency may need client approvals and a clear separation between creative review and production edits.

Compare current billing units: individual subscriptions, team access, project limits, AI consumption, required exports and extra services used for schedules or call sheets. A download or signup described as free does not mean every required feature is included. Check the current offer in the account and reproduce the actual roles before comparing totals.

For a four-person crew, determine who edits the shot list, who approves it and who simply reads the issued plan. Do not assume all four need the same access. Include the client reviewer separately. An affordable tool that forces repeated manual transfers can cost time; a sophisticated platform can add unnecessary administration to a simple job.

Assess trust through understandable correction, exports and ownership. Assess reliability by revising and reopening a real sample. Assess innovation by whether a feature removes a specific handoff while preserving review. An overlooked spreadsheet or specialist app can be the right answer when it performs the job cleanly. Avoid invented ratings and universal rankings.

When a visual workspace is insufficient.

If the day requires a dedicated live tracking workflow, a particular exchange format or formal production reports, require a demonstrated fit. Keep the appropriate system authoritative for that function. A visual board can still retain the source and creative references while another application runs the schedule.

Seven mistakes to catch before issuing the list.

One row for an entire scene.

A scene title cannot describe several distinct camera decisions. Break the scene into the coverage the edit needs, while retaining the scene reference. Do not create extra rows merely to hit a predetermined count.

No reviewed timing assumptions.

A complete-looking table can be impossible to shoot. Review shared preparation, capture, resets and non-shot work in the schedule. The builder preserves notes but does not calculate elapsed time or optimise order.

Using script order as the shooting plan.

Compare practical setup grouping with light, sound, continuity and availability. Keep stable IDs while reordering. Protect any action that cannot be repeated or returned to its original state.

Ambiguous technical vocabulary.

Agree labels and add references for unclear moves or framing. Separate intended values from confirmed equipment. “Cinematic shot” does not tell a camera team how to prepare.

Missing audio requirements.

Check dialogue, action sound, room tone and separately recorded sound against the editorial plan. A silent visual insert can be acceptable; an interview with no usable sound usually cannot serve its intended purpose.

Separating the list from its source.

Record the source revision and reconcile changed scenes or brief sections. Retain traceable records instead of updating only the client-facing storyboard while the crew uses an obsolete shot list.

Failing to identify essential coverage.

When the day slips, the team needs an agreed basis for cutting work. Protect the story and required deliverables first. Discuss changes with the creative and production owners; a status count cannot decide what the edit can lose.

Pre-shoot review checklist.

Your shot list.
Ready for the next setup.

Load the original example, enter your own shots, track status and export the complete workbook. The visible filter does not remove shots from exports. XLSX import accepts this builder’s workbook structure and validates the full candidate before replacing your draft.

Load the example or add a shot to begin.

ExcelJS 4.4.0, MIT, creates and reads the workbook locally. There is no implemented upload or browser autosave; save before closing. XLSX contains Shots and Project sheets; Project retains full notes and the format marker required for restore. Shot cells are stored as text, not executable formulas. This importer rejects formulas, rich text, hyperlinks and unknown structures rather than guessing a mapping. Very long cells can be awkward to read in spreadsheet software; their full text is retained in JSON and Markdown. No schedule optimization, footage analysis or approval is inferred.

Questions from brief to final pickup.

How do I make a shot list for a video shoot?

Start from the controlled source, identify the beats the viewer needs, choose coverage, review technical requirements, group practical setups, estimate the work and mark essential shots. Share one identifiable version and retain the editable source.

Which columns should I keep?

Keep identity, action, framing, sound and the practical information your crew uses. The camera specification here has twelve fields; the builder combines some and adds purpose, performers, priority and status. Extend your wider production record when separate technical or timing fields are required.

How many shots does a two-minute video need?

It depends on the story, performance, visual style and edit. The twenty-four-shot example illustrates one approach; it is not a benchmark. A continuous observation and a detailed demonstration can have similar durations and very different capture needs.

How long does a setup take?

Review preparation, capture and reset with the people doing the work. Equipment, lighting, performance and access change the estimate. Avoid applying a generic minute value to every row, and account for shared preparation only once where appropriate.

Should I use script order or shooting order?

Keep the scene and shot references linked to the source, but arrange the working plan around practical constraints. Review light, sound, access, continuity and performers before choosing an order.

How does a storyboard differ from a shot list?

The storyboard explains planned visual relationships. The shot list specifies what the production must capture. Transfer stable frame references into the list where helpful, then add practical information the drawing cannot communicate.

How should I number shots?

Agree a readable production convention, such as scene number plus a letter. Keep the identifier stable when row order changes and record insertions or deletions as revisions. The builder requires unique shot IDs but does not impose one numbering convention.

Can AI draft the list from a script?

Some tools document assisted drafting. Use authorised source material, inspect the proposal and correct action, coverage and equipment assumptions. A generated list does not establish available resources, a workable schedule or approved creative decisions.

Is Storyflow free?

Check its current offer and account access directly. A standalone generator page and a production workspace can have different terms. Test the required features and export before relying on an entry offer for the whole workflow.

Is StudioBinder’s shot list free?

Its site offers a signup route and describes several shot-list features. Verify the current plan access for the specific feature, sharing route and output you need. Avoid assuming every advertised function belongs to the entry tier.

Is Shot Lister worthwhile for a small crew?

Trial it when someone actively runs the day and updates the plan while shooting. Test the actual devices, progress workflow and collaborator access. The value depends on your production process and the current subscription scope.

Can I use Google Sheets or Excel?

Yes, a structured spreadsheet can be a useful shot list. Keep IDs, sort complete rows, use consistent labels and control revisions. The builder exports a real XLSX; restoration accepts its specific two-sheet format, not arbitrary spreadsheets.

Is Notion suitable for shot planning?

A database can link shots to source material and review decisions. Agree the schema, test a practical mobile view and inspect the export. Flexible properties do not automatically create an issued on-set plan.

How should I share the list with a client?

Give the client an appropriate review view of the creative decisions. Open the actual link or export as a recipient and verify permissions and version identity. Keep production contact details and unrelated records in their controlled documents.

What belongs on an interview shot list?

Specify the reliable primary interview coverage and sound plan, relevant context and visual material needed for edits. Review additional angles, reactions and inserts according to the story rather than assuming every interview needs the same camera arrangement.

What happens when the day runs behind?

Review remaining essential coverage and the reasons each item matters. Discuss scope changes with the responsible creative and production owners. Record pickups explicitly and inspect captured media before deciding a shot is no longer owed.

Useful distinctions

Is a shot list the same as a storyboard?

A storyboard visualizes the planned sequence; a shot list records individual capture requirements. Use both when a drawing or reference explains something the text cannot. This builder stores a textual checklist rather than generating storyboard images.

Do I need exactly twelve columns?

No. This is a compact starting framework. Separate camera bodies, frame rate, sensor, lighting, take counts or timing when your production needs those records. Do not fill unused fields with invented values just to complete the grid.

Can I restore any Excel file?

No. Restore accepts this builder’s two-sheet format with its exact twelve headers and project marker. Unknown columns, formulas and invalid statuses are rejected while your current draft stays intact. Save JSON as the simplest full backup.

Does Captured mean the shot is approved?

No. It is the status you enter. Check actual focus, sound, continuity and performance in the real media workflow. Record a pickup when something specific still needs capture.

Prepare your next video shoot with Super