UGC Video Approval Checklist for Brand Teams

To approve a UGC video, compare a named version with the agreed brief, record observable problems at specific timestamps, and recheck the replacement before signing off. Separate required corrections from new creative requests. An approval should identify the exact file and intended use; “looks good” in a busy chat leaves too much unresolved.

This checklist is for brand teams reviewing commissioned creator videos before production acceptance or release. It does not predict performance from a rough cut. Use the UGC creative brief template to agree on the work before filming, and the raw footage and edited deliverables guide to define which files belong in the handoff.

Start with a reviewable submission

Ask for an asset ID, version number, review link, intended placement, and the brief version used to make the cut. Name one person who consolidates feedback and one person authorized to approve it. Other specialists can contribute without sending the creator conflicting instructions.

Before watching, gather the approved message, required demonstration, agreed deliverables, product reference, and any approved claim wording. If these were never agreed, resolve that gap explicitly. Do not turn a new internal preference into a claim that the creator failed the brief.

Record the agreed review window and revision scope. There is no universal number of included revision rounds: use the actual production agreement. A correction to a missing agreed shot and a request for a new location may have different scheduling and cost implications.

Review the video in three passes

First, watch the whole video at normal speed. Write down what the viewer would understand about the product and what action the video asks them to take. Then inspect execution with sound, captions, and product details in view. Finally, preview the intended placement with its interface overlays. A clean player alone cannot show whether a platform button will cover important text.

Use concrete evidence for each decision:

TikTok's auction in-feed ad specifications, updated June 2026, explain that safe zones vary with dimensions, caption length, and additional formats. They also warn that previews can differ from live display across devices. Use the relevant current template and placement preview; a single permanent “safe zone” is not a complete acceptance test.

Treat claims and disclosure as review items

Check whether a creator is describing actual experience and whether product claims match what the brand can support. The FTC's Endorsement Guides Q&A, explaining the 2023 revisions, says endorsements must reflect honest opinions or experiences and cannot carry claims the advertiser could not lawfully make. Send unresolved claims to the responsible brand reviewer before release.

For an endorsement with a material connection, review the disclosure in the context where viewers will encounter it. The FTC's Disclosures 101, published November 2019, advises putting a video disclosure in the video, not only in its description, and explains why both audio and visual disclosure can help. Do not assume a platform's built-in label alone settles every case. The applicable review depends on the content and its use.

Classify the feedback before sending it

Use these working categories to make decisions explicit. They are an operating method, not an industry standard or a substitute for your agreement.

The first two categories may overlap. Missing an agreed demonstration can also block release. Record both the requirement and the consequence, instead of arguing about whether the video is “good.” Uncertainty is a hold for the relevant owner to resolve, not automatic approval or proof of creator error.

Write one actionable change per note

Each note needs an asset/version, timestamp or range, observation, required change, owner, and resolution check. “Make it more premium” is a direction for a conversation; it is not a verifiable correction. Replace it with the specific agreed requirement, or label it as a new creative request.

For example: “DESK-A V02, 00:06–00:09: the divider installation is not visible. Add the insertion close-up required by brief section 3. We will check that the full action is visible and the caption does not cover the slot.” This tells the editor what to fix and tells the reviewer what to verify.

Resolve contradictory internal comments before sending the list. If one reviewer wants a faster cut and another needs a longer demonstration, the consolidating owner must decide which requirement takes priority. Keep a separate record of superseded notes so they do not reappear as fresh requests in the next round.

Download the UGC video review worksheet (CSV). It includes clearly labeled hypothetical rows and a blank row for your own asset. Add access-controlled review links in your working copy; the public template contains no client or creator data.

Worked example: reviewing a desk organizer video

Imagine an agreed deliverable: one product demonstration, two opening variations, and corresponding clean exports. The approved brief requires showing how a divider is installed. These examples are hypothetical, not client results.

In V02, the first opening says “fits every desk,” but the approved wording only describes the product's adjustable compartments. The demonstration skips the insertion, and a placement CTA covers the instruction caption. A stakeholder also asks for a different room after filming.

The consolidated decision is to hold the affected exports, replace the unapproved claim with approved wording, restore the agreed close-up, and adjust the caption position. The new room is logged separately as a scope decision. The editor receives a single list, not four competing message threads.

The revised close-up sits in a sequence shared by both openings. Therefore, inspect both revised variants, not only the first one. Check that clean exports use the same approved picture cut. If one version passes and another still contains the old claim, identify the accepted version separately and keep the affected one on hold.

Approve a version, then check readiness to release

A useful approval record includes the asset ID, exact filename or immutable review version, decision, approver, date, approved placement, and any remaining conditions. A replaceable link labeled “final” is insufficient by itself. If the file changes after approval, identify the replacement and review the affected parts again.

Use clear states such as approved, changes requested, and awaiting a decision. “Approved subject to fixing the claim” should stay pending for release until the replacement has been checked. Record what was verified, not merely that the editor replied “done.”

Creative approval also does not establish that the brand has the required usage rights, platform account authorization, or a working destination. Keep those checks separate. An approved cut can still be held from publication while permission, disclosure, or landing-page issues are resolved. Platform acceptance and campaign results remain separate outcomes.

Build the review process into production

Agree on review ownership, source materials, deliverables, and revision scope when commissioning the work. Then use the same asset IDs from the brief through review and final delivery. This makes the next decision traceable without treating every comment as a fresh production request.

If your team needs an ongoing creator production process, explore Creator Factory or book a call to discuss the brief, review responsibilities, and handoff requirements.

Sources and platform guidance checked November 7, 2026. The worksheets and review method are Holy Marketing's editorial planning tools, not legal approval, platform certification, or a guarantee of performance.