Build a provenance sheet with one record per shot and separate entries for its component layers. Label filmed, licensed, generated and composited material distinctly so a reviewer can locate an unresolved question without reopening the entire production history.
Choose useful shot boundaries
Give each shot a stable identifier and time range, then link it to the current edit version. If a shot moves, preserve its identifier and update its location. For an Indian agency managing several language edits, record which versions contain the same underlying material.
Do not classify a whole video as “original” or “AI-generated” when it contains mixed sources. A generated background behind a filmed performer is a composite with at least two provenance paths. Music and narration need their own references even when they span several shots.
Use a component-level inventory
For each shot, record:
- Shot ID, timecode and edit version.
- Component name and type: filmed, licensed, generated or composited.
- Creator, supplier or provider, where documented.
- Input origins and permission-document references.
- Transformations, such as cropping, replacement or layering.
- Intended channels, territories and language versions.
- Open review question, responsible person and status.
For generated components, retain enough process information to identify the relevant inputs and output version. This is an editorial recordkeeping recommendation, not a claim that a particular platform supplies provenance metadata.
Hypothetical four-layer shot
Suppose a fictional 12-second Bengaluru café promotion includes shot S03 from 00:06 to 00:09. It combines an original cup photograph, a licensed tabletop texture, a generated abstract background and independently recorded narration.
Create four component entries. The photograph entry references its creator's permission; the texture entry references the specific licence; the background entry identifies its cleared inputs; the narration entry points to the agreed recording scope.
Evaluate S03 by checking whether every layer has an identifiable origin and a resolved use question. If only the texture's campaign scope is unclear, mark that layer and every edit containing it. Replacing it should trigger a new version and a fresh review, not deletion of the old history.
Resolve precise gaps before export
Pause affected shots when an essential component lacks traceable permission evidence. Ask for clarification or replace that component with a documented alternative. Seek professional review for ambiguous agreements rather than marking them cleared by assumption.
If procuring production access, check the AI tools catalog for access format and saved terms before buying. Marketplace account, code or token offers are not proof of official subscription equivalence; they also do not prove asset provenance.
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. That does not establish clearance for every composite layer. The inventory and hypothetical shot are editorial guidance, not legal advice.