Track permissions at asset level and connect each expiry to the campaign versions that use that asset. A video remaining online does not, by itself, answer whether its underlying music, footage or likeness permissions still cover that use.
Separate platform rights from asset licences
Runway says that, as between you and Runway, you retain ownership and rights to uploaded and generated content. Its usage-rights statement also says generations have no non-commercial restrictions imposed by Runway and require no formal credit.
That platform statement should not replace a review of underlying permissions. Ask separately what each source-asset licence or approval covers, including duration, channel and territory. Do not assume an AI edit extends a source permission or removes its review conditions.
Build a calendar that triggers action
Create one record per asset-permission combination, with these fields:
- Asset and version: A stable identifier, not just a filename such as final-video.
- Evidence location: Where the approved permission record is held.
- Permitted context: The documented purpose and any questions still unresolved.
- Territory: For example, India only if that is what the actual record states.
- Channels: Organic social, paid placements, website or other specifically reviewed uses.
- Start and expiry: Include the time zone when timing matters.
- Renewal owner and review date: Who decides before the expiry arrives?
- Affected outputs: Every language cut, short excerpt and campaign placement using the asset.
- Fallback action: Pause, replace or request renewal, subject to the reviewed terms.
Use reminders as workflow prompts, not as evidence that renewal has occurred.
Hypothetical example: a festive campaign
Suppose a fictional Indian retailer has three reviewed permission records: music through 30 November, a performer depiction through 31 December, and a background illustration with no recorded end date. The film has English and Marathi versions plus a six-second advertisement.
Set an editorial review reminder for 10 November and a decision deadline for 20 November. These are chosen planning dates, not platform requirements. Link the music record to all three outputs.
Evaluate readiness on 20 November: is renewal documented, is an approved replacement ready, or must the affected placements pause? “Renewal requested” is not the same status as “renewal confirmed.” The illustration's missing end date also needs clarification rather than an assumption of perpetual use.
Stop distribution drift
Pause expansion into a new channel or territory until the relevant permission scope is reviewed. Next, reconcile the calendar against the actual live campaign inventory; forgotten excerpts can otherwise escape the review.
If purchasing production access through the AI tools catalog, check access format and save terms before buying. Marketplace account/code/token offers are not proof of official subscription equivalence, and an access period is separate from an asset-permission period.
Sources and scope
Source material checked 29 October 2026; features/policies may change. Runway usage rights establishes the bounded provider-rights statements above, not the terms of third-party assets. The calendar, reminder dates and stop decisions are practical editorial advice, not legal interpretations.