These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Podcast Management
- Features
- Content and revisions
Content and revisions
Content and revisions across the linked podcast production record.
OverviewApproved Content×
Podcast Management · Content and revisions
New
Approved Content
Published waits for the editor
| Title | Status | Project | Owner | Published at | |
|---|---|---|---|---|---|
| Approved ci-107 | Approved | PRJ-7812 | 14 Oct | ||
| Approved ci-183 | Approved | PRJ-1808 | 15 Oct | ||
| Approved ci-933 | Approved | PRJ-3568 | 06 Oct | ||
| Approved ci-762 | Approved | PRJ-9119 | 13 Oct | ||
| Approved ci-552 | Approved | PRJ-4669 | 14 Oct |
6 of 6 records
Approved ci-107Content items · CI-83295
ApprovedProjectPRJ-7812
Published at14 Oct
What you can do
Keep the working decision visible
Each content item belongs to a project and a named owner. Its status follows editorial work from draft through editing and review. Attached files retain their version and upload date. The reviewer must examine the current revision, its linked content item and the relevant rights coverage before recording approval.
The content status says where editorial work stands; the file record says what was reviewed. Keep both linked to the project and the named person who approved the revision. The Editor later uses the approved content record when checking whether publication can be recorded.
How the work is organized
- Trace the owner. Keep the editorial status on the content item. Compare the file upload date and version with the material the Editor is actually reviewing; a prior approval belongs to its earlier file.
- Follow the links. Follow the content item back to its project and owner. Open each attached revision before selecting the current release candidate.
- Make the decision. Ask the Rights Manager to compare permitted uses and dates with the planned episode. The Editor records the reviewer on the selected file and approves the linked content only after that check.
What to agree during setup
Agree how the Editor identifies the latest file when several revisions are attached. Decide who returns a changed script to review and who checks whether the existing agreement still covers it. Rehearse a new upload after an earlier approval; the current file needs its own decision.
Check the handoff on an actual case
An editor receives revised episode copy after an earlier file was reviewed. They open the content item, compare the current file version with the earlier revision and ask the Rights Manager to check permitted use. The reviewer records approval against the current file. A later file upload calls for its own review; the earlier signoff cannot stand in for approval of new material.
The Editor hands the approved content item and its reviewed file to the Producer. The Producer can check the content status before scheduling the linked episode. If another revision arrives, the Editor revisits its rights coverage and records a fresh decision before publication.
The Editor can compare a revised attachment with the version that was previously approved. The upload date and reviewer make the sequence visible, while the linked content status shows the current editorial decision. Keep the selected revision clear during the handoff.
What your team sees
- Content In Review — Content items awaiting the Editor’s decision, with their project and owner.
- File Versions — Compare upload dates, versions and recorded reviewers for the linked content.
Follow the work through
What it keeps track of
Data model- 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.
- People
- Staff and contributors involved in podcast production and distribution. The User link resolves to the authenticated platform user.
- Rights agreements
- Rights and permitted uses agreed with a party for a specific content item.
Who uses it
Permissions- Editor
- , Rights Manager.
Set up Podcast Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.