The team has collected dozens of images, but a new campaign turns up only small copies from message threads. Nobody knows which version is approved, which product the scene belongs to or whether the source photograph can be used again.
A library should help people choose current material and trace its origins. That requires source files, clear statuses, usage information and update rules.
Choose attributes employees actually use to find images: brand, product, service, campaign, scene, language and format. Do not make the generation model the sole organising principle.
Assign a permanent asset identifier. Filenames should distinguish versions, while approval details and restrictions should also be stored in an asset record.
A small team can use shared storage and a register with an owner. A specialised system is justified when its capabilities suit the volume, search requirements and approval workflow.
Prepare a clear structure:
Do not mix drafts with publication material simply because both look finished. Status must indicate whether a file can be published and for which tasks.
Save the generation description, service, model and available settings where needed for continuation. They help recreate the working approach, but do not guarantee an exact repeat generation.
Every crop, language version and advertising format needs a link to its source. Related files can then be found when the product or logo changes.
Do not overwrite approved versions without a history. Save a new revision with the change description and acceptance date. Record separately whether only the crop changed or the image content changed too.
Before seasonal reuse, check that the product and terms are current. The article on campaigns using existing product photographs explains preparation.
Keep information about photograph and reference sources, agreed uses and required permissions. Note customer, campaign, channel or time restrictions where applicable.
Distinguish concepts, images of actual products and verified case study material. A concept image cannot be moved into a portfolio as a photograph of completed work merely because it was approved for another task.
Link the visual to the product, packaging or character version. If an essential detail changes, flag where a new review is needed. For style, keep an approved series reference, beyond “use the same approach as before”.
Define who adds material, checks accuracy, approves publication and archives files. An employee needing a finished banner should easily find the permitted export.
An archive preserves history but must not resemble a set of current options. When a file is withdrawn or replaced, find its uses on the website, in advertising and presentations. Moving it to another folder does not itself update published copies.
Set up backups within the storage system's capabilities and check recovery of a required source file. Version history is useful, but should not be treated as a verified recovery method without checking.
Illustrative example. A product label changes. The asset record flags the old version, related banners and the product page are located, and replacements are assigned. Old files remain as campaign history but are excluded from selection for new publication.
Check the system on a real task: can another employee find the right version, understand its restrictions and hand it to a contractor without tracking down the creator? The article on maintaining consistent brand identity complements the team rules.
When ordering a new AI visual content series, agree both images and handover contents: sources, working files, exports and approved-version information. Storage organisation and library maintenance require a separately agreed scope.