A creator opens your brief and has to make several decisions fast: who is watching, what the video should say, what should be on screen, how long it should be, and what happens at the end. When any of those is missing, the creator fills the gap with a guess. The result is technically a video and practically unusable.
The fix is a one-page brief with eight fields. It is short enough to fill in ten minutes and specific enough that two different creators would produce recognisably similar work.
Copy the UGC creator brief template
1. Audience
Who this is for, and what they already know:
2. One message
The single idea the viewer should understand:
3. Required proof
What must be visible on screen to support the message:
4. Format and length
Vertical video / text-led video / carousel; target seconds:
5. Opening line
The first sentence or on-screen text:
6. Next step
What the viewer should do (visit, sign up, watch the demo):
7. Review rules
Who approves, what must be checked, what must not be claimed:
8. Usage
Where the asset may be posted, and for how long:Keep the wording plain. If a field needs a paragraph of explanation, the message is not clear yet. Rewrite the message first, then fill the rest. The marketing for startups guide covers choosing the message before choosing the channel.
Why each field earns its place
1. Audience changes the opening
A founder who already knows the product needs a different first sentence than someone who has never heard of it. Write down what the viewer already knows. It prevents the classic mistake of explaining the category to an audience that only wanted the answer. For hook options, see the free hook lines library.
2. One message, not three
A short video that tries to explain the product, the pricing and the founder story at once usually communicates none of them. Pick the one idea the viewer should repeat to a colleague. Everything else belongs in a different asset. The UGC ad script template breakdown shows how one message shapes a full script.
3. Required proof is the honesty field
This is where most briefs fail. “Show the dashboard” is a suggestion; “hold on the next-step section long enough to read it” is a requirement. Decide what the viewer must actually see. Then do not let the edit remove it. If the proof does not exist yet, the video is not ready to claim the outcome. Related: turning a product demo into a short video.
4. Format and length are a decision, not a default
Vertical video suits movement and a spoken hook. A text-led video suits a point that needs reading time. A carousel suits a sequence of steps. Name the format and the target length so the creator does not guess. The carousel workflow is the right test when the message needs more than one screen.
5. The opening line is the test
Write the first sentence exactly. If it sounds like an ad, rewrite it. A useful test: would a real person say this to a colleague? The UGC hooks guide groups openings by intent so you can pick one that matches the message.
6. Name the next step
“Learn more” is not a next step. Decide what the viewer should do and make sure the video can actually support it. If the next step is a demo, the video should show the feature the demo covers.
7. Review rules prevent claims drift
Name the reviewer and list anything that must not appear: invented metrics, fake customer quotes, a feature that does not exist, a competitor claim you cannot source. Review is not a formality; it is where the brand keeps control. The social creative review guide provides a reusable checklist.
8. Usage is part of the brief
Say where the asset may be posted and for how long. A clip made for an owned organic channel is not automatically cleared for paid media, and creator usage terms differ. Put the answer in writing before work starts.
A filled example, so the template is not theoretical
Here is one brief for a fictional project-notes app. Every detail is an editorial illustration, not a claim about a real product:
1. Audience
Freelance designers who already take client calls and forget the next step.
2. One message
After a call, the decisions and next steps can live in one place.
3. Required proof
Hold on a note that shows both "Decisions" and "Next step" on screen, readable on a phone.
4. Format and length
Vertical video, 15-20 seconds, spoken hook plus a real screen recording.
5. Opening line
"You took the call. Where did the next step go?"
6. Next step
Watch the 20-second demo on the trial page.
7. Review rules
No invented reminder feature; no claim that notes are shared automatically.
Reviewer: founder. Must check the demo shows the exact screen named in the script.
8. Usage
Organic Reels and TikTok for 30 days; paid usage needs a separate approval.The difference between a vague and a usable brief
| Field | Too vague | Usable |
|---|---|---|
| Audience | "Designers" | "Freelance designers who take client calls" |
| Proof | "Show the app" | "Hold on the Next step section for two seconds" |
| Opening | "Make it catchy" | "You took the call. Where did the next step go?" |
| Review | "Check it looks good" | "Founder checks the named screen and every claim" |
The pattern is simple: replace adjectives with observable conditions. "Catchy" cannot be approved or rejected consistently. "Hold on the Next step section for two seconds" can.
Mapping the brief to a human creator or an AI workflow
| Brief field | Human creator | AI workflow |
|---|---|---|
| Audience and message | Actor direction and script notes | Prompt context and scene direction |
| Required proof | Shot list and props | Reference media and a real recording to cut in |
| Format and length | Camera and runtime | Aspect ratio, duration and model settings |
| Review | Approval before usage | Inspect the generated result before download |
Using this brief with an AI video workflow
In Vidmake, the brief maps to the inputs the workflow already asks for: message, format, reference material and review. Write the brief first, then generate. A focused prompt produces a controllable result; a vague prompt produces a clip you cannot direct. Start with the AI UGC video generator workflow, or run it from an AI assistant through theMCP server.
A quick quality check before you approve
- Can a new viewer tell who this is for within three seconds?
- Is there exactly one message, stated in plain words?
- Is the required proof visible and readable on a phone?
- Does the opening line sound like a person, not a slogan?
- Is the next step real and reachable?
- Would the reviewer approve every claim without adding context?
FAQ
What should a UGC creator brief include?
At minimum: the audience, the single message, the proof the viewer must see, the format and length, the opening line, the intended next step, the review rules, and how the asset may be used. If any field is missing, the creator has to guess.
How long should a UGC video brief be?
Short enough to read in two minutes. One page with concrete fields beats a long brand document. Put the exact message and the required proof at the top, then add examples and anything that must not appear.
Do I need a brief for AI-generated UGC?
Yes. A prompt is a brief. The same fields still apply: audience, message, setting, action, duration, format and what must be visible. A focused brief is the difference between a controllable output and a random clip.
Who should approve the finished video?
Someone who knows the product and the audience well enough to confirm every claim. Keep an approval step before publishing or downloading, and name the reviewer in the brief so the decision is not ambiguous.
Can one brief cover several videos?
Use one brief per message, not per format. If you plan to test several openings for the same message, write the core brief once and change only the hook line and the expected action for each variation.