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.
| Check | How to check it at metadata level | Pass | Partial | Fail |
|---|---|---|---|---|
| 1. Coverage | Ask which years the rights log, asset manager and e-sign account each cover | All three overlap for 3+ years | Overlap shorter, or one system replaced mid-period | No overlapping period |
| 2. Version on the rights record | Ask whether exceptions are recorded per cut or per title | Exceptions name the affected versions | Per title, with a notes column used sometimes | Per title only |
| 3. Restriction in asset metadata | Ask whether each version carries a territory or restriction field | Field on every version | Used on some titles, or in version notes | Editors rely on memory and email |
| 4. Version and territory on the release | Ask whether the release form names the version and territories | Both named, as fields | One named, or written in free text | Form names the title only |
| 5. Corrections recorded as corrections | Ask how a withdrawn or reissued release is handled and referenced | Reissue cites the original, with a reason | New envelope, no reference but traceable by date | No record of reissues |
| 6. Approvals and timestamps | Ask whether each version's approver and date are kept | Asset history kept for the full period | Kept recently; older history lost in a migration | Not kept |
| 7. Outcome | Ask whether delivery QC checks version against territory, and logs it | Logged check per delivery | Checked, not logged | Not 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:
- "The release form names version and territory, so the agent sends the training-ground cut." Check 4 passes.
- "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.
- "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.
| Check | Score | What the team said |
|---|---|---|
| 1. Coverage | Pass | Rights log, asset manager and e-sign all from 2018 |
| 2. Version on the rights record | Partial | Version column added to the clearance log in 2021 |
| 3. Restriction in asset metadata | Pass | Territory field required on every version |
| 4. Version and territory on the release | Fail | Release template names the episode only |
| 5. Corrections recorded as corrections | Partial | Reissues are new envelopes; subject line cites the episode, not the original envelope |
| 6. Approvals and timestamps | Pass | Asset history kept since 2018 |
| 7. Outcome | Pass | Delivery 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.
| Check | What the tool records by design | So the question is |
|---|---|---|
| 6. Approvals and timestamps | iconik 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. Corrections | A 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 record | EIDR 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.