Operating ProcedureExecution layer

Client Visual Handoff and Asset Rights Transfer (Handoff)

A handoff with 7 steps: Freeze the approved asset set at a named version before anything moves.

By InnovaAI ResearchPublished

What are the steps?

handoff

Client Visual Handoff and Asset Rights Transfer (Handoff)

  1. 01

    Freeze the approved asset set at a named version before anything moves

    Tag the final folder with a date and revision number, then archive every rejected variant in a separate directory so the client cannot accidentally pull an unapproved frame into a live campaign.

  2. 02

    Export each deliverable in the formats the client's channels actually accept

    Social placements typically need 1200x630 PNG for link previews, which is the exact output Mosaicora produces for Open Graph images, while print and signage work needs vector or high-DPI raster files.

  3. 03

    Document the generation method behind every asset in a one-page provenance sheet

    Note which model or platform produced the image, whether it was upscaled or inpainted, and whether any stock element was composited in, because clients increasingly ask this during their own legal review.

  4. 04

    Confirm commercial usage rights in writing for each tool used in the build

    Platforms differ on indemnification and training-data provenance, so a retainer that mixes outputs from several generators needs a per-asset rights note rather than one blanket statement.

  5. 05

    Transfer editable source files, not just flattened exports

    Hand over the layered or vector originals plus any custom style reference images, so the client's in-house team can extend the system without regenerating from scratch.

  6. 06

    Run a live walkthrough with the client's designated asset owner

    Thirty minutes covering folder structure, naming conventions, and the two or three prompts or style presets that reproduce the look, recorded for anyone who joins later.

  7. 07

    Log the handoff in the account record with a named recipient and date

    This closes the delivery loop and gives the agency a defensible record if a client later disputes which version was approved for publication.