UGC Script Templates: 10 Copyable Beat Sheets (With Timings)

Short answer: a good UGC script template is a beat sheet, not a speech: timed beats (hook, proof, push) with the job of each beat and placeholders for facts you can actually show. Below are ten copyable UGC script templates with timings, a table to pick the right one, and the rules that keep the delivery sounding like a person.

The paradox of UGC scripts is that the content has to sound unscripted, but unscripted content mostly rambles. The fix: script the structure, improvise the words. Give a creator (or yourself) the timings and the point of each beat, then let the sentences come out naturally. If you need the process for writing a script from scratch and briefing a creator, see how to write a UGC ad script. For the strategy around all of it, see the UGC ads playbook.

Which UGC script template should you use?

Copy a complete 12-second product-demo script

0–3s | VISUAL: [reaction or screen-led opening]
TEXT: Still sorting [tasks] one by one?
3–6s | VISUAL: show [three tasks] in [Inbox].
TEXT: Start with [the unsorted tasks].
6–9s | VISUAL: perform [Move to Today] and show the result.
TEXT: Choose what belongs in [Today].
9–12s | VISUAL: hold on the completed action.
TEXT: Try it with your next [project].

Use the bracketed template as production instructions, not an actor’s invented personal experience. If your product needs more steps, show them or narrow the promise. Watch the finished task-board example.

The rules that make UGC scripts sound real

• Write the way people talk. Short sentences, everyday words. Complex sentence structure is the loudest tell that something was written.
• Keep one stumble. A restart or a moment of finding the word. Perfect fluency reads as performance.
• Include a hedge in first-person stories. A caveat or initial doubt makes a real person's praise believable.
• Be specific, and only with facts you can support. A named task or a verified number beats 'saves you money.' Never invent a figure to sound specific.
• Say the brand name sparingly. Once or twice is usually enough; repetition is an advertising tic.
• Match the close to the offer. A soft 'try the free tier' fits many short-form ads; a direct offer can fit retargeting. Test both.

Template 1: The 15-second app ad

0–3s | HOOK: reaction clip (filmed or AI UGC). Caption: 'Wait, [specific task] takes one tap?'
3–8s | WOW: hard cut to the screen recording of [input] becoming [visible result]. VO: 'I just [simple action] and it [does the rest].'
8–13s | SUPPORT: one more capability. VO: 'And it [second verified capability].'
13–15s | CTA: app name on screen. 'Try [app name] free.'

The reaction opener is creative, not customer testimony, so keep the caption a question or observation rather than a claim of personal use. If you cannot verify a time saving, describe the action instead of inventing a number.

Template 2: The 30-second testimonial

0–3s | BEFORE: the specific before-state. 'I was spending [real time] on [real task].'
3–10s | DOUBT: 'Someone recommended it. I assumed it was [their actual concern].'
10–22s | TURN: what changed, in a result they can support. '[Specific outcome they experienced].'
22–27s | HEDGE: one honest limitation. '[Setup / learning curve / missing feature] was annoying.'
27–30s | CTA: soft recommendation. 'If you [situation], try [low-friction step].'

Only a real customer with real experience should deliver this. Do not hand it to an actor or an AI character; in the US, for example, the FTC's rule on consumer reviews and testimonials prohibits fake testimonials, including ones attributed to people who do not exist. See UGC rights and best practices.

Template 3: The problem-agitate-solve skit

0–3s | PROBLEM: the frustration, performed. [Person staring at the painful task]. No dialogue needed.
3–6s | AGITATE: caption escalates. 'every. single. [week].'
6–12s | PIVOT: discovery moment. A text, a tab, a tip. 'wait, what is this'
12–18s | SOLVE: demo insert. The same task done in the product.
18–20s | CLOSE: one line. '[Short relief line].'

Template 4: The skeptic's conversion

0–3s | HOSTILE OPEN: arms crossed. 'I genuinely wanted this to fail.'
3–8s | WHY: 'Everyone kept recommending it, which made me want to try it less.'
8–18s | TEST: 'So I gave it [time] and tried to [break it / use it for X].' Show the test.
18–25s | CONCESSION: 'It [did the thing]. [One thing it didn't do].'
25–28s | GRUDGING CLOSE: 'Fine. It's good. I'm annoyed about it.'

This is a first-person experience format: use a creator or customer who really tested the product, or rewrite it in third person over a demo.

Template 5: The direct comparison

0–3s | SETUP: 'I tried both so you don't have to.'
3–12s | OPTION A: what it does well, honestly. Show it.
12–22s | OPTION B: the difference that matters, shown not claimed.
22–28s | VERDICT WITH A CONDITION: 'If you need [X], get the other one. For [Y], this.'

Template 6: The unboxing / first-run

0–3s | MID-ACTION OPEN: already opening the box or the app. No 'hey guys.'
3–10s | REVEAL: genuine first reaction, kept as recorded.
10–20s | FIRST USE: in real time. Small fumbles are fine.
20–25s | FIRST IMPRESSION, HEDGED: '[Honest positive], but [honest caveat].'

Template 7: The founder demo

0–3s | ORIGIN HOOK: 'I built this because I hated [repeated task].'
3–12s | THE PROBLEM: specific and personal. 'For [time], I did this manually every [day].'
12–22s | WHAT YOU BUILT: screen recording while you talk.
22–28s | HONEST ASK: 'It's [early / new]. Try it and tell me what's missing.'

Template 8: The comment reply

0–2s | QUESTION ON SCREEN: a real comment, used with permission or anonymized.
2–5s | RESTATE: 'Someone asked whether it works for [use case].'
5–18s | ANSWER BY SHOWING: demo the exact thing they asked about.
18–22s | INVITE: 'Ask me anything else and I'll make another one.'

Template 9: The 'still using it' follow-up

0–3s | DURABILITY HOOK: '[Time] later. Do I still use it?'
3–10s | HONEST USAGE: '[How often], but not for what I expected.'
10–20s | SURPRISE: the feature that turned out to matter, demoed.
20–25s | QUALIFIED VERDICT: 'Would I pay again? [Answer]. [Honest condition].'

Template 10: The niche-specific reframe

0–3s | NAME THE AUDIENCE: 'If you're a [specific role] who still [repeated task], watch this.'
3–8s | THEIR PAIN: named precisely enough that they feel seen.
8–18s | SAME DEMO, THEIR FRAME: identical footage, narration in their vocabulary.
18–22s | CLOSE IN THEIR LANGUAGE: 'Now [role-specific result] is in [actual destination]. See how [app name] works.'

How many words fit in each script length?

Conversational speech usually runs around two to two and a half words per second. Use these as drafting targets, then read the script aloud with a timer; captions and pauses will change the real number.

How to brief a creator with these templates

1. Send the beat sheet, not a script. Timings and the point of each beat. Say explicitly: 'use your own words.'
2. Ask for the hedge. Tell them a caveat is welcome; many creators assume you want pure praise.
3. Specify what must be shown, not what must be said. Visual requirements are fixed; phrasing is flexible.
4. Ask for two takes with different energy. The second is often looser and better.
5. Request raw files. You will want to re-cut and re-hook the footage later.

The full briefing workflow, with a creator brief template and a weak-line vs strong-line edit exercise, is in how to write a UGC ad script. For more first lines to drop into any template, use the hook ideas swipe file.

Common mistakes with UGC script templates

• Leaving placeholders vague. '[Benefit]' becomes 'saves time.' Replace every bracket with something the camera can show.
• Giving testimonial templates to performers. First-person experience templates (2, 4, 6, 9) need people who really had the experience.
• Front-loading the brand. Nobody cares about the name until the hook has earned attention.
• Too many features. One promise per script. If a second feature does not support the first, cut it.
• Skipping the read-aloud. If you run out of breath or stumble on every take, the script is too dense.