A script is organized for reading. A shot list is organized for making and editing images.
Turning one into the other is not a matter of asking AI to invent camera angles for every sentence. The useful work is identifying dramatic beats, deciding what the audience must see, and creating enough purposeful coverage to assemble the scene.
This guide includes a reusable conversion template and a worked example.
Start with a scene objective
Before listing shots, write:
- Scene objective: What is the scene doing in the story?
- Character objective: What does the active character want right now?
- Change: What is different at the end?
- Audience information: What must the viewer notice or understand?
- Continuity risks: Which people, objects, states, or spatial relationships must persist?
If those answers are vague, the shot list will become decorative.
Mark beats before shots
A beat is a meaningful change in action, information, emotion, or power. Mark beats directly in the script.
Example:
INT. WORKSHOP – NIGHT
Lena enters carrying a sealed case. [Beat 1: arrival]
She sees fresh mud beside the back door. [Beat 2: evidence]
A floorboard creaks behind her. [Beat 3: threat]
Instead of turning, she switches off the light. [Beat 4: decision]
Do not assign a new shot to every line. Decide what must be shown for each beat.
Use this shot-list template
| Field | Purpose |
|---|---|
| Scene / shot ID | Stable identity across generation and editorial |
| Beat | Connects the shot to story progression |
| Shot purpose | Explains why the shot exists |
| Framing | Wide, medium, close-up, insert, or custom composition |
| Action | Observable action during the shot |
| Camera intent | Movement, angle, or stillness and its reason |
| Planned duration | Helps storyboard and editorial timing |
| Required references | Character, location, prop, style, or prior frame |
| Continuity constraints | What must not drift |
| Audio dependency | Dialogue, cue, effect, or music timing |
| Status | Planned, candidate, selected, approved, or locked |
| Notes | Review instructions or known limitations |
Shot purpose is the most important field. “Close-up of Lena” describes framing. “Reveal that Lena expected the intruder” describes editorial purpose.
Worked example
| ID | Beat | Purpose | Framing/action | Duration | Critical constraints |
|---|---|---|---|---|---|
| 07A | Arrival | Establish workshop geography and case | Wide; Lena enters frame left | 4 sec | Door, table, case, screen direction |
| 07B | Evidence | Show what changes her attention | Insert; wet boot print | 2 sec | Mud color and floor texture |
| 07C | Evidence | Connect the clue to her response | Medium; Lena stops but does not look down | 3 sec | Eyeline toward print |
| 07D | Threat | Establish unseen presence behind her | Over-shoulder; shadow crosses wall | 3 sec | Light direction and room layout |
| 07E | Decision | Reveal she is prepared | Close-up; slight smile, light switches off | 4 sec | Face, wardrobe, hand position |
| 07F | Consequence | End on controlled darkness and case latch | Insert; latch opens in darkness | 2 sec | Same case design |
This list gives generation a target and editorial a structure. It also identifies the fragile details before they drift.
Separate required coverage from optional coverage
Label each shot:
- Required: the scene cannot communicate its action or change without it.
- Protective: gives the editor a way to adjust timing or hide a difficult transition.
- Optional: an alternate emphasis or visual flourish.
Generate required shots first. Then test the rough cut. Protective coverage should solve a demonstrated editorial problem, not merely increase the number of clips.
This can significantly reduce wasted generations.
Add technical intent only where it matters
Camera details should serve the shot purpose.
Useful notes include:
- screen direction
- eyeline
- lens feel
- camera height
- movement start and stop
- foreground relationship
- action entry and exit
- clean handles for editing
Avoid false precision. Naming an exact lens does not guarantee model behavior, and elaborate instructions can obscure the critical constraint. “Locked medium frame; preserve the doorway behind Lena; no camera drift” may be more actionable than a paragraph of cinematography jargon.
Attach references by job
Do not provide a pile of undifferentiated images. Label what each reference controls:
- identity reference
- wardrobe reference
- location layout
- prop design
- lighting or palette
- composition reference
- motion reference
- previous-shot continuity frame
When references conflict, state which one wins. The shot list should inherit the approved production rules rather than forcing each operator to reconstruct them.
Review before generation
The director or production lead should check:
- Does every beat have enough coverage?
- Does every required shot have a clear purpose?
- Can the geography be understood?
- Are reactions available where the edit needs them?
- Are continuity-critical details documented?
- Are any shots duplicating the same information?
- Can expensive or unstable shots be simplified?
- Does the planned duration fit the scene?
- Are required and optional shots separated?
Then assemble a timed storyboard. If the scene does not work with rough frames, adding motion will make the problem more expensive.
Use AI as an assistant, not the authority
AI can accelerate:
- identifying characters, props, locations, and wardrobe
- proposing a first-pass beat breakdown
- checking for missing coverage
- formatting shot records consistently
- spotting continuity dependencies
- suggesting simpler alternatives
Human review remains essential. The system does not know which silence matters, when an unconventional cut is intentional, or whether an apparent continuity error serves the story.
A useful pattern is:
- strict extraction from the screenplay
- human-approved beat structure
- creative coverage suggestions
- director or production-lead review
- storyboard validation
- generation
Ciaro Pro’s screenwriting, storyboard, and production workflows can keep these records connected from script through edit.
Copyable scene-to-shot worksheet
Use this for each scene:
- Scene number and slug:
- Scene objective:
- Character objective:
- Beginning state:
- Ending state:
- Beats:
- Required audience information:
- Continuity risks:
- Required shots:
- Protective coverage:
- Optional shots:
- Audio dependencies:
- Approval owner:
- Ready for storyboard: yes / no
- Ready for generation: yes / no
A good shot list is not a list of camera ideas. It is a production agreement about what the scene must show, why each shot exists, and what the downstream edit needs.
