How often does a client ask for old footage right after you thought the project was closed?
The project is delivered. The final invoice is paid. The editor has already moved on to the next job. Then a message lands 4 months later: "Can we get a vertical cut for a campaign?" or "Do you still have the interview selects without graphics?" or "We need the subtitle file and clean audio for localization."
That request is not the problem. The problem is what happens next. One producer checks 3 drives. Another opens an old chat. The editor tries to remember whether the final master lives in Google Drive, Dropbox, or on a local RAID. A finished project suddenly becomes an emergency search operation.
This is getting more expensive, not less. Teams are making more videos, repurposing more footage, and keeping more options alive after launch. That means a weak archive process now hits time, margin, and client trust at the same time.
What usually goes wrong after delivery
Most studios do not fail because they forgot to save a file once. They fail because they never defined what "archive" means in operational terms.
- Everything stays on expensive active storage - raw footage, cache files, exports, proxies, screen recordings, and random duplicates all sit in the same live folders.
- Nobody knows what must be kept - is the project file enough, or do you need camera originals, audio stems, subtitles, motion templates, and brand assets too?
- Retention is implied, not written - the client assumes you store everything forever, while the studio assumes the opposite.
- Closeout has no owner - once delivery happens, everyone mentally moves on and no one finishes the archive step.
- Retrieval is treated like a favor - the team spends half a day restoring a project, but the work never reaches the estimate or invoice.
The result is predictable. Either the studio overpays for storage forever, or it under-manages the archive and pays later in panic, unpaid labor, or both.
How to build an archive workflow that actually works
You do not need a huge media asset management rollout to fix this. You need a clear archive policy, a closeout routine, and visible ownership.
1. Define archive tiers before the project closes
Do not ask "What should we keep?" at the moment of cleanup. Decide by asset type.
A simple studio policy can use 3 tiers:
- Must keep - signed final masters, subtitles, clean audio, project files, licensed assets, and the exact deliverables promised in the deal.
- Keep for a limited period - camera originals, proxies, working graphics packages, intermediate exports, and interview selects.
- Delete after handoff - render cache, temp exports, duplicate transcodes, and failed experiments that have no legal or commercial value.
This is where many teams save real money. Not every file is archival. Some files support editing. Some support legal proof. Some support future upsells. Some are just debris.
What to do: create one retention table per asset type with a default period. For example, keep signed masters longer than temp working files, and keep source material longer on recurring client accounts than on one-off jobs.
2. Turn project closeout into a checklist, not a vibe
Archive quality is mostly decided in the 30 minutes after delivery. If closeout is informal, archive quality will also be informal.
Your closeout step should answer 5 questions:
- What files are part of the official archive package?
- Where is the archive location for this project?
- Who verified that the files open and match the delivered version?
- What is the retention deadline?
- What is billable if the client returns later for retrieval or a new cut?
Without this, the archive becomes a half-finished handoff. Someone uploads a final file to Vimeo or YouTube, another person keeps the project locally "just in case," and nobody knows which copy is authoritative.
What to do: add archive closeout as a required status before a project can move from delivered to closed.
3. Store retrieval metadata, not just the files
Many studios think archive means storage. In practice, archive is also findability.
If a producer cannot answer these questions in 60 seconds, the archive is weak:
- Which drive, bucket, or server holds the project?
- Are the source files complete?
- Which version was approved by the client?
- Are subtitles, clean audio, and graphics packaged?
- What rights or license limits apply to the materials?
- Who is the last person who touched the archive?
Basalt helps tie retention dates, delivery notes, and archive ownership to the project itself instead of leaving them in someone’s memory.
Metadata can stay simple. You do not need a giant taxonomy. You need the minimum facts that make future retrieval boring instead of heroic.
What to do: keep a standard archive record with project name, archive path, asset package contents, retention deadline, owner, and any paid retrieval terms.
4. Separate storage policy from client promise
Studios get burned when internal storage habits accidentally become client expectations.
If you never state the rule, the client may assume:
- you keep everything forever;
- retrieval is instant;
- new cutdowns are a small favor;
- source files are included automatically;
- re-exporting old projects does not affect your schedule.
That is not a technical problem. It is a scope problem.
Write archive terms into your commercial process. Define how long source materials are kept, what is included in final delivery, how retrieval requests are handled, and when restoration work becomes billable. This protects the relationship because the client hears the rule early, not during a frustrating search.
What to do: add one short archive paragraph to your estimate, contract, or final delivery note.
5. Plan for restore work as production work
An archive request is still work. It may involve pulling data from cold storage, relinking media, opening an old project version, checking fonts or plugins, exporting new formats, and validating that nothing broke.
Studios often lose money here because the task feels administrative. It is not. Restore work is post-production work with context debt.
That debt grows over time:
- storage may have moved;
- the editor may be unavailable;
- fonts or effects may have changed;
- the client may want a new format, language, or aspect ratio;
- the original approval history may be unclear.
What to do: price archive retrieval and legacy re-export as separate line items, or define a minimum service fee for projects that reopen after closure.
The minimum viable archive process for a small studio
You can build a usable archive system this week without buying anything new.
- Make a list of active and recently delivered projects.
- Create 3 retention categories: must keep, keep temporarily, delete.
- Add one archive owner per project.
- Define one naming rule for the final archive package.
- Record one archive location and one retention date for every closed project.
- Add a paid retrieval rule for reopened projects.
That alone will reduce search time, storage waste, and awkward client conversations.
Checklist: is your archive workflow protecting margin?
- Every delivered project has an archive owner
- The team knows which files are archival and which are disposable
- Source footage, project files, subtitles, and final masters are not mixed with temp files
- The archive location is recorded at the project level
- Retention periods are written down by asset type
- Client-facing archive terms exist before delivery
- Reopened projects trigger a billable restore workflow
- Someone verifies the archive package before the project is marked closed
- Old projects can be found in under 60 seconds
If 3 or more boxes stay unchecked, the studio is probably paying archive costs in hidden labor instead of visible process.
Frequently Asked Questions
Should we keep every source file forever?
Usually no. Keep what supports legal protection, future reuse, and the agreed service level. Delete or tier down files that only create storage cost without future value.
Is a review link the same as an archive?
No. A review page is useful for approval history, but it is not the same as a complete preservation plan for source files, project files, stems, subtitles, and restore readiness.
When should archive retrieval become billable?
As soon as reopening the project takes real team time. If someone needs to locate files, restore media, check the approved version, or export a new asset, that is a service, not a courtesy.
Who should own the archive process?
The producer or project manager should own the policy and closeout status. Editors can package files, but archive responsibility should not live in whoever exported the final cut last.
Related Reading
- AI Post-Production Workflow: Keep Control of Every Cut - more versions make archive discipline more important
- Video Production Brief Template: What to Ask Before Kickoff - archive expectations should be defined before production starts
- How to Build a Client Review Process That Actually Works - clear approvals reduce confusion when old versions return later
Summary
Archive problems rarely look urgent when a project ships. They become urgent later, when a client wants a re-cut, a new language version, a clean master, or the original selects.
That is why archive workflow belongs inside production management, not as an afterthought on a hard drive. Start small: define retention tiers, assign an archive owner, and make closeout a required step. The studio will spend less time searching, less money storing junk, and less margin rescuing old projects for free.