Section 1: AI Filmmaking Pipeline and Responsible Use · Lesson 2 of 5 (2 of 45) · 60 minutes · Evidence: Production flow chart
Ask a group of beginners what the first step of making an AI film is and many will say, “open the video tool.” Experienced producers say something different, because they have been burned by it. Starting with the video tool is like starting a house with the paint. Today you map the order of work so that each step has what it needs before it begins, and so that one change does not quietly wreck three days of work.
Production journal: write your answer below.
What must a filmmaker understand before they can map the path from concept through script images voice motion editing and delivery?
In lesson 1.1 you listed the parts of the capstone. A pipeline adds order and direction: the output of one stage becomes the input of the next. The stages of an AI film are concept and brief, script, storyboard and still images, voice and sound, motion, editing, and delivery. Each stage produces a file that the next stage consumes: a brief, a script document, an image set, an audio track, a clip folder, an editing project, an exported film.
A dependency is a stage that cannot start properly until another one is finished. Motion clips depend on approved still images. Timing in the edit depends on the length of the voice track. Captions depend on the final script wording. When you draw a dependency, write the reason in a few words on the arrow: “images need locked script,” not just a line. The reason is what lets you decide whether two stages can safely overlap.
Iteration means repeating a stage to improve it: generating again, rewriting a line, re-cutting a scene. Some iteration is cheap (a new still image) and some is expensive (changing the script after the voice is recorded). A review gate is a checkpoint where the work must be checked against a stated standard before the next stage may begin. A gate has three parts: a question, a person who answers it, and a result (pass, fix or stop). Put gates before the expensive stages, not after them.
Rework is almost always caused by an early decision made late. A character look changed after thirty images are made. A rights problem found after the edit. A script that runs long, discovered when the voice is already recorded. So a good map puts the consent and rights check twice: once before anything is generated, and once before the film is shared.
A student plans a ninety-second documentary-style piece about a community garden. Her map shows brief, script, shot list, images, narration, motion, edit and export. The gate after the script asks “Are all facts and names checked, and does the narration fit ninety seconds when read aloud?” and is answered by her teacher. A dependency arrow from narration to edit reads “edit timing follows narration length.” Beside the image stage she writes the output name: 02_images_approved. She marks the gate after the narration as the one that causes the most rework if skipped.
Watch a creator build a short animated video from a story idea. Pay attention to the order of the work, not the look of the result. Pause whenever the creator moves from one stage to the next and ask: what did the previous stage have to deliver for this step to work?
Notice how often one step feeds the next without anyone checking it. The creator takes a script into a tool, takes the tool’s output into another tool, and each handoff is a chance for a mistake to travel forward. The tools do the producing. The creator is the one who notices that a line is too long, that a picture does not match its sentence, or that two scenes were made with different looks.
Draw a quick sketch as you watch: boxes for stages, arrows for handoffs. Mark each arrow with the file that travels along it, and put a star where you would add a review gate. By the end of the clip you should have the first draft of a pipeline map and a short list of places where trouble could have been caught earlier.
As you study, record each decision point in your production journal.
| Decision point | What the filmmaker does | What the tool automates | What still needs human review |
|---|---|---|---|
| Hand the script to the visual stage | Splits the script into scenes and writes an image prompt for each | Generates the images for every prompt | Whether each image matches its scene and whether the set looks like one film |
| Hand images to the motion stage | Selects the approved images and describes the movement wanted | Animates each image into a clip | Whether motion is believable, faces still match, and nothing strange appears in the frame |
| Hand clips and voice to the edit | Orders clips against the narration and trims to fit | Plays back and renders the timeline | Whether pacing, timing and captions agree with the final script wording |
| Export for delivery | Chooses the format and checks the whole film once more | Renders the final file | Whether credits, disclosure and rights records are complete before sharing |
Studio task: Arrange workflow cards and justify dependencies between stages.
Your teacher will give your group a set of workflow cards, one per stage, plus a few extras such as “final rights check” and “script review.” If you work alone, write the cards on paper.
Copy your final arrangement into the template below.
Coaching tips. If two cards both seem first, ask which one the other needs. If a gate has no reviewer, nobody is checking anything. Make sure both rights-and-consent checks appear, one early and one at the end. When you justify an overlap, name what could go wrong if you were mistaken.
Order of stages: ______ > ______ > ______ > ______ > ______ > ______ > ______ > ______ Dependency 1: ______ cannot start until ______ gives it (file: ______) Dependency 2: (repeat for every pair) Two stages that can overlap and why: ______ Gate: question ______ | reviewer ______ | result (pass / fix / stop) ______ Early decision the teacher changed: ______ -> stages to redo: ______ Stage with the most rework: ______
Studio task: Create a flow chart for the proposed film with review gates and file outputs.
Draw the pipeline for the film you are proposing. Use paper, a drawing tool or a table in a document, as long as it is readable by someone who has not met you.
Checklist before you submit:
Identify the stage most likely to cause rework and explain why.
Deliverable: Production flow chart.
Submit the production flow chart. The file must use the course naming convention and include enough process evidence to show the student's decisions and revisions.
File name (course naming convention): AIF_S01-L02_production-flow-chart_v01_YOURINITIALS
| Criterion | Advanced | Proficient | Developing | Beginning |
|---|---|---|---|---|
| The work addresses the stated story or production purpose. | Flow chart covers concept through delivery for the proposed film and shows clear, specific outputs for every stage. | Flow chart covers all stages for the proposed film with file outputs. | Flow chart omits a stage or output, or is generic rather than about this film. | Flow chart is missing or not about the proposed film. |
| The student applies the required method accurately and produces usable capstone evidence. | Dependencies carry reasons, gates have question, reviewer and fail action, and overlaps are justified. | Dependencies and at least three gates are correct and clearly drawn. | Some dependencies are reversed or gates lack a reviewer or question. | Stages are listed with no real dependencies or gates. |
| The student identifies at least one quality issue and records a meaningful revision decision. | Identifies the rework-prone stage with a sound reason and makes a specific map change that reduces the risk. | Identifies a rework-prone stage and records a meaningful revision. | Names a risky stage but makes no change. | No quality issue or revision recorded. |
| The work complies with consent rights attribution privacy disclosure and school policy. | Both rights-and-consent checks are placed, with reviewers, and a no-cost fallback is shown for tool-dependent stages. | Both rights-and-consent checks appear and policy is followed. | Only one rights check appears. | No rights or consent checks appear. |
Requirement: Include consent and rights checks before generation and publication.
A pipeline map is also a responsibility map. Put a rights and consent check before the first generation, because that is when you decide whose face, voice, music or style you are going to use, and put a second check before publication, because that is when the film leaves the classroom. At each check, ask who or what is in this film and how you know it is allowed. If you cannot answer, the work stops at that gate until your teacher confirms a safe replacement.