Define the update you expect to make
Archive an AI campaign around its likely next use. An agency expecting a price change needs editable offer graphics. A brand planning another language needs access to the approved voice script, captions and audio components. A team commissioning a new product colour needs the approved references and a clear record of which product details were fixed during production.
Agree the archive's contents, retention period and person responsible for access as part of delivery. Record what the studio will keep and what the client will receive. That agreement helps the next producer estimate an update without reconstructing the whole job from email attachments.
Keep the approved edit and its dependencies together
Retain the final project, the approved sequences and the media those sequences use. Include graphics, fonts where their licence permits sharing, audio, captions and any linked compositions needed to open the edit. Add a short note naming the editing application version and any required plug-ins.
Adobe's Premiere project-transfer guide explains how Project Manager can collect selected sequences and copy their media to a new location, or consolidate and transcode it. Treat collection as one step in the handover. Open the collected project and check its dependencies before calling the archive complete.
Keep the approved final export alongside the project as a visual reference. If a font is missing or an effect renders differently when the project is reopened, the reference makes the discrepancy visible.
Preserve the approved AI outputs and their context
Keep the actual image and video files selected for the campaign, including the versions used before retouching or finishing when those are part of the agreed archive. Name the approved references and record useful generation settings, model information and prompts where available and appropriate to share.
A prompt is only part of the production record. The next editor needs the selected output that made it into the film, plus the retouch, composite or grade that turned it into the approved shot. Saving those assets gives a future update a concrete starting point.
Mark rejected concepts clearly and keep them outside the approved delivery folder. If an early product rendering has the wrong label or proportions, the archive should make that status obvious to someone who never attended the review.
Test a small change before closing the job
Consider a fictional travel-accessory campaign with a 15-second film, three social crops and a seasonal offer card. The likely update is a new offer at the end of the film. Ask another editor to open the collected project, locate the approved sequence and change the offer in a duplicate sequence. They should be able to find the typeface, replace the text and export a short review without searching the original editor's computer.
If that test fails because an image remains linked to a desktop folder or a graphic requires an unavailable plug-in, resolve the dependency while the production team is still available. Where an editable element cannot be transferred, agree and document the usable alternative with the recipient.
For future offer versions, the clean-master guide explains which overlays and background material to prepare.
Leave a clear index and verify retrieval
- Approved version: Identify the final master, sequence and approval date.
- Dependencies: List application versions, plug-ins, fonts, linked files and any items the recipient must obtain separately.
- Assets: Identify approved source media, generated outputs, graphics, audio and captions.
- Usage: Point to the existing permissions and licence records, including any limits relevant to reuse. Ask the responsible owner to confirm a proposed new use.
- Storage: Name the archive location, access owner and agreed retention period.
- Reopen check: Record who opened the package, which sequence they checked and any unresolved dependency.
Keep a separately stored backup according to the team's storage policy, and test that the package can be retrieved. A folder's presence in a cloud drive does not tell the next producer whether all of its files are available locally or whether the project opens successfully.
Use the delivery checklist to define the initial handover. When the next campaign request arrives, the revision brief can identify the approved starting version and the exact change required.
Start a project 