Editable UGC Project Handoff Checklist for Creators

01

Which project file and sequence should you deliver?

Include the primary editable project and identify one unambiguous delivery sequence.

Deliver the native project, library, or project archive accepted by the brand. In the README, state the editing application and exact version used. If the recipient needs an older Premiere version, discuss compatibility before delivery; Adobe documents XML export as one route for moving work to an earlier major version, although some information may not transfer perfectly (Adobe).

Remove abandoned tests when safe, but do not destructively simplify the approved edit. Name the main sequence clearly—for example, Brand_Product_Concept_9x16_v03—and give the matching reference export the same base name. This prevents the next editor from guessing which timeline produced the approved video.

1. ☐ Native editable project, library, or accepted archive
2. ☐ Editing application and exact version
3. ☐ Clearly labeled main sequence
4. ☐ Matching sequence and reference-export version numbers

02

Which source media and proxies belong in the package?

Include every original file used by the edit and any proxies needed for an efficient handoff.

Collect all video clips, voice-overs, product images, screen recordings, stills, room tone, sound effects, and other source media. Do not rename or rearrange media after collection unless you retest the package. Premiere can mark clips offline when linked files are moved, renamed, or deleted (Adobe).

If you used proxies, place them in a dedicated folder and verify that they correspond to the full-resolution originals. Proxies are lower-resolution editing copies; they are not substitutes for the master media. Adobe’s Premiere workflow normally uses full-resolution media for export unless proxy output is specifically selected (Adobe).

1. ☐ Original video, audio, photos, screen recordings, and voice-over
2. ☐ Full-resolution media rather than proxies alone
3. ☐ Clearly separated and predictably named proxy files
4. ☐ Preserved camera-card structure where relevant

03

What linked graphics, fonts, and captions are required?

Collect linked design assets, document font requirements, and provide captions in editable and portable forms.

Include logos, product images, overlays, backgrounds, stock media, Photoshop or Illustrator files, motion-graphics templates, and linked After Effects projects. A Premiere package may not automatically collect every dependency behind a dynamically linked composition, so verify those files separately.

List each font family, weight, source, use, and approved fallback. Do not automatically redistribute font files. Adobe says Adobe Fonts files cannot be packaged or transferred to another user; the receiving editor needs appropriate access or licensing (Adobe).

Keep captions editable in the timeline and include a sidecar file such as SRT when available, plus a transcript if useful. Premiere can export captions as burned-in text, embedded data, or a separate sidecar file (Adobe). Label languages separately and check spelling, timing, punctuation, and brand capitalization.

1. ☐ Logos, product images, design files, templates, and linked projects
2. ☐ Font list, licensing notes, usage, and fallbacks
3. ☐ Editable timeline captions
4. ☐ Caption sidecar files and transcript where available

04

How should you document music, color, and effects?

Supply transferable assets where permitted and document every dependency the recipient may need to license or install.

For music and sound effects, record the track title, artist, library, asset or receipt ID, download date, permitted usage, and attribution requirement. Include the audio file only when its license permits transfer. Platform-specific access should not be treated as universal permission: TikTok’s Commercial Music Library, for example, exposes music cleared for specified TikTok commercial uses and regions (TikTok).

Collect or document custom LUTs, camera transforms, raw sidecars, effect presets, transitions, codecs, and third-party plug-ins. State plug-in names and versions. Adobe notes that third-party plug-ins and LUTs can contribute to project-specific rendering problems, which makes a flattened visual reference important (Adobe).

1. ☐ Music and sound-effect identification and license records
2. ☐ Transferable audio files or clear replacement instructions
3. ☐ LUTs, presets, transforms, and raw sidecars
4. ☐ Plug-in, transition, and codec names and versions

05

Which exports and documentation make the handoff understandable?

Provide a visual target, useful alternate exports, and a README that explains the package without a call.

At minimum, include a version-matched reference export showing the intended timing, framing, graphics, captions, color, and audio balance. Also include the approved high-quality master and any contracted alternates: clean or textless video, no-caption video, caption-burned review copy, voice-over stem, or music-and-effects stem.

The README or delivery manifest should identify the brand, campaign, concept, creator, application version, main sequence, frame size, frame rate, audio sample rate, exports, folder map, fonts, plug-ins, LUTs, music records, known exclusions, delivery date, and contact details. State plainly when an asset has been omitted because it cannot legally be transferred.

1. ☐ Version-matched reference export
2. ☐ Approved master and requested clean variants
3. ☐ Requested audio stems
4. ☐ Complete README or delivery manifest

06

How do you run the required relink test?

Move the complete package away from its working location, open the copied project, and export from that copy.

Copy the delivery folder to another drive, computer, user account, or temporary directory. Disconnect or rename the original working-media location if practical, then open only the copied project. This matters because Premiere can use current or previous file paths when searching for offline media, allowing an incomplete package to appear healthy on the creator’s computer (Adobe).

Confirm that originals and proxies reconnect, graphics display, captions remain editable, fonts are available or documented, and LUTs and effects load. Compare the main sequence with the reference export, then complete a fresh test export. Fix every unexplained offline item before uploading.

1. ☐ Copy the package to a genuinely separate location
2. ☐ Open the copied project rather than the working project
3. ☐ Confirm that no required media or graphics are offline
4. ☐ Check captions, fonts, effects, LUTs, and proxies
5. ☐ Compare against the reference export
6. ☐ Complete and review a fresh test export

07

What should you archive after delivery?

Keep an unchanged copy of the final package and preserve its creative context separately.

After the relink test passes, create the delivery archive and retain an identical archive copy. Keep the final manifest and reference export with it so you can establish what was sent if the project returns for revisions.

ATIYO can organize the brief, roadmap, assets, iterations, brand context, and reusable learnings around the work. It does not replace the editable project package or licensing records. Media performance remains in the ad platform, while ATIYO preserves creative context and learnings recorded by the user.

1. ☐ Final delivery archive created after testing
2. ☐ Identical retained archive copy
3. ☐ Manifest and reference export stored with the archive