> 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/run-launch-readiness.md).

# Run Launch readiness

Read the Campaign launch checklist, follow the next safe action, and confirm that every required area is current before publication.

Launch readiness brings the commercial, Inventory, Creative, delivery, and review state of one Campaign together. Use it to find the next blocker and confirm that the exact setup can continue to publication.

Launch readiness does not replace the work in each area. It shows whether that work is complete, current, and connected to the same Campaign setup.

## Before you start

Complete the Campaign plan as far as possible. You should have current commercial terms, Flights, Inventory, Creative assignments, delivery settings, and required episode ad breaks.

If you changed the Campaign after its last test, prepare and check the exact setup again before you expect Launch readiness to pass.

## Open Launch readiness

1. Open **Monetization**.
2. Open **Campaigns**.
3. Select the Campaign.
4. Open **Launch readiness**.

The page shows six checklist areas and one **Next action**. Read the checklist from top to bottom, then use the displayed action to resolve the first blocking dependency.

## Read the launch checklist

| Area                      | Ready means                                                                                      | Common blocker                                                                                            |
| ------------------------- | ------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------- |
| Commercial approval       | The current Campaign terms and delivery goals have the required approval.                        | Terms changed or the required commercial review is incomplete.                                            |
| Inventory and reservation | Every Flight has deliverable Inventory and enough reserved capacity.                             | A Flight has no published Inventory package, or capacity is not reserved.                                 |
| Creative coverage         | Every Flight has an eligible audio or video Creative for its complete delivery period and scope. | A Creative is missing, not prepared, outside its rights, or does not cover the required format or market. |
| Campaign setup            | Podigee prepared one exact setup from the current Campaign and all connected records.            | A Campaign, Flight, Inventory, Creative, ad break, policy, or delivery input changed.                     |
| Launch checks             | The exact prepared setup passed the current delivery checks.                                     | The checks failed, were not run, or no longer match the current setup.                                    |
| Publication review        | The configured review rule is satisfied or can be confirmed during publication.                  | An independent review is required and has not been approved.                                              |

Every required area must be ready. A passed item below a blocked item does not override the blocker.

## Follow the next safe action

The **Next action** card names one concrete repair path. It can link you to commercial approval, capacity, Flight Inventory, Creative coverage, episode ad breaks, integration checks, or publication review.

Complete that action, then return to Launch readiness. The next blocker appears only after the earlier dependency is complete. This prevents several unrelated warnings from competing for your attention.

![The current One Podigee Launch readiness page shows a blocked Inventory connection, a clear repair action, and an earlier passed setup that is no longer valid for publication.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-bb208a14199e200f3bef18aadaa9d1f5a1dd235f%2Fdoc-monetization-052-inventory-blocker.jpg?alt=media)

*A passed earlier setup cannot approve the changed Campaign while current Inventory is blocked.*

In this example, commercial approval and Creative coverage are ready. The current Campaign is still blocked because one Flight is not connected to deliverable Inventory. The operator must select **Review Flight Inventory**, choose published Inventory for the podcast, and run the Campaign checks again.

## Do not use a stale result

The **Prepared Campaign setup** section keeps earlier results for traceability. It can show that an earlier setup passed, but that result is not current proof after a connected record changes.

Use these rules:

* **Passed** is valid only when it belongs to the current exact setup and current check suite.
* **Refresh needed** means that a connected record changed after the check.
* **Blocked** means that the current exact setup failed at least one required check.
* **Not run** means that no result exists for the current setup.

Do not publish based on an earlier setup reference or a passed result shown only in the traceability section.

## Check destination support

Launch readiness includes the delivery methods used by the Campaign. A Podigee-controlled audio or video path must have its required media, ad breaks, policies, and delivery setup. A connected destination must also have current evidence for every capability that the Campaign uses.

If a provider controls final delivery, Launch readiness confirms Podigee's setup and connection evidence. It does not turn a local check into production certification by that provider.

## Check the publication review

The review state follows your workspace rule:

* **Confirm when publishing:** The person who publishes confirms the exact setup. This works for a solo operator.
* **Optional:** You can publish without a separate review or ask a teammate for advice.
* **Required:** A different authorized teammate must approve the exact checked setup.
* **Approved:** The required review is complete for the exact setup.

If the Campaign changes after approval, the review might no longer apply. Follow the new review state shown on the page.

## Confirm readiness before publication

Continue only when:

* Commercial approval is ready.
* Inventory and reservation are ready.
* Creative coverage is ready.
* Campaign setup is ready.
* Launch checks passed for the current exact setup.
* Publication review is satisfied or can be confirmed during publication.

A ready checklist does not publish the Campaign. Publication is a separate action with its own confirmation and delivery safeguards.

## Expected result

Launch readiness shows no unresolved blocker for the current exact Campaign setup. Each checklist area is ready, the latest launch checks are current, and the publication review state is clear. The Campaign can continue to the separate publication action without changing live ads yet.


---

# 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/run-launch-readiness.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.
