Before reusing a delivered UGC video, identify the exact asset, describe the new use and compare it with the documented agreement. Keep missing or conflicting information open until it is resolved. Accepting a final file, having it on your computer or being able to launch an ad is not the same evidence as a confirmed scope for that proposed use.

Name the asset and the proposed use

Start with one file and version, or the link to an existing creator post. “The bowl video” is too vague if the folder contains a captioned export, a clean export and a later cutdown. Record which version you plan to use, which account will publish it and whether it will be an ordinary post or a paid ad.

Find the agreement and any later changes that both parties confirmed. Read their scope instead of filling gaps with assumptions about what production payment, credit or a tag includes. This guide helps organize that comparison; it does not decide legal ownership or replace advice on an unclear agreement.

The production brief and delivery review answer different questions. A file may meet the creative brief while the team still needs to confirm a new channel, a longer period or an edited version. Keep those questions separate so a reuse request does not silently become part of an earlier acceptance.

Build a record with evidence, not just checkboxes

A manual record for one asset and one proposed use

Scroll sideways to see all columns.

A manual record for one asset and one proposed use
FieldWhat to record
AssetFilename/version or post link; identify any proposed new export.
DestinationPlatform, placement and exact publishing account; include any agreed territory or audience limits.
Type of useOrganic posting, paid advertising or another specifically described use.
TimingAgreed start and end, time zone, and what is agreed about existing posts when the period ends.
EditsThe actual requested changes: cutdown, captions, translation, new voiceover or other modification.
Separate elementsMusic and other included material; evidence covering the intended use.
Evidence and actionAgreement reference, who confirmed it and when; unresolved question, responsible person and next decision.

For each field, write “confirmed for this proposed use,” “needs clarification,” or “proposed change.” Add the supporting reference beside the status. These are internal tracking labels, not a legal certification. A checkbox without a traceable agreement is not useful evidence.

Keep agreements and any authorization codes in an appropriate private location. Share only what the people handling the collaboration need. Record a reference in the worksheet rather than placing private codes in a public document.

Check platform authorization and music separately

TikTok says Spark Ads can use another creator’s organic post with that creator’s authorization, and that the authorization-code duration can be customized. If that is your proposed format, record the relevant platform authorization alongside the agreed scope. Do not use a working code as a substitute for checking the account, dates, edits and other terms the parties actually agreed.

Music needs its own check. TikTok’s Commercial Music Library guidance says businesses cannot use its general music library for commercial use. It identifies organic content, video ads and branded content as commercial TikTok activities. An unpaid brand post can therefore still fall within that guidance; “organic” does not settle the music question.

For other original or licensed sounds, the same TikTok guidance tells businesses to ensure a proper license. Check the relevant track and intended placement. The cited page does not establish permission to export a track to another platform or a website. Treat a change of destination as a reason to recheck, not as proof that the old permission follows the file.

Use the platform’s official authorization process where needed; do not request the creator’s password. A scope record, platform authorization and evidence for included material answer different questions. None should be silently substituted for the others.

Example: one file, three different decisions

This is a fictional training example, not a Stage campaign or a standard licensing term. Suppose the written record covers bowl-demo-v2.mp4, unchanged, on the brand’s named TikTok account as an organic post, from 1 October 2026 at 00:00 until 1 November 2026 at 00:00, Asia/Riyadh. Assume the music check for that exact use has been completed. Paid ads, edits and any extension are not included in this example’s confirmed scope.

Compare the proposal with the fictional record

Scroll sideways to see all columns.

Compare the proposal with the fictional record
Proposed useRecord status and next action
Post the unchanged file on the named account on 10 OctoberMatches the recorded scope. Check that the actual file and planned post still match before publishing.
Run a 15-second cutdown as a paid ad on 10 OctoberProposed change: confirm the edit and paid use, recheck music, and complete any platform authorization required by the chosen ad format.
Publish the unchanged file on 5 NovemberOutside the recorded interval. Request an extension and document the agreed dates before treating this use as confirmed.

The result comes from the invented agreement, not a universal rule that organic rights are free or that every extension has a particular fee. If the real agreement is silent or contradictory, label the point unresolved and obtain clarification. Do not infer permission from a lack of reply.

Also clarify what should happen to an existing post when an agreed period ends. The worksheet should record the parties’ actual arrangement; it should not invent a universal removal rule.

Send a specific request, then update the record

Proposed new use
Asset or post and exact version:
Current agreement reference:
New platform, placement and publishing account:
Organic or paid use:
Requested start/end and time zone:
Requested edits and other changes:
Music or other material that needs a separate check:
Please confirm whether this scope is acceptable, any conditions or additional fee, and any required platform authorization.
We will keep this proposed use pending until the relevant points are agreed.

Send the inquiry to the appropriate person; a request is not an agreement. Once the scope is settled, retain the original record and add the dated update, who confirmed it, the exact asset it covers and the final decision. Do not rewrite the old entry so that it appears the broader use was always included.

  • Before publication, compare the scheduled file, account, format and date with the latest record.
  • Assign someone to revisit time-limited arrangements before the agreed period ends.
  • If the plan changes again, reopen the affected fields instead of copying an old “confirmed” label.

The useful outcome is a specific answer about this asset and this proposed use. If an unresolved point requires legal interpretation, seek qualified advice rather than turning an internal worksheet into a ruling.

How this fits UGC Stage

UGC Stage is an application in development connecting brands and UGC creators. Its planned collaboration workflow keeps conversations, references, files and feedback with the project. Keeping the agreed use and later clarifications beside the relevant delivery can help both parties find the current context. This worksheet is a manual record, not an automatic license check or expiry-alert feature in Stage. Join the brand launch list to hear when the application becomes available.

Explore the application

Sources and notes

Practical guidance from the UGC Stage team. Examples are educational, not customer results or income guarantees.