This before-and-after reading is part of the clearance-to-release records guide. The keys that join the pieces are mapped in the clearance-to-release record chain; this page shows what a reader loses without them.
Before: three exports, read separately
Illustrative. A 330-person documentary and factual producer, fictional, completes a feature documentary about a postwar shipyard. One archive photograph is licensed worldwide except the UK, where a separate agency controls the rights.
Rights manager export. Element: archive photograph 22. Territory: worldwide excluding UK. Term: perpetual. Status: cleared with exception. Nothing says which cut of the film uses the photograph, or whether a cut without it exists.
Media asset manager export. Feature asset with two versions: version 7, approved by the editor and the director on one date, and version 8, approved by the post supervisor eleven days later. In iconik, each asset version represents a new media file, usually created at an editorial review or approval step, and Asset History records who performed each action and when. So the export proves both cuts existed and who approved them. It does not say why version 8 exists or how it differs.
E-sign export. One completed envelope. The Certificate of Completion lists the envelope ID, subject ("Shipyard feature: release for delivery"), originator, and the executive producer's signing events with timestamps. A Docusign certificate also lists an Envelope Updated entry for each correction; there are none. The form names the film. It does not name a version or a territory.
Read alone, each export answers its own system's question and nothing else. A buyer, an auditor or a model trained on any one of them would conclude the film was simply cleared, cut and released.
After: the same release, joined by version
Join the exports on title plus version code and a sequence appears.
- The clearance coordinator records the UK exception on photograph 22.
- The editor cuts version 7 with the photograph; it is approved for worldwide use outside the UK.
- The post supervisor cuts version 8, replacing photograph 22 with a cleared alternative, for UK broadcast.
- The executive producer signs one release for "the film".
- Months later, a UK broadcaster licenses the film. The delivery log shows version 8 sent, because delivery QC checked the territory against the rights record.
The joined history is a complete decision with an exception and an outcome. The release form was imprecise; a downstream control caught it. That is far more useful as operating evidence than any single export, and it is the kind of record AI developers training or evaluating rights and compliance workflows rarely find in public. What data is missing from AI training explains why connected decision records are scarce.
What is lost, and where the context lives
| What a reader needs | Rights export alone | Asset export alone | E-sign export alone | Where the missing context lives |
|---|---|---|---|---|
| Which cut carries the restricted element | Not stated | Not stated | Not stated | Edit decision list or version notes, joined to the rights record |
| Why a second cut exists | Implied by the exception | Not stated | Not stated | Rights exception plus version history |
| Which version was authorized | Not stated | Not stated | Not stated, unless the form names it | Release form field, or the delivery log |
| Which territories the release covers | Exception only | Not stated | Not stated, unless the form names it | Rights record joined to the release |
| Who caught a mismatch, and when | Not stated | Not stated | Not stated | Delivery QC log or distributor correspondence |
| Who approved each step | Clearance approver | Reviewer per version | Signer with timestamps | Already present in each system |
The last row is the reassuring one: approvals are usually well recorded everywhere. The first four rows are the context that only a join provides. A shared version code is what makes the join possible; EIDR assigns a permanent ID to each title and version, and many companies use an internal code in the same way.
When the joined history is most at risk
Context disappears at system changes. A company replacing its rights system or media asset manager can migrate titles and files cleanly and still drop the version links that tie restrictions to cuts. Afterward, three intact exports survive and the decision they recorded does not. The guide to rights clearance changes before a platform migration covers that event in detail, and it is the moment a partner's question is most timely.
Three questions, asked of the head of post-production or the rights lead, show whether the after version exists:
- Does the clearance log or rights system record which versions an exception affects?
- Do release forms name the version and territories, and since when?
- Does delivery QC check the version against the territory, and is that check logged?
Who can authorize the introduction, and what stays unknown
The sponsor is someone who can open a licensing discussion and knows which rights the company holds outright: usually the CEO, COO, head of business affairs or general counsel. The media advisor introduction guide covers how to raise the topic, and rights-cleared data explains the rights questions a buyer will ask.
The company must meet the program tests: 50+ full-time employees at peak (freelance crew and contractors excluded), 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.
Unknown until SourceX reviews it: third-party rights in the media, talent and personal data, which record types are in scope, and any offer. Partners never ask for or handle rights records, media files or signed releases, and this page does not imply SourceX connects to iconik, Docusign or any rights system. Partners sign the Channel Partner Agreement before submitting introductions. The media and production industry page covers the wider fit.
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 producer you work with can join its rights, version and release records, or is about to migrate a system that holds those links, register as a partner, check it against who qualifies, and read the program terms before introducing its business affairs lead.