# Rights clearance changes: pre-migration inventory | SourceX

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

Before a rights platform migration, inventory the three records that explain each content rights clearance change: the rights schedule versions showing what was permitted by territory, media, language and term before and after; the approval conditions attached to the clearance; and the release versions cut to satisfy them. Note which system holds each, the years covered, who owns it and when access to the old platform ends. Then introduce the executive who can authorize a data discussion; licensing depends on rights, qualification and use.

## What is a content rights clearance change?

It is any change to what a distributor, broadcaster or studio may do with a title after the first clearance: a territory removed because a music license covers fewer countries, a language added, a window shortened, a platform excluded. Each change is a negotiation between rights dimensions, and modern rights systems model those dimensions explicitly. Rightsline's API, for example, represents rights by [media, territory, language and channel](https://api-docs.rightsline.com/avails/avails-overview), with term and exclusivity as their own objects; its availability output can express an exclusion in plain text, such as a [worldwide right excluding named countries](https://api-docs.rightsline.com/avails/avails-get-availability); and its conflict engine lets users define [how overlaps, exclusivities and restrictions are treated](https://www.rightsline.com/features/avails-and-conflict-engine/).

That configuration is itself history. The rules a rights team set for overlaps, and every schedule version they produced, show how the company reasoned about clearance over years. A migration that imports only today's rights lines keeps the answer and loses the reasoning.

## What should be inventoried before a rights platform migration affects content rights clearance changes history?

Inventory record classes, years covered, system owners and the real access deadline. A migration typically converts current rights lines and open deals, and may leave superseded schedule versions, audit history, avails rules and attachments behind in a platform that will go read-only.

Here is an Illustrative register for a fictional 280-person independent film and series distributor. Each cell is metadata from a conversation, not a document.

| Record class | System today | Years held | Owner | Migration plan |
|---|---|---|---|---|
| Rights schedule versions per title and deal | Old rights platform | 9 | Rights operations | Current version only |
| Avails and conflict rules | Old rights platform configuration | 6 | Rights systems lead | Rebuilt by hand; old rules undocumented |
| Clearance memos and approval conditions | SharePoint library | 9 | Business and legal affairs | Stays; links to deals not re-pointed |
| Underlying music, footage and talent licenses | Clearance team repository | 12 | Clearance team | Outside the project plan |
| Release version log naming territory cuts | Media asset system | 7 | Post-production | Current cut linked only |
| Licensor and distributor correspondence | Shared mailboxes | 8 | Sales and acquisitions | Separate email retention rules |

SharePoint's own behavior shows why "which version moves?" matters: its libraries keep a version history, and [restoring an earlier version](https://support.microsoft.com/en-us/sharepoint/documents-and-library/restore-a-previous-version-of-an-item-or-file-in-sharepoint) does not remove it but makes a copy the latest version. A migration tool that copies only the latest file drops that trail unless someone asks for it.

Four questions complete the inventory:

1. Does the new platform import superseded schedule versions, or only the current state?
2. Are the old overlap and exclusivity rules written down anywhere outside the old system?
3. Is each clearance memo linked to the schedule version it changed?
4. On what date does the old platform go read-only, and have exports been tested?

A partner records the answers, not the records. Do not collect schedules, contracts, exports or logins, and do not recommend keeping anything beyond the company's retention policy, its licensor agreements or the authority of the person asking. Mail retention is covered in [an email platform migration](/guides/an-email-platform-migration), and Box-based repositories in [Box retention policy export](/systems/box-retention-policy-export).

## Work through one territory change the migration would hide

Take an Illustrative documentary episode cleared for subscription streaming in the U.S. and Canada. A later schedule version removes Canada because a music license covers the U.S. only; an approval condition requires the track to be replaced; a re-edited release version restores Canada. After a current-state migration, the new platform shows an episode cleared for both countries, with nothing to say that it was briefly not, or why a second cut exists. The detailed case walk-through belongs on the exception examples page linked below; for the inventory, the question is whether the superseded schedule, the condition and the first release version all have a home.

## Ask the rights operations head about coverage and rights

The head of rights operations knows where schedules, rules and memos live and what the migration converts. Authority to discuss licensing usually sits with the CEO, COO or head of business and legal affairs. Ownership is the delicate part: the company's operating records are often its own, but licensor agreements frequently carry confidentiality terms, and the underlying content is a separate rights question entirely. See [rights-cleared data](/questions/rights-cleared-data) and [data rights documentation for AI licensing](/guides/data-rights-documentation-for-ai-licensing); SourceX's rights review decides.

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, and the first valid introduction within the 90-day window is credited when the company submits a verified application.

Unknown until SourceX reviews it: buyer interest in this record type, the rights result, the de-identification required and any offer. Neighboring reading: [assessing production workflows in a media company](/guides/how-to-assess-production-workflows-in-a-media-company), [how advisors introduce media and production clients](/guides/how-advisors-introduce-media-and-production-clients-to-a-data-licensing-opportunity), the [production schedule change log](/data-types/production-schedule-change-log), the [media and production page](/industries/media-and-production) and the [industries hub](/industries).

## Go deeper on content rights clearance changes

- [Content rights clearance changes referral brief template](/resources/content-rights-clearance-changes-referral-brief-template): a fill-in brief with metadata fields only and one completed Illustrative example.
- [Content rights clearance changes exception examples](/guides/content-rights-clearance-changes-exception-examples): one clearance change worked step by step.
- [Content rights clearance changes records across systems](/guides/content-rights-clearance-changes-records-across-systems): a system map of rights platform, repository and asset system records and their keys.
- [Who can license content rights clearance changes records](/questions/who-can-license-content-rights-clearance-changes-records): a decision tree for who can approve a discussion.

## 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 distributor or studio client is replacing its rights platform and superseded schedules and clearance memos are not on the migration list, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce the executive who can authorize the discussion.

## Sources

- https://api-docs.rightsline.com/avails/avails-overview
- https://api-docs.rightsline.com/avails/avails-get-availability
- https://www.rightsline.com/features/avails-and-conflict-engine/
- 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
