UGC Script Template: 7 Formats Brands Can Adapt

What should a UGC script include?

A UGC script should include the target viewer, one opening hook, the customer problem or desire, a visible product action, supportable proof, a concise CTA, and production notes. It should also identify exact claim language, prohibited statements, disclosure requirements, and the parts the creator may rewrite in their own voice.

Separate the message from the wording. The message is the idea the viewer must understand. The wording is how the creator expresses it. A brand may need exact language for a regulated disclaimer or product fact, but most transitions and reactions sound more credible when the creator can adapt them.

Write for the screen, not a document. Mark the action that occurs beside each line: open the package, show the interface, apply the product, reveal the texture, compare the two settings, or display the final state. If the proof is never visible, the script is only a claim.

Decide whether the speaker is a paid creator, customer, employee, or founder. Do not script paid talent to imply an unpaid customer relationship or personal result they did not experience. The UGC creator definition guide explains how production and distribution models change the assignment.

Copyable UGC script template

Use the template as a message map, then read it aloud before sending it to a creator. The finished version should fit the intended runtime without rushed delivery. Replace every bracketed field and attach the approved product facts, must-show shots, file specifications, rights, and feedback process.

Label each line as exact, message required, or optional. Exact language should be rare and justified. Message-required lines let the creator preserve the fact while changing the sentence. Optional prompts give the creator another route if the original transition feels forced.

Use the free UGC hook generator to create opening directions, then choose only hooks that match the product proof available in the asset. A dramatic hook that the body cannot resolve will create confusion rather than a useful test.

Seven UGC script examples by format

Choose the script format according to the communication job. Demonstrations explain an action, tutorials teach a narrow task, reviews give an honest assessment, routines create context, objections answer hesitation, comparisons clarify a choice, and unboxings show setup or first use. Do not force every product into the same problem-solution pattern.

1. Problem-solution demonstration

Hook: “If [specific problem] keeps happening, check this part first.” Body: show the starting condition, introduce the product, perform the action, and display the approved proof. CTA: invite the viewer to see the relevant option or instructions. Avoid claiming the product solves every cause of the problem.

2. Product walkthrough

Hook: “Here is what actually happens when you use [product] for [task].” Body: move through setup, the core action, and the useful output. Show real screens or product behavior with safe data. CTA: connect the next step to the workflow just demonstrated.

3. Short tutorial

Hook: “Three steps to [narrow outcome] without [relevant friction].” Body: teach one step at a time and place the product where it is genuinely needed. CTA: point to the full process, product page, or trial. Confirm instructions with the product owner before filming.

4. Testimonial-style review

Hook: “What I noticed after trying [product] for [honest context].” Body: describe the real experience, show the product, name who it may suit, and include a relevant limitation. CTA: keep the recommendation proportionate to what the creator actually knows.

5. Routine integration

Hook: “The part of my [morning/workout/work] routine that used to slow me down.” Body: show the surrounding routine, transition into the product action, and return to the broader task. CTA: make the product's role clear without pretending it caused the entire routine outcome.

6. Objection-handling video

Hook: “I thought [specific concern] too, so here is what to check.” Body: answer with an approved fact or visible demonstration, then qualify any limitation. CTA: direct the viewer to specifications, sizing, compatibility, or another useful decision page.

7. Use-case comparison

Hook: “Choose [option A] when [condition], and [option B] when [different condition].” Body: compare against one defined criterion and show both routes fairly. CTA: help the viewer choose rather than making an unsupported universal-best claim.

For more format detail, use the UGC video examples guide. It breaks down the proof and production job behind each structure.

Adapt the script to the creator and placement

Keep the audience, product truth, proof, and CTA stable; adapt vocabulary, setting, pace, and delivery to the creator's demonstrated style. Then adjust framing, runtime, captions, and safe areas for the actual placement. One generic master script rarely serves every creator and channel equally well.

Review several recent creator samples before assigning a format. A creator who excels at calm tutorials may not be the right fit for rapid comedic objections, and a strong lifestyle creator may need different direction for a technical screen recording. Match the script to evidence, not a broad label such as authentic.

Ask the creator to flag lines they would not naturally say or cannot personally substantiate. The brand still owns factual accuracy, but a creator can identify forced phrasing before it reaches the first draft. Record approved changes so reviewers do not later treat them as deviations.

Use the creator screening checklist to evaluate the production skills required by the script. If the asset will run across several placements, define the master composition and each additional export instead of assuming one crop will work everywhere.

Control claims, disclosure, and production details

Give creators a product-truth sheet with approved facts, prohibited statements, disclosure instructions, pronunciations, and evidence requirements. Put visual actions beside spoken claims and define who reviews compliance. A creator's natural delivery does not remove the brand's responsibility for accurate advertising.

The FTC's endorsement guidance covers material connections and honest endorsements. Paid, gifted, affiliate, and other relationships can require clear disclosure. Platform disclosure tools may add requirements but do not replace the team's review of applicable law and market rules.

Avoid universal claims, fake scarcity, fabricated first-person outcomes, unsupported comparisons, and visual demonstrations that create a misleading impression. In sensitive categories, route scripts through the relevant legal, medical, regulatory, or compliance owner before production.

Attach the script to a complete UGC campaign brief. The brief should cover deliverables, product handling, file naming, captions, audio, deadline, revision process, and intended usage; the contract should cover the commercial agreement.

Turn one script into a useful creative test

Create variants around one deliberate variable: hook, proof order, objection, creator delivery, or CTA. Keep the audience, offer, product truth, and landing destination controlled when possible. Label every file and map it to the brief so the launch result can guide the next script instead of producing an unexplained winner.

Write scripts in components. A hook file, body sequence, proof clip, and CTA can be planned as separate deliverables when the agreement includes them. This gives editors legitimate combinations without pretending that raw footage or additional versions were included for free.

Use a simple naming pattern such as campaign-audience-concept-hook-creator-version. Record what changed between versions. When several major elements change together, treat the result as a new concept rather than proof that one line caused the difference.

The UGC campaign guide connects the script to sourcing, rights, production, launch, and measurement. Review the result as evidence for the next hypothesis, not as a guaranteed formula for other products or audiences.

Conclusion

A practical UGC script controls what must be true and visible while preserving the creator's credible voice. Start with the audience, hook, problem, product action, proof, and one CTA. Add claim and disclosure guardrails, then plan variants around a deliberate test. Use the free campaign brief generator to package the script for production, or Start free when the assignment is ready for creator sourcing.

Frequently asked questions