How do I organize raw UGC footage so editors can find every usable moment?

01

What folder structure keeps originals safe while making selects reusable?

Separate archival storage from editorial organization: originals establish the source of truth, while role-based selects make useful moments easy to retrieve.

Adobe Premiere bins can contain source files, sequences, and other bins, allowing editors to create nested project structures. Premiere editing is also non-destructive, meaning edits in the project do not alter the underlying source footage. Those mechanics support a two-layer UGC library: stable originals plus editorial records that point to usable ranges within them. Adobe’s bins overview explains this underlying organization model.

A practical top-level structure is: 00_INBOX, 01_ORIGINALS_READ_ONLY, 02_SELECTS_BY_ROLE, 03_WORKING_MEDIA, 04_PROJECTS_AND_SELECT_SEQUENCES, 05_ITERATIONS, 06_APPROVED_EXPORTS, 90_UNUSABLE, and 99_RIGHTS_BRIEFS_AND_RELEASES. Inside the originals archive, use CREATOR/YYYY-MM-DD_SHOOT. Inside working media, separate proxies, transcripts, synchronized audio, and other generated files.

Do not copy one source video into several role folders. A single statement may address an objection, describe a sensory detail, and provide an honest personal reaction. Represent those uses with multiple tags, markers, subclips, or database records pointing to the same original. Premiere markers can identify specific moments and hold comments, while subclips can represent named In and Out ranges without replacing the source. See Adobe’s markers overview.

02

Which communication roles should every UGC library include?

Use a controlled role taxonomy that describes what each moment contributes to an edit, and allow a clip to carry more than one role.

A hook is an opening statement or visual intended to earn attention. Useful sub-tags include question, confession, result-first, contrarian statement, and visual interruption. A problem state shows the frustration, failed alternative, inconvenience, or emotional condition that precedes the product.

A demonstration clearly shows setup, application, use, cleanup, or a process. A sensory detail communicates texture, sound, material, fit, scale, consistency, taste, or movement. Keeping these categories separate helps an editor find visual evidence without reviewing every talking-head take.

Claim-safe proof is footage whose express and implied claims have been reviewed and matched to appropriate support. It can include a demonstrable feature, substantiated result, qualified comparison, or accurately described personal experience. Objection footage addresses hesitation about matters such as complexity, fit, durability, price, or skepticism. A clip should not receive a proof label merely because it sounds confident.

A reaction records surprise, relief, approval, discovery, or another genuine response. A transition is connective footage such as picking up the product, opening packaging, changing scenes, or moving a hand through frame. A CTA communicates the next action. Room tone is uninterrupted ambient sound from the recording environment that may help an editor smooth audio cuts.

Keep unusable material outside normal search results while retaining a reason code. Examples include bad focus, severe noise, an incorrect product variant, missing rights, a prohibited claim, or an accidental disclosure of private information. Distinguishing technical, rights, and claim failures makes it clear whether a take can be repaired, reviewed, or must never be used.

03

What metadata makes raw footage genuinely searchable?

Metadata should identify the source, describe the product and editorial function, establish usage permissions, and preserve the clip’s history across iterations.

For identity and lineage, record an asset ID, original filename, parent source asset ID, creator, shoot date, take number, brief or roadmap ID, and source In and Out timecodes. The asset ID should remain stable even if a working file is renamed. A select made from 00:12:05 to 00:12:18 can then be traced to the exact original and recovered if a project file breaks.

For product context, record product, variant, shade, size, flavor or model, packaging version, language, and market where relevant. For editorial context, add primary role, secondary roles, transcript keywords, orientation, shot type, audio condition, quality status, and suggested position such as opening, body, or close. Orientation should be recorded explicitly—such as 9:16, 1:1, or 16:9—rather than inferred from a filename.

For permissions and compliance, record rights status, permitted channels, territory, usage start and expiration dates, paid-media permission, required disclosure, and claim-review status. Keep the release or agreement reference beside the record rather than relying on a vague label such as approved.

Premiere can search XMP metadata properties and values, and its metadata tools can carry information such as descriptions, copyright details, and workflow fields. Adobe notes that some XMP changes are written to source files. If your definition of an untouched original requires the file to remain bit-for-bit unchanged, write metadata only to working copies or maintain it in an external catalog. See Adobe’s guidance on searching XMP metadata.

04

How should creators ingest and tag a new footage delivery?

Process every delivery in the same order so originals, rights information, transcripts, selects, and editorial notes cannot drift apart.

The first viewing should concentrate on file integrity and technical quality. The second should identify communication roles and useful time ranges. Separating those passes reduces the chance that a persuasive line distracts from a focus, audio, rights, or claim problem.

Transcribing spoken source files makes dialogue searchable and reduces repeated scrubbing. Premiere can transcribe individual source files and display their dialogue in its Transcript panel, according to Adobe’s source transcription documentation. Transcripts still need human review for product names, technical terms, and ambiguous speech.

1. Copy the complete delivery into 00_INBOX; do not reorganize files while a transfer is incomplete.
2. Verify that expected files open correctly, then place camera originals in the read-only archive under creator and ISO-formatted shoot date.
3. Assign one immutable asset ID to each original while retaining the creator’s original filename as metadata.
4. Attach the brief, product, variant, orientation, rights document, and applicable usage dates.
5. Generate working proxies or synchronized audio without overwriting the archived source.
6. Transcribe spoken footage and correct important product names, claims, and keywords.
7. Review for technical failures, rights concerns, disclosure problems, and statements requiring claim review.
8. Review again for communication roles; add markers, subclips, or source ranges with primary and secondary tags.
9. Build select sequences or filtered views for hooks, problems, demos, proof, objections, reactions, transitions, CTAs, and room tone.
10. Move rejected ranges or files out of normal search results and assign a specific unusable reason code.

05

How should files, selects, and iterations be named?

Use deterministic names containing stable IDs and version numbers; avoid subjective labels such as “good” or “final.”

A workable source-select pattern is [asset-id]_[creator]_[product-variant]_[role]_[orientation]_[take-or-range]. Examples include A0142_Maya_Serum30ml_Hook_9x16_T03.mov for an original take and A0142-S02_Maya_Serum30ml_Demo_9x16_001205-001218 for a select derived from a bounded source range.

For edited variations, use [concept]_[hook]_[body]_[cta]_v##, such as C07_H03_D02_CTA01_v04. Keep the timeline and export version synchronized. Adobe recommends year-month-day ordering, leading zeros, coordinated sequence and export numbers, and avoiding the word “final” in versioned filenames. Those conventions are documented in Adobe’s project setup guidance.

Each iteration record should identify its concept, source asset IDs, select ranges, hook, body, CTA, editor, version, and the variable deliberately changed. If the hook is the variable, keep the remaining recorded ingredients explicit rather than calling the export merely hook test. Google’s experiments guidance recommends testing one variable at a time and keeping experiment records so previous findings can inform later work. See Google Ads Experiments guidance.

06

How do you separate usable proof from risky advertising claims?

Give proof footage an explicit review status, retain its supporting reference, and keep unreviewed or prohibited claims out of normal editorial search results.

The FTC states that advertising must be truthful, non-deceptive, and supported by evidence where appropriate; this applies to both express and implied claims. Creator footage does not become substantiated simply because the creator sincerely repeats a result or because the product is visible on screen. Review the complete impression created by the words, demonstration, captions, graphics, and edit. See the FTC’s Advertising FAQs for small businesses.

Useful statuses include APPROVED_OBJECTIVE_CLAIM, HONEST_SUBJECTIVE_EXPERIENCE, NEEDS_SUBSTANTIATION, DISCLOSURE_REQUIRED, and DO_NOT_USE. “Claim-safe” should mean reviewed under your process, not guaranteed legally safe in every edit. A compliant source line can acquire a different implication when shortened, juxtaposed with a demonstration, or paired with an unsupported on-screen result.

Record material-connection and disclosure requirements alongside rights. The FTC says endorsements should reflect honest experience and material connections such as payment should be disclosed. Necessary qualifications should be clear and conspicuous rather than hidden away from the relevant statement. Editors need this information at selection time, not after a cut is complete.

07

How can ATIYO preserve the connection between footage and creative iterations?

ATIYO can preserve creative context around assets, briefs, roadmap work, iterations, and reusable learnings, while source media and performance reporting retain their distinct roles.

A footage taxonomy remains useful without ATIYO: it can live in Premiere, a spreadsheet, or another asset catalog. The operational problem appears when briefs, source assets, edits, decisions, and later learnings are stored in different places. ATIYO is designed to organize those creative-strategy records so a team can retain the relationship between what was requested, which asset was used, what changed, and what was learned.

Creators using ATIYO can follow the broader Content Creator Workflow, review the process for uploading and storing assets in the Vault, and connect source material to planned work by attaching a Vault asset to a roadmap creative. Maintain the immutable asset ID and source time range in the relevant record so the editorial lineage remains portable.

Media performance remains in the ad platform. ATIYO preserves the creative context and learnings around the asset, including what was tested, which source footage was used, and what the team learned. ATIYO does not connect to ad accounts, buy media, calculate ROAS, or independently know performance unless a user records the relevant information.