Practical guide · Prepared with AI assistance
Make your visual archive searchable and secure. Separate approved files, raw footage and usage permission records.
Three takeaways from this article
- Standardise version naming.
- Keep approved material separate.
- Record usage restrictions.
Design folders for the person searching them
The person who created a file may remember what was filmed yesterday; a new team member will not. Use brand, campaign, product and date information clearly in the archive. Choose version numbers instead of names such as final, final2 and latestfinal. Keep an accessible record, separate from the file, of who may use the visual, for what purpose and with which permission.
Keep approval status visible
Separate raw files, files being edited, files awaiting approval and files ready to publish. Do not leave material whose usage period has expired or whose product information has changed in the current folder. Moving old versions to an appropriate archive rather than deleting them may make comparisons easier. Restrict access to backups; do not store private customer or employee material behind a publicly accessible link.
Example: a campaign with three products
In a hypothetical campaign, each product has raw footage, selected images and a final posting file. When a price changes, the version prepared for publication must be updated as well as the design file. Including the source product code in the archive makes all related derivatives easier to find. Do not put personal information such as a customer's phone number in a file name.
Action card: Turn the plan into a concrete deliverable
The table below is a working example prepared for this guide. Fill the rows using your own resources and workflow; do not mark unverified information as completed deliverables.
| Decision / task | Requirements to be considered ready |
|---|---|
| File name | Product, date, format and version |
| Status | Distinguishing raw, draft and approved material |
| Permission record | Permitted uses and restrictions |
| Backup check | A file copy that can actually be opened |
Test the archive regularly
Ask another team member to find the latest approved version of a randomly selected piece of content. If they find the wrong file, simplify the folder structure. Having a backup does not mean restoration has been tested; check that critical files can be accessed and opened. Do not add material with unclear usage permissions to an automatic publishing pool.
Tagging with AI
Image descriptions and topic tags can be generated, but personal identities or sensitive characteristics must not be inferred. Compare the tool's suggestions with product information. Assess privacy and usage terms before uploading files to an external service. Human review is necessary because tagging errors can cause the wrong material to be selected from the archive.
Pre-publication checklist
- Standardise version naming.
- Keep approved material separate.
- Record usage restrictions.
- Test opening files from the backup.
Frequently asked questions
Can all files be kept in one folder?
It may be possible for a small number of files, but it makes searching harder as the team grows. Organise folders around the need to find files again and choose the correct version.
Should old designs be deleted?
Consider the required retention period and intended use. Separating old files from the current publishing pool reduces the risk of misuse while preserving the ability to go back.
This guide was prepared with AI assistance. Fictional examples are not customer results. No reach, sales, or search ranking is promised. The person responsible for the business should conduct a final review of accuracy and scope before publication.
Let's adapt this approach to your brand.
Let's define the scope of your needs together.
Explore the relevant service