Prepare a version-linked evidence file before publication so a rights complaint can be investigated without reconstructing the entire production. The file should show what was used, what evidence was reviewed and where the creative appeared. It is a response aid, not proof that a complaint is invalid.
Index evidence rather than collecting everything
Assign the project an identifier and name a person responsible for maintaining its response file. Use references to restricted records instead of copying private documents into a widely shared folder.
Keep factual notes separate from interpretations. “Permission email dated 12 September covers version B” is more useful than “All rights sorted,” especially when a later export introduces new material.
Avoid uploading complaint correspondence or identity records to an AI service as a default investigative step. Decide what information is actually needed and who should review it.
Create a complaint-response evidence index
Include these entries:
- Asset register: component IDs, origins and timeline locations.
- Permission register: relevant documents, scope questions and reviewers.
- Provider terms: dated records of the material relied upon.
- Approval register: approver, exact version and outstanding conditions.
- Publication register: destination, publication identifier and responsible contact.
- Change history: replacements, edits and derivative exports.
- Incident log: complaint received, affected material and actions taken.
Keep the original complaint intact within the appropriate restricted record. Summaries should distinguish what the complainant alleges from what the team has independently confirmed.
Reconstruct a hypothetical disputed clip
Hypothetical example: a fictional studio publishes a 35-second English video and a 20-second Hindi cutdown. A contributor questions a photograph visible for two seconds.
The index should reveal whether both exports contain that photograph, which permission record was reviewed and who controls each publication. If the Hindi version uses a cropped derivative, connect it to the same source asset rather than treating it as unrelated.
Evaluate the file by asking a colleague to locate the two exports, the relevant permission and the publication contacts without guessing. Missing links become preparation tasks, not assumptions about the complaint’s merits.
Preserve records and decide the next action
Stop further distribution of the questioned component while the responsible team assesses the issue. Next, consider whether to pause affected publications, seek clarification or obtain qualified advice. Do not promise a particular platform response or dispute outcome.
If selecting tools for future production, check access format and save marketplace terms through the AI tools catalog. Marketplace account/code/token offers are not proof of official subscription equivalence or a replacement for project evidence.
Sources and scope
Source material checked 29 October 2026; features/policies may change. Runway usage rights establishes user ownership and rights as between users and Runway, no Runway-imposed non-commercial restriction on generations, and no formal credit requirement. It establishes no complaint procedure or outcome here. The evidence index and response suggestions are editorial advice, not legal advice.