A useful AI video shot list does more than number camera angles. It connects story purpose to reusable assets, generation instructions, continuity and a pass/fail decision. Without those fields, teams produce clips that look attractive but cannot be edited together.

The template

Field

What to record

Shot ID

Stable project identifier, not just row number

Story beat

What changes for the audience

Required assets

Character, location, prop and voice versions

Start state

Position, emotion and prop state before action

Main action

One observable action

End state

Condition needed by the next shot

Framing

Establishing, medium, close, insert or other purpose

Camera intent

Static, follow, reveal or motivated move

Audio

Dialogue, ambience, effect, music cue

Continuity notes

Eyeline, screen direction, costume, weather, time

Acceptance criteria

What must be true to keep the take

Priority

Essential, supporting or optional

Worked example: the empty station

Source situation: a courier enters a closed station, finds a suitcase belonging to her missing brother and hears a train approaching on a suspended line.

SH-010 — Arrival

  • Story beat: Establish isolation and objective.
  • Assets: Courier v03, station-night v02, shoulder bag v01.
  • Start state: Exterior doors closed; courier outside.
  • Action: She pushes through the doors and scans the empty concourse.
  • End state: She notices the lockers at frame right.
  • Framing: Wide establishing shot.
  • Audio: Door echo, distant electrical hum.
  • Acceptance: Same coat and bag as later shots; lockers visible; no additional people.

    SH-020 — Recognition

    • Story beat: The task becomes personal.
    • Assets: Courier v03, station-night v02, suitcase-brother v02.
    • Start state: Courier approaches bench.
    • Action: She stops when she recognizes the scratched suitcase.
    • End state: Her hand reaches toward its broken handle.
    • Framing: Medium moving to close detail.
    • Continuity: Bag remains on left shoulder; suitcase scratch faces camera.
    • Acceptance: Recognition is readable through stopped movement; prop matches canonical reference.

      SH-030 — Impossible arrival

      • Story beat: The world violates expectations.
      • Assets: Station platform v02, courier v03.
      • Start state: Her hand rests on the suitcase.
      • Action: Platform lights activate in sequence as train sound grows.
      • End state: She turns toward the tunnel.
      • Framing: Profile medium shot with platform depth.
      • Acceptance: Light change is visible; turn finishes facing the next shot's screen direction.

        Why acceptance criteria matter

        “Looks good” cannot guide a production team. An acceptance criterion should be observable:

        • The same prop appears with the correct damage.
        • The character completes the turn.
        • The final frame leaves edit space.
        • No unplanned crowd enters the station.
        • The dialogue line is complete and intelligible.

          Separate mandatory requirements from preferences. A slightly different camera move may be usable; a missing suitcase is not.

          Keep prompt text out of the master logic

          The shot list describes production intent. Provider-specific prompt wording can live in a linked field or generation record. This prevents the story plan from becoming obsolete when a model or provider changes.

          ElserStudio's local-first production workflow keeps scripts, canonical World assets, shots, generated results and composition connected on one canvas. The authoritative asset reference can remain stable while individual generation attempts change.

          Versioning rules

          • Never reuse a Shot ID for a different story purpose.
          • Increment the take, not the Shot ID, when regenerating.
          • Version assets when identity or design changes.
          • Record which asset version produced an accepted take.
          • Update downstream continuity notes after editorial changes.

            FAQ

            Should prompts be inside the shot list?

            Keep the stable action and continuity intent in the master list. Store provider-specific prompt text alongside each generation attempt.

            How detailed should camera instructions be?

            Specify the storytelling purpose and essential framing. Avoid decorative camera movement that does not support the action.

            What is the difference between a shot and a take?

            A shot is the planned editorial unit. A take is one generated attempt to realize it. One shot may have several candidate takes.