1. Podcast Management
  2. Features
  3. Rights agreements
Feature · Rights agreements

Rights agreements

Rights agreements across the linked podcast production record.

OverviewActive Rights Coverage
Podcast Management · Rights agreements

Active Rights Coverage

Rights agreements

New
Party nameAllowed usesStarts atEnds atContentContract
Party 683AU-11321 Oct25 OctCI-2590CNT-539
Party 520AU-75627 Oct29 OctCI-6010CNT-737
Party 747AU-92826 Oct31 OctCI-4149CNT-359
Party 312AU-13715 Oct18 OctCI-5450CNT-890
Party 660AU-60817 Oct20 OctCI-7058CNT-708
6 of 6 records
Party 683Rights agreements · RA-33273
Allowed usesAU-113
Starts at21 Oct
Ends at25 Oct
ContentCI-2590
ContractCNT-539
Example screen with sample data

What you can do

Keep the working decision visible

Rights agreements identify the party, permitted uses, effective dates, contract attachment and content item they cover. The Rights Manager checks the agreement against the specific material under review. Editors need that result before approving a file revision. The contract and dates give the team a concrete basis for deciding whether a planned use is covered.

Keep an agreement attached to the content it covers. A changed contract can be attached to its agreement record for review. The Editor can then read the use terms in the same chain as the content and episode.

How the work is organized

  • Trace the owner. Link each agreement to the content it covers. Read the party, permitted uses, effective dates and contract before deciding whether the planned episode use is covered.
  • Follow the links. The Rights Manager checks the agreement against the current material and planned release time. The Editor uses that check when reviewing a file revision.
  • Make the decision. Keep the contract on the agreement and check its dates when a publication plan changes. A linked agreement alone does not establish that every use or date is covered.

What to agree during setup

Agree which party grants each use and how the team records the permitted use in the agreement. Decide who checks a changed release date against the agreement period. Rehearse an interview segment whose planned use falls outside the recorded dates.

Check the handoff on an actual case

A guest agrees to use an interview segment in the podcast feed during a defined period. The Rights Manager links the agreement to the content item and records the permitted use and dates. When an editor reviews a new file version, they compare its intended use with the agreement. If the release timing falls outside the period, the team resolves the agreement before approving the revision.

The Rights Manager tells the Editor which agreement covers the current revision and intended use. The Editor checks that result before recording approval on the file. If the terms change, update the agreement and repeat the review for the affected content.

If a guest grants use for the podcast feed but the team plans another use, the Rights Manager reads the permitted-use text before the Editor approves the file. The agreement dates must also cover the intended release. Keep the contract accessible from the content item.

What your team sees

  • Active Rights Coverage — Inspect agreements with dates that cover the planned use.
  • Content In Review — Find content awaiting review alongside its linked agreement.

What it keeps track of

Data model
Rights agreements
Rights and permitted uses agreed with a party for a specific content item.
Content items
Individual pieces of content produced within a project, from draft through publication.
Content files
Versioned files attached to a content item, each requiring its own review and approval.

Who uses it

Permissions

Set up Podcast Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started