Key takeaways
- Approve product facts before generating a presenter or scene.
- Record implied visual claims as well as spoken claims.
- Use observable acceptance criteria rather than vague style words.
A useful AI UGC creative brief tells the production team what must remain true, not just what the video should feel like. Before choosing an avatar or generating a scene, document the product, audience question, approved claim, evidence, and next action. That record becomes the standard for judging every draft.
Without it, a plausible render can quietly change the product. A bottle gains a pump, a dashboard gains an unavailable feature, or a presenter describes an experience nobody had. These are not cosmetic mistakes. They change the information a prospective customer receives.
Build a compact product truth pack
Start with the exact product version being promoted. Include clear reference photographs or accurate screen recordings, current specifications, included items, available variants, limitations, and the destination page. Identify the source of each fact and when it was checked.
Separate facts from aspirations. “Supports three saved presets” is a feature if confirmed in the current product. “Makes every morning effortless” is a broad promise that may imply more than the evidence supports. A truth pack should make that difference obvious before a script is written.
For physical products, show the front, back, sides, labels, scale, and any feature that moves. For software, capture the real task in a prepared account and note the relevant plan or permissions. Do not let a generated reference become the source of truth for a later generated scene.
Connect the pack to your brand voice guide, but keep voice preferences separate from factual requirements. A friendly tone can change. The actual package contents cannot change simply because a shorter sentence sounds better.
Define one viewer and one decision
A brief becomes difficult to execute when it addresses everyone. Describe the situation rather than inventing an elaborate persona. For example: someone comparing desk lamps because their current lamp takes too much room. The video needs to help that person judge footprint and adjustment, not explain every possible lighting use.
Write the viewer's question as a real question. Then write the smallest useful answer the video can demonstrate. This creates a clear boundary for the script. Details that do not support the answer can move into a product page or a separate video.
Specify the next step honestly. If the destination is a comparison page, ask viewers to compare sizes. If it is a trial registration, disclose relevant terms where needed. “See the dimensions” and “Buy now” represent different levels of commitment and should not be interchangeable defaults.
A narrow video can still belong to a larger campaign plan. The campaign carries the wider story; the individual creative should earn its attention by resolving a specific uncertainty.
Map every claim to evidence
Create a short claim record for each statement or implied visual. Write the proposed claim, the supporting source, the exact scene that will communicate it, and the person who can approve it. Add any qualification that must remain visible or audible.
The visual matters as much as the narration. A generated scene of a lamp illuminating an entire room can imply output that the spoken script never explicitly claims. An interface showing instant completion can imply a speed or capability that the real product does not provide.
The FTC's endorsement guidance is useful when a presenter appears to recommend a product. Endorsements must reflect honest opinions or experiences, and an advertiser needs support for the claims conveyed. Treat this as a review of the overall message, not a search for a magic disclaimer.
For a synthetic presenter, explicitly prohibit invented first-person experience. The FTC's testimonial rule guidance addresses false testimonials and explains why a fabricated customer story is not simply a stylistic choice.
The working brief, field by field
Use the following fields as a starting point. They are production instructions rather than a form that must be filled with lengthy prose.
- Viewer situation: what the person is trying to decide and what they already know.
- Single promise: the one supported answer the video will provide.
- Evidence: reference assets, approved facts, and the owner of each fact.
- Scene sequence: what must be shown, including the product demonstration.
- Presenter role: narrator, demonstrator, or genuine customer, with clear boundaries.
- Language: approved terminology, pronunciation, tone, and prohibited claims.
- Delivery requirements: aspect ratio, intended placement, captions, destination, and required disclosures.
- Acceptance criteria: the checks that determine whether the asset is ready.
Keep a change log beside the brief. When a product fact changes, identify which scripts and scenes depend on it. Otherwise, a team can approve the new brief while continuing to export the old video from a shared folder.
An illustrative brief for an adjustable desk lamp
Imagine a brand selling a lamp with a clamp base and three brightness settings. Its prospective buyer wants more working space. The approved promise is that the clamp occupies a defined part of the desk edge, shown with real measurements. This example does not describe a tested product or customer outcome.
The opening shows a crowded desk and introduces the footprint question. The evidence scene uses real footage of the clamp on a compatible desk. The next scene demonstrates the actual adjustment range. The closing directs viewers to check the published compatibility measurements before buying.
The presenter may say, “Here is how the clamp fits this desk.” They may not say, “It fits every desk,” unless that expansive claim can be supported. A generated room scene can establish context, but it cannot substitute for the compatibility demonstration.
Acceptance requires the sold lamp configuration, readable measurement information, correct brightness terminology, no invented customer experience, and a destination page that contains the promised compatibility details. A reviewer can apply those conditions without guessing what “premium but authentic” was meant to achieve.
Plan accessibility before the edit
Include captions and meaningful visual explanation in the brief instead of adding them at export. If a feature is visible only for a moment, a viewer may miss it while reading. If all explanation is spoken, a person watching without sound may not understand the demonstration.
W3C's media accessibility guidance describes components such as captions, transcripts, and descriptions according to the content. Use it to identify what your particular video communicates through sound and through vision.
Specify where captions can appear without covering product evidence. Record important non-speech sounds that carry meaning. If an audible click confirms that a latch is locked, the caption or visual explanation should convey that information accurately.
This is also where localization requirements belong. A later translation may be longer than the original, so keep layouts and scene timing flexible. Avoid burning essential copy into footage that will be expensive to revise.
Review the brief with a deliberately rough draft
Before spending time on polished generation, review a script and rough scene sequence. Ask whether the evidence answers the viewer question, whether the product facts are clear, and whether the next step matches the destination. Fix those structural problems before reviewing skin detail or lighting.
Use the caption generator to explore supporting copy only after the claim is approved. Generated wording should be checked against the truth pack just like a human draft. A more engaging phrase is not useful if it broadens the promise.
Finish by assigning owners for factual review, creative review, and publication checks. Keep the approved brief with the final assets so another editor can understand the reasoning later. You can prepare adjacent visual explanations with Caroush's free tools, while maintaining a separate, explicit review process for the video itself.
Sources
Frequently asked questions
How long should an AI UGC brief be?
Long enough to remove important uncertainty. A concise brief plus a linked product truth pack is usually more useful than a lengthy document repeating style adjectives.
Should the brief include a complete script?
Include one if the wording is already approved. Otherwise specify the viewer question, claim boundaries, scene evidence, and required terms before asking for script options.
Can generated images serve as product references?
They can communicate a visual direction, but they should not establish product facts. Use verified photographs, recordings, specifications, and package information as the source of truth.
Who should approve the finished video?
Assign a product-fact owner and an editorial reviewer, with specialist review where the claim requires it. The publisher should also verify current placement and disclosure requirements.
About Garry
Gaurav Sapkota builds Caroush, a workspace for creating, scheduling, and publishing social content.
