A published-ready film, process portfolio, and oral defense.
Students manage final production, use critique to revise, verify legal and accessibility requirements, assemble a process portfolio, and defend the finished film.
Section 9: Capstone Completion and Exhibition · Lesson 1 of 5 (41 of 45) · 60 minutes · Evidence: Capstone schedule and status board
Eight sections of work are now sitting in your folders: a script, a character bible, voice tracks, a lip-sync shot, an animated sequence, a rough edit. Most unfinished films do not fail because the filmmaker lacked talent. They fail in the last stretch, when twenty small jobs all seem equally urgent and nobody can say which one to do first. Today you stop feeling busy and start knowing exactly what is left, in what order, and who owns each piece.
Production journal: write your answer below.
What must a filmmaker understand before they can set milestones dependencies review gates and completion criteria for the final film?
A capstone plan answers four questions: what is still missing, what must happen before what, when each piece is due, and how you will prove it is finished. Start with an inventory. Walk through the capstone evidence list one item at a time: script and scene breakdown, character bible and consistency grid, prompt and decision log, voice authorization record and final audio package, lip-sync comparison, animation take log, editable CapCut project evidence, rights, provenance and AI-use disclosure, and finally the captioned master, web export, process portfolio, oral defense and reflection. Beside each item write one of three words: done, partial, or missing. Be honest. A partial item is not a done item.
A milestone is a checkpoint you can verify, such as ‘rough cut screened’ or ‘every music and image source recorded’. A good milestone has a date and an observable finish: someone else could look at it and say yes or no. A dependency is a link between two tasks: task B cannot start, or cannot finish, until task A is complete. You cannot caption a scene before the dialogue is final. You cannot export a master before the rights check passes. Draw each dependency as an arrow from the earlier task to the later one.
The critical path is the longest chain of linked tasks from now to the finish. If any task on that chain slips, the whole film slips. Tasks that are not on the chain have slack: they can run late without moving the finish date. Spend your best hours on the critical path first, and put slack tasks into the gaps.
A review gate is a stop sign built into the schedule: work cannot pass until a named person checks it against stated criteria. Your capstone needs at least three gates: a rough cut critique, a rights and accessibility check, and a final export check. A gate is not a formality. If the check fails, the work goes back, and the schedule must show time for that return trip. Track status with the same few words every time, for example not started, in progress, blocked, in review, done. ‘Almost done’ is not a status.
A student making a documentary-style short about a school garden listed fourteen jobs. Arrows showed that the final export depended on captions, which depended on the locked audio, which depended on re-recording two narration lines, which depended on a written permission from the speaker for the new takes. That chain of four jobs was the critical path. A colour-correction pass and a thumbnail looked more fun, but neither blocked anything, so they were scheduled last. The plan also placed the rights gate three days before the exhibition, leaving room to fix a failure.
Organized creators who finish and publish a short film follow a recognizable order of operations, even when they work alone. Study the order below as if you were looking over a producer’s shoulder, and pause at each decision to ask who is deciding, the person or the software.
They begin with the finished product and work backward: what files must exist on the last day, and what has to be true for each one? Next they split the film into units, usually scene by scene, because scenes can be finished in any order but a scene’s picture, sound and captions must be finished together. They keep their text, picture and audio material in clearly named folders so nothing has to be hunted for later. They also leave a visible gap between ‘finished generating’ and ‘finished editing’, because rework is common. A generator can produce a clip in moments, but only a person can tell whether the clip is the one the story needs.
Notice two habits. First, they treat the schedule as a living document and change it when a task proves slower than expected, rather than hoping. Second, they decide early what ‘finished’ means: the film is ready when it meets its listed criteria, not when the maker is tired of it.
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 |
|---|---|---|---|
| Define the finish line | Lists every file and record that must exist at delivery | Nothing; it is a planning judgment | That the list matches the capstone evidence list, not just the film |
| Break work into units | Splits the film by scene and by evidence item | May suggest a list if asked | That no required item, such as the consent record, is missing from the list |
| Order the tasks | Draws dependencies and finds the longest chain | A planning or spreadsheet tool may sort dates | Whether each arrow is real and whether the date is realistic |
| Place review gates | Adds a named checker and criteria before key hand-offs | Nothing decides whether a gate passes | That time is reserved for failed checks to come back and be fixed |
Studio task: Sequence remaining tasks and identify the critical path.
Work with a partner on the sample inventory your teacher provides, or on a partly finished film of your own. The goal is to sequence the remaining tasks and find the critical path.
Coaching tips. If your chain has only one or two tasks, you are probably hiding dependencies; ask what ‘ready to start’ means for each task. If everything seems to be on the critical path, your tasks are too big or your dates are not honest. When two tasks look equal, put the one that others are waiting for first. Use the template below to keep the work in one place; you will carry it into the independent studio.
Evidence item | Owner | Status | Depends on | Due | On critical path (Y/N) 1 ______ | ____ | ______ | ______ | ___ | __ (repeat for every remaining task) Critical path (task numbers in order): ______ Review gates: 1 ______ (checker ____ date ____) 2 ______ 3 ______ Completion rule: the film is finished when ______ Biggest risk and my fallback: ______
Studio task: Create the final production plan with deadlines and evidence owners.
Build the real capstone plan for your own film. Use only your own records and your own project folder.
Checklist before you submit:
Name the next task that blocks two or more later tasks.
Deliverable: Capstone schedule and status board.
Submit the capstone schedule and status board. 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_S09-L01_capstone-schedule-and-status-board_v01_YOURINITIALS
| Criterion | Advanced | Proficient | Developing | Beginning |
|---|---|---|---|---|
| The work addresses the stated story or production purpose. | The plan covers every capstone evidence item, ties each to the story’s purpose, and shows a clear completion rule. | The plan covers the film and the evidence list and states what finished means. | The plan covers most of the film but leaves out some required evidence items. | The plan covers only editing or has no connection to the film’s purpose. |
| The student applies the required method accurately and produces usable capstone evidence. | Dependencies are accurate, the critical path is correct, and owners, dates and status words are used consistently. | Dependencies and critical path are mostly correct; every task has an owner and date. | Some dependencies are missing or some tasks lack an owner or date. | No usable sequence, critical path or owners. |
| The student identifies at least one quality issue and records a meaningful revision decision. | Names a real risk or schedule issue, makes a specific change to the plan because of it, and explains why. | Identifies at least one issue and records a meaningful change to the plan. | Notes a risk but makes no clear change. | No risk or revision recorded. |
| The work complies with consent rights attribution privacy disclosure and school policy. | Rights, consent, disclosure and accessibility checks are gated before export, with fallbacks that cost nothing. | Rights, consent and disclosure checks are scheduled before export. | Compliance checks appear but are late or lack a checker. | Compliance is missing, or the plan depends on paid credits. |
Requirement: Schedule rights consent and disclosure checks before final export.
Your schedule is also a promise to the people in your film and to your audience. Put the consent, rights and disclosure checks on the calendar the same way you schedule editing, and give each an owner. If a contributor’s written release has not arrived, that task is blocked, and a blocked task blocks the screening. Never plan to ‘sort out permissions after export’. If your plan seems to need paid generation credits, redesign it around school-approved or no-cost routes, and write that fallback into your risk list.