Give each accepted asset one stable identity
Use an asset ID that persists across edits, with a version that changes when the content changes. Keep filenames clear enough that a publisher can distinguish a vertical cut, a square crop and a caption sidecar without opening everything.
A practical illustrative name is demo01-creator07-vertical-v03.mp4. It is a suggested convention, not a required platform format. Avoid using final, latest or approved as the only identity because those words cannot distinguish two different files.
Deliver a manifest beside the files
Write the technical settings the actual publisher needs rather than copying an arbitrary export preset. Confirm aspect ratio, supported codec and size constraints against the current destination. Keep the master available for authorised future derivatives.
Link the rights schedule from the manifest; do not copy an ambiguous sentence such as “full rights” into every row. The schedule should identify exactly what the downstream team can do.
| Item | Record |
|---|---|
| Master video | Asset ID, version, dimensions and duration |
| Derivatives | Parent master and crop or trim |
| Captions | Matching language and file version |
| Thumbnail | Accepted still or cover reference |
| Approval | Immutable file or hash and decision |
| Rights | Channels, territory and usage window |
| Publishing copy | Approved caption and destination |
Inspect captions and crops as part of acceptance
YouTube recommends reviewing automatic captions because speech recognition can misrepresent the spoken content. Check names, product terms, numbers, negations and disclosure language against the accepted audio. A correct video with a wrong caption can communicate a different claim.
Review each delivered crop. A horizontal master can look fine while a vertical version removes a warning or pushes a disclosure under platform controls. Do not describe a crop as accepted until it has been checked in its intended viewing context.
The creator usage-rights guide helps define permissions that the manifest must expose. Choose each derivative for its destination using the short-form production guide.
Separate editable material from permitted use
An editable project can help another editor adapt content, but its possession does not create rights to every included element. Identify music, stock, fonts, likeness permissions and any limitations the publisher needs.
Deliver credentials through no asset folder at all. A project file or screen recording can accidentally contain private paths, tokens or account data. Inspect the exported materials and use the brand’s agreed access controls for non-public working files.
Accept exceptions explicitly rather than hiding them
These examples show why a folder-upload confirmation is not acceptance. The publisher should know which files it can use now and which require another decision.
Do not repair a missing permission by removing the rights column. Keep the asset available privately while the authorised owner resolves the intended use.
| Issue | Status | Action |
|---|---|---|
| Caption sidecar missing | Delivery incomplete | Provide matching language file |
| Two different v03 masters | Identity conflict | Confirm accepted hash |
| Paid-use term unspecified | Permission unresolved | Review rights before use |
| Thumbnail not approved | Publishing blocked for that surface | Approve or use accepted alternative |
Run one final publisher rehearsal
Ask the downstream owner to identify the correct file, caption, destination and rights window from the manifest alone. If the owner needs a separate chat to interpret a row, improve the row before handoff.
Archive the accepted manifest with the immutable files. Later corrections should update the version and affected references together. A durable handoff saves the next team from guessing which export the brand actually approved.
Sources and further reading
Prepared with AI assistance using the linked references. Planning tables and worked scenarios are illustrative, not client results. Check current product, platform and market requirements before using them.