Clarify a UGC client brief before filming
Ask focused questions about deliverables, claims, demonstrations, and approval so a vague UGC brief becomes a recording plan you can act on.
EasyLines team8 min read
AI-generated editorial illustration.
On this page 8 sections
- 1. Start with the job of this particular video
- 2. Make the deliverable count unambiguous
- 3. Ask which claims and words are approved
- 4. Resolve what the camera must actually show
- 5. Translate style references into usable choices
- 6. Send one concise approval summary
- 7. Use a ready-or-blocked check before the session
- 8. Frequently asked questions
Before filming a UGC client video, clarify what must be delivered, what the viewer should understand, what you can honestly say, and who can approve the exact script and demonstration. Turn vague preferences into decisions someone can confirm. A shot list becomes useful once those decisions are clear; it cannot resolve a brief that asks for incompatible outcomes.
Start with the job of this particular video
Ask who the video is speaking to and what that person should understand or do after watching. “Make it engaging” does not identify a task. “Show a first-time buyer how the lid opens” does. You can then judge proposed lines against that task. A sentence about packaging may be pleasant, but it may not belong in a short explanation of the lid.
Ask where the asset will be used and what surrounds it. A video made for a product page may need to stand alone differently from a clip introduced by other campaign material. You are gathering creative context, not deciding platform rules from memory. Ask the client to identify the intended placement and provide the current delivery requirements that apply to this assignment.
Request one main message and an order of priority for secondary points. If the client lists five benefits as equally essential, explain that you need a decision about which one leads the piece. That conversation can happen before anyone writes a hook. TikTok’s Creative Codes guidance recommends a clear brief while allowing creators to work in their style; clarity and natural delivery can coexist.
Make the deliverable count unambiguous
Ask how many distinct finished videos, alternate openings, and raw recordings are expected. “Three hooks” might mean three complete videos with different beginnings, or three opening clips to combine with one body. Those are different filming plans. Write the count in plain language and ask the client to confirm which interpretation matches the assignment.
Clarify orientation, intended duration, language, required pronunciation, and delivery format. Ask whether the client wants a clean recording for their editor or a finished asset prepared elsewhere. EasyLines focuses on prompting and recording; plan any editing or captioning in your separate finishing workflow. Do not let an assumed app feature become part of your delivery promise.
Confirm who supplies logos, product spellings, and any required on-screen text. If a name has an unfamiliar pronunciation, request an audio example or a clear spoken reference. Resolve practical details about delivery location and the review date as well. This checklist handles production decisions; it does not substitute for separately agreed commercial terms or interpret the legal scope of an engagement.
Ask which claims and words are approved
Separate required facts from suggested creative language. Ask the client to mark any sentence that must be delivered exactly and any phrase you can paraphrase. Request the source for a product specification that matters to the demonstration. A creator should not strengthen a cautious statement just because a more dramatic sentence sounds like a better opening.
Check the personal-experience language. If you have only received the product today, a script saying you have relied on it for months does not describe your experience. Explain that mismatch and propose wording about what you can presently observe or demonstrate. If the assignment depends on experience you do not have, hold that part of the script for clarification rather than inventing a story.
Ask who approves claims that you cannot verify from the product itself. The practical outcome should be a named contact and a confirmed version of the wording, not a general reassurance that everything is fine. If important support is missing, mark the line unresolved. You can keep planning neutral footage while waiting, but do not build the central performance around an unsupported promise.
Resolve what the camera must actually show
Ask which visual moment makes the message understandable. For an opening mechanism, the client may need a close view of the tab, a complete open-and-close cycle, or a comparison with an earlier design. Saying “show the product clearly” does not decide among those options. Describe the proposed action and ask which view will satisfy the brief.
Check the physical product variant. Color, packaging, accessory, and label differences can matter to a client reviewing a launch asset. Confirm that the item you received matches the item they expect to appear. If a key demonstration requires an accessory you do not have, flag it before the filming slot rather than substituting a different action without discussion.
Ask about the state of the product at the start and end. Should a bottle begin sealed or already open? Does the label need to remain facing the camera? Must the final frame show the product alone or in your hand? These answers become a shot list after approval. They also reveal whether a requested thirty-second runtime leaves enough time for the actual movement.
Translate style references into usable choices
Ask the client what they like about each reference. It could be the conversational voice, handheld framing, bright setting, slow demonstration, or the order of information. A reference video contains many choices; copying all of them can reproduce things the client never intended. Name two or three relevant qualities in your own words and request confirmation.
Clarify the boundaries of “natural.” Does it allow a small wording change while retaining the approved claim? Is a visible pause acceptable? Should the opening feel like a direct explanation or an introduction to a demonstration? These are creative decisions, not universal definitions of UGC. The answer should guide your performance without requiring you to impersonate another creator.
If two references conflict, present the conflict plainly. One might use a calm continuous demonstration while another cuts between many brief reactions. Ask which approach should guide this asset and which details are optional. A concrete choice is easier to approve than a request for more general inspiration, and it prevents you from making a hybrid nobody actually requested.
Send one concise approval summary
Consider this hypothetical bottle brief: “One authentic video, around thirty seconds, show all features, three hooks.” A useful clarification would say: “Please confirm one thirty-second body with three separate opening clips, focused on the opening mechanism. I will show one complete open-and-close action. The line about capacity uses your supplied specification. I will describe the opening I can demonstrate, with no long-term personal-use claim.” This is a production example, not a real client exchange.
Add the proposed opening, closing line, action description, and any unresolved question to the summary. Identify the version and ask the designated approver to confirm those specific items before the main recording. If the product action is difficult to describe, propose a short framing test as part of the agreed workflow. A test is useful when it resolves a named decision; it should not become endless unrequested speculative production.
Keep the approved summary beside the script and check incoming changes against it. When wording changes, update the version label so the performer and editor work from the same instructions. Record who approved which version in your project notes. “Approved” without an identifiable version leaves uncertainty about whether the approval covers the words, the demonstration, or merely the general idea.
Use a ready-or-blocked check before the session
You are ready to film when you can name the viewer, deliverable count, priority message, exact required wording, visible action, and approver. A minor background preference may remain flexible. A missing central claim, wrong product variant, or unclear deliverable count deserves resolution before the expensive part of the session. Keep the distinction tied to the consequence of the unknown.
Once the decisions are confirmed, use the UGC shot list to turn them into footage. The thirty-second script example helps shape a focused spoken sequence. Those tools become more effective when the brief already tells you what success for the assignment looks like.
EasyLines is preparing to launch as a teleprompter and recorder. Join the waitlist if you want help keeping approved lines near the lens when you record. Keep client decisions and approval records in your own project notes so the recording remains attached to the brief it was made to satisfy.
Frequently asked questions
What is the first question to ask a UGC client?
Ask who the viewer is and what this video should help them understand or do. Then clarify the exact assets expected.
Does an approved idea mean the script is approved?
Do not assume that. Identify whether approval covers the concept, exact wording, demonstration, and specific version.
What if required claims do not match my experience?
Flag the mismatch and propose an observable demonstration or accurate wording. Do not invent personal experience.
Should I film while details are unresolved?
You can prepare flexible setup work, but resolve missing central claims, product requirements, and deliverable counts before committing to the main take.
Sources and further checks
Coming to iPhone and iPad
Put your next script on EasyLines.
A little help with the words. More room to be yourself. Join the waitlist and we’ll email you at launch.
