To deliver UGC raw footage to a brand, confirm the exact camera clips it needs, keep those files separate from edited exports, add a readable file list, and test the recipient’s download access. A clean video without captions is still an edit; it does not replace the recordings used to make it. This guide gives you a practical handoff process, a worked example and a message template, with Trendy helping you prepare the creative material that comes before delivery.
Research checked 14 November 2026. This is an evergreen production guide. The sample assignment and filenames below are fictional, not a customer campaign or evidence of results.
First answer: what does the editor mean by raw footage?
A request for “the raw files too” is incomplete. An editor might want individual camera recordings to create a different opening, the approved edit without captions, or the project containing the timeline. Each request produces a different package. Ask what the next person needs to change before copying files into a folder.
In creator work, raw footage often means recordings before the final edit. It does not automatically mean the technical RAW recording format. A normal phone recording can be an unedited source clip even when the camera saved a compressed video file. Use a concrete description: “six selected original camera files, with recorded audio, no trimming or added text.”
| Deliverable | What the recipient receives | What it does not provide |
| Selected original clips | The agreed camera files, including the captured sound | Every recording on your phone |
| Trimmed selects | Agreed useful sections exported from particular takes | Untouched originals unless separately included |
| Clean edited master | A completed edit with specified layers omitted | Unused takes or an editable timeline |
| Captioned final | The finished viewing version with agreed captions | The ability to remove burned-in captions |
| Editable project | A project plus the media and dependencies agreed for it | Guaranteed compatibility with every editor |
Do not use “clean” without explaining it. Does it mean no subtitles, no music, no graphics, or all three? A master with speech but no music serves a different purpose from a silent file. Record the answer in the delivery note rather than relying on a folder name.
If the assignment is still being discussed, use the UGC brief template to define the package first. The process below starts once you know which materials are due.

Build the handoff around the next edit
Imagine a small sports-accessory shop commissioning a demonstration of packing a foldable gym bag. Its editor wants to test two openings using the same packing sequence. The agreed package contains six selected camera clips and two finished viewing versions. It excludes the editing project and unrelated recordings. There is no real brand, price or performance claim behind this example.
The important question is whether the editor can reconstruct the promised sequence. A beautiful close-up of a zipper is not a substitute for a missing wide shot showing the bag being packed. Match each file to a role: opening, action, detail or closing line. Identify gaps before the recipient discovers them in the timeline.
Here is a compact manifest for that fictional batch. “Source” means the name of the original retained in your own archive; the delivery name makes its role readable. Keep that relationship even if you use a different naming system.
| Delivery name | Source file | Purpose and note |
| BAG_HOOK-A_T02.mov | IMG_4102.mov | Spoken opening about finding a towel; selected full take |
| BAG_HOOK-B_T01.mov | IMG_4104.mov | Alternative opening about packing for a class |
| BAG_PACK_T03.mov | IMG_4110.mov | Continuous packing action; keep the sequence intact |
| BAG_ZIP_T02.mov | IMG_4113.mov | Close view of the actual zip closing |
| BAG_CARRY_T01.mov | IMG_4115.mov | Carrying the packed bag; no durability claim |
| BAG_CLOSE_T02.mov | IMG_4118.mov | Spoken closing line about checking dimensions |
This is a file register, not proof that the product has any particular capacity or strength. The item shown, spoken facts and recorded action must agree. If you need help planning what evidence to film, the UGC product demonstration guide covers the earlier shooting stage.
Step 1: copy the recordings before reorganizing them
Make a working copy of the agreed recordings and verify that it opens before renaming or selecting anything. Keep the original camera filenames in your archive. Work on copies so an accidental rename or deletion does not break the only relationship between a recording and your notes.
On iPhone, Apple documents an option to export unmodified photos and videos to external storage. Use the instructions appropriate to your device and software. If you need the original, do not quietly substitute an export from a social app or a completed editing timeline.
On another phone or camera, use its supported file transfer method and check the resulting files. Do not promise that every messaging attachment is recompressed or that every cloud route preserves originals. The useful question is what your chosen route actually delivers. A small test file can reveal an unexpected conversion before you send a large batch.
Keep archive and delivery separate. Your archive might contain false starts, personal conversations or other clients’ material. The delivery folder should contain only what this recipient is meant to receive. Check both image and sound; a private conversation can remain audible even when nobody else appears in the shot.
Step 2: select takes without changing their meaning
Watch every selected clip from beginning to end with sound. Check the action, focus, speech and product consistency. If the agreement calls for full original takes, preserve them. If it calls for trimmed selects, identify them as trims and retain the source reference.
A useful selection is more than a technical pass. Consider whether the editor has the start and end of an action, a usable pause around spoken lines and enough context to understand what happened. Do not remove a failed action from a file and then label the result an uninterrupted demonstration. Explain necessary cut points in the manifest.
Keep observations specific. “T02 is the selected take; T01 contains an interrupted line” is actionable. “Use the best one” transfers your selection work to the editor. If a necessary shot is absent, report the gap and discuss a pickup rather than adding an unrelated clip to make the count look complete.
Step 3: separate files by what they are
A small package can use three clearly named folders: selected originals, final edits and delivery notes. Add a project folder only when it is part of the assignment. Keep your private archive outside the shared parent so it cannot be included accidentally.
For the example, put the six camera clips in selected-originals. Put BAG_HOOK-A_9x16_v01.mp4 and BAG_HOOK-B_9x16_v01.mp4 in final-edits. Put one manifest document in delivery-notes. That makes nine delivered files: six sources, two edits and one register. If you add a separate clean master, change the count and explain its purpose.
Use filenames that communicate a small number of things consistently: project, role, take or version, and format when useful. The source clip uses a take number; a changed finished edit uses a version number. Renaming v01 to “final” does not tell anyone whether it replaced v02.
Record technical details where they matter to this editor: actual dimensions, frame rate, duration, recording format and audio treatment. Do not turn your preferred settings into universal UGC requirements. If the recipient needs a different format, agree on a conversion copy and keep the original distinguishable from it.

Step 4: test access and the downloaded file
Upload to the delivery location agreed with the recipient. Google’s current Drive sharing guidance distinguishes viewing, commenting and editing, and notes that organization policies can limit external access. Choose access for the intended reviewer; a public link is not a default requirement for client work.
Then test the recipient’s actual task. Can they reach the correct folder, see the right batch, download a source clip and open it? Testing while signed into the owner account proves very little about another person’s permissions. For restricted sharing, ask the intended recipient to confirm from their invited account; a signed-out access-denied screen may be expected.
Downloading deserves its own check. Google’s download help explains that an owner can restrict downloads. A working preview therefore does not establish a usable handoff. Do not grant editing rights merely to troubleshoot a download without first understanding the relevant permission.
Google also documents video playback in Drive. Compare a downloaded file with your local copy before declaring that a soft preview means the original was damaged. Check duration, picture, audio and file details. Matching byte size is useful evidence, but on its own it is not a complete content comparison.
For a visual example of the distinction between a stored file and its sharing action, see 14 Olexiy Maltsev’s original mobile Drive tutorial, published 23 May 2018 in Russian. Notice the separate access controls rather than copying its old button layout. Use the current help above for today’s interface. This is a source link, not an inline player or a demonstration of UGC results.
Step 5: send a note that makes review possible
The handoff message should answer what is included, what changed, which files are current and what response you need. Keep it short enough to read beside the folder. A link alone makes the reviewer infer all of those things.
Adapt this fictional example:
“Hi! The gym-bag batch is ready at [delivery link]. It contains six selected original camera clips with recorded sound, two captioned 9:16 edits, and one manifest: nine files in total. Current edits are BAG_HOOK-A_9x16_v01.mp4 and BAG_HOOK-B_9x16_v01.mp4. The editable project and additional clean masters are outside this package. Please confirm that you can download and open the originals. For creative feedback, send one consolidated list identifying the filename and time position by [agreed review date].”
Technical receipt and creative acceptance are separate. “The files download” confirms access; “this edit is approved” records a different decision. Follow the review and payment arrangements you already agreed rather than inventing new terms in the delivery message.
If you replace a clip, issue a specific change note. For example: “BAG_CLOSE_T03.mov replaces BAG_CLOSE_T02.mov; the closing line now matches the approved wording. The other five source files are unchanged.” Update the manifest and make the current set unambiguous without silently overwriting a file the editor may already be using.
When something goes wrong
| Symptom | Check before resending | Practical next action |
| The brand requests access | Recipient account and folder permissions | Confirm the invited account or agreed sharing method |
| Preview works but download fails | Download restrictions and current provider help | Correct the relevant setting or use the approved alternative |
| Downloaded video will not open | Original playback and recipient software support | Test one agreed compatible conversion, clearly labeled |
| Only the captioned final arrived | Manifest versus the promised source list | Upload the missing camera clips; do not rename the edit “raw” |
| Editor cannot find a needed action | Source names, roles and actual recordings | Identify the clip or report that a pickup is needed |
| Two versions look current | Version numbers and change note | Name the replacement explicitly and update the manifest |
Use Trendy to prepare reusable creative material
The delivery becomes easier when the original script has clear scene roles. Trendy’s creator app helps develop profile-informed ideas, scripts, carousels and posts. Give it your audience, product facts, available location and the material the editor needs; review the proposed output against what you can honestly film.
A practical request is: “Plan a gym-bag demonstration for people heading to an evening class. I can film packing, closing the zip and carrying the actual bag. Draft two distinct openings, a ready-to-shoot script with spoken lines and camera actions, and a source-shot checklist. Do not invent capacity, comfort tests, customer experience or results.”
Keep the final checklist with your content notes, then add the actual filenames after filming. Planning labels help you know what to capture; they are not evidence that a file exists or that the brand has accepted it. You still select, inspect, transfer and verify the delivery yourself.
One creative direction can also produce different platform-native drafts when the assignment permits them. A Reel or TikTok needs a visible action and speakable script. An Instagram carousel can explain the packing sequence slide by slide; a visual post can show one permitted original still. A LinkedIn post can discuss the production decision, an X post can share one concise lesson, and a Threads post can invite people to describe their own packing problem. Agree which of these are actual deliverables before adding them to the folder.
Final checklist and common questions
- The package matches the agreed list, including the meaning of raw and clean.
- Every delivered file has been watched or opened, and source references remain traceable.
- The manifest counts the actual current files and explains any gaps or replacements.
- The intended recipient can download and open a representative source clip.
- The delivery note requests receipt and explains the agreed feedback step.
Does raw footage include every take?
Only if that is the agreed package. Selected full takes, all usable takes and trimmed selects are different scopes. Name the clips and treatment instead of assuming that “all files” means your entire camera roll.
Can a clean export replace an editing project?
No. It provides a viewing file with specified layers omitted. A project is a separate deliverable whose software, media and dependencies need their own agreement and compatibility check.
Does delivering files mean I can publish them in my portfolio?
Keep portfolio publication, brand usage and file delivery as separate agreed actions. Refer to your existing arrangement before posting. A technical handoff checklist does not decide publication permissions.
What should I improve after the first delivery?
Record the exact question that caused extra work: an unclear filename, a missing close-up, an ambiguous clean version or a blocked download. Add that check to the next shot plan or handoff note. A useful improvement is one that makes the next editor’s task clearer, rather than simply creating a larger folder.