Archive Intake Interviews: Asking the Right Questions Before Files Enter Storage
Most media archives do not fail because of storage. They fail because the files arrived without context. A folder of clips labeled with dates and vague names becomes unusable within a year, not because the files are damaged but because nobody can say why they were kept, what they show, or whether they are still accurate. An intake interview is a short, structured set of questions you answer for each batch of media before it enters long-term storage. It turns archiving from a filing chore into a set of decisions. The method below works for a personal creator library, a small brand's image collection, or any body of public-facing video and photos, and it applies no matter which platform or site the finished work appears on.
Why interview a batch instead of a single file
Reviewing files one at a time invites inconsistency. You may tag one clip thoroughly and skim the next, and by the end of a shoot your attention has drifted. Treating a batch as a unit forces a shared set of answers. A batch might be one photo session, one month of short videos, or everything from a single location. Give the batch a short name that describes its origin, such as the date and the setting, and record the interview answers in one plain text file kept next to the media. The file does not need to be elaborate. Its job is to keep the reasons for the batch alongside the batch itself.
Batch interviews also reveal duplication. When you list what the batch contains, you often discover that three versions of the same frame exist, or that a set of drafts was never meant to be public. Catching this at intake is far cheaper than discovering it during a later cleanup.
The five intake questions
Question one asks what the batch is for. Possible answers include publishing, reference, reuse in future work, or simply keeping a record. A batch with no clear purpose is a candidate for shorter retention or for deletion. Question two asks where the media came from: which device, which session, which collaborator, and whether any part was produced by someone else. Provenance matters later when you need to explain a file or decide whether it can be reused.
Question three asks what the batch shows and what it does not. Write a sentence or two describing the subject matter in neutral terms. Avoid adjectives that will mean nothing in five years. Question four asks what rights or permissions attach to the material. If someone else appears in the frames, or if a location or piece of music is involved, note what you were told and by whom. Do not treat this as legal advice; treat it as a record of what you know. Question five asks how you expect to retrieve the batch. If you cannot describe a likely search, the tags are probably too thin.
Deciding what gets a longer retention period
Not every batch deserves the same treatment. A useful way to decide is to sort batches into three groups: working material, reference material, and finished output. Working material includes raw captures, outtakes, and drafts. It is valuable for a while, usually until the finished version is locked, and then its value drops. Reference material includes location scouting, lighting tests, and style studies that you may want to consult again. Finished output is what the audience saw, and it is the easiest to recover from a public source, which means your archive copy mainly serves your own records.
Set a review date for each group rather than an indefinite hold. Working material might be reviewed three months after the project closes; reference material annually; finished output whenever your catalog is audited. A review date turns a vague intention into a scheduled decision.
A short checklist for each intake session
Before closing an intake session, confirm the following in plain language. Does the batch have a name that someone else could understand? Is the purpose written down in one sentence? Is the provenance recorded, including any collaborator or device? Are rights notes present for any identifiable person, location, or licensed audio? Has the batch been checked for duplicates and superseded drafts? Is there a review date? Can you describe two or three ways you would search for this batch later?
If any answer is no, leave the batch in a staging folder rather than the archive. Staging is a holding area, not a failure. It keeps the archive clean and signals that the batch still needs attention.
Finally, keep the intake notes in the same system as the media, not in your memory or a separate app you may abandon. An archive is only as good as the context stored with it, and context that lives in your head disappears the moment you forget it.