# Clearance-to-release metadata packet | SourceX

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

A partner can note, from a conversation with the head of post-production or rights, which systems hold each step from rights exception to approved edit to release authorization (usually a rights manager or clearance log, a media asset manager and an e-signature tool), the years and rough number of titles each covers, who administers them, and whether a territory restriction is carried into the final release record or left behind in the rights system. Nothing is opened or copied; review comes later.

## The field that has to survive: one restricted clip, three systems

This example is Illustrative, built for this page. A factual production and distribution company with about 320 staff makes a six-part documentary series. Episode 3 uses an archive news clip licensed for North America only.

- **Rights manager.** The clearance coordinator records a rights exception: clip 14, territory North America, term seven years.
- **Media asset manager.** The domestic cut is version 4 of the episode asset and includes clip 14. The international cut, version 5, replaces it with a cleared alternative. Both sit under one asset.
- **E-sign.** The executive producer signs a release authorization: "Episode 3 approved for delivery." The form names the series and episode, not the version or the territory.
- **Months later.** A sales agent prepares a delivery to a European broadcaster and asks which file to send. The signed release cannot answer; only the rights record and the version history together can.

The matrix below is the page's evidence asset: which of five fields each system carries for that episode.

| Field | Rights manager | Media asset manager | E-sign release |
|---|---|---|---|
| Title and episode | Present | Present | Present |
| Edit version (v4 or v5) | Missing: rights are recorded at title level | Present | Missing |
| Territory restriction | Present: North America only | Missing, unless a custom metadata field is used | Missing |
| Restricted element (clip 14) | Present | Present inside the v4 edit | Missing |
| Approver and date | Clearance approver | Reviewer on each version | Signer with timestamps |

Read across the territory row: the restriction lives in one system only. That single-cell fact is what a partner should learn to ask about, and it is the case this page is built around.

## What metadata can a referral partner collect about clearance-to-release without reading private content?

The packet is a set of short answers, one block per system plus one for the joins.

**Rights manager or clearance log.** Tool or format (system, spreadsheet, clearance reports); years covered; rough number of titles and exceptions per year; whether exceptions are title-level or version-level; who administers it.

**Media asset manager.** Tool; years covered; rough number of assets and versions; whether versions carry restriction or territory fields; whether version history is kept; who administers it. In iconik, for example, each asset version represents a new media file, usually from an editorial review or approval step, and Asset History shows who performed each action and when, so the version itself is usually well recorded; the question is whether a restriction travels with it.

**E-sign.** Tool; years of envelopes; rough number of release authorizations per year; whether the form names version and territory; who holds the account. A Docusign Certificate of Completion lists the envelope ID, signer events with timestamps and an Envelope Updated entry for each correction, so the date and signer are rarely the gap. The content of the form is.

**Joins and exceptions.** Which identifier links the three (EIDR ID, internal version code, title name); EIDR assigns a permanent ID to each title and version, so a company that registers versions has a ready-made join; whether the company knows of releases where a restriction was missing; how those are caught (delivery QC, distributor query, legal review).

**Unknown until review.** Third-party rights in the media, talent and personal data, the scope of what could be licensed, buyer interest and any offer. For a broader screen, use the [media and production screening worksheet](/resources/a-referral-screening-worksheet-for-media-and-production-businesses); the [chain-of-title question](/questions/chain-of-title-training-data) explains why rights history matters.

## Who can authorize a discussion, and does the company qualify?

The sponsor is usually the CEO, COO, head of business affairs or general counsel: someone who can open a licensing discussion and knows which rights the company holds outright. Name the head of post-production and the rights or clearance lead as the people who can answer the packet. The [media advisor introduction guide](/guides/how-advisors-introduce-media-and-production-clients-to-a-data-licensing-opportunity) covers how to raise the topic.

Check the basics: 50+ full-time employees at peak (freelance crew and contractors excluded, which matters in production), 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.

What stays unknown until SourceX reviews it: demand for the record types, the rights review result, how third-party and personal data would be handled, the offer and any reward. More context: [production workflows in a media company](/guides/how-to-assess-production-workflows-in-a-media-company), the [media and production industry page](/industries/media-and-production) and the [systems hub](/systems).

## Go deeper on clearance-to-release records

- [How rights, edit and release records link](/guides/clearance-to-release-record-linkage): a record-chain table of each step, its record, its key and its system.
- [Clearance-to-release completeness checklist](/resources/clearance-to-release-completeness-checklist): a pass, partial or fail scorecard for judging whether the records are complete enough to discuss.
- [What a release record alone leaves out](/guides/clearance-to-release-missing-context): one Illustrative episode read before and after its surrounding context is added.

## 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 media client can say where its territory restrictions live and whether they reach the signed release, [register as a partner](/register), check it against [who qualifies](/who-qualifies), and keep the [program terms](/terms) open when you introduce its business affairs lead.

## Sources

- https://www.eidr.org/
- 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://refer.sourcex.si/terms
