A Clean Creator Deliverables Handoff Folder Structure

A clean creator handoff separates final approved files, review versions, source material, copy, and rights notes, then inventories everything in one manifest. The folder should let a brand identify the correct asset without guessing from “final” filenames or opening every video.

Start with the deliverables list

Before creating folders, list every public post and delivered file from the agreement and brief. Assign a stable deliverable ID such as D01, D02, and D03. Keep that ID consistent in filenames, review records, captions, and invoices.

For each deliverable, record:

• Platform and publishing account
• Format, aspect ratio, duration, and language
• Public post versus brand-delivered file
• Required caption, thumbnail, link, and code
• Review status and approved version
• Usage and rights notes
• Publication or handoff date

The campaign-file retention guide helps decide what belongs in the durable archive after the active handoff ends.

Use a predictable top-level structure

A practical folder can look like this:

Brand_Campaign_Creator_2026-10-12/
  00_README_AND_MANIFEST/
  01_FINAL_APPROVED/
    D01_Reel/
    D02_Stories/
  02_CAPTIONS_AND_LINKS/
  03_THUMBNAILS_AND_STILLS/
  04_REVIEW_VERSIONS/
  05_SOURCE_IF_INCLUDED/
  06_RIGHTS_AND_CLEARANCE_NOTES/

Do not include 05_SOURCE_IF_INCLUDED merely because the template has it. Raw footage and project files belong only when the deal requires them. Do not put tax forms, banking information, or unrelated private material in a creative handoff.

Name files for identity, not optimism

Use names that describe campaign, creator, deliverable, version, format, and status. For example:

Northstar_Fall_Jordan_D01_v03_APPROVED_9x16.mp4

For a working review version:

Northstar_Fall_Jordan_D01_v02_REVIEW_9x16.mp4

Do not use final, final2, and final_really_final as the only version system. “Approved” should be added only after a named reviewer approves that exact file. Preserve the file's original extension and avoid punctuation that breaks common transfer tools.

If the brand has an asset-ID standard, map your names to it in the manifest instead of creating a competing code.

Build a manifest that answers review questions

Use a spreadsheet or readable CSV with one row per file:

| Deliverable | Filename | Version | Status | Specs | Decision | |---|---|---|---|---|---| | D01 | Exact file | v03 | Approved | 9:16, duration | Approver/date | | D02-S1 | Exact file | v02 | Approved | 9:16, duration | Approver/date |

Add file size, checksum when useful, review URL, caption filename, usage note, and publication instruction. The manifest should identify the controlling brief and delivery package version.

The raw-footage organization guide provides a deeper structure for source media when it is part of the scope.

Separate approved finals from context

Put only approved, ready-to-use files in 01_FINAL_APPROVED. Review versions can remain in a clearly labeled folder if the brand needs the history. Never place a rejected draft beside an approved file with nearly identical names and no status field.

Keep captions, links, codes, alt text, and posting instructions in their own package, tied to deliverable IDs. State offer dates and time zones. A technically correct video can still publish with the wrong caption or expired code.

Apply the first-try approval guide to every file in the final folder, then compare manifest counts with the agreed deliverables.

Add rights and clearance notes without overpromising

For each final asset, note the intended media, territory, term, editing scope, and known third-party components. Reference the controlling agreement rather than paraphrasing a broad legal guarantee.

Include:

• Music source and use status
• Talent and location status
• Brand-supplied assets
• Creator-identity ad permission if applicable
• Known restrictions or expiration dates
• Contact for rights questions

File delivery itself does not necessarily transfer copyright ownership. The agreement and applicable law control rights.

Deliver securely and obtain receipt

Use a named recipient, access controls, and an expiration date appropriate to the campaign. Test access from the recipient's perspective. Keep a local or controlled archive until the brand confirms integrity.

Send a handoff note:

Package [name/version] contains [count] final approved assets and [count] supporting files. The manifest lists filenames, versions, decisions, and rights notes. Please confirm download and completeness by [date]. The link expires [date].

If you replace a file, increment the package and asset versions, update the manifest, and send a correction note. Do not silently overwrite an approved file behind the same URL.

Record delivery, receipt, access expiry, and archive or deletion treatment at campaign closeout.