Build an asset register before AI creative multiplies

AI does not only increase creative output.

It increases creative ambiguity.

One product image can produce dozens of backgrounds, crops, models, languages, and video variations. The team sees efficiency. Six weeks later, nobody knows which version is approved, which one changed the product shape, or where a synthetic person is still live.

An asset register gives every file an operating identity. It is the bridge between making creative quickly and governing it responsibly.

Give every asset a durable identity

File names are not an asset system.

Assign a unique ID that stays with the concept across exports and placements. Record the campaign, product, ASIN or SKU, creative type, language, aspect ratio, owner, and creation date. Link the source file and the exact published exports.

For AI-assisted work, record the production method and tool. Save prompts or workflow references when practical, along with the original product image used as grounding. If a real person’s likeness or licensed stock contributed to the output, connect the release or license.

The goal is not surveillance of designers. It is the ability to reconstruct how a buyer-facing claim came into existence.

Separate four approval questions

One green approval status hides too much.

Review product truth, rights, brand quality, and compliance separately. A beautiful image can misstate package count. A factually accurate image can use material outside the license. A rights-cleared asset can still need a disclosure. A compliant asset can still feel off-brand.

Give each review an owner, decision, date, and note. Use conditional approval when an asset is allowed only in certain markets, channels, or crops.

This structure prevents a media buyer from reading “approved” as permission to publish the file everywhere forever.

Track where the asset is live

An archive is not a register unless it connects to distribution.

Record each placement: detail page, Sponsored Brands creative, display ad, Brand Store, email, landing page, social post, or retailer portal. Include marketplace, audience, launch date, campaign ID, and expected end date.

Automate the connection where tools allow it, but keep an owner responsible for reconciliation. Agencies should return placement data in the same format as internal teams.

When an issue appears, the register should answer two questions in minutes: where is this file live, and who can take it down?

Add a content fingerprint when the same visual is exported many ways. A perceptual hash, source-image ID, or campaign family can connect a square social crop with a wide marketplace banner even when the file names differ. This becomes especially useful when an agency has flattened layers or a platform has recompressed the upload. The register should also distinguish a concept from a literal file. A disclosure problem may require retiring every derivative in the concept family, while a compression defect may affect only one export. That distinction keeps response work proportional and prevents an unsafe master from surviving through an overlooked crop.

Add expiration and replacement rules

Creative becomes wrong even when nobody edits it.

Packaging changes. Product colors shift. Promotions expire. Certifications lapse. A model release may have a term. A comparison claim may depend on an old competitor product. A disclosure standard may be revised.

Add review and expiration dates to assets with time-sensitive elements. Connect each old file to its approved replacement. When a hero image changes, trigger checks for duplicated versions in ads, Stores, and external landing pages.

Retirement should be a workflow with confirmation, not a note that says “stop using.”

Make the register part of production

Do not wait until launch week to document a folder.

Create the asset record when the brief is opened. Add source evidence during production. Collect approvals before export. Require a valid asset ID when the media team publishes the file.

Keep required fields short enough that people will use them. Automate thumbnails, dimensions, hashes, and timestamps. Reserve human effort for meaning: product truth, rights, permitted use, and the reason for approval.

Sample the register monthly. Untraceable live assets should be treated as defects, even if their performance is strong.

The Operator Read

Creative velocity without asset control creates hidden debt.

The debt appears when a product changes, a disclosure question arrives, or a buyer reports an impossible feature shown in an image. Teams then spend days searching drives and campaign managers for files that should have been identifiable from the start.

Give every asset an ID. Separate product, rights, brand, and compliance approvals. Connect the approved export to every live placement and retire it deliberately.

AI makes more creative possible. The register makes that output operable.