This worked case is part of the content rights clearance changes guide, which covers what to inventory before a rights platform migration. Here the job is to show one hard case step by step, so a media workflow consultant can recognize the same pattern at a client.
The setup: a series cleared for two countries
Illustrative. A fictional 210-person independent film and series distributor licenses a six-episode documentary series to a streaming service for subscription video on demand in the U.S. and Canada, in English and French, for three years from delivery. All names, dates and counts are invented for this page.
At signature, the rights manager shows every line cleared. Think of the deal as a grid: six episodes, two countries, two languages, one medium and one three-year term, 24 cleared cells in all. The exception is about to remove one cell, and the work of the next seven weeks is putting it back without breaking the deal.
Step by step: who decided what, and which record shows it
| Date | What happened | Who decided | Record created | Where it lives |
|---|---|---|---|---|
| March 4 | Deal closed; all six episodes cleared for both countries | Head of sales and business affairs | Rights schedule v3 | Rights manager |
| April 18 | Music supervisor finds the sync license for one track in episode 4 covers the U.S. only | No decision yet; problem raised | Licensor email; cue sheet with the track flagged | Shared mailbox; document repository |
| April 19 | Canada removed for episode 4; delivery date at risk | Rights operations head | Rights schedule v4 with a one-episode exclusion | Rights manager |
| April 23 | Business affairs approves delivery on condition that the track is replaced in a Canada version | Head of business affairs | Clearance memo naming the condition and approver | Document repository |
| May 2 | Editor delivers episode 4 version 2 with a library track; QC passes | Post-production supervisor | Release version log; QC report | Media asset system; document repository |
| May 5 | Canada restored for episode 4, version 2 only | Rights operations head | Rights schedule v5 tied to the version | Rights manager |
| May 9 | Streaming service accepts delivery of all six episodes | Buyer's delivery team | Delivery acceptance notice | Shared mailbox |
Seven dated steps, five deciding roles, three systems and a mailbox. The April 19 schedule is the moment the exception becomes visible in the rights manager. Why a single song can do this is a matter of law, not software: the copyright owner of a recording holds the exclusive right to authorize its reproduction and use in other works, and the Copyright Office describes those rights as a bundle that can be divided and licensed separately. A sync license limited to one country is one such slice, and the series could not be wider than its narrowest slice.
The branch point: two fixes, one chosen
On April 19 the distributor had two reasonable options:
- Carve Canada out of the license for episode 4, renegotiate the fee with the streaming service and deliver five episodes for Canada.
- Cut a Canada version with a replacement track, keep the deal whole and accept the editing cost and a tight delivery date.
The clearance memo records that the head of business affairs chose the second, and why: renegotiation would reopen the whole deal, while a replacement cue was cheap and fast. That reasoning is the part of the history no schedule shows. Without the memo, version 5 looks like nothing happened. With it, the record shows an exception, an authorized action and a checked result, in that order.
Why this sequence is useful evidence
The case answers questions a final schedule cannot:
- Where did the problem start? In an underlying music license, not the master deal. A model trained only on final schedules would never learn that distinction.
- Who had authority to resolve it? A named business affairs head, not the rights coordinator who edited the line.
- Was the fix verified? QC passed on version 2 before Canada was restored, and the buyer accepted delivery four days after the restoration.
- Is the chronology intact? Every record carries a date, and the dates fall in a logical order: problem, restriction, approval, fix, check, reinstatement, acceptance.
That pattern of exception, authorized decision and verified outcome is the kind of decision record AI systems for media operations could learn from. Adjacent patterns appear in production schedule change logs, in procurement approvals and exception workflows and in the general case for exception handling data.
What a current-state report would show instead
Run a standard availability report on May 10 and the series looks unremarkable: both countries, both languages, every episode, one term. The report is correct and tells a reviewer nothing about April. Compare what each view can answer:
| Question a reviewer asks | Current-state report | Full record chain |
|---|---|---|
| Was anything ever restricted? | No sign of it | Yes, Canada for one episode for 16 days |
| What caused it? | Not recorded | An underlying music license limited to the U.S. |
| Who chose the fix? | Not recorded | The head of business affairs, in a dated memo |
| Which cut is cleared for Canada? | Not stated | Version 2 only |
| Was the fix checked before release? | Unknown | QC passed May 2; buyer accepted May 9 |
The right-hand column is what makes the history worth anything outside the company. It is also the column most likely to be lost when a rights platform is replaced or a mailbox is purged, which is why the system map for these records matters before any migration.
Recognizing similar cases at a client
A consultant does not need documents to find cases like this. Ask the rights operations head three questions and write down only the answers:
- In the last few years, how often did a permitted territory, language or medium change between signature and delivery? A rough count is fine.
- For one such title, can you find the schedule before and after, the approval and the version that resolved it?
- Do those records sit in one system, or across the rights manager, a repository, the asset system and mailboxes?
If the answers suggest a long, traceable history, the next question is who can approve a discussion. The who-can-say-yes tree for clearance records covers that, and what rights-cleared data means explains why the company's operating records are a different matter from the films and tracks they describe.
The introduced company needs 50+ full-time employees at peak (contractors excluded), a 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. Partners sign the Channel Partner Agreement before submitting; the first valid introduction within the 90-day window is credited when the company submits a verified application. Buyer interest, the rights result, de-identification and any offer stay unknown until SourceX reviews the opportunity.
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 distributor client can trace even a handful of territory changes from problem to accepted delivery, register as a partner, check the company on who qualifies and read the program terms before introducing the rights operations head.