How to organise a multi-scene AI film without losing your mind halfway through

You started the project with real momentum. The first few scenes generated well, you had a clear idea of the story, and everything felt manageable. Then, somewhere around scene four, the cracks appeared. You have forty-odd video clips sitting in a downloads folder, three of them are called "final", two more are called "final_v2", and you cannot remember which version of the corridor shot had the lighting you actually liked. By scene six you are regenerating things you already had, spending credit on problems that were already solved.

This is not a creative failure. It is a filing failure, and it happens to almost every solo AI filmmaker who does not set up a structure before the first generate. The good news is that the fix is not complicated. It is just a set of habits applied consistently, and once they are in place, a twelve-scene short film becomes as manageable as three scenes used to feel.

Start with a scene registry, not a folder

Before you generate a single frame, open a plain spreadsheet or a markdown file and write out every scene in your project as a numbered row. Each row should hold: the scene number, a two or three word label (INT-KITCHEN-ARGUMENT, EXT-ROOFTOP-DUSK), the shot count you are aiming for, the status (not started, generating, reviewing, locked), and a notes column for prompt decisions you want to carry forward.

This file is your ground truth. Everything else, folders, exports, audio stems, references, hangs off this registry. When you are mid-project and disoriented, you open this file first.

The folder structure that does not lie to you

Create one top-level project folder. Inside it, one subfolder per scene named with its number and label:

```
/my-film/
/00_references/
/00_audio/
/stems/
/sfx/
/01_int-kitchen-argument/
/generates/
/selects/
/exports/
/02_ext-rooftop-dusk/
/generates/
/selects/
/exports/
/99_assembly/
```

The `generates` folder holds everything that comes back from the model, named automatically or renamed immediately on download. The `selects` folder holds only the clips you have reviewed and decided to use. Nothing goes to `selects` without a conscious decision. The `exports` folder holds any clips you have processed, upscaled, or colour-treated. The `99_assembly` folder holds your edit project file and final renders.

The discipline here is the `selects` folder. Keeping generates and selects separate means you always know what you are actually working with. Your edit timeline should pull only from `selects`, never from `generates`.

Naming your clips so they tell you what they are

Rename every clip the moment it lands. A consistent pattern removes ambiguity:

```
SC01_rooftop_wideshot_A.mp4
SC01_rooftop_wideshot_B.mp4
SC01_rooftop_closeup_A.mp4
```

Scene number, location label, shot type, take letter. That is all you need. When you come back to this project after two days away, or when you are exporting a platform cut at midnight, you will not have to open a single clip to know what it contains.

Logging your prompt decisions

Every time a generate works well, write down why. Keep a `prompt-log.md` inside the relevant scene folder. A brief entry is enough:

```
SC01_rooftop_wideshot_A
Prompt: wide establishing shot, rooftop at dusk, woman standing at railing,
background city lights soft focus, 35mm film grain, static camera
Settings: [model settings as used]
Notes: the soft background came from dropping any hard city detail from prompt.
Keep this approach for SC04 which has same location.
```

This log has two jobs. First, it lets you replicate success later in the project when continuity matters. Second, it stops you wasting time regenerating a take that was already good but that you forgot about.

Reviewing dailies as a discipline, not an afterthought

At the end of each session, before you close anything, spend ten minutes doing a quick review pass. Open your scene registry. Update statuses. Move anything worth keeping from `generates` to `selects`. Write one sentence in the notes column about where you left off.

This ten minutes is what separates a project that finishes from one that stalls. The human brain is not a reliable cache for forty video clips. The registry is.

When to lock a scene and move on

Set a rule for yourself before the project starts: a scene is locked when you have selects covering every shot on your list, reviewed at normal speed with audio playing. Once a scene is locked, you do not regenerate from it unless the edit makes a continuity problem visible. Locking prevents the perfectionism spiral that kills solo projects.

Update your registry to show the lock date. That date matters more than it seems: it tells you how long scenes are taking, which helps you budget the rest of the project honestly.

The next session, try building the registry and folder structure before you open any model interface. Sequence first, generate second.