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.
What should a delivery manifest include?
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.
Talk to us
Pick a 30-minute slot, or DM us on Telegram.
Bring a sample delivery manifest. We can discuss what the publisher still has to reconstruct.
Pricing is scoped to your brief. We reply within one working day.
How does editable material differ 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.
Frequently asked questions
What should a UGC asset handoff include?
Hand over the accepted files with a manifest a publisher can act on without asking in chat. List the master video with asset ID, version, dimensions and duration, each derivative with its parent and crop, matching caption files, the accepted thumbnail, the approval hash, the rights schedule and the approved publishing copy and destination. The video, captions, permitted uses and destination should all identify the same asset and version.
How should UGC video files be named for delivery?
Give each accepted asset a stable ID that persists across edits and a version number that changes when the content changes. A suggested convention is demo01-creator07-vertical-v03.mp4, which lets a publisher tell a vertical cut, a square crop and a caption sidecar apart without opening them. Avoid final, latest or approved as the only identity, because those words cannot distinguish two different files.
Do automatic captions on creator videos need checking before publishing?
Yes. YouTube recommends reviewing automatic captions because speech recognition can misrepresent what was said. Check names, product terms, numbers, negations and disclosure language against the accepted audio, since a correct video with a wrong caption can communicate a different claim. Review every crop in its intended viewing context as well, because a vertical version can cut a warning or push a disclosure under platform controls.
Does an editable project file give a brand full rights to UGC?
No. An editable project helps another editor adapt the content, but possessing it does not create rights to every element inside it. Identify music, stock, fonts, likeness permissions and other limits, and link the manifest to a rights schedule that states channels, territory and usage window instead of a vague phrase like full rights. Our guide to iGaming creator usage rights explains how to define those permissions.
How do you check a UGC handoff is ready for the publishing team?
Run a publisher rehearsal: ask the downstream owner to find the correct file, caption, destination and rights window from the manifest alone, and fix any row that needs a separate chat to interpret. Log exceptions such as a missing caption sidecar, two different v03 masters or an unspecified paid-use term instead of hiding them. Our casino UGC agency team can build that handoff into production when you share the formats and downstream users.
Results from campaigns our team has run
Solana community brand · KOLs on X
Retardio
15M+ impressions on X
Read the Retardio caseWeb3 game · gaming creators, streams and events
Illuvium
6,550 new players and 24,000+ followers
Read the Illuvium caseMove-to-earn app · creators on X and YouTube
STEPN
5,344 new users and 949 NFTs sold
Read the STEPN case
3betmedia launched in 2026; most of these campaigns ran before the name existed. See all 19 cases.
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.
Related reading
- casino UGC agency
- iGaming Creator Usage Rights: A Brand-Side Guide
- iGaming short-form video agency
- Short-Form Content Accessibility Checklist
- Creator Content Library Rights Tracker
- Commissioning Casino App Walkthrough Videos
- Hire UGC Creators for Green-Screen Videos
- UGC B-Roll Shot List: Make the Footage Reusable
