UGC claims handoff prompts that keep facts and creative choices separate.

Prompt the owner to classify every statement before drafting

Ask for the product name, intended audience, channel, offer, substantiation sources, required wording, prohibited claims, and final approver. For every proposed statement, ask whether it is a verified fact, supported comparison, subjective opinion, creative premise, presenter experience, or unresolved claim. Request the source, date, scope, and expiration for factual material. Ask who the presenter is and whether customer status, likeness, voice, script, and territory are authorized. Require explicit disclosure language and placement. These prompts organize supplied evidence; they must not invent experience, rankings, urgency, savings, results, endorsements, or proof when an answer is missing.

• Statement classification
• Substantiation pointer
• Presenter provenance
• Disclosure requirement

Draft hooks and beats inside the approved claim boundary

Prompt for several opening angles using only the approved facts, then ask which audience problem each hook addresses and which visual could truthfully support it. Build a short beat list for setup, demonstration, qualification, disclosure, offer, and call to action. Mark any line that depends on first-person experience and remove it unless the identified presenter can truthfully make that statement. Ask for captions that preserve qualifications rather than shrinking them away. Keep product packaging, interface, price, and outcome visuals tied to provided assets. The drafting artifact remains text for human review, not evidence that a named service generated, approved, or can execute the ad.

Use adversarial review prompts before the next handoff

Ask a reviewer to identify the strongest implied claim, the source supporting it, who appears to speak, what a reasonable viewer could misunderstand, and whether the visual changes the meaning of the words. Challenge fake-customer provenance, unqualified comparisons, before-and-after implications, hidden sponsorship, missing synthetic-media labels, unclear prices, unsafe demonstrations, and unsupported performance language. Require a disposition for every issue: approve, revise, remove, or escalate. Then export only the approved version with sources and consent scope. This review sequence makes a manual boundary safer; it does not create a system integration, guarantee compliance, or report reach, conversion, or return on spend.