Clearance-to-release completeness checklist: seven checks that show whether a territory restriction reaches the release

Short answer

A clearance-to-release trail breaks when a restriction stops one system short of the release: recorded against the title but not the cut, missing from the asset metadata, or absent from the signed release form. Seven checks show where that happens, each scored pass, partial or fail from yes-or-no questions about practice. Nobody opens a rights record, a media file or an envelope. A company that fails the release form check but logs the mismatch at delivery still has a strong trail.

Visual briefFull-size diagram
A scorecard table of seven clearance checks, each receiving a pass, partial or fail chip in turn, while a horizontal completeness bar fills segment by segment and stops short at the release form check.
Illustrative scoring for a fictional distributor: four passes, two partials and one fail on the release form.

This scorecard is part of the clearance-to-release records guide. The keys behind each check are mapped in the clearance-to-release record chain.

The seven checks

Ask the head of post-production and the rights or clearance lead. Score "not sure" as partial.

CheckHow to check it at metadata levelPassPartialFail
1. CoverageAsk which years the rights log, asset manager and e-sign account each coverAll three overlap for 3+ yearsOverlap shorter, or one system replaced mid-periodNo overlapping period
2. Version on the rights recordAsk whether exceptions are recorded per cut or per titleExceptions name the affected versionsPer title, with a notes column used sometimesPer title only
3. Restriction in asset metadataAsk whether each version carries a territory or restriction fieldField on every versionUsed on some titles, or in version notesEditors rely on memory and email
4. Version and territory on the releaseAsk whether the release form names the version and territoriesBoth named, as fieldsOne named, or written in free textForm names the title only
5. Corrections recorded as correctionsAsk how a withdrawn or reissued release is handled and referencedReissue cites the original, with a reasonNew envelope, no reference but traceable by dateNo record of reissues
6. Approvals and timestampsAsk whether each version's approver and date are keptAsset history kept for the full periodKept recently; older history lost in a migrationNot kept
7. OutcomeAsk whether delivery QC checks version against territory, and logs itLogged check per deliveryChecked, not loggedNot checked

Scoring bands

  • Ready to discuss: five or more passes, no fail, and check 2 or check 4 passes.
  • Discuss with a known gap: check 4 fails, but check 7 passes. The release was imprecise and a logged control caught it, which is a labeled exception with an outcome.
  • Not yet: checks 2, 4 and 7 all fail. The restriction exists in one place only, and nothing downstream recorded whether it was honored.

These bands describe an archive; they do not predict acceptance. Suitability for AI training or evaluation is decided in SourceX's review.

The test case: a territory restriction absent from the final release

Run this case explicitly, because it decides check 4 and check 7 together.

Illustrative. A weekly football magazine show carries league match highlights licensed for the UK and Ireland only. A second cut swaps them for training-ground footage the producer owns, for every other market. The executive producer signs "Season 2 approved for delivery". Months later a sales agent prepares a delivery to a sports channel in Brazil.

Ask: which file would be sent, who would decide, and where would that decision be recorded? Three possible answers, in descending order of usefulness:

  1. "The release form names version and territory, so the agent sends the training-ground cut." Check 4 passes.
  2. "The form names only the episode, but delivery QC checks the rights log and records the version sent." Check 4 fails, check 7 passes: discuss with a known gap.
  3. "The agent would ask the editor." Checks 4 and 7 fail; the decision lives in someone's memory.

A company that gives the second answer and can say "we catch it at QC, and it is logged" has a more credible trail than one that says "our releases are always correct", which nobody can show.

An Illustrative completed scorecard

Illustrative. A 240-person factual entertainment distributor, fictional, scored in one call with its head of post-production and clearance manager.

CheckScoreWhat the team said
1. CoveragePassRights log, asset manager and e-sign all from 2018
2. Version on the rights recordPartialVersion column added to the clearance log in 2021
3. Restriction in asset metadataPassTerritory field required on every version
4. Version and territory on the releaseFailRelease template names the episode only
5. Corrections recorded as correctionsPartialReissues are new envelopes; subject line cites the episode, not the original envelope
6. Approvals and timestampsPassAsset history kept since 2018
7. OutcomePassDelivery QC logs version against territory

Result: discuss with a known gap. The restriction travels from rights to asset metadata to delivery; only the release form drops it. From 2021 the rights side is version-level too. That is a clear, honest description to hand SourceX.

Why these checks can be scored by asking

The tools most studios already run keep enough history that a lead can answer from memory of how they are set up, without opening anything.

CheckWhat the tool records by designSo the question is
6. Approvals and timestampsiconik treats each new media file as an asset version, typically created at a review or approval step, and its history log names the person, the action and the time"How far back does asset history go, and did a migration cut it?"
5. CorrectionsA Docusign completion certificate logs signer events with times and an update entry for each correction, but a finished envelope cannot be corrected, so a later change means a void or a fresh envelope"When a release is redone after signing, what points the new envelope at the old one?"
2. Version on the rights recordEIDR models one film as several edits, each with its own derived clips and trailers, which is the level a restriction belongs at"Is the exception filed against the edit, or against the film?"

Each answer is a habit or a setting, never a record.

Who answers, and who authorizes

Checks 1, 3 and 6 belong to post-production; check 2 to the clearance lead; checks 4 and 5 to business affairs or whoever owns the release template; check 7 to delivery or QC. None of them can authorize a licensing discussion. The CEO can, often with the COO, head of business affairs or general counsel sponsoring it internally. Chain of title for training data explains why rights history is the first question a buyer asks.

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 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. For a first screen use the media and production screening worksheet; for wider context see production workflows in a media company, and if the studio sits in a portfolio, the portfolio review handoff checklist.

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 scores ready to discuss, or fails only the release form check with a logged delivery control, register as a partner, check it against who qualifies, and read the program terms before introducing its sponsor.

  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

Is a fail on the release form check a dealbreaker?

No. If delivery QC catches territory mismatches and logs them, the trail still has an exception and an outcome. Say so; it is a better description than claiming every release is correct.

What if clearances are tracked in spreadsheets?

Score them the same way. A clearance log with a version column passes check 2 as well as a rights system does.

Who should be in the scoring call?

The head of post-production and the rights or clearance lead, with business affairs if release forms are theirs. Thirty minutes is usually enough.

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. support.docusign.com/s/articles/FAQs-related-to-correcting-envelo…
  5. eidr.org/how-we-work
  6. 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