Operating ProcedureExecution layer

Model Swap and Re-Render Decision Record (QA)

A checklist with 7 steps: Freeze the approved prompt and reference assets before any model change.

By InnovaAI ResearchPublished

What are the steps?

checklist

Model Swap and Re-Render Decision Record (QA)

  1. 01

    Freeze the approved prompt and reference assets before any model change

    Store the exact prompt string, seed, aspect ratio, duration, and reference images in the client job folder so a re-render is reproducible rather than re-imagined.

  2. 02

    Render the same shot on at least two backends and label outputs by model

    A multi-model workspace such as Froging lets a team run one prompt across Kling, Veo, and MiniMax variants; a single-model studio like AIProductAds or MiniMax H3 Max requires a separate pass per environment. Tag every file with model name and render date.

  3. 03

    Score each render against three fixed criteria: prompt adherence, character consistency, audio sync

    MiniMax H3 outputs run 4 to 15 seconds with native stereo audio and lip-sync, so audio drift is a real failure mode on dialogue shots and must be checked frame by frame, not eyeballed once.

  4. 04

    Reject any render where lip-sync or brand marks break, regardless of visual quality

    A clip that looks strong but misaligns spoken audio or distorts a logo cannot go to a client, and the category has no reliable brand-safe lip-sync at scale yet.

  5. 05

    Log the winning model, settings, and rejection reasons in a shared decision record

    One row per shot: prompt version, model, resolution, duration, verdict, and the specific defect that killed the losing renders. This becomes the reference for the next campaign.

  6. 06

    Confirm commercial-use terms for the chosen backend before the asset leaves the building

    Rights language shifts between contract cycles; 105 of 175 AI tools changed monetization-relevant terms between June 23 and October 3, 2026, so re-read the terms on the specific model used for each client deliverable.

  7. 07

    Route the approved render to human finishing and note what the model could not do

    Hand the editor the decision record so the finishing pass targets the known gaps (narrative continuity, transitions, brand typography) instead of redoing work the render already solved.