How to Read a UGC Brief and Handle Revisions Professionally

Most revision problems start before filming, when the creator and the brand understood the brief differently. This guide gives you a worksheet to catch those gaps, the questions to ask, a sensible revision policy, and scripts for the requests that go beyond it. If you're a brand writing a brief, use our UGC brief template instead.

What a UGC brief should tell you

Briefs range from a detailed document to two lines in a chat. Whatever the format, you need answers to these before you film. Anything missing becomes a question for the brand.

The brief-breakdown worksheet

Copy this into your notes for every project and fill it in from the brief. Writing it in your own words is how you find what's unclear. Anything you can't fill in goes on your question list.

PROJECT: [BRAND] / [PRODUCT]                      DATE RECEIVED: [DATE]

1. GOAL (one sentence, my words):
   This video needs to [get viewers to ... / show that ... ] for [PLACEMENT].

2. AUDIENCE: [WHO] who [PROBLEM / SITUATION]

3. KEY MESSAGE (one line): [ ]

4. MUST SAY:        [ ]
   MUST SHOW:       [ ]
   MUST NOT SAY:    [ ]
   APPROVED CLAIMS: [ ]   (Anything about results, health, or comparisons?
                           Ask if not listed.)

5. FORMAT: [testimonial / demo / unboxing / problem-solution / other]
   SCRIPT: [full script / talking points / my choice]

6. DELIVERABLES:
   Videos: [#]   Length: [ ]s   Ratio: [9:16 / 4:5 / 1:1]
   Hooks per video: [#]   Captions: [yes/no]   Raw footage: [yes/no]
   Music: [none / brand-supplied / my choice]   File format: [ ]

7. SETTING / LOOK: [location, wardrobe, props, product placement]

8. TIMELINE:
   Product arrives: [ ]   Draft due: [ ]   Brand feedback by: [ ]   Final due: [ ]

9. USAGE: [organic / paid ads / my handle] for [TERM], [TERRITORY]

10. REVISIONS INCLUDED: [#] round(s)   Feedback from: [NAME / ROLE]

11. MY QUESTIONS:
   - [ ]
   - [ ]

12. RISKS I SEE: [unclear claims / tight timeline / product not used yet / ...]

Questions to ask before you film

Send all your questions in one message, numbered, so the brand can answer quickly. Only ask what the brief doesn't already answer. Pick from this list:

• Where will this run first: paid ads, organic, or the product page?
• Is there a past video or ad from your brand that you'd like this to feel like? And one you didn't like?
• Are there exact phrases or claims I must use, or must avoid?
• Can I adapt the script into my own words, or should I read it as written?
• How should the product appear: packaging visible, in use, a close-up of the label?
• Do you want captions burned in, or a clean version too?
• Who will give feedback, and is there anyone else who needs to approve?
• When can you send feedback after I deliver the draft?
• Will any ads run from my account (Spark Ads or partnership ads)?
• Is there anything you've learned from past creator videos that I should know?

Confirm the scope in writing before you start

Once the questions are answered, send a short recap and ask for a yes. Keep it in the same place you'll deliver the work, such as the platform chat or the email thread, so there's one record. This message is what you'll point back to if the scope changes later.

Thanks, [NAME]! Here's what I'll deliver, so we're on the same page:

- [#] video(s), [LENGTH]s, [RATIO], [#] hook(s) each, captions [on/off]
- Angle: [ONE-LINE CONCEPT]
- Key lines: [MUST-SAY ITEMS]
- Draft by [DATE], assuming the product arrives by [DATE]
- [#] revision round(s) included, on feedback within the brief
- Usage: [WHAT WAS AGREED]
- Price: $[TOTAL]

Reply "confirmed" and I'll start. If anything's off, tell me now and I'll adjust.

How many revisions to include

There's no industry standard. A common approach is one round in the base price, with a second round in a larger package or as a paid add-on. What matters more than the number is defining what counts:

Write your policy on your rate card and in your scope recap: "Includes one revision round, meaning one consolidated set of changes within the agreed brief, requested within [X] days of delivery." The window matters, so a project can actually close. Put a price on extra rounds, too; the rate guide shows how to set one.

Platforms can have their own revision rules. On CreatorsUGC (our platform), for example, brands can request revisions before approving a delivery, so read the platform's process alongside your own policy.

How to handle feedback professionally

1. Ask for one consolidated list. Notes trickling in one at a time turn one round into five.
2. Read all of it before replying. Sort each note into "fix," "in scope," or "out of scope" using the table above.
3. Confirm back. Repeat the changes in a short list and say when you'll deliver.
4. Raise out-of-scope items once, politely, with a price. Don't silently do extra work and resent it, and don't refuse without offering an option.
5. Deliver with a short note listing what changed, so the reviewer doesn't have to search for it.

Thanks for the notes! Here's what I'll change:
1. [CHANGE]
2. [CHANGE]
3. [CHANGE]
I'll send the updated version by [DATE]. This is the included revision round, so if
there's anything else you'd like changed, let me know now and I'll fold it in.

Scripts for out-of-scope requests

The goal is to keep the relationship warm and the scope clear. Acknowledge the request, explain in one line why it's different, give a price or option, and make it easy to say yes.

Totally get it. A [NEW ANGLE] could work well. That's a new concept rather than a
revision of this one, since it needs a new script and a reshoot. I can do it for
$[PRICE] and deliver by [DATE]. Want me to go ahead? The current video is still yours
to use as agreed.

Happy to add those. Extra hooks are $[PRICE] each and a [15s cutdown / 4:5 version]
is $[PRICE], so [TOTAL] for everything you listed. I can deliver them with the revision
on [DATE] if that works.

Thanks for these. We've used the included revision round, so this would be an extra
round at $[PRICE]. If you can send any remaining notes together, I'll handle them all
in that one round and deliver by [DATE].

Thanks for flagging that. Changing [LINE / CAPTION] is quick and I'll do it at no charge.
Removing [CLAIM] from the spoken part means re-recording that section, which is $[PRICE].
Alternatively, I can cover it with on-screen text at no charge. Which do you prefer?

I want this to work for you, but I'm not comfortable saying [CLAIM] because I
[haven't seen that result / can't verify it]. I can say [HONEST ALTERNATIVE] instead,
which keeps the same message. Would that work?

Before you deliver: final check

• Every must-say line is in, and nothing on the must-not-say list.
• Product name, pronunciation, and packaging are correct.
• The hook lands in the first 2 to 3 seconds.
• Captions are spell-checked and inside the platform safe zones.
• Length, aspect ratio, and file format match the scope recap.
• Audio is clear, without background noise or copyrighted music the brand didn't approve.
• Files are named clearly, for example [BRAND]_[ANGLE]_[HOOK1]_9x16.mp4.
• Your delivery note lists what's included and how many revision rounds remain.

Projects that end smoothly are the ones that turn into more work. After approval, see how to turn one project into repeat clients, and if you need structures for the script itself, UGC script templates.

FAQ

Sources

1. Disclosures 101 for Social Media Influencers — Federal Trade Commission

CreatorsUGC publishes this guide. We run a UGC marketplace, so we have an interest in the topic — we link to independent sources for facts and label illustrative examples.