Turn a script into a practical shot list covering essential actions, sound and setup needs, with a filming budget that separates necessary shots from extras.
Direct answer: Break the script into the claims and actions viewers must understand, then assign each one a shot that actually shows the required information. Record framing, action, sound, location, dependencies and priority, and group the shoot by practical setup rather than script order. Capture and check essential coverage before spending time on decorative alternatives.
A script says what the audience will hear or learn. It does not automatically tell you what the camera must record. “Connect the cable securely” may need a close view of the correct port and the completed connection, not a wide shot of someone sitting at a desk.
The shot list closes that gap. Its job is to prevent an editor discovering that the one action needed to explain the process was never filmed.
Use the script-to-shot coverage plan
The script-to-shot coverage plan is an editorial method for turning an approved script into observable footage. Start with the viewer's task and work backwards to the images and sound that make it understandable.
This is the preparation layer within a practical AI video workflow. AI can suggest options, but it cannot confirm that your location, equipment or subject will support them. A plausible list still needs a practical check.
Before planning, identify the final video's intended duration, aspect ratio, audience and destination. Confirm access to the location, consent or permissions for people appearing, and the equipment you already have. Use dummy accounts and synthetic information for screen demonstrations so filming does not expose private data.
Keep a versioned copy of the approved script. If a later change alters an action or claim, update the linked shot requirements rather than hoping the footage will still fit.
Translate each script section into visible evidence
Read one section and ask what the viewer must see to understand it. Classify the need as an action, a comparison, a result, a location or an explanation that may be clearer as a diagram. Do not assume every sentence needs a separate shot.
For a practical demonstration, identify the state before the action, the action itself and the result that proves it worked. If the result is a small indicator, frame it so viewers can see it on the intended screen. A shot that looks attractive but hides the relevant detail does not cover the requirement.
Some claims cannot be demonstrated by generic footage. A person typing does not establish that a security control works. Use an accurate screen demonstration, a labelled illustration or a source-based explanation instead of letting decorative footage imply evidence it does not provide.
Give each essential requirement a script reference. The link can be a paragraph number or a short phrase. This lets the editor see why the shot exists and whether a script revision makes it unnecessary.
Keep the list usable on the day
| Field | What to write | Why it changes the shoot |
|---|---|---|
| Shot identifier | A unique short number or label | Connects footage, script and take notes |
| Required information | The action or detail the viewer must understand | Prevents decorative footage replacing coverage |
| Framing and movement | Wide, medium or close view; any necessary movement | Establishes camera position and visibility |
| Sound | Dialogue, demonstration sound or separate narration | Determines recording and quiet-location needs |
| Setup and dependencies | Location, props, account state and people | Reveals work needed before the camera rolls |
| Priority and status | Essential or optional; captured and checked | Protects the core video when time runs short |
Adobe's shot-list guidance similarly distinguishes practical details such as location, shot type, camera angle and movement, and discusses organising work around setup. Those are planning concepts, not a guarantee that a particular list prevents every production problem. Adobe guide to making a shot list.
Keep descriptions brief enough to scan. Put complex safety, permissions or technical instructions in an attached production note rather than burying them inside every row. The shot list should point to those requirements without pretending to replace them.
Separate essential coverage from interesting options
My recommendation is to mark a shot essential only when losing it would prevent the viewer understanding a required point or leave the editor unable to build a coherent sequence. A second angle may be useful, but it is not automatically essential.
Optional shots can improve pacing, atmosphere or flexibility. They deserve time after the important action is captured correctly. The alternative, justified on more complex productions, is planned redundant coverage for fragile or unrepeatable events. In that case, explain what failure the extra shot protects against.
Do not confuse production priority with final screen time. A two-second view of a critical switch may be more important than a long presenter introduction. Allocate attention according to what the audience needs to see.
Group the filming order by setup
Once the script coverage is complete, group shots that share a camera position, lighting arrangement, location or screen configuration. Preserve their script references so the filming order does not become the editing order by accident.
Check continuity requirements before moving a prop or changing a device state. If you need to show the initial configuration and the completed result, capture both before resetting or packing away the setup. Avoid irreversible demonstrations when a safe dummy example can show the same process.
For software footage, prepare a clean test account and verify the current interface on the actual device. Do not script an imaginary button because a planning tool suggested it. If the required action cannot be shown safely, change the demonstration or use an explicitly labelled illustration.
Budget a 150-second explainer
Imagine a 150-second explainer requiring nine essential shots and four optional shots. The timings below are illustrative production assumptions, not industry averages or observed results.
Assume the essential shots use three setups at ten minutes each: 3 × 10 = 30 minutes. Allow four minutes per essential shot for recording and immediate checking: 9 × 4 = 36 minutes. Reserve 15 minutes for a final coverage and sound check. The essential plan takes 30 + 36 + 15 = 81 minutes.
If each optional shot needs three additional minutes within those same setups, four extras add 4 × 3 = 12 minutes. The full plan takes 81 + 12 = 93 minutes.
With a 90-minute location window, the plan is three minutes over before allowing any unexpected problem. Three optional shots would use nine minutes and reach 90 exactly, still without contingency. A safer choice may be two extras, leaving three minutes unallocated, or simplifying the planned setups.
The example shows why dividing shoot time by final video length is not a useful planning rule. A 150-second output does not imply a 150-second recording task. Setup, repeat takes, checking and recovery consume time even when the final edit is short.
Check coverage before leaving the location
Review the essential shots on a screen large enough to inspect the relevant detail, and listen to recorded sound through an appropriate monitoring arrangement. Confirm that the action, result and any required text are actually usable. A file existing on the card does not establish that it contains the shot you need.
Mark which take is preferred and why. Record any problem the editor must know, such as a missing result shot or an explanation that needs separate narration. Keep the original media and use the project's normal backup process before reusing cards or deleting files.
Create your first list in 40 minutes
- Spend ten minutes marking the approved script's essential visual and sound requirements.
- Use 15 minutes to assign shots and record practical dependencies.
- Spend ten minutes grouping by setup and calculating the time needed for essential coverage.
- Use five minutes to remove or downgrade shots that do not justify their cost.
Stop adding creative options when an essential action remains unclear or unsafe to demonstrate. Resolve that requirement before filming. On the day, do not leave a setup until you have checked the footage needed to explain it.
Related guides
Frequently asked questions
Is a shot list the same as a storyboard?
No. A shot list is a practical record of the footage and production details you need, while a storyboard uses images to plan the sequence or composition. You may use both, but a simple instructional video can often begin with a clear shot list and a few sketches for difficult views. Do not spend time drawing every frame if the uncertainty concerns equipment, access or the action itself. For a visually complex sequence, storyboards can reveal problems that words leave ambiguous. Choose the planning form that resolves the actual production question rather than treating either document as compulsory decoration.
How many shots should a short video contain?
There is no reliable universal number. The necessary shots depend on what viewers must understand, how much action occurs and whether a single view can show it clearly. Start with coverage of the required information, then add alternatives when they improve comprehension or protect against a specific editing problem. A fast-cut style may use many shots without teaching more, while a well-framed continuous demonstration may need few. Check the intended screen size and audience. Do not force the script into an arbitrary shot count or assume that more angles automatically make the result more professional.
Can AI generate the shot list from my script?
It can propose a first list from material you are authorised to submit, but verify every requirement against your real location, equipment and subject. Generated suggestions can assume unavailable camera movements, invented interface steps or access to footage you do not have. Ask for script references and essential-versus-optional priorities, then remove anything that does not serve the viewer's task. Keep confidential scripts within approved handling arrangements. A short manually prepared list may be faster than correcting an elaborate generated plan. The useful output is a feasible coverage plan, not a cinematic description that cannot be filmed.
Should I film in the same order as the final script?
Not necessarily. Grouping shots by location or setup can avoid repeatedly moving equipment, provided you preserve the references needed to assemble the final sequence. Check continuity and device state before changing the order, especially when an action alters something you cannot easily restore. Some demonstrations or events must be captured sequentially because their state changes are part of the evidence. In those cases, the process determines the filming order. Keep the script relationship visible so an efficient shoot does not leave the editor with footage that is difficult to match to the intended explanation.
What if the essential shot cannot be filmed safely?
Change the demonstration rather than treating the shot list as an instruction to take the risk. Use an appropriate dummy setup, a labelled diagram, authorised existing footage or a different explanation when that preserves the required meaning. Do not expose private accounts, operate unfamiliar hazardous equipment or bypass safeguards merely to obtain a convincing image. For specialist environments, involve someone qualified to assess the activity. If the real process cannot be shown accurately under safe conditions, state that limitation. An attractive but unsafe or misleading demonstration is not essential coverage worth preserving.
How do I make the list useful for an editor who was not present?
Keep shot identifiers, script references, preferred takes and concise notes about problems or missing coverage. Explain what each essential shot is meant to show, not only its camera angle. Include the approved script version and any changes made during filming. Store those notes with the authorised media package so they do not depend on a conversation the editor missed. Do not claim that a take is usable unless you checked it. A small amount of accurate context helps the editor distinguish deliberate choices from accidental gaps and prevents them spending time searching for footage that was never captured.
Sources and verification
- Adobe: how to make a shot list, consulted 11 September 2026 for shot-list fields and setup-oriented planning. No quoted practitioner experience is adopted as the author's own.
- The parent guide was read in supplied local publication files because its public route was unavailable. The coverage method and production timings are editorial constructions.
This article is practical guidance. Apply it in proportion to your tools, evidence, risks, and responsibilities.
