You can responsibly proceed with a client's AI remix only after reviewing whether the permission chain covers the proposed inputs and transformations. A client sending a finished video is a starting point for questions, not a complete clearance record.
Define the remix before requesting permission
Write down the intended changes: new framing, altered backgrounds, translated narration, shortened sequences or a changed depiction of a person. Review each separately. Permission to distribute an existing film should not be assumed to answer every question about creating variations.
Runway's statement that users retain ownership and rights as between themselves and Runway does not establish what a client's original production agreement permits. Its absence of provider-imposed non-commercial restrictions likewise does not resolve contributor permissions.
Complete a permission-chain worksheet
Create one entry for each link in the chain:
- Client authority: who commissioned the original and who can approve this proposed reuse?
- Production agreement: does the supplied document address source materials, adaptations and third-party components?
- Contributors: which performers, narrators, photographers, composers or outside studios need clarification?
- Embedded assets: identify music, stock clips, illustrations, logos and fonts requiring review.
- Transformation scope: describe the exact change, audience, channels, territories and duration.
- Evidence: record the relevant document, unanswered question and authorised reviewer.
Keep confidential agreements in approved storage. Use internal references in the worksheet rather than copying sensitive contractual text into a generation service. Do not upload customer or private material for exploratory testing.
Hypothetical festival-video variation
Suppose a Bengaluru agency is asked to turn a fictional 30-second festival greeting into three 10-second advertisements. The requested changes include replacing the background and making the on-screen presenter appear to speak a new sentence.
The hypothetical production agreement covers delivery of the original greeting, while the presenter permission describes only the recorded performance. The worksheet should flag the newly depicted speech as unresolved rather than treating it as ordinary trimming.
Evaluate whether each variation can be traced to specific permission. A practical alternative is a new text-only ending using approved wording and independently cleared assets. Do not clone the presenter's voice or likeness without consent.
Stop at the weakest unresolved link
Pause any variation whose essential transformation lacks clear approval. Ask the client to obtain clarification from the appropriate rights holder or a qualified reviewer; do not ask a tool to decide the permission question.
For later tool procurement, use the AI tools catalog to compare access format and save offer terms before buying. Marketplace account, code or token offers are not proof of official subscription equivalence. Keep those offer terms separate from provider documentation.
Sources and scope
Source material checked 29 October 2026; features/policies may change. Runway usage rights supports the limited provider ownership and commercial-use statements. The permission-chain worksheet and hypothetical remix are editorial review guidance, not legal advice or evidence that any particular transformation is technically supported.