Creative workflows

Move from a stock-footage shortlist to the edit

Keep preview selections, approved source files and usage decisions connected as stock material enters a shared production library.

Keep a selection connected to its approved source

A stock-footage shortlist often begins with previews and ends with different source files supplied for production use. Preserve the connection between them. Suite provides a shared filesystem where the team can reach preview references, approved sources and editorial projects without confusing their roles.

Record the vendor asset ID and the production's own source ID for each candidate. Keep the person responsible for usage approval in the record. This guide describes production organization; the responsible owner must determine whether the actual usage is permitted under the relevant agreement.

Separate selection from approval

Give candidates a clear state: being considered, approved for the specified use, rejected or awaiting a decision. A preview's presence in the shared library is not evidence that its use has been cleared. An agent helping find material should return candidates and provenance, not silently make the approval decision.

Keep the intended use with the selection, including the project and delivery context. If that context changes, route the decision back to the owner rather than assuming an earlier approval covers the new work.

Plan the source replacement

When an approved production file arrives, record which preview it replaces and verify timing, frame rate, crop and audio. A higher-quality file may not be a drop-in replacement if its duration or start differs. Use the editing application's supported relink process and inspect the resulting timeline.

Adobe's media and project guidance for Productions provides application-specific shared-storage practices. Suite's role is the accessible media path beneath the chosen project structure, not an automatic licensing or relinking service.

Retain provenance at delivery

Include the accepted source IDs and responsible approval record in the project's delivery documentation. Keep preview files distinguishable so they do not accidentally become final exports. An automated check can report whether a timeline's declared inputs match the approved manifest when the application exposes that information.

Test the workflow with one preview-to-source replacement and have a second editor verify the result. Success means the approved asset is usable in the edit and its origin remains clear. Explore Suite Managed for a shared library that supports those source relationships throughout production.

Put the idea to work

Start with your workflow.

Bring shared files into your familiar applications with Suite Managed, or connect your own supported storage with S3 Native. S3 Native requires at least 20 TB of active storage.