What should you do when a real-person model reference is withdrawn?

Record the request and assign a responsible owner

Imagine an illustrative accessories campaign using an authorized photograph of a real adult model. The person later asks the brand to stop using that reference. A designer sees the request, but scheduled posts and another contractor's image exports still depend on it. The first task is to connect the request to actual work, not generate a replacement face immediately.

Record when the request arrived, the identity of the reference and the stated scope in a suitable private location. Assign the rights or privacy owner to assess the agreement and applicable obligations. This guide is an operational checklist, not a legal determination that every permission has the same withdrawal or retention consequences.

Hold new uses while the scope is reviewed

Stop launching new generations with the affected reference and flag related scheduled creative for review. Check whether any task is already pending; record its state rather than assuming a cancellation control exists. If assistance is needed, use the appropriate support route and provide only the evidence necessary to resolve the operation.

Do not replace the source file under the same identifier or quietly rename it. That would break the connection between the request and dependent outputs. ICO explains withdrawal where consent is the lawful basis under UK GDPR. Ask the responsible reviewer how that applies; it is not a universal rule for every model contract.

Build a reference-change response table

List external copies as well as Itemlume results: editor projects, shared folders, retailer media and advertising accounts. An output may have been cropped or renamed, so use the campaign lineage and thumbnails to locate it. Mark unknown destinations for investigation instead of reporting the response complete.

Act on decisions without claiming automatic removal

Review the affected records in Models, My assets and Generation tasks as appropriate. This workflow does not assume automatic authorization revocation, derived-asset deletion or remote takedown in Itemlume. Authorized people must make changes in the actual systems that hold the files or publications and verify the resulting state.

Keep necessary request and action evidence privately according to the responsible owner's instructions. Do not publish the person's documents in a defect report or public example. When a platform copy cannot be changed directly, use its proper support process and record the unresolved status; a local deletion should not be described as global erasure.

Approve a replacement and close the usage record

Choose a separately authorized adult reference or a suitable fictional character, then review new outputs independently. Do not blend the withdrawn reference into the replacement to preserve a familiar appearance. Revisit captions and campaign roles so the change does not continue the same unauthorized identity claim through different wording.

The accessories team should close the checklist only after responsible owners confirm each required action or explicitly record an outstanding destination. Save who decided the scope, what changed and what remains unresolved. This illustrative process supports accountable follow-through; it does not promise complete deletion from third-party archives or establish legal compliance by itself.