Delivery is part of the product
A folder full of final-final exports creates risk. The client should immediately understand what is approved, where each asset belongs, which files are editable, and what references or instructions are needed to reproduce the system.
Use a predictable package
Keep the structure stable across projects.
- 01_Brief-and-approvals: scope, selected direction, feedback records.
- 02_References: client-provided assets and approved generated anchors.
- 03_Approved-masters: high-resolution stills, clean video, and audio masters.
- 04_Platform-exports: named by channel, ratio, size, and version.
- 05_System-docs: prompt templates, settings, repair notes, and limitations.
Make status visible in every filename
Use project, asset function, ratio, version, and approval status. Archive rejected or superseded work outside the delivery folder. A clean handoff saves support time and prevents an old, inaccurate, or unapproved asset from being published.
Continue building
Learn the complete production system.
The Academy connects prompt structure to references, first frames, motion, editing, distribution, and monetization.
Explore the Academy