Module 8. One cut becomes eleven deliverables. This is the week most people lose, and it is the most mechanical work in the entire pipeline, which means it is the least excusable place to lose a week.
You finished the film. Now it needs to exist as:
Eleven exports, each with a spec you will get slightly wrong at least once.
There is not one creative decision in that list.
Every item is a rule, applied exactly, and checked against a number.
The specs live in a file, like everything else in this course. Not in your head, not in a bookmark, not in the platform's help page you will look up again next month.
delivery/
youtube-master.md 16:9, codec, bitrate, loudness, captions sidecar
vertical.md 9:16, safe areas, burned captions
square.md
cutdown-15.md which section, and why that one
"Read the current published delivery requirements for each platform in delivery/ and tell me where my files disagree with what I have written down. Do not change my files, just report."
Platform specs change and this deck will be out of date before you are. The durable move is a file you can re-verify, not a number you memorised.
A 16:9 film squeezed to 9:16 is not a vertical film. It is your film with the sides cut off, and the subject is frequently in the part you cut off.
Automatic reframing that "tracks the subject" will happily track the wrong subject through your best shot, and it will do it confidently, at every shot, in one pass.
Reframe automatically, then look at every single shot. The tool makes eleven versions in minutes so that you have time to actually watch the one that matters.
You transcribed everything in Module 7.
"From the transcript, build captions: a sidecar file for the platforms that take one, and a burned-in version for the platforms that do not. Check no caption runs past its shot, and flag anything over two lines."
Then read them. Transcription is very good and not perfect, and a wrong caption is the single most visible error in a finished film, because it is the only mistake spelled out in words on screen.
Same pattern as Modules 4, 6 and 7. By now you can write this prompt yourself.
"Export every version indelivery/from the locked timeline, todeliverables/<spec>/, named<film>-<spec>-v<n>. Log the settings used for each. Skip anything already exported at this version. Report what failed."
Start it and go and do something else. The last mechanical week of your project happens while you are not there.
The thing that separates work that looks professional from work that looks close is that somebody checked it against a list before it went out.
"QC every deliverable against its spec: duration, resolution, aspect, codec, bitrate, integrated loudness, true peak, and whether captions exist where the spec says they should. Give me a table, one row per deliverable, pass or fail per column."
A table with a fail in it is worth more than a confident all clear.
Never report a delivery as done because the export said done. Open the file.
An export can complete successfully having rendered the wrong timeline, the wrong range, a muted track or a version of the cut from Tuesday. The success message is about the process, not about the film.
Ask for evidence you can see:
"For every deliverable, give me the first frame, a frame from the middle and the last frame, at the real output resolution, in one contact sheet per version."
The film ships. In four months a platform changes a spec, or a client wants a different cutdown, or you want to remake a shot with a better model.
What you need is not the film. It is everything that made it.
"Archive this project: the bible, shots.json, every log, the paper edit, the transcript, the EDLs, the project file and the approved takes. Leave out proxies and superseded takes. Write me a manifest with a checksum for every file, and tell me the total size before you start."Never trust a backup you have not restored from.
"Restore the archive to a scratch folder, verify every file against the manifest, and tell me anything missing or changed."
Do this once, now, on a project that is finished and safe. The alternative is finding out on the project where it matters, which is always the one where it matters.
Your cut from Module 7.
delivery/ spec files for every platform I am posting to, from their current publishedrequirements, and date each one."*
Steps 5, 6 and 8 are the ones people skip, and they are the three that catch real failures.
delivery/ holding every spec as a dated file you can re-verifydeliverables/ with every version, versioned and loggedYour film is out, in every shape it needed, and you can rebuild any of it in a year.
The Library. Three hundred generations, a naming scheme that survives, and finding the one good take from six months ago in four seconds.
Verified against Claude Code 2.1.220 · 2026-07-30.