PROPOSED PROJECT
Footage Rights Tracker
Show producers which clips need permission before a video is released. Match clips to supplied licenses, check where and until when they can be used, and show the relevant license passage beside each flagged scene for the rights team.
The clip fits the edit. Does the permission fit the use?
Requested release / 15 Nov 2026
Worldwide / unpaid + paid social
Station exterior
Supplied terms matchL-17City aerial
Paid use excludedL-22Archive arrival
Record missingNo supplied recordPaid social adverts.
The release brief includes paid placements as well as unpaid posts.
“Worldwide unpaid social posts only, from 1 October to 31 December 2026. Paid advertising is excluded.”Authored example clause / not a real license
Put the restriction
next to the actual use.
A fictional three-clip promo is planned for worldwide unpaid social posts and paid social adverts on 15 November 2026. Record L-17 covers the first clip’s supplied date, territory, and placements. L-22 excludes paid advertising for the second clip. The third clip has no supplied permission record. The review therefore shows one supplied-term match, one placement conflict, and one missing record; none is approved for release by this demo. All clauses are authored examples, not real licenses or legal advice.
WHAT IS USUALLY DONE
A producer checks a cut against a folder of licenses and email approvals. The footage name in the edit may differ from the license attachment, and a permission for unpaid social posts may be mistaken for permission to run the same clip as an advert. Missing paperwork is easy to overlook.
WHAT SOVRUN CAN DO FOR YOU
Sovrun would connect each clip in an edit to the team’s supplied permission records and intended release plan. Document models propose the relevant passages for territory, placement, dates, and other conditions. A review sheet shows the source wording next to the requested use, separates matching supplied terms from conflicts and missing records, and sends unresolved items to the rights team. Staff confirm the interpretation and approve the release decisions.
A review queue
with the evidence beside it.
The requested date, territory, and placements are compared with each supplied passage. Missing records stay missing. Even a match goes to the reviewer, who reads the full agreement and checks conditions beyond these extracted fields.
Station exterior
Supplied terms match“Worldwide use in unpaid social posts and paid social adverts from 1 October to 31 December 2026.”
Review the complete agreement and any other conditions before approval.
Release decision: pendingCity aerial
Paid use excluded“Worldwide unpaid social posts only, from 1 October to 31 December 2026. Paid advertising is excluded.”
Ask the rights team to obtain further permission or replace the clip for paid placements.
Release decision: pendingArchive arrival
Record missingNo passage to cite.
No use conditions to compare.
Find the permission record and confirm it belongs to this exact source clip.
Release decision: pendingKnow what needs a decision.
Keep the evidence with the clip.
A first build covers a defined edit, its supplied permission folder, and one release plan. These are examples of the review outputs; the demo makes no actual permission decisions.
Three clips. Three different states.
- C01 / L-17
- Supplied terms match
- C02 / L-22
- Paid use excluded
- C03
- Record missing
Resolve the paid cut.
- C02Further paid-use permission or a replacement.
- C03The exact clip’s permission record.
A match is not an approval.
- Requested release
- 15 Nov 2026
- Records linked
- 2 of 3 clips
- Release approvals
- 0
- Decision owner
- Rights team
How we’d make it happen.
Match clips to their supplied records
Read the edit list and permission folder. Confirm exact clip identifiers or ask the producer to resolve ambiguous matches before comparing terms.
Compare the intended use
Place the requested territory, date, and placement beside the cited passage. Flag a conflict or missing information without treating a plausible match as approval.
Record the rights team’s decision
The reviewer checks the complete agreement and any additional conditions. Attach approval, replacement, or permission requests to the clip and export the review record.
Where AI helps
Document-reading models locate candidate clip identifiers and permission passages in the supplied files. Matching code compares the agreed structured fields with the requested use and date. Ambiguous wording, incomplete records, uncertain file matches, and unsupported conditions remain unresolved. The system cites supplied text rather than inventing permission or deciding a legal question.
What people approve
The production and rights teams confirm the clip-to-document match, interpret the complete agreement, and review any conditions beyond the extracted passage, including music, performers, credit wording, and restrictions. A field match is not release approval. Only the designated reviewers can authorize use, seek further permission, replace a clip, or record a decision.
What we’d need to start
- An edit list with clip IDs, original file paths, and timeline ranges
- Supplied licenses and permission records with their related attachments and versions
- The proposed release date, territories, placements, required credits, and responsible rights reviewers
How we’d test it
Test renamed clips, incomplete attachments, permission periods ending before release, paid placements excluded from an otherwise matching permission, and clips with no record. Each finding must open the exact passage and version. Measure missed restrictions and false alarms with the rights team’s labeled examples. Confirm that matching extracted fields never automatically changes a clip to approved.
Prepared for Media & entertainment. We would agree on the work after reviewing your brief, materials, and requirements.
This is a proposed project, not completed client work. The visuals and numbers show example outputs, not measured results.
