# Rights clearance records: a system map | SourceX

Canonical: https://refer.sourcex.si/guides/content-rights-clearance-changes-records-across-systems
Last updated: 2026-11-04

Five keys reconstruct a content rights clearance change across systems: the title identifier, the deal or contract reference, the media, territory, language and term on each line, the release version identifier and the date of each schedule version. They are held partly in the rights manager, partly in the document repository and partly in the media asset system, with the triggering correspondence in shared mailboxes. If any key is missing, the clearance memo and the schedule cannot be matched, and the case falls apart into unrelated files.

This system map is part of the [content rights clearance changes guide](/guides/workflow-content-rights-clearance-changes). It answers one question for media workflow consultants: where each record lives, what joins it to the others, and who owns each system.

## Five systems, one clearance change

A single clearance change touches more systems than most rights teams expect:

- **Rights manager.** Holds deals, rights lines and schedule versions, each line describing where, how, in which language and for how long a title may be used.
- **Document repository.** Holds clearance memos, underlying licenses, QC reports and signed agreements. Often SharePoint or a similar library.
- **Media asset system.** Holds release versions and the version log that names which cut went where.
- **Shared mailboxes.** Hold the licensor or clearance coordinator email that raised the problem.
- **Delivery portal or buyer correspondence.** Holds the acceptance notice that closes the case.

The rights manager also stores configuration: the business rules a rights systems lead set up when the platform was implemented, and every later change to them. Two companies with identical contracts can get different answers from differently configured systems, so the configuration belongs on the map as a record in its own right.

## The system map: record, linking key and owner

| System | Record | Linking key it carries | Owner |
|---|---|---|---|
| Rights manager | Deal record with rights lines | Deal reference; title ID | Rights operations |
| Rights manager | Schedule version history | Schedule version date; media, territory, language and term | Rights operations |
| Rights manager | Configured business rules | Rule name and effective date | Rights systems lead |
| Document repository | Clearance memo with approval condition | Title in file name; deal reference in text, sometimes | Business affairs |
| Document repository | Underlying music, footage or talent license | Title ID; license reference | Clearance team |
| Media asset system | Release version log and QC report | Release version ID; title ID | Post-production |
| Shared mailbox | Licensor or coordinator correspondence | Title in subject line, if anyone typed it | Sales or clearance team |
| Delivery portal | Acceptance notice | Deal reference; buyer's order number | Sales operations |

Some companies use a shared industry identifier rather than an internal code. EIDR, for example, registers series, seasons and episodes, then a separate Edit record for each creative version, such as a broadcast cut, and a Manifestation for each technical version. A company that records EIDR Edit IDs on its rights lines has already solved the release version join. Read down the third column. Only the title identifier appears nearly everywhere, and even that is sometimes free text. The deal reference connects the rights manager to the memo and the acceptance; the release version ID connects the asset system to the right that was reinstated. Each is a join to confirm, not assume.

## How each key joins, and what breaks it

| Key | Joins | What is lost if it breaks |
|---|---|---|
| Title ID | Rights line to memo, underlying license and version log | Which title, or which part of a series, the restriction applied to |
| Deal or contract reference | Rights line to agreement, memo and acceptance | Whether the change came from the master deal or an underlying license |
| Media, territory, language and term | Schedule line to memo wording | Whether memo and schedule describe the same restriction |
| Release version ID | Version log to the reinstated right | Which cut satisfied the condition |
| Schedule version date | Rights history to document history | Whether approval came before or after the restriction |

Document repositories help with the last key. SharePoint keeps a version history for library files, and restoring an earlier version makes a copy the latest version instead of deleting what came after, so the sequence of memo drafts can survive. Whether a company's repository kept versions on, and for how long, is a question for its administrators.

## One fully joined case (Illustrative)

A fictional distributor, invented for this page, and a different case from the [worked exception example](/guides/content-rights-clearance-changes-exception-examples). A feature film is licensed to a broadcaster for free television in Germany and Austria. Two months later the clearance team learns that one archive clip is cleared for Germany only. Austria is excluded, business affairs approves an Austria cut with the clip replaced, post-production delivers it, and Austria is reinstated for that cut.

| Record | System | Keys present | Joined to |
|---|---|---|---|
| Schedule versions before, during and after | Rights manager | FTR-0187; deal D-3305; dated versions | Memo by deal and date |
| Archive house email flagging the clip | Shared mailbox | FTR-0187 in subject | Exclusion by date and title |
| Clearance memo with the replacement condition | Document repository | FTR-0187; deal D-3305 | Both schedule versions |
| Austria cut log and QC report | Media asset system | FTR-0187-AT2 | Reinstated line by version ID |
| Broadcaster acceptance | Delivery portal | Deal D-3305 | Deal record |

Every identifier above is invented. All five keys held, so a reviewer can rebuild the sequence in minutes. Strip the version ID from the reinstated line and nobody can say whether the Austria right covers the original cut or only the new one.

## Questions for the rights operations head

Write down only the answers; never take exports or logins.

1. Does each schedule version keep its own date, or does the rights manager show only the current line?
2. Is the deal reference written into clearance memos, or only the title?
3. Does the rights line note which release version satisfied a condition?
4. Where do licensor and clearance coordinator emails go after a change is resolved?
5. Who administers each of the five systems, and would they confirm what history each can export?

Export capability varies by product, version and contract, so the answers should come from the company's administrators, not from vendor marketing. When the answers look promising, the [referral brief template](/resources/content-rights-clearance-changes-referral-brief-template) turns them into a one-page handoff. For wider context see [rights-cleared data](/questions/rights-cleared-data), [assessing production workflows in a media company](/guides/how-to-assess-production-workflows-in-a-media-company) and the [media and production page](/industries/media-and-production).

The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Partners sign the Channel Partner Agreement before submitting; the first valid introduction within the 90-day window is credited when the company submits a verified application. Rights, buyer interest and any offer remain unknown until SourceX reviews the opportunity.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client's rights manager, repository and asset system share enough keys to rebuild past clearance changes, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before introducing the rights operations head.

## Sources

- https://eidrdotorg.atlassian.net/wiki/spaces/ERL/pages/2328756242/Data%2BModel%2BMetadata%2BFramework
- https://support.microsoft.com/en-us/sharepoint/documents-and-library/restore-a-previous-version-of-an-item-or-file-in-sharepoint
- https://refer.sourcex.si/terms
