How to preserve an approved AI model reference across campaign handoffs

Start with the handoff failure you want to prevent

Imagine a brand using an adult virtual model called Maya in its spring campaign. Later, someone saves a new reference with shorter hair under the same local filename. The next designer cannot tell whether the face was intentionally changed, only the styling was revised, or the wrong image was selected. This illustrative problem is about preserving decisions after approval, rather than choosing the cast initially.

Keep the approved reference file unchanged in the merchant's own organized records. Give it a stable identifier and a descriptive revision name. The human-readable name remains useful, but it should not be the only link between an identity and its source. Do not claim that a familiar name guarantees identical generation across future scenes.

Store the minimum context needed to reuse it responsibly

The record should identify whether the reference came from Official models or Your models, which image was approved, what campaign it served and who reviewed it. For a personal reference involving a real adult, retain the relevant permission record in a suitable private location; do not place sensitive documents in a public creative guide or asset caption.

Botika's custom-model guide emphasizes recurring identity and agreement about the intended use of a cast. Itemlume's model library should not be confused with that competitor's exclusive-model service. Saving a reference in Your models does not itself establish exclusivity or ownership of a generated face. The version record described here is an external merchant workflow, not a built-in licensing system.

Distinguish a styling revision from a replacement identity

Avoid treating every different expression as a new identity version. Equally, do not label a noticeably different face as a harmless styling update because the filename is familiar. The record should describe the decision people actually made.

Link outputs without promising automatic synchronization

When using Models and the model picker in other workbenches, confirm the selected reference visually before generating. Keep the resulting asset identifier or downloaded filename beside the reference version in your own records. Existing generated files do not become corrected merely because you later choose a different reference.

My assets and Generation tasks help locate completed work and task progress, but this guide does not assume automatic reference version history, propagation or rollback. A spreadsheet or project document can hold the additional handoff information. Keep it simple enough that the next person can find the approved image without reconstructing the entire conversation.

Hand over one approved starting point and clear exceptions

A practical handoff contains the approved reference thumbnail, stable filename, campaign role, allowed styling direction and links to representative accepted outputs. Include a short exception note when a particular angle or accessory repeatedly obscures the product. This supplements the contact-sheet review; it does not replace checking new results for identity drift and product errors.

Archive superseded versions rather than silently overwriting them, following your own retention and permissions requirements. Before a new campaign, confirm that the reference and intended use remain appropriate. That small check lets the cast evolve deliberately while keeping earlier published images traceable to the version that actually produced them.