Getting Finished Projects Ready for the Archive Before Winter
Mid autumn is a good moment to close out the year's projects. Here is how to prepare finished work for long-term archive and walk a colleague through the handover.
Priya Raman · · 5 minutes to read
Why autumn suits a handover push
Mid autumn tends to be a quieter stretch between the summer shoots and the end-of-year rush. Deliveries are out, clients have signed off, and the drives on your desk hold projects that nobody is actively touching. That is exactly the point at which a project should be handed over, while the people who made it still remember what the files mean.
Left alone, a finished project begins to lose its context within weeks. Someone moves to another job, a folder gets renamed, a drive is reused. By the time a client asks for a recut next spring, nobody can say which export was the approved one or where the original camera cards ended up.
This article covers the handover part of archive work only: what a checklist should hold, how to prepare the project itself, and how to walk a colleague through it so the knowledge does not stay in one head.
What a handover checklist should contain
A good checklist is short enough to finish in one sitting and specific enough that two people would tick the same boxes. Start with identity: project name, client, shoot dates, and the person who owns the project through to archive. Then list the locations of every asset group, meaning raw footage, project files, audio, graphics and final exports.
Next, record decisions that are not visible in the files. Which cut was approved, which version went to broadcast or the web, and which alternates were deliberately kept. Add any licensing notes for music or stock material, since those restrictions travel with the project.
Finish with status lines: what was verified, by whom, and when. A checklist with a name beside each line is far more useful than one that simply says done.
- Project name, client, dates and owner
- Locations of footage, project files, audio, graphics, exports
- Approved cut and any kept alternates
- Licensing and usage notes
- Verification: who checked what
Preparing the project before you close it
Before anything moves to long-term storage, tidy the project against your folder and naming convention. Remove obvious duplicates, empty folders and render caches that can be regenerated. Keep what cannot be recreated: original media, project files, final masters and the documents that explain them.
Check that the project file opens and finds its media from the archive location, not only from the working drive. This is the most common failure. Links to a path that no longer exists mean an editor must relink hundreds of clips by hand.
Write a short readme at the top of the project folder in plain language. Two or three paragraphs on what the project is, how the folders are laid out and where to start are enough for a stranger to find their way in.
Choosing what goes into long-term storage
Not everything deserves the same care. Final exports and original footage are the core of most archives, and these should sit on at least two separate storage locations. Intermediate renders, proxies and temporary exports can usually be dropped once the project is signed off.
Decide this per project type rather than per file. A documentary with irreplaceable interviews keeps more than a quick social cut built from library clips. Write your rule down once so the next person does not have to guess.
Label physical drives clearly on the outside and keep a matching entry in a simple index. A drive without a label is a mystery within a year, however carefully its contents were organised.
- Keep: originals, project files, masters, readme
- Review: alternates, graded stills, audio stems
- Drop: caches, proxies, duplicate renders
Walking a colleague through it
The handover is not finished until someone else has used it. Ask a colleague who was not on the project to open the readme, find the approved export and locate one named piece of original footage, using only your checklist and folder layout. Sit beside them and stay quiet.
Every hesitation tells you something. If they cannot find the music licence, the checklist is missing a line. If they open the wrong export, your naming needs a clearer marker for the final version.
Fix what the walk-through reveals while the project is still fresh, then record the date and the colleague's name on the checklist. That small step turns a private tidy-up into a shared, verified record.
Making it a habit through the winter
One handover is useful, but the value comes from repeating it. Set a regular point, such as the end of each delivery, when the checklist is filled in and the project is closed. A project that is handed over the week it finishes costs a fraction of one rescued a year later.
Keep the checklist in a shared location where every editor and producer can reach it, and review it a couple of times a year. Add a line when something goes wrong, remove one that nobody uses.
If several people close projects, agree who signs off the archive step. One named owner per project keeps the process from dissolving into assumptions during a busy production season.
A handover checklist, a tidy project and a colleague who has tested both will do more for your archive than any storage upgrade. Use these quieter autumn weeks to close out finished work while its details are still in reach, and make the walk-through part of how every project ends, not a chore saved for later.
Send us a message
- Call us
- (505) 214-0873
- By email
- [email protected]