Draft, Test, Approved: Organizing Assets in ZMS AI

A campaign can slow down even when the creative work looks finished.

Imagine a shared folder containing these files:

final.pngfinal_new.pngfinal_v4.pngfinal_use_this_one.png

One image is square. Another is vertical. One contains an old date, while another has the correct product packaging. Nobody remembers which file was reviewed or where it is meant to appear.

A workspace such as ZMS AI can keep image and video generations in one creation library. That helps gather related work, but a library alone cannot explain whether an asset is still an idea, part of a test or cleared for publishing.

A simple manual status system can help:

Draft → Test → Approved

These are not ZMS AI interface features. Add them to filenames, a project sheet or an internal review note. Not every asset needs to pass through all three labels. Use Test only when a controlled comparison is actually planned.

Draft Means “Still Open”

A Draft is an idea that can still change.

It may be useful for discussing composition, color, camera direction or product placement. It is not ready for a public channel or paid campaign.

A draft may still contain:

• temporary copy;
• an unverified product detail;
• an unfinished crop;
• the wrong aspect ratio;
• reference material that has not been reviewed.

Calling this file “final” creates confusion. Calling it “Draft” gives the team a clear instruction: discuss it, revise it, but do not publish it.

For example:

CoffeeLaunch_ProductTable_9x16_Draft_0917

Test Means “One Defined Question”

A Test asset should answer a specific question.

For example:

• Does the close product shot communicate faster than the wide shot?
• Is the text readable in the square version?
• Does a quieter background make the package easier to notice?

A comparison becomes difficult to interpret when the framing, background, copy and format all change together. Before using the Test label, record four things:

1. What changed?
2. What stayed fixed?
3. Where will the asset be used?
4. What result will be reviewed?

Two files:

CoffeeLaunch_CloseShot_9x16_TestA_0917CoffeeLaunch_WideShot_9x16_TestB_0917

The difference is visible without opening every file.

Test does not mean accurate, compliant or suitable for every placement. It only means the asset has a defined role in a comparison.

Approved Needs a Scope

“Approved” should always answer another question:

Approved for what?

A vertical asset may be approved for paid social but not for a website banner. A product image may have correct packaging while its copy still needs review. Approval should apply to one exact file and one recorded use.

A short approval note can include:

• intended placement;
• required format;
• approved copy;
• reviewer;
• approval date.

A filename:

CoffeeLaunch_ProductPour_9x16_ApprovedPaidSocial_0917

Do not replace the reviewed file while keeping the same name. If the visual, text or crop changes, create a new version and review it again.

Use a Filename and One Small Project Record

A filename does not need to hold the whole creative brief. It only needs enough information to prevent the wrong asset from being used.

A practical structure:

Campaign_Asset_Format_Status_Date

If the model matters:

Campaign_Asset_Format_Model_Status_Date

Including the model records where an output came from. It does not mean different models use identical controls or produce directly comparable results. Available settings depend on the selected workflow.

Keep the remaining details in a small spreadsheet or project note:

AssetStatusIntended useMain changeReviewerProduct tableDraftInternal reviewFirst composition—Close shotTestVertical socialTighter framing—Product pourApprovedPaid socialFinal copy checkedReviewer

For a small project, one row per serious candidate may be enough. The record should point to the exact exported file, especially when several versions look almost identical.

Approval Is More Than Appearance

An asset should not move to Approved only because it looks polished.

Check four areas:

• copy, dates, prices and product facts;
• logos, packaging and readable text;
• permission for reference material and recognizable people;
• current rules of the intended channel.

Generated imagery should not be used be used as proof of product performance, safety or effectiveness. Any factual claim needs support outside the generated visual.

Results and controls can vary across models and settings. Approval applies to the file that was reviewed, not to every future result created from a similar prompt.

A Creation Library Is Not a Permanent Archive

According to the current ZMS AI website, generated works may remain in My Creations for up to six months. That makes the library useful for active projects, but it should not be treated as a permanent archive.

After approval:

1. Download the exact reviewed asset.
2. Save it in the campaign folder.
3. Preserve the approved filename.
4. Keep the review note beside it.
5. Store the brief and authorized references when required.

This makes it easier to revisit a campaign without guessing which online preview became the published version.

“Final” Is Not a Status

The word “final” says very little. A file can be final for a designer but still be waiting for copy review. It can be ready for one placement and wrong for another.

• Draft: discuss or revise.
• Test: use for one defined comparison.
• Approved: publish only within the recorded scope.

The goal is not to add more administration. It is to stop the wrong file from becoming the campaign.