Table of Contents
- Before the Launch Folder Locks
- Display, Retention, and Credit Do Separate Work
- What the Inventory Has to Name
- Credits Travel With the Files
- Approval Sits on the UAT Sheet
- One Exhibit for the Redline Meeting
Before the Launch Folder Locks
A producer keeps the campaign folder open on the last afternoon of QA. The Flash build is in there, with the motion assets and the launch screenshots. Local server directories are already being sorted into a delivery package and an internal backup archive. The client's staging environment is about to come down.
What may the studio keep, and what may it show?
Portfolio display, preservation copies, and collaborator credits belong in the production agreement. An email after launch is a poor place to discover that nobody wrote them down.
Final delivery directories for Flash-era campaigns routinely held 150 to 400 individual files: compiled SWF binaries, uncompressed QuickTime reference movies, XML configuration trees, layered Photoshop comps. That pile is the creative archive. It is also the pile that leaves with the staging server.
Informal portfolio requests sent 30 to 60 days after launch frequently went unanswered. The client's campaign manager had already rotated onto a new product cycle. In my experience, the last reliable week is the one when staging is still up. Producers and creative directors who want interactive experiences they can still open, and motion design and reels they can still show, settle retention, display, and credit while that manager is still on the account.
Display, Retention, and Credit Do Separate Work
Archive terms in a master services agreement do three different jobs. Write them as three clauses.
Public Display
Public display is permission to show agreed project materials in specified contexts: a studio portfolio, a presentation, an editorial case study. Standard embargo periods for public case studies run from 14 to 90 days after the initial media buy goes live. A seasonal retail window pushes the wait toward the long end of that range. Name the context and the date, or the permission floats.
Private Preservation
Private preservation is the right to retain agreed files and documentation under access and security conditions. Copies typically live on local offline storage or on non-indexed studio servers, behind multi-factor authentication, limited to full-time staff. A file in that vault can stay off the reel. Showing it takes the display clause.
Collaborator Credit
Collaborator attribution is a separate agreement about names, roles, placement, and corrections. It does not transfer with either of the other two grants.
Client legal teams routinely strike broad portfolio clauses — intellectual property exposure and unreleased product give them the grounds. Studio principals who split the ask into these three buckets give counsel something narrow enough to mark up instead of delete. Branded digital culture survives in the case study only if that markup leaves a usable remainder.
What the Inventory Has to Name
The Package That Still Plays
A self-contained preservation package for an interactive microsite needs the root SWF, every child SWF loaded through MovieClipLoader, local copies of the XML data feeds, embedded font outlines, and the FLV video streams, encoded with the On2 VP6 codec or with Sorenson Spark.
Early studio contracts asked for permission to display the final URL or the compiled application alone. External XML feeds, remote PHP scripts, and third-party streaming video servers went offline within a year. The portfolio piece broke. An archive inventory has to name externally loaded media, runtime requirements, and server-dependent interactions, or the retained build is a shell.
Blank Stage Risk
Retaining only the top-level compiled Flash container, without localizing relative paths to child SWFs, external XML configuration trees, and On2 VP6 FLV streams, produces a blank stage once the client's ad server is decommissioned.
Stills, Recordings, and the Reel Cut
Source files, delivered builds, screenshots, screen recordings, and written process documentation are five different materials. Each line of the schedule should say whether the studio may retain it, show it, or leave it behind.
Screenshots and screen recordings carry interactions the runtime can no longer execute. Process notes carry decisions the build will not explain. Together they are what a brand campaign case study can still quote after the servers go dark.
Commercial music synchronization licenses and union talent agreements for voiceover or on-camera performance frequently expire 12 to 24 months after the initial broadcast or digital flight date. Public cuts then mute or replace those tracks. The private copy can keep the original mix under the storage rules already written.
Air-gapped NAS volumes and LTO tape backups are audited every 18 to 36 months. The audit checks checksum integrity and whether legacy runtime players still execute on virtualized operating systems. Custody without a playback test is storage.
Five Lines for Counsel
Put five points in front of counsel, in writing: permission to retain copies, authorized custodians, storage conditions, access restrictions, and treatment of the files after the production relationship ends.
Where the studio works as a white-label subcontractor, file-level retention of working project files rarely survives an agency-of-record master agreement that compels destruction or return of raw.fla and.aep assets on final payment; in that seat, put the ask on delivered builds, stills, and recordings instead.
Credits Travel With the Files
Record the credit schedule beside the deliverables, not in a later email. It should hold agreed public names, project roles, studio affiliations where they matter, and the approved wording.
Producers compile the contributor ledger during the transition from design lock to technical build. They lock exact role phrasing with freelance animators and sound designers before those invoices are settled. That is the window the ledger actually has.
Phrase Before Payment
Confirm public role wording with freelance animators and sound designers while their invoices are still open. After settlement, the schedule has to live on whatever phrasing was already approved.
A typical interactive campaign credit schedule lists 8 to 18 individual roles. Internal creative direction and ActionScript architecture sit on different lines from external 3D animation, custom typography, and sound design. Write each line as a contribution description. Leave ownership language out of the block, so a credit does not read as responsibility for the entire campaign.
Assign one person to collect approvals and maintain the record. Disputed credit inquiries and spelling corrections, once verified, move to live portfolio pages and to Vimeo or YouTube descriptions within 5 to 10 business days. Studio history and people stay accurate only if someone owns that update.
Approval Sits on the UAT Sheet
Make archive approval a production milestone. The path runs from proposal to handoff, and each step has a document attached to it.
- During scoping, name the archive uses: portfolio, presentation, editorial case study, private preservation.
- Before production starts, negotiate the permissions and name the approver.
- Before launch, assemble the display package and bind it to the User Acceptance Testing sign-off sheet.
Account leads who attach the package to UAT catch the client's brand manager while that person is still inside the launch schedule. The review happens in the same week as the rest of the sign-off, under the same production pressure.
What the Brand Manager Reviews
The package delivered at final QA normally holds 6 to 12 high-resolution still frames, a screen-captured walkthrough of 60 to 120 seconds encoded at 60 frames per second, and 250 to 400 words of draft case-study text. Proposed credits travel in the same packet.
Written Sign-Off Only
Name the approval role, hold a 10-to-15-business-day review window, and require written sign-off. If that sign-off slips, escalate to the agency producer. Clearance is the written reply, inside the window.
One Exhibit for the Redline Meeting
Picture a Flash microsite that loads images from outside the shell and carries an accompanying motion sequence. Ahead of contract redlining, the executive producer drafts a single-page exhibit. One block lists the runtime files for restricted retention on the studio's private server. Another lists the flattened captures intended for public display. A third lists contributor roles for the credit schedule.
The hypothetical delivery is specific enough to mark up: a 450 KB shell SWF, 18 externally called asset SWFs, 12 high-bitrate FLV motion sequences, and a local XML localization file supporting three languages. Restricted retention covers that shell, those dependencies, and the localization file, with custodians and storage conditions named. Public approval covers selected screenshots and a walkthrough. The credit schedule lists roles as contributions.
Bring this material-by-material schedule to the contract discussion. Assign the approver before production begins.
A linear 90-second screen recording preserves the visual timing of the introductory motion sequence and still omits 4 of the 5 interactive product exploration branches built into the navigation tree.
















