Review every asset, derivative and publication connected to the contributor when their permission changes. First establish what they are asking to change; then map the affected work. Do not assume either that everything must disappear immediately or that a platform ownership statement settles the issue.
Clarify the requested change
Record the contributor’s request accurately and acknowledge it without promising an outcome that has not been assessed. Ask whether the concern covers future work, existing publications, specific channels, particular languages or a defined campaign.
Distinguish an objection to one edit from a request concerning every use of a likeness or voice. Record the requested timing and any immediate concern, while referring contractual questions to the responsible reviewer.
Keep personal correspondence restricted. Production colleagues generally need the affected asset identifiers and action status, not the contributor’s private explanation.
Draw a consent-change impact map
Build the map as linked entries rather than a single “consent withdrawn” label:
- Source node: original recording, photograph or contribution.
- Permission node: relevant document and unresolved interpretation questions.
- Derivative nodes: crops, translations, cutdowns, audio edits and composites.
- Distribution nodes: published, scheduled, delivered or archived versions.
- Control node: person or organisation able to act at each destination.
- Action node: hold, investigate, replace, seek clarification or complete review.
For every connection, record an asset identifier and evidence of the link. Also inspect reusable templates: a contributor’s material may remain embedded in an unfinished campaign.
Work through a hypothetical language campaign
Hypothetical example: a contributor’s authorised appearance is used in a fictional 45-second English explainer, two Hindi cutdowns and one scheduled Marathi adaptation. The contributor asks to stop future promotional use but says nothing about existing educational publications.
Mark the scheduled adaptation for review before release. Identify whether each published version is promotional or educational under the project’s own records, but do not decide the contractual meaning from those labels alone.
Evaluate the map by tracing each derivative back to the contribution and naming who can act on it. A missing publication contact is a practical gap even when the permission document is available.
Separate ownership from the response decision
Stop new uses of the affected contribution while material ambiguity is being reviewed. Next, clarify scope, obtain appropriate advice and record the agreed actions against each version. Replacing one master file is not evidence that all derivatives were addressed.
For future procurement, use the AI tools catalog to check access format and save offer terms before buying. Marketplace account/code/token offers are not proof of official subscription equivalence.
Sources and scope
Source material checked 29 October 2026; features/policies may change. Runway usage rights states that users retain ownership and rights as between themselves and Runway; it also describes commercial-use freedom from Runway’s non-commercial restrictions and no formal credit requirement. It does not resolve contributor contracts or permission changes. The impact map is editorial guidance, not legal advice.