1. Podcast Management
  2. Features
  3. Distribution receipts
Feature · Distribution receipts

Distribution receipts

Distribution receipts across the linked podcast production record.

OverviewReceipts Awaiting Confirmation
Podcast Management · Distribution receipts

Receipts Awaiting Confirmation

Confirmed waits for the producer

New
PlatformExternal IDPublished atStatusEpisode
PLT-773EI-93725 OctPendingEPS-8444
PLT-417EI-41716 OctPendingEPS-5972
PLT-929EI-75519 OctPendingEPS-2089
PLT-242EI-61913 OctPendingEPS-6460
PLT-955EI-38008 OctPendingEPS-6990
6 of 6 records
PLT-773Distribution receipts · DR-69217
Pending
External IDEI-937
Published at25 Oct
EpisodeEPS-8444
Example screen with sample data

What you can do

Keep the working decision visible

A distribution receipt belongs to one episode and records the platform, external identifier, acknowledged publish time and confirmation status. The producer captures the platform evidence and checks the linked episode and content item before accepting it. Confirmed receipts give the Editor the delivery evidence for the publication decision.

Keep failed evidence visible for follow-up, and keep each receipt linked to the actual episode. The receipt is a platform record, while the episode and content item carry separate publication states. Reading all three prevents a pending receipt from being mistaken for a completed release.

How the work is organized

  • Trace the owner. Keep each platform and external identifier on the receipt for the correct episode. A pending receipt records work to check; confirmation follows the provider acknowledgment and its publish time.
  • Follow the links. Follow the receipt to its episode and the episode to its operational content item. Check those links before accepting platform evidence.
  • Make the decision. Keep a failed receipt visible so the Producer can investigate it. The Editor checks confirmed receipts when deciding whether the linked content can be published.

What to agree during setup

Agree which provider acknowledgment and timestamp the Producer will use. Decide how to identify an existing receipt when the same platform sends an event again. Test a delayed acknowledgment and a repeated platform and external identifier against the same episode.

Check the handoff on an actual case

A platform returns an external identifier for a scheduled interview episode. The producer records a pending receipt, checks the provider acknowledgment and confirms it once the external identifier and acknowledged time are available. If another receipt repeats the same platform and identifier, the team resolves the duplicate rather than counting it as another delivery. The Editor then reviews the confirmed evidence with the approved content item.

The Producer gives the Editor the confirmed receipts for the scheduled episode. The Editor checks the linked content approval and the platform evidence before recording publication. A pending or failed receipt stays open for investigation; its status does not prove delivery.

For an episode sent to more than one platform, inspect each platform receipt independently. One confirmed acknowledgment cannot settle another pending receipt. The Producer checks the external identifier on each record before the Editor considers the episode ready for publication.

What your team sees

  • Receipts Awaiting Confirmation — Find pending platform evidence by episode and external identifier.
  • Confirmed Receipts — Check acknowledged publish dates for confirmed platform records.

What it keeps track of

Data model
Distribution receipts
Per-platform distribution evidence captured for a published episode.
Episodes
Podcast episodes linked to their operational content record, with series, episode number, audio and publish schedule.
Content items
Individual pieces of content produced within a project, from draft through publication.

Who uses it

Permissions
Producer
, Editor.

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