What is included in the kit?

It includes a delivery checklist, folder layout, upload manifest, filename example, usage-information request, missing-file note, and reshoot request. You can customize the note fields and copy the full kit.

Can creators upload footage here?

No. This page does not receive, host, store, or transfer media. Use the instructions with the approved delivery service your team already uses.

Does the kit confirm footage usage rights?

No. The usage questions help both sides document what still needs confirmation, but the kit does not create a contract, grant permission, or verify ownership.

Do I need email delivery to use it?

The complete kit is available immediately. The optional mailing-list form sends only the contact information entered into that separate form.

UGC Creator Handoff Kit

1. Delivery checklist

Complete these checks before sharing a folder or transfer link.

Match the deliverable count · Must checkCompare the delivered files with the approved brief and count every opening, talking take, reaction, b-roll clip, demo, and CTA.Expected and delivered counts

Keep originals separate from previews · Must checkInclude the original full-resolution files as separate takes. Put previews or creator-edited references in their own folder so they cannot replace the originals by accident.

Spot-check the delivered filesPlay the first and last seconds of every file and spot-check audio. Confirm the transfer finished and filenames did not change or duplicate.

Remove unrelated private material · Must checkRemove unrelated personal files, screenshots, account exports, and hidden temporary files before sharing the folder.

2. Folder layout

Use this small folder tree so source roles stay obvious after download.

01_openingsPlace one spoken or visual opening in each file, including alternate deliveries.

02_ugcPlace problem, experience, reaction, proof, and CTA takes here. Keep clean versions beside any reference edit.

03_broll and 04_demoPlace silent lifestyle or product b-roll in the first folder and clean screen recordings in the second.

05_reference and 06_documentsPlace optional edited examples in reference; place the manifest, brief, and usage-information record in documents.

3. Upload manifest

Create one row per media file. The copied kit preserves your manifest notes.

File identityRecord the exact filename, folder, file type, orientation, duration, and whether it is an original or reference.File facts

Creative contentName the creative role and summarize the spoken line, movement, or app action so an editor can search without opening every clip.Content summary

Known issuesCall out background noise, a stumble, focus change, blocked screen, cut-off handle, or any other known limitation without hiding it.Known issues

Brief match and status · Must checkMark the brief item or reshoot request the file satisfies. Do not label usage as approved unless the separate approval record confirms it.Brief match and approval record

4. Naming example

Use a filename that stays useful after files leave the delivery folder.

Filename patternPattern: app_creator_role_concept_take_version.ext. Use short lowercase tokens and one separator consistently.My approved pattern

Complete filename exampleExample: tempolist_maya_opening_forgetful_take02_v1.mov. The name identifies the app, person, source role, concept, take, and version.

Replacement-file ruleNever reuse a filename for a replacement. Increase the take or version and write the replaced filename in the manifest.

5. Usage-information request

Copy these questions into the handoff. They identify missing information; they do not grant or verify rights.

Who and what appears · Must checkList every person, recognizable private location, third-party logo, artwork, screen, or voice included in the files.People and third-party material

Proposed usage typesState whether the proposed use includes organic posts, paid media, creator-handle ads, raw footage, edited derivatives, or still frames.Proposed use to confirm

Placement detailsWrite the channels, regions, proposed start date, and proposed usage period that the appropriate people still need to confirm.Channels, regions, and proposed term

Approval-record handoff · Must checkName where the signed or written approval record is stored and who owns the final review. Do not attach private contracts to a broadly shared media folder.Approval record owner

6. Missing-file note

Use this neutral format when the folder is incomplete.

Missing-file note openingMessage opening: “Thanks for the handoff. We matched the folder against the approved brief and could not find the items below.”

Exact missing-file listList each brief item, expected count, folder checked, and closest filename found. Ask whether it is unavailable, renamed, or still uploading.Missing-file details

Missing-file note closeMessage close: “Please reply with the filename or confirm it is unavailable. We will not assume a different clip is an approved replacement.”

7. Reshoot request template

Request a replacement by naming the instruction and observable issue, not by giving vague performance feedback.

Reshoot request openingMessage opening: “We need one replacement take for the item below. The request is based on the approved capture direction, not ad performance.”

Specific replacement directionIdentify the original filename, brief instruction, observable issue, and what should remain unchanged in the replacement.Replacement details

Feasibility and timingAsk the creator to confirm feasibility and a revised delivery date before recording. Record any agreed scope or fee change in the appropriate agreement, not this kit.Confirmation

UGC Creator Handoff Kit

1. Delivery checklist

2. Folder layout

3. Upload manifest

4. Naming example

5. Usage-information request

6. Missing-file note

7. Reshoot request template

Get the next app-marketing tool.

Hand off creator footage without the follow-up scramble

What to know before you use it.

Keep planning free. Use ClipStitchr when it is time to produce.