One release, read twice: what a standalone rights, asset or e-sign export loses in clearance-to-release

Short answer

Most of the meaning is lost. Each system, exported alone, tells a confident but partial story: the rights manager knows a restriction exists, the media asset manager knows two cuts exist and who approved them, and the e-sign tool knows someone authorized "the film" on a date. Only when the three are joined by title and version does the record show a decision: a restriction found, a clean cut made for one territory, and a release that should have named it.

Visual briefFull-size diagram
A signed release form with blank version, territory and delivery fields that fill in as three context pieces slide in from the asset versions, the rights record and the delivery log.
Illustrative documentary. The signature is on the form; the version, territory and delivery come from other systems.

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.

  1. The clearance coordinator records the UK exception on photograph 22.
  2. The editor cuts version 7 with the photograph; it is approved for worldwide use outside the UK.
  3. The post supervisor cuts version 8, replacing photograph 22 with a cleared alternative, for UK broadcast.
  4. The executive producer signs one release for "the film".
  5. 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 needsRights export aloneAsset export aloneE-sign export aloneWhere the missing context lives
Which cut carries the restricted elementNot statedNot statedNot statedEdit decision list or version notes, joined to the rights record
Why a second cut existsImplied by the exceptionNot statedNot statedRights exception plus version history
Which version was authorizedNot statedNot statedNot stated, unless the form names itRelease form field, or the delivery log
Which territories the release coversException onlyNot statedNot stated, unless the form names itRights record joined to the release
Who caught a mismatch, and whenNot statedNot statedNot statedDelivery QC log or distributor correspondence
Who approved each stepClearance approverReviewer per versionSigner with timestampsAlready 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:

  1. Does the clearance log or rights system record which versions an exception affects?
  2. Do release forms name the version and territories, and since when?
  3. 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.

  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 single export loses the most?

The e-sign export, usually. It proves a signature and a date but, unless the form named them, says nothing about which cut or which territories were authorized.

Can the joined history be rebuilt after a system migration?

Sometimes, if the old system's version codes were carried across or a delivery log recorded them. If the links were dropped, the history may survive only as three separate exports.

Is the joined history itself what gets licensed?

Possibly, as operating records of decisions. Whether any media is in scope, and under which third-party rights, is decided in SourceX's rights review, not by the partner.

Sources

  1. app.iconik.io/help/pages/asset/versions
  2. app.iconik.io/help/pages/asset/history
  3. support.docusign.com/s/document-item
  4. eidr.org
  5. 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