Content rights clearance changes across systems: a map of records, linking keys and owners

Short answer

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.

Visual briefFull-size diagram
Five system nodes, the rights manager, document repository, media asset system, shared mailbox and delivery portal, arranged around one case card, with labeled keys such as title ID, deal reference and version ID traveling along the connectors to join them.
Illustrative: five systems and the keys that join one clearance change into a single case.

This system map is part of the content rights clearance changes guide. 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

SystemRecordLinking key it carriesOwner
Rights managerDeal record with rights linesDeal reference; title IDRights operations
Rights managerSchedule version historySchedule version date; media, territory, language and termRights operations
Rights managerConfigured business rulesRule name and effective dateRights systems lead
Document repositoryClearance memo with approval conditionTitle in file name; deal reference in text, sometimesBusiness affairs
Document repositoryUnderlying music, footage or talent licenseTitle ID; license referenceClearance team
Media asset systemRelease version log and QC reportRelease version ID; title IDPost-production
Shared mailboxLicensor or coordinator correspondenceTitle in subject line, if anyone typed itSales or clearance team
Delivery portalAcceptance noticeDeal reference; buyer's order numberSales 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

KeyJoinsWhat is lost if it breaks
Title IDRights line to memo, underlying license and version logWhich title, or which part of a series, the restriction applied to
Deal or contract referenceRights line to agreement, memo and acceptanceWhether the change came from the master deal or an underlying license
Media, territory, language and termSchedule line to memo wordingWhether memo and schedule describe the same restriction
Release version IDVersion log to the reinstated rightWhich cut satisfied the condition
Schedule version dateRights history to document historyWhether 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. 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.

RecordSystemKeys presentJoined to
Schedule versions before, during and afterRights managerFTR-0187; deal D-3305; dated versionsMemo by deal and date
Archive house email flagging the clipShared mailboxFTR-0187 in subjectExclusion by date and title
Clearance memo with the replacement conditionDocument repositoryFTR-0187; deal D-3305Both schedule versions
Austria cut log and QC reportMedia asset systemFTR-0187-AT2Reinstated line by version ID
Broadcaster acceptanceDelivery portalDeal D-3305Deal 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 turns them into a one-page handoff. For wider context see rights-cleared data, assessing production workflows in a media company and the media and production page.

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, confirm the company on who qualifies and read the program terms before introducing the rights operations head.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Which key breaks most often?

SourceX publishes no measured rate. In conversations, the release version identifier is often missing from the rights line, and the licensor email that started a change often sits outside every system. Both are worth asking about first.

Can a partner test the joins without seeing records?

Yes. Ask the rights operations head to pick three past changes and report, for each, whether the schedule versions, memo, version log and acceptance can be found and matched by title and deal reference. Counts and yes or no answers only.

Sources

  1. eidrdotorg.atlassian.net/wiki/spaces/ERL/pages/2328756242/Data+Model+…
  2. support.microsoft.com/en-us/sharepoint/documents-and-library/resto…
  3. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment