How to work through it

01

Anchor the ad in a supportable campaign claim

Name the audience, placement, decision, approved proposition, substantiation, and prohibited implication before writing a script. Creative urgency never replaces legal, brand, or factual review. For a controlled test, preserve the continuity note, and ask the identity reviewer to record destination fit before the production checkpoint.

02

Compare against a stable acceptance frame

Use the same inputs, review dimensions, and stopping rules for every candidate. Record tradeoffs separately from availability so a promising test is not mistaken for verified product support. For a controlled test, preserve the input snapshot, and ask the identity reviewer to record human approval before the editorial approval.

03

Evaluate the ad-production request without assuming a generator

Treat creator, maker, builder, and generator language as a production job rather than evidence that a local tool exists. Define authorized inputs, the supportable product claim, required scenes, brand constraints, captions, review stages, and handoff format. Compare revisions on controllability and factual fidelity instead of unsupported speed or quality promises. Record the acceptance decision, evidence gap, reviewer, and next verification trigger in the handoff. At handoff, preserve the claim inventory, and ask the brand reviewer to record claim scope before the final sign-off.

04

Build a sequence around proof and viewer context

Open with the audience problem, demonstrate only supported attributes, keep offer conditions legible, and end with an accurate next step. Plan aspect-ratio variants without assuming automated placement or publishing. Before approval, preserve the decision history, and ask the model evaluator to record claim scope before the rights check.

05

Review disclosure, claims, and destination consistency

Confirm that visuals, narration, captions, landing-page facts, synthetic-media disclosure, offer terms, and calls to action agree. Do not infer conversion, approval, reach, or return on spend. During review, preserve the decision history, and ask the continuity editor to record input provenance before the evidence refresh.

06

Keep the evidence ledger attached to the decision

No affirmative product, model, customer, or performance claim is established by the supplied evidence. Record the source, verification date, claim scope, unresolved gap, and the decision that the evidence can support. Search demand must never be reused as capability proof. During review, preserve the test fixture, and ask the delivery owner to record visible continuity before the evidence refresh.