Handover, Archiving and Long Term File Storage

What should be handed over at the end of a project, what an archive must contain to be usable in three years, and who owns what.

The end of a video project is usually treated as the moment the final file is delivered, and the archive is whatever happens to remain on a drive. Two years later, when the client wants a small edit or a new language version, the question of what still exists and who has it becomes expensive. The archive is a deliverable, and deciding what it contains belongs in the quotation rather than in a panicked search.

A usable archive contains more than the finished films. It needs the source media, the project files from the edit, grade and graphics applications, the generated material with the settings that produced it, the 3D scenes and models, the fonts, the licensed music with its licence documents, the approved brand assets used, the final deliverables in every version, and a short readme explaining what is what. Missing any one of these can make the rest unusable.

Fonts are the item most often forgotten and most reliably fatal. A project file opened in two years on a different machine will substitute a missing typeface silently, and every title in the film will shift. Archiving the actual font files alongside the project, with a note of their licence, costs nothing and prevents a rebuild.

Licence documentation belongs in the archive for the same reason. A music track, a stock clip or a talent release whose terms cannot be located is a track that cannot safely be reused, which means a re-edit in future requires re-licensing or replacement. Keeping the licence PDFs with the project turns a future question into a two minute check.

For generative work the archive needs an additional item that conventional projects do not: a record of how each shot was produced. The reference frames, the conditioning inputs, the settings and the approved outputs. Without it, producing a matching shot later is guesswork, because the same description will not reproduce the same result. Studios that keep this log can extend a campaign a year later; studios that do not have to rebuild the look.

Ownership should be settled explicitly rather than assumed, because the two parties usually assume differently. Most studios treat project files and source assets as their working material; most clients assume they receive everything. Neither position is unreasonable and both are negotiable, but discovering the disagreement when the studio has closed or the relationship has ended is the expensive version of the conversation.

For 3D assets in particular the ownership question has real value attached. A correct model of a product or a machine can be re-rendered for years, and whether the client owns it or licenses its use changes what future work costs. Poushneh (2021) found that perceived proximity to a virtual product influenced purchase intention, and an asset that can create that proximity repeatedly is worth negotiating over explicitly rather than leaving to custom.

Storage should be planned rather than incidental. Source media for a shoot day is substantial, and a studio producing regularly accumulates a great deal of it. The practical arrangement is tiered: active projects on fast local storage, recent projects on slower local storage, and completed projects on redundant archive storage with a second copy off site. A single copy on a single drive is not an archive, it is a drive that has not failed yet.

Retention periods should be agreed rather than indefinite. Keeping everything forever is expensive and eventually unmanageable. A reasonable policy keeps source media for a defined period, perhaps two years, and the final deliverables, project files and generative records indefinitely, since those are small and are what a future edit actually needs. Stating the policy in the contract means the client can request extended retention if they want it.

The handover document itself is a small piece of work with a large payoff. A single page listing what was delivered, where the archive is, what it contains, what the licences permit and until when, who owns what, and who to contact, turns an archive from a folder into something a person who was not on the project can use. Mirzaei et al. (2025) argue that project approaches should be customised to the project at hand, and the amount of handover formality needed scales with how likely the material is to be revisited, which for corporate clients is almost always.

References

Poushneh, A. (2021). How close do we feel to virtual product to make a purchase decision? Impact of perceived proximity to virtual product and temporal purchase intention. Journal of Retailing and Consumer Services, 63, Article 102717. https://doi.org/10.1016/j.jretconser.2021.102717

Mirzaei, M., Mabin, V. J., & Zwikael, O. (2025). Customising hybrid project management methodologies. Production Planning & Control, 36(9), 1188–1205. https://doi.org/10.1080/09537287.2024.2349231