A creator delivers a polished 24-second video. The brand approves it. Two weeks later, the editor gets a new request: open with a different question, remove nine seconds, replace the spoken call to action, and show the product action that the original cut only described.
The folder contains the final export, one generic product shot, and perhaps a project file. It looks complete. It is not complete for that edit.
The solution is not to add “send all raw footage” to every brief. Define the likely next edits before filming, then name the exact recordings, clean versions, and project dependencies those edits require. A concise, purpose-built handoff is often more useful than every false start, duplicate take, and accidental camera roll clip.
That distinction matters because “raw UGC footage” is not a standardized package. It may mean individual camera clips, selected unused takes, a caption-free assembled video, or optional clips sold separately. It does not automatically mean a RAW recording codec, every take, an editable project, or permission to use the files however you like.
“Raw footage” is a label; the deliverables are the agreement
Current public provider instructions use the same word for materially different files.
Billo’s April 2026 help page describes optional extras that a creator may offer after a shoot: alternate hooks, B-roll, extra takes, and photos. A brand previews low-resolution versions, buys selected assets individually at creator-set prices, and then receives the full-quality files. The page says video originals are 1080p or higher. These extras are not promised on every order.
By contrast, Twirl’s July 2024 creator instructions define a “raw edit” as B-roll, voiceover, and talking-head clips already assembled into one video, but without captions or background music. The page explicitly says this is not a delivery of the individual raw files.
Insense’s modular-content guide treats hooks, B-roll, and calls to action as separate building blocks. Its example for a minimum 60-second video asks for two to five hooks, specified B-roll shots, and two or three CTAs. Those quantities are one provider’s workflow example, not a universal minimum for every UGC job.
Write what you need without relying on the label:
| Deliverable | What it gives the editor | What it does not prove |
|---|---|---|
| Unedited camera clips | Separate recorded files before the final assembly | That every take is included, usable, or licensed |
| Usable selects | Chosen takes that meet the brief | That rejected, duplicate, or accidental takes are included |
| Alternate hooks or CTAs | Different recorded openings or endings | That a new line can be invented later from an old performance |
| Specific B-roll | Coverage of named actions, angles, or details | That generic product beauty shots cover every future cut |
| Clean dialogue | Understandable speech without added music | That a separate WAV or isolated studio stem exists |
| Clean assembled export | The approved picture and dialogue without specified overlays | That individual clips or an editable timeline are included |
| Project package | A path to continue the original timeline | That unused clips, fonts, plug-ins, or every source file are present |
Also keep raw and RAW separate. In this article, raw means source or minimally processed deliverables. RAW in a camera specification refers to a recording format or codec workflow. Most creator assignments do not need professional camera RAW; they need ordinary files that match the planned edit and can be opened reliably.
Work backward from the next edit
A useful brief begins with verbs: change the opening, shorten the body, replace the CTA, show the product action, recaption, reframe, change the music, or continue the original timeline. Each verb creates a different dependency.
| Later edit | Minimum useful input | What a nearby file cannot do |
|---|---|---|
| Change to a new spoken opening | A recording of the alternate hook | A new visual over the old audio does not create the new sentence |
| Replace the spoken CTA | An alternate CTA recording | A new end card changes text, not the creator’s spoken words |
| Shorten a line | A shorter take or speech with removable sentence boundaries | B-roll can hide the picture cut, but cannot supply missing words |
| Cover a cut | Relevant B-roll with enough usable duration | A still product hold may not show the required action |
| Add new captions | Intelligible dialogue, plus a clean picture when old captions are burned in | An SRT file cannot erase text rendered into the pixels |
| Change music | Dialogue without the old music, or a usable dialogue stem | A stereo file does not prove dialogue and music are isolated tracks |
| Reframe for another aspect ratio | A composition that keeps the face, product, and action inside the new crop | Higher resolution cannot recover something recorded outside the frame |
| Continue the exact animated edit | A dependency-aware project package | A folder of camera clips does not reproduce timing, titles, or effects |
This is why “more footage” is an incomplete recommendation. More duplicates do not solve a missing spoken CTA. Ten generic close-ups do not show an unrecorded product action. A project file does not guarantee that an unused hook was collected with it.
The reverse is also true: not every edit needs the whole camera roll. If the only planned change is replacing captions and music while keeping the approved picture and dialogue, one verified clean assembled export may be sufficient.
A worked handoff: turning 24 seconds into 15
The following desk-organizer case is an original synthetic teaching example. It is not a creator campaign or a performance test. Its job is to make the file dependencies visible.
The approved 24-second baseline uses:
- 4 seconds of hook
H01 - 14 seconds of body
B01 - 4 seconds of spoken CTA
CTA01 - 2 seconds of static product B-roll
R01
The requested 15-second variation needs a different opening, a shorter body, a different spoken CTA, and a close-up of a pen being placed in the left slot. Its timeline is:
| Target time | Source | Function |
|---|---|---|
| 0–3 seconds | H02 source 2–5 seconds |
Alternate spoken hook: “Where do the pens go?” |
| 3–10 seconds | B02 source 2–9 seconds |
Short clean body take |
| 6–8 seconds | R02 source 2–4 seconds |
Pen-placement picture over continuing B02 audio |
| 10–13 seconds | CTA02 source 2–5 seconds |
Alternate spoken CTA |
| 13–15 seconds | R02 source 4–6 seconds |
Reuse the same clip’s product hold; camera audio muted |
The arithmetic is 4 + 14 + 4 + 2 = 24 seconds for the baseline and 3 + 7 + 3 + 2 = 15 seconds for the new cut. On a 30 fps timeline, that is 720 frames versus 450 frames. The two-second R02 cutaway at 6–8 seconds is simultaneous with the body audio, so it is not added again to the total.
A readable filename exposes each clip’s role:
HB32_DEMO_CR01_HOOK_H02_T01_V9x16.mp4
That pattern is:
PROJECT_OR_PRODUCT + CREATOR + ROLE + VARIANT + TAKE + ORIENTATION
Use stable role labels such as HOOK, BODY, CTA, and BROLL. Give source takes a take number and finished exports a version number. Do not call five duplicated downloads five variants.
Now compare three folders against the same requested edit:
| Folder | Contents | What it can actually do |
|---|---|---|
| Incomplete for the named edit | Captioned/music-mixed final F01_REF, old hook H01, generic hold R01 |
Provides reference, but not the new spoken hook, short body, new spoken CTA, or pen action |
| Sufficient for cosmetic changes only | Clean assembled final F01_CLEAN |
Can support new captions and music while preserving the baseline; cannot create H02, CTA02, or the missing action |
| Sufficient for the 15-second variation | H02 + B02 + CTA02 + R02 |
Supplies the four distinct recordings required for the requested cut |
Inspect the annotated 15-second video or the clean target export. These geometric illustrations and synthetic speech demonstrate editing dependencies; they are not real creator footage.
The third folder is small by design. It does not include every outtake, a separate WAV that was never recorded, an editable project that no one needs, or old baseline clips the new variation will not use.
Remove one file before approving the manifest
A quick “removal test” exposes whether a file is essential, replaceable, or irrelevant:
- Remove
H02: the requested spoken opening is blocked because no other file contains that line. - Remove
CTA02: a new graphic CTA remains possible, but the requested spoken CTA is blocked. - Remove
B02from the four-file folder: the short body is blocked. In a larger archive containingB01, an editor might join two complete sentences from that longer take and cover the visible cut withR02; whether the audio join sounds natural still requires inspection. - Remove
R02: the exact pen-placement action is blocked. A generic hold can cover a cut, but it cannot show the action. - Remove an optional close-up
R03: nothing changes, becauseR02already supplies the needed action and final hold. - Remove
F01_CLEANfrom a folder that also has every baseline source: the cosmetic update is still possible, but it becomes a rebuild rather than a simple replacement of captions and music.
This test prevents two opposite mistakes: collecting unusable clutter and assuming every missing item requires a reshoot.
Specify usable footage, not just file duration
Technical requirements should follow the chosen workflow. A reasonable example for a vertical paid-social edit might be 9:16, 1080 × 1920, 30 fps, SDR, and intelligible embedded dialogue without added music. That is an example specification, not a rule for every creator, camera, or placement.
Record these details in the manifest:
- Orientation and composition: not only “vertical,” but where the face, product, hands, and demonstrated action must remain visible.
- Resolution, frame rate, and color workflow: enough to match the editor’s timeline and output, without automatically demanding 4K/60 fps.
- Focus and exposure: the promised action and product detail must be readable throughout the usable interval.
- Usable in and out points: the file’s total duration is not the same as usable coverage.
- Handles: extra recorded time before and after the intended selection, when the workflow needs room to trim.
- Audio state: embedded dialogue, separate recorder, room tone, music added, or silent B-roll.
- Clean state: captions, other graphics, music, filters, and color treatment should be separate yes/no fields.
The Insense sample brief asks creators to film vertically and add one to three seconds at the beginning and end of raw clips. Treat that as a concrete brief example, not an automatic entitlement to three useful seconds on every file. A six-second clip can still fail a three-second action request if only seconds 2–4 contain a focused, unobstructed action: 4 − 2 = 2 usable seconds, leaving a one-second shortfall.
Reframing needs the same discipline. To crop a centered 1080 × 1920 vertical frame to a full-width 4:5 image, the retained height is 1080 × 5 ÷ 4 = 1350 pixels. The crop removes 1920 − 1350 = 570 pixels, or 285 pixels from the top and bottom when centered. That is 29.6875% of the original height. A 4K version loses the same proportion. More pixels can improve detail; they do not bring an off-frame product back into view.
For sound, ask for the state the editor needs: “clear dialogue without added music” is often better than reflexively demanding a separate WAV. Require a separate audio file when the creator actually records double-system audio or the post workflow needs isolated tracks. Then include the matching filename, sample rate, and sync reference. Do not infer isolated stems from the word “stereo.”
Decide between a clean export and a project handoff
A clean export and an editable project solve different problems.
A clean assembled export is efficient when the brand wants to preserve the approved picture and spoken performance while replacing captions, graphics, or music. Specify what “clean” removes. Caption-free, graphics-free, music-free, ungraded, and unedited are not synonyms.
Adobe’s current Premiere caption-export documentation distinguishes captions burned into the video from embedded or sidecar captions. Burned-in captions are rendered into the picture. A separate subtitle file can help create or revise captions, but it does not restore the clean pixels underneath old text.
A project handoff is justified when another editor must continue the exact timing, animation, title design, or audio treatment. Even then, “send the project” is not a complete specification.
Adobe’s Premiere Project Manager instructions allow the sender to collect media used by selected sequences—and also offer an “Exclude Unused Clips” option. A properly opening project can therefore omit an unused alternate hook that the next variation needs.
Interchange formats add another boundary. Descript’s timeline export chart says video clips and trimming can transfer into Premiere, while captions, titles, transitions, and several effects do not. Apple similarly warns in its Final Cut Pro consolidation guide that third-party FxPlug content must be tracked and moved manually.
When project continuity is required, request a package that includes:
- the native project or agreed interchange file;
- all required source media, including named unused alternates;
- fonts, graphics, licensed audio information, and plug-in requirements;
- a reference export of the approved timeline;
- the application and version used; and
- an open-and-relink test on the receiving system.
Skip this package when a fresh recut from clearly named source clips is the intended workflow. More complex is not automatically more complete.
Download and inspect before the review window closes
A link that plays is not yet an accepted source delivery.
Frame.io’s download instructions explicitly offer a choice between the original file and a smaller proxy for an individual clip. Google Drive’s video help says users can upload video at any resolution, while browser playback is capped at 1920 × 1080. In other words, the viewer is useful for review, but it does not by itself establish the downloaded file’s original resolution or metadata.
Review clocks also differ by provider. These are examples, not a general industry standard:
| Provider term checked | Public review rule |
|---|---|
| Billo | Its October 2025 auto-approval help page says content in “Requires approval” is automatically approved after three business days without an approval or change request. |
| Collabstr | Its terms, last updated September 9, 2025, define a 72-hour review period after delivery. |
| Twirl | Its revision policy dated August 11, 2025 asks brands to review within seven days and warns that creators may delete content or no longer have raw files after auto-approval. |
Before accepting, download the original files and perform an actual handoff check:
- Compare filenames and asset IDs with the agreed manifest.
- Open every file; scrub the beginning, usable interval, and end.
- Listen to dialogue and confirm whether music is mixed in.
- Check resolution, orientation, frame rate, duration, audio tracks, and file size from the downloaded file.
- Confirm the promised line, action, and clean-state fields—not merely that a file exists.
- Open and relink the project on the receiving system when a project was included.
- Store an approved copy under brand control before any stated retention period expires.
- Submit any valid correction through the provider’s designated review field.
That last step can be procedural, not cosmetic. Billo’s June 2026 edit and reshoot instructions say chat messages are not recognized as formal requests and do not stop the auto-approval timer. The same page treats new scenes, new mentions, and a changed CTA as outside a reshoot request when they were not in the original brief.
First classify the problem. A smaller proxy may require a new download. A missing clean export may require a new export if the source still exists. A project that loses titles may require dependency repair. A hook that was promised but duplicated may be a correction. A new action that was never ordered is new capture scope. Those are not the same request or the same cost.
File possession and editing rights are separate
Receiving an MP4 does not answer where, how long, or how extensively the brand may use it.
For the US legal baseline, 17 U.S.C. §202 separates ownership of a material copy from ownership of copyright. Transfer of the copy does not, by itself, transfer rights in the copyrighted work. A platform or creator agreement may grant or assign rights, but the file delivery alone is not the grant.
Put these questions next to the deliverable list:
- Which named files does the license cover: final content only, clean exports, purchased extras, or all listed source clips?
- May the brand cut, rearrange, caption, crop, dub, and combine them with other assets?
- Which organic channels, paid channels, accounts, territories, and durations are included?
- When does the permission begin: delivery, acceptance, or payment?
- May agencies, contractors, or affiliates receive working copies?
- What uses are excluded, including resale, another brand’s advertising, or synthetic likeness creation?
Provider defaults can be narrow. Collabstr’s current terms make the accepted content requirements important to the rights granted and state that, when rights are not transferred, the advertiser receives a limited license for approval purposes. That is a platform-specific default, but it illustrates why “we have the files” is not enough.
Editing permission is not permission to change the meaning of an endorsement. The FTC’s 2023 Guides Concerning the Use of Endorsements and Testimonials in Advertising say an endorsement may not be presented out of context or reworded in a way that distorts the endorser’s opinion or experience. A shorter version should therefore preserve the creator’s actual meaning, even when the contract allows editing.
A copy-ready raw UGC handoff block
Replace the brackets before putting this into a creator brief or statement of work:
Planned post-delivery edits: [new hook tests / shorter body / alternate CTA / recaption / new music / target crops].
Capture deliverables: [number] named hook recordings; [number] body takes with sentence boundaries; [number] named CTA recordings; and the following B-roll actions: [specific action, angle, and minimum usable duration]. Deliver selected usable takes, not every accidental or duplicate take.
Clean assembled export: [included / not included]. “Clean” means: captions [absent/present], other graphics [absent/present], added music [absent/present], color treatment [state].
Project package: [not required / required]. When required, include the native project, required media, named unused alternates, fonts/graphics/audio documentation, plug-in list, application version, and a reference export.
Technical workflow: [orientation and composition], [resolution], [frame rate], [color workflow], [audio state]. Leave [handle duration] before and after the intended action or line. Keep [face/product/action] inside the planned [target crops].
Packaging: Use
PROJECT_CREATOR_ROLE_VARIANT_TAKE_ORIENTATION.ext. Include a manifest with file duration, usable in/out, spoken line or action, audio state, clean-state flags, and the edit each asset enables.Review and retention: Upload via [method]. Brand will download and inspect originals within [review window]. Creator/provider availability of original files after [date or event] is [term]. Corrections apply to agreed deliverables; new scenes or lines require separately agreed scope.
Rights: The agreement separately states the covered files, permitted edits, channels, territory, term, start condition, contractor access, and exclusions. File delivery alone does not expand those rights.
The goal is not the largest folder. It is a folder that answers a practical question before the creator packs away the product: Can the editor build the changes we are likely to request from the files we have actually ordered?
Use the handoff files
Download the complete synthetic editing kit for all 13 source clips in the manifest’s folder structure, both manifests, the field guide, and the checklist.
Download the filled 24-to-15-second manifest, blank manifest, field guide, acceptance checklist. The filled manifest names each source file and its usable interval.
Sources
- For Brands: Unlock Raw Footage from Your Creators, Billo, April 24, 2026.
- For Brands: How to request edits and reshoots, Billo, June 2, 2026.
- Why was my video approved?, Billo, October 31, 2025.
- What Are The “Raw” and “Final” Edits?, Twirl Help Center, July 18, 2024.
- Revision Request Policy, Twirl Help Center, August 11, 2025.
- How to source Modular content (Raw footage), Insense Help Center, date not stated; checked September 8, 2026.
- Sample Brief — UGC with a Script, Insense Help Center, date not stated; checked September 8, 2026.
- Export caption tracks, Adobe, updated January 7, 2026.
- Copy projects, Adobe, updated January 7, 2026.
- How can I download files?, Frame.io V4 Knowledge Center, checked September 9, 2026.
- Store & play video in Google Drive, Google Drive Help, date not stated; checked September 8, 2026.
- Timeline exports, Descript Help Center, date not stated; checked September 8, 2026.
- Consolidate projects and libraries in Final Cut Pro for Mac, Apple Support, date not stated; checked September 8, 2026.
- Terms of Service, Collabstr, last updated September 9, 2025.
- Chapter 2: Copyright Ownership and Transfer, U.S. Copyright Office, §202.
- Guides Concerning the Use of Endorsements and Testimonials in Advertising, Federal Trade Commission, July 26, 2023.
