PlaysbyMoat8
Back to the library
The workflow guideMarketing

Create new campaign scenes from approved talent references

Generate additional images and short video scenes from an approved set of performer reference photos. This can support later creative variants when a campaign needs scenes beyond the original shoot.

6 implementation stepsIntermediate

How this works

Generate additional images and short video scenes from an approved set of performer reference photos. This can support later creative variants when a campaign needs scenes beyond the original shoot. Extending a talent campaign requires both identity fidelity and fidelity to the agreed use. New scenes can imply endorsements, activities, or contexts the performer never approved, even when the face looks consistent.

Use the authorized reference set and campaign scope to generate a small number of additional scenes. Review identity, clothing, product interaction, and contextual implications before optional animation. Keep approved originals and a record of permitted usage with the production handoff.

Before you start

Talent authorization

Confirm permitted likeness use, channels, contexts, and duration.

Reference coverage

Use approved images that represent the intended appearance.

Campaign brief

Define new scenes and what must remain unchanged.

Prepare the inputs

talent_references
Required

Authorized images

Use the correct person and approved versions.

usage_scope
Required

Permission record

Check each proposed scene falls within the agreed context.

scene_requests
Required

Descriptions

Avoid unapproved claims or sensitive situations.

brand_product_assets
Required

Approved references

Preserve product details.

output_spec
Required

Still or video formats

Specify dimensions and duration.

Implementation, step by step

  1. Check scene scope

    • Compare requested scenes with the talent's authorized campaign use.
    • Identify any new implication or context that needs resolution before generation.

    Checkpoint: A permitted scene list.

  2. Prepare the identity anchor

    • Inspect reference images for facial features, appearance, and required wardrobe details.
    • Choose references appropriate to the new angle without inventing unseen identifying details.

    Checkpoint: A controlled reference set.

  3. Generate still candidates

    • Create the requested scenes with the approved person and product context.
    • Keep version labels and reject identity drift or misleading interactions.

    Checkpoint: A reviewed still shortlist.

  4. Animate selectively

    • Animate only approved stills when motion serves the campaign.
    • Inspect face, hands, clothing, and product continuity throughout the clip.

    Checkpoint: A selected motion candidate.

  5. Review the campaign meaning

    • Check that pose, setting, and copy do not imply an unapproved endorsement or activity.
    • Compare the complete asset with the authorization and original references.

    Checkpoint: A usage-compliant review record.

  6. Package the deliverables

    • Export the requested files and retain source-version and approval links privately.
    • State which assets are final candidates and which require further review.

    Checkpoint: A clear campaign asset package.

Decisions along the way

A scene exceeds the approved context

Hold it for scope resolution rather than generate speculatively.

Identity is inconsistent

Reject and regenerate from the approved anchor.

Animation introduces an unintended gesture

Replace the take or use the reviewed still.

What you will produce

extended-campaign-assets

Image and video files

Provides additional candidates within the campaign scope.

Include: scene_id · reference_version · format · review_status

talent-asset-review.csv

CSV

Documents the relevant acceptance checks.

Include: asset_id · identity_check · context_check · product_check · decision

Check the result

  • Compare identity against the approved reference set.
  • Inspect the whole animated take for drift.
  • Check product details and exact copy.
  • Confirm the scene remains within authorized use.

When something goes wrong

Generation repeatedly alters facial features

Use a simpler angle or stop and request a better reference.

Context implies an unapproved statement

Change the scene or remove the implication.

Export loses visual quality

Re-export from the reviewed source and inspect the actual file.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Create a new office scene for an approved campaign performer.

Inputs

Synthetic example. Synthetic permission covers business-software promotion in office settings; a proposed scene places the person in a medical endorsement.

Expected result

Synthetic expected result. Hold the medical scene as outside scope. Produce only the office concept and review identity and product interaction before delivery.

Run a small pilot

Start small

A few scenes within one clearly authorized campaign.

Record the baseline

Record identity rejections, revision effort, and context issues.

Agree success criteria

Agree likeness and usage fidelity before expanding the asset set.

Stop or revise

Stop when authorization or identity accuracy cannot be established.

Keep the scope clear

  • An approved image set does not authorize every possible new context.
  • Do not publish or reuse the likeness outside the documented campaign permission.

Check before using

Confirm the agreed rights cover synthetic reuse. Check identity consistency and avoid presenting generated scenes as records of real events.

Business activities

  • Create and publish content
  • Run advertising and acquisition tests

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Approved performer reference images · Required scene and campaign style

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗