# How to prepare a social media launch asset folder

Make the approved version, caption and destination identifiable without opening every file. Separate source work, review versions and publishable exports, then keep the actual publication decisions in a manifest the receiving team can access.

Launch and folder owner:
Receiving team:
Manifest location:
Asset identifier:
Purpose and intended destination:
Approved export path and version:
Source-file path if included:
Caption and subtitle paths:
Language and crop:
Maintained destination URL:
Approval record location:
Permission or supplied-asset record location:
Publication date and time zone:
Dependencies or unresolved issue:
Receiving access and playback check:
Replacement or superseded version:


## Example folder structure

"Location","Contents","Use"
"manifest","Asset references, approved versions, destinations and schedule","Start here when preparing publication"
"source","Included editable projects and their linked materials","Editing and future reuse within the actual arrangement"
"review","Versioned previews awaiting a decision","Client or team review"
"approved","The exports approved for publication","Use the version identified in the manifest"
"copy","Caption, subtitle and language files","Match wording to the approved asset"
"records","Approvals and relevant permission references","Resolve who approved which use"


## Check from the receiving side

- [ ] The receiving team can open the folder without the creator's personal session.

- [ ] Approved exports play with the expected audio and subtitles.

- [ ] Editable files have the linked materials needed to open them.

- [ ] Each language and crop has its own correct version reference.

- [ ] The destination and timing match the current launch arrangement.

## Example replacement

If a price line changes after approval, create a new export version, obtain the relevant approval and update the manifest. Mark which file it replaces so a publisher does not select the old version from memory.

Keep personal participant information and private customer records out of a broadly shared launch folder. Store only the access and permission references the receiving team actually needs for its role.