How to brief UGC creators so the footage is actually usable
Bad briefs create beautiful chaos—great lighting, zero usable lines. A brief template with shot specs, legal rails, and the 'deliverables box' editors need before anyone says 'we can fix it in post.'
On this pagetap to expand
A brief that says "just be authentic" is not a brief—it is a horoscope.
Creators are not mind readers; they are talented contractors who will give you exactly what you asked for—which is often nothing, because you wrote vibes.
Last reviewed: April 2026. Paid partnerships must follow disclosure norms—FTC guidance on endorsements and influencers plus each platform’s branded content tools.
The one-page brief skeleton (non-negotiable fields)
- Brand + SKU (exact product variant)
- Audience tension (plain language)
- Approved claims list (bullets, nothing else is speakable)
- Forbidden phrases (competitors, medical outcomes, income claims)
- Proof plan (demo, unboxing, screen record)
- Deliverables (see section below)
- Technical specs (resolution, fps, orientation)
- Wardrobe / location bans (logos, messy backgrounds, noisy cafes)
- Disclosure line (exact wording + on-screen placement)
- Deadline + upload method (Drive link naming convention)
If your brief fits on a sticky note, your edit bay will fit in a therapy waiting room.
Deliverables box (copy verbatim into contracts)
Minimum package:
- A-roll: three full reads of the script (tight, medium, loose energy)
- Hooks: three alt opens (first two seconds only)
- Product inserts: label readable for two continuous seconds each take
- B-roll: five inserts (pour, squeeze, click, open, close)
- Room tone: twenty seconds silent in the same space
- Slate: creator says SKU + date at start of each file (sounds nerdy, saves lives)
Shot specs editors quietly pray for
| Spec | Why it matters |
|---|---|
| 4K or highest native | reframing vertical from horizontal |
| 24 or 30 fps consistent | avoids janky conform |
| Eye-line near lens | connection without creepy stare |
| Hands visible in demos | otherwise "magic product" vibes |
Example brief excerpt (fictional skincare)
Approved: "helps skin feel more comfortable during retinoid nights" (if legal approved)
Forbidden: "fixes eczema," "clinical cure," competitor names
Proof: show texture on back of hand + night routine clip
CTA: "Shop trial kit—terms on site"
Audio: the villain of usable UGC
Brief must include:
- lav mic requirement or acceptable phone setup
- no music under dialogue unless licensed
- clap sync if multiple devices (rare, but happens)
If audio is trash, your "UGC" becomes a subtitle museum.
The "two takes" rule for critical lines
For hook and CTA lines, request:
- Take A: exact scripted line
- Take B: same meaning, natural synonyms inside claims rails
Editors marry the best halves.
Internal links
Appendix: revision policy language (plain English)
Included revisions: focus, exposure, framing, audio noise reduction feasibility, one retake for flubbed approved lines.
Not included: new claims, new SKU, new storyline, "actually can we try a totally different concept."
Publish this early—surprise revisions are how friendships end and invoices begin.
Lighting and location: stop apologizing in color grade
Add two lines creators actually understand:
- Key light + fill minimum (window-only is fine if consistent)
- Background must be intentional: clean corner, real kitchen, or branded shelf—never "random hotel hallway" unless that is the brand
Bad lighting is not "authentic." It is unusable—editors will lift shadows until your product looks like a crime scene chalk outline.
Props list (tiny, high ROI)
If your product needs a spoon, towel, phone, or glass of water—ship props or reimburse with a line item. Otherwise creators improvise with a KFC napkin and you will spend three emails debating whether it is "on brand."
Example "bad brief" vs "good brief" (same product)
Bad: "Make it feel Gen Z."
Good: "Audience: first-job renters who hate meal prep Sundays. Proof: 60s cook. CTA: trial box. Forbidden: 'cheap' language. Deliverables: A-roll + 3 hooks + B-roll list attached."
E-E-A-T: briefs are operational documents
The best teams version briefs like code: v1.0 shipped, v1.1 legal tweak, v1.2 offer update. If your brief is always FINAL_FINAL, your Drive is lying to you.
Key takeaways
- Structure beats vibe—deliverables and rails in writing.
- Audio and inserts are not optional extras.
- Claims lists protect creators and the brand.
Post-mortem: what editors delete first (so brief against it)
Editors quietly delete:
- forty seconds of throat-clearing
- shaky macro where label never focuses
- "funny" tangents that fight the CTA
- music beds that mask bad audio decisions
If your brief prevents those four, you have bought hours back.
People also ask
What should a UGC creator brief include?
Truth rails, deliverables, tech specs, disclosures, deadlines.
How do I brief UGC for Meta vs TikTok?
Same spine, different pacing and text safe zones.
What deliverables should I request?
Alt hooks, multiple reads, B-roll, room tone, slates.
FAQ
How do I stop robotic reads?
Script hooks + bullet beats + one allowed improv lane.
How does Pinnacle AdForge help?
Connected briefs—signup.
If the brief is fuzzy, the footage will be art—just not the kind that fits in a nine-sixteen conversion story.
Last line, seriously: put the SKU photo and label close-up in the brief attachments—creators should not be guessing which variant is "the good one."
If you want one more blunt rule: never send a brief as a voice note unless you also send the same requirements in text. Voice notes are for friendship—briefs are for accountability.