# Clearance-to-release record chain by version ID | SourceX

Canonical: https://refer.sourcex.si/guides/clearance-to-release-record-linkage
Last updated: 2026-11-04

A company connects clearance-to-release records with one key that all three systems share: title plus edit version. The rights exception should name the version it restricts, the media asset manager already tracks versions and who approved them, and the signed release should name the version and territory it authorizes. Title names alone join loosely, because restrictions apply to particular cuts. In most chains the weak link is the release form, which names the show but not the cut.

This record chain is part of the [clearance-to-release records guide](/guides/chain-clearance-to-release), which covers the metadata packet a partner collects. This page does one job: step, record, key and system, and where each join fails.

## The chain for one Illustrative show

Illustrative. A 280-person unscripted and branded content studio, fictional, produces a ten-part food travel series. Show 6 uses a commercial music cue licensed for the U.S. and Canada only. The studio cuts one version for those two countries and one for everywhere else, with the cue swapped out.

| Step | Record | Key | System |
|---|---|---|---|
| 1. Rights exception | Cue licensed for U.S. and Canada, five-year term | Title, show number, element ID; version code if recorded | Rights manager or clearance log |
| 2. Edit versions | Version 3 (with cue, U.S. and Canada) and version 4 (cue replaced, rest of world) | Asset ID plus version number | Media asset manager |
| 3. Version approval | Reviewer approves each version on a known date | Asset history entry per version | Media asset manager |
| 4. Release authorization | Executive producer signs "Show 6 approved for delivery" | Signing record ID; title and show number on the form | E-sign |
| 5. Delivery | Version 4 file sent to a broadcaster in Germany | Version code and destination on the delivery log | Delivery or QC log |

Illustrative. The studio, series, cue and versions are fictional.

Read the key column. Steps 2, 3 and 5 carry a version. Step 1 carries one only if the rights coordinator records exceptions per version. Step 4 does not carry one at all, so a signed release cannot say whether version 3 or version 4 was authorized for Germany.

## Where each link breaks, and how it is repaired

| Link | How it breaks | Repair the company may already have | Question to ask |
|---|---|---|---|
| Rights exception to version | Exception recorded against the title only | Clearance log column for affected versions | "Are restrictions recorded per cut, or per title?" |
| Version to version | International cut saved as a new asset, not a version | Naming convention linking the two | "Is the clean cut a version of the same asset?" |
| Version to release | Release form names the show only | Template field for version code and territories | "Does the release form name the version and territories?" |
| Release to reissued release | Corrected release sent as a new envelope with no reference | Envelope subject or note citing the original | "When a release is reissued, how is the first one referenced?" |
| Release to delivery | Delivery log keyed by title, not version | QC log that records the file's version code | "Does delivery QC check the version against the territory?" |

In the Illustrative show, the third row is the weak link and also the easiest to describe. If the studio added a version and territory field to its release template in a known year, every release after that date joins cleanly, and earlier ones join only through the delivery log. "Version field on release forms since 2022" is exactly the kind of fact SourceX needs.

## What each system can hold, by its own documentation

- **A version identifier (step 2 and step 5 key).** EIDR, the registry the industry uses for audiovisual IDs, gives every title and every version a permanent identifier, and its data model lets one film hold several edits, each with its own clips, trailers and derived material. A studio that registers its cuts can join on that ID; most join on an internal code such as "S1-E6-v4".
- **Versions and approvals (steps 2 and 3).** iconik creates a new asset version whenever a new media file arrives, usually at an editorial review or approval point, and its Asset History records which user did what and at what time. That is why these two hops rarely break.
- **The signature (step 4).** Docusign's Certificate of Completion carries the envelope ID, subject, sender, every signer event with a timestamp, and an Envelope Updated line for each correction. It settles who signed and when. Version and territory appear only if the form had fields for them.
- **A redo after signing (step 4 again).** Docusign allows corrections only while an envelope is still in process. Once completed, the only routes are voiding it, where possible, or sending a fresh envelope, so a reissued release always begins a second record, joined to the first only if someone writes the link down.

## Describing the chain without moving any record

The partner's role is to learn which key each system carries and since when, from the head of post-production or the rights lead. A complete answer fits on a few lines: rights exceptions per version since 2020, versions in the asset manager since 2018, release forms name version from 2022, delivery QC logs version code throughout, internal version codes rather than EIDR. Score each link pass, partial or fail with the [clearance-to-release completeness checklist](/resources/clearance-to-release-completeness-checklist); see [what a release record alone leaves out](/guides/clearance-to-release-missing-context) for the same kind of show read with and without its context.

None of this implies SourceX has a connector for iconik, Docusign or any rights system. How records would move is decided after review, and any export field nobody has checked should be marked unknown. The export side of signed envelopes is covered on the [Docusign bulk download page](/systems/docusign-bulk-download-envelopes).

## Who can authorize the introduction

The CEO is the person who can authorize a licensing discussion; the COO, head of business affairs or general counsel, who know which rights the company holds outright, often sponsor or advise. The head of post-production and the clearance coordinator can describe the chain but cannot authorize a license. Rights history is often the deciding question; [rights-cleared data](/questions/rights-cleared-data) and [chain of title for training data](/questions/chain-of-title-training-data) explain why.

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 itself, 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 sign the Channel Partner Agreement before submitting introductions. The [media and production industry page](/industries/media-and-production) 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 studio or distributor you advise can say which key each step carries and when its release forms began naming versions, [register as a partner](/register), check it against [who qualifies](/who-qualifies), and read the [program terms](/terms) before introducing its business affairs lead.

## Sources

- https://www.eidr.org/
- https://www.eidr.org/how-we-work
- https://app.iconik.io/help/pages/asset/versions
- https://app.iconik.io/help/pages/asset/history
- https://support.docusign.com/s/document-item?language=en_US&bundleId=oeq1643226594604&topicId=gpa1578456339545.html
- https://support.docusign.com/s/articles/FAQs-related-to-correcting-envelopes-in-DocuSign?language=en_US
- https://refer.sourcex.si/terms
