Cross-platformWorkflow & organisationImage-to-video

How AI Filmmakers Organise Clips and Shot Prompts

By Marco Cavazzana · Updated · 2 min read
ShareEmail
Short answer
Organise AI film work by scene and shot, not by tool: give every shot an ID, keep each generated take with its exact prompt, start frame and settings, and mark the chosen take. Then a reshoot or a client change means rerunning one known prompt instead of hunting through several platforms' histories.

An AI short or ad can easily mean hundreds of generations across several tools: stills for start frames, clips in one or two video models, upscales and fixes. By the edit, the hard part is no longer making shots but knowing which take is which, and what prompt made it.

Traditional productions solved this long ago with scene and shot numbers, slates and take logs. Borrow the same structure:

  • Scene: a location or beat, such as "S03 market at night".
  • Shot: one camera set-up within it, such as "S03-02 slow push-in on stall".
  • Take: each generation of that shot, kept with its prompt and settings.

What to keep for every take

KeepWhyStart with
Shot IDLinks the clip to the script and the editScene and shot number, e.g. S03-02
PromptRerun or adjust a take exactlyThe full text as sent
Start (and end) frameImage-to-video takes depend on themThe still file and where it came from
Tool, model and settingsDuration, mode, camera or motion settingsWhatever the tool lets you set
StatusSeparates the chosen take from the restRejected, maybe, chosen

A workflow that holds up in the edit

  1. Write a simple shot list first: one line per shot with its ID and intent. It doubles as your prompt plan.
  2. Put the shot ID in your notes or file names for every take, in every tool, so the still and every clip made from it share the same ID.
  3. Save each take with its prompt as you go, not at the end of the day. Busy days are when prompts get lost.
  4. Mark the chosen take and keep the near-misses; they are often the starting point for a fix.
  5. Export with the IDs intact, so the editor and the prompt record line up.

For moving a still into a video model, see which image-to-video platform suits which job.

Handling client changes and reshoots

When a client asks for "the same shot, but warmer", the shot ID takes you to the chosen take, its prompt and its start frame in seconds. Change one thing, rerun, and save the new take under the same ID. Keeping the full history per shot also helps you show what was made and how when a client asks.

Try it

Write shot prompts in a consistent order so takes are easy to compare and adjust:

S03-02 | slow push-in on a noodle stall at night | rain, steam rising, neon reflections on wet ground | handheld feel, shallow depth of field | 5 seconds

Keep the shot ID at the start of your own record (and the prompt, if the tool ignores it), then change one element per take, such as the camera move or the light, so you know what made the difference.

Frequently asked questions

How do I keep track of AI video clips across different tools?
Organise by scene and shot rather than by tool. Give every shot an ID, use it for every take in every platform, and keep each take with its prompt, start frame and settings in one place.
What should I save with each AI video generation?
Save the clip, the exact prompt, the start and end frames if you used them, the tool, model and settings, and whether it is the chosen take. That is enough to rerun or adjust any shot later.
How do I handle client changes to an AI-generated shot?
Go back to the chosen take by its shot ID, reuse its exact prompt and start frame, and change one thing at a time. Save the new take under the same ID so the history of the shot stays together.

Nothing you makeis lost.

Free · No card · Read-only · 2-minute setup

DreamdriveFree plan · Chrome
Add to Chrome — it’s free