This template belongs to the content rights clearance changes guide. Use it after a first conversation with the rights operations head, and write only what someone at the company will confirm.
Blank brief template
Copy the field names and answer each in a line or two. "Unknown" is acceptable.
| Field | What to write | Who usually knows |
|---|---|---|
| Subject line | One plain sentence naming the task and any access event | You, with the sponsor |
| Company | Sector, country, full-time headcount at peak | CEO or CFO |
| Catalog | Kind of titles and rough size, for example independent features and documentaries | Head of sales or rights |
| Task | Which changes are tracked between signature and delivery: where, how, in which language and for how long | Rights operations head |
| Records | Schedule versions, clearance memos with conditions, release version logs, QC reports, correspondence | Rights operations head |
| Systems | Rights manager, document repository, media asset system, shared mailboxes | Rights operations head with IT |
| Coverage and volume | Years each system holds; changes per year as an estimate with its source | Rights operations head |
| Access event | Any documented date: platform migration, read-only date, license end | Rights systems lead |
| Open question | The one completeness question nobody can answer yet | Rights operations head |
| Decision-maker | Head of business affairs or general counsel, with the sponsor named | Rights operations head |
| Not shared | A fixed line: no contracts, titles, licensor names, exports or logins | You |
Filling in the fields that cause trouble
Most fields are simple. Five need care.
- Records. Say whether superseded schedule versions are kept or overwritten. A system that stores each exclusion as its own dated line holds a different history from one that only shows the present.
- Systems. List every place a decision could be written down, including the two shared mailboxes. If the company records industry identifiers, say which; EIDR, for instance, gives each creative version of a title its own Edit ID, which makes release versions much easier to match.
- Coverage. Split it by system. Memo coverage often starts later than schedule coverage. Ask whether the repository kept earlier drafts of each memo or only the latest file.
- Catalog. Describe which rights the company holds, not which titles. The Copyright Office describes copyright as a bundle of rights that can be divided and owned separately, so "streaming and free TV rights for North America on most titles" tells a reviewer far more than a title list would.
- Open question. Make it testable. "Can each territory change be traced to its approval condition and the release version that satisfied it?" is a question SourceX can check. "Is the data good?" is not.
Completed example (Illustrative)
A fictional distributor, invented for this page. All figures are placeholders.
Subject: Clearance change history before our rights platform migration (Illustrative)
Company: independent distributor in the U.S., about 260 full-time staff at peak.
Catalog: roughly 1,100 titles, mostly features and documentaries, licensed to streaming services and broadcasters.
Task: tracking changes to permitted territories, media and terms between deal signature and delivery, and the versions cut to resolve them.
Records: rights schedule versions, clearance memos with approval conditions, release version logs, QC reports, licensor correspondence.
Systems: current rights manager (history conversion unconfirmed), document repository, media asset system, two shared mailboxes.
Coverage and volume: about nine years of schedules; memo coverage strongest in the last five; an estimated 40 to 70 clearance changes a year, per the rights operations head.
Access event: old platform read-only from the migration go-live date the company sets.
Open question: when a permitted territory changed before distribution, can each change be traced to its approval condition and the release version that satisfied it?
Decision-maker: head of business affairs, with general counsel; rights operations head as sponsor.
Not shared: no contracts, licensor names, titles, exports or logins.
That is enough for SourceX to judge fit: size clears the threshold, the systems and years are clear, there is a real access event and a checkable question. The system map shows the keys behind the open question.
Before you send it: a five-point check
- Every figure has a source at the company, or says unknown.
- No title, licensor, buyer or fee appears anywhere, including the subject line.
- The decision-maker is an officer or business affairs lead, not the person who runs the rights manager. The who-can-say-yes tree helps confirm it.
- The access event is a date the company gave you, or is left blank.
- The rights operations head has read it and agreed it can be forwarded.
Sending the brief
Let the rights operations head forward it to business affairs with a short covering note; the warm introduction brief helps with that note, and the client opportunity brief generator produces a similar summary. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. Sector context is on the media and production page.
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.
When the rights operations head has approved the brief and named the business affairs lead who will read it, register as a partner, confirm the company on who qualifies and read the program terms before it goes out.