> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/grow-and-monetize/monetization/manage-back-catalog-and-future-episode-supply.md).

# Manage back-catalog and future-episode supply

Prepare published, back-catalog, and scheduled episodes for monetization while keeping media, ad-break, inventory, and forecast state current.

The Podigee Audio Video Ad Server can use eligible episodes from the current catalog of a show. Each episode must still have current media, publisher authority, and approved ad breaks before it can become sellable supply.

Use this task to prepare published episodes, add older episodes to supply, or prepare scheduled episodes before they become public. It also explains what to check after episode content changes.

## Before you start

You need:

* Access to the show in **Podcast** and its workspace in **Monetization**.
* Permission to edit episodes and manage Inventory.
* A published Inventory package that uses the current catalog of the show.
* Delivery-ready audio or video for each episode that you want to monetize.
* Publisher authority and applicable demand policies for the show.
* Approved ad breaks for each eligible media source.

## 1. Review the episode catalog

1. Go to **Podcast > Episodes**.
2. Use search and the status filters to find the episodes that you want to prepare.
3. Use the tile view for a visual review or the list view for a larger catalog.
4. Check the status of each episode.

The main states have these meanings:

* **Published:** The episode is public. It can become sellable when its media, authority, and ad breaks are ready.
* **Scheduled:** The episode has a future publication time. You can prepare it, but Podigee does not treat it as public supply before that time.
* **Delivery needs attention:** The episode is public, but one or more delivery requirements are missing or no longer current.
* **Draft:** The episode is not public inventory.

![The episode catalog shows a scheduled episode, a published episode, and a back-catalog episode that needs delivery attention.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-0eb17e88a79b5c04054673a2f246d2b4d9030f6b%2Fdoc-monetization-028-episode-supply-catalog.jpg?alt=media)

*Use search and status filters to review current, scheduled, and back-catalog episodes together.*

{% hint style="info" %}
A published episode does not enter monetized delivery just because it exists in the feed. Podigee also checks its current media, publisher authority, policies, and approved ad breaks.
{% endhint %}

## 2. Check a current published episode

1. Open the episode.
2. Preview its current audio and video.
3. Find **Ad breaks and monetization**.
4. Check the available media formats and the total number of breaks.
5. Check how many breaks are ready for delivery, need review, or need a refresh.
6. Select **Manage ad breaks** when a placement needs work.

![A published episode has playable audio and video, three ad breaks, and all three breaks ready for delivery.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-73e07e377712534a25d3af0729cb78d976c86d73%2Fdoc-monetization-028-current-episode-readiness.jpg?alt=media)

*Confirm the media and ad-break state before you rely on an episode as sellable supply.*

The episode is ready for its next serving release when the required media is current and each applicable break is ready. Campaign eligibility, targeting, capacity, and pacing still determine whether an ad is selected for a listener.

## 3. Prepare a scheduled episode

You can complete most preparation before the episode becomes public.

1. Open the scheduled episode.
2. Add its final audio or video recording.
3. Wait until media processing is complete.
4. Select **Review monetization setup**.
5. Prepare and review the episode's ad breaks.
6. Confirm its exact publication date and time.
7. Return after processing or editorial changes and check that every required item is still ready.

![A scheduled episode shows that its recording is not ready and offers an action to review its monetization setup.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-e730dd0d0e54d0cc552d8e8c23e9336809b0b272%2Fdoc-monetization-028-scheduled-episode-readiness.jpg?alt=media)

*Prepare media and ad breaks before publication. The episode does not become public supply early.*

Podigee preserves the exact future publication time. A scheduled episode does not enter public delivery before that boundary, even when its media and ad breaks are ready.

## 4. Add a back-catalog episode to supply

Older published episodes can become valuable supply, but they need the same current checks as a new episode.

1. Filter the episode catalog by **Delivery needs attention**.
2. Open an episode and add or restore its current source media.
3. Wait for audio or video processing to finish.
4. Confirm that Podigee has publisher authority for the episode and show.
5. Prepare the current ad-break placements.
6. Complete the configured review step for those exact placements.
7. Return to the episode and confirm that no break needs review or a refresh.
8. Check the matching Inventory package and calculate a current forecast before you reserve more capacity.

Do not assume that older published episodes already run ads. An episode without a current delivery state, ready media, or approved breaks stays out of eligible monetized delivery.

## 5. Recheck supply after content changes

Podigee treats changed episode content as a new exact version. This rule prevents an old approval from being applied to media that a reviewer did not inspect.

After you change episode metadata, chapters, audio, or video:

1. Open the episode and preview the current media.
2. Check whether any break shows **Needs refresh**.
3. Rebind affected placements to the current media.
4. Check the position, capacity, and fallback behavior again.
5. Review the new exact placements under the workspace review rule.
6. Check the Inventory package and its forecast again.

The public episode and its feed enclosure keep a stable address during editorial updates. Behind that address, Podigee prepares the new exact content and media version. Active listener delivery stays pinned to one verified version until the replacement is ready, so one response cannot mix old and new episode content.

## 6. Understand the Inventory and forecast effect

An Inventory package that follows the current show catalog uses the latest eligible source for each episode. It excludes a source that is not ready, has lost authority, or has been replaced by a newer current source.

When the eligible source set or Inventory package changes:

* A previous forecast can become stale.
* Existing booked Flight terms do not change automatically.
* Podigee does not silently reserve more or less capacity.
* You must calculate a new forecast before you make a new reservation or adjust delivery.

This keeps editorial changes separate from commercial commitments. It also makes a capacity change visible to the operator before it affects a Campaign.

## 7. Remove an episode from public supply

When you unpublish an episode or remove the publisher's authority, Podigee removes it from current public supply. Do not assume that an earlier Campaign can continue to serve against that episode.

Before you remove it:

1. Check active Campaigns and Flights that use the related Inventory package.
2. Check whether the change makes their forecast stale or reduces available capacity.
3. Adjust the commercial plan when required.
4. Unpublish the episode or revoke its authority.
5. Confirm that it no longer appears as eligible current supply.

## If an episode does not become ready

* **Recording preview is not ready:** Add the required media or wait for processing to finish.
* **Delivery needs attention remains:** Check current media, publisher authority, policies, and ad breaks. Correct each missing item.
* **A break needs refresh:** Rebind it to the current media and review the exact placement again.
* **A scheduled episode appears too early:** Confirm its publication date, time, and time zone. Do not publish it manually unless you intend to make it public now.
* **A back-catalog episode has no playable source:** Restore or replace the source before you prepare monetization.
* **The forecast is stale:** Calculate a new forecast. Do not rely on the earlier capacity result.
* **A current source disappeared from supply:** Check whether its media is ready, its authority is valid, and a newer source revision replaced it.

## Result

Current published episodes have ready media and approved ad breaks, scheduled episodes are prepared without becoming public early, and selected back-catalog episodes can enter eligible supply. Content changes remain tied to exact versions, while Campaign reservations and forecasts stay under operator control.

Next, learn how episode media, chapters, intros, outros, trailers, ad breaks, and feed delivery work together.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/grow-and-monetize/monetization/manage-back-catalog-and-future-episode-supply.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.