> 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/fix-a-forecast-or-capacity-conflict.md).

# Fix a forecast or capacity conflict

Resolve stale forecasts, insufficient supply, and reservation conflicts without changing a live promise by accident.

Use this guide when a forecast is stale, a Flight cannot cover its goal, a reservation has expired, or another operator changed the same supply. A forecast is planning evidence. A reservation protects supply. Neither one is earned delivery or invoice evidence.

Do not promise more capacity because the upper forecast range looks large. Use the current result, the correct unit, and the current reservation state.

## Identify the conflict

Open **Monetization > Campaigns > Campaign > Check and reserve capacity** and record:

* Campaign and Flight name.
* Flight version and schedule.
* Inventory package version.
* Billable unit and requested goal.
* Forecast calculation and expiry time.
* Available supply and expected delivery.
* Reservation status, quantity, and protection end.
* The message shown by the page.

Then choose the matching situation:

* The forecast is stale or expired.
* Available supply is lower than the Flight goal.
* Another operator changed the reservation.
* The reservation is partially released or expired.
* The plan needs a new commercial promise.

## Refresh a stale forecast

Recalculate when a Flight, Inventory package, targeting rule, frequency cap, reservation, or validity period changed.

1. Select **Refresh forecast** or **Recalculate forecast**.
2. Wait for the new result.
3. Check the calculation time and validity time.
4. Review available supply, expected delivery, fill, revenue, cost, and assumptions.
5. Select **Use this forecast** only after the result matches the current Flight version.

![The One Podigee Capacity page shows a selected video forecast with enough supply, expected delivery, revenue, cost, and a Reserve capacity action.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-293947828d3e1fd17ff90edb55d2b157c3becbcc%2Fdoc-monetization-038-forecast-selected.jpg?alt=media)

*Selection alone does not protect capacity. The reservation must succeed.*

Do not use an old selected forecast after a version or reservation change. The old result may no longer describe the available supply.

## Resolve insufficient supply

When available supply is lower than the requested goal:

1. Check the media type, markets, dates, targeting, frequency, pacing, and separation rules.
2. Check whether supply is already reserved by another Flight.
3. Check whether the Inventory package has current capacity and cost evidence.
4. Choose one authorized correction:
   * Reduce the Flight goal.
   * Widen a targeting or market rule that the buyer and publisher permit.
   * Select another eligible Inventory package.
   * Add another eligible show or media format.
   * Change the schedule or pacing rule.
5. Save the new Flight or Inventory version.
6. Calculate a new forecast and review the changed commercial result.

Do not remove consent, brand safety, publisher, or frequency rules only to make the number pass. Record the reason for a material change in the Campaign plan.

## Resolve a concurrent reservation change

If the reservation stops because capacity changed:

1. Leave the current reservation unchanged.
2. Refresh the Capacity page.
3. Read the current reservation quantity, version, and owner.
4. Recalculate the forecast for the current Flight and Inventory versions.
5. Select the new forecast.
6. Decide whether the buyer promise still fits the remaining supply.

![The One Podigee change reservation dialog shows the protected Flight, current quantity, state, expiry, change type, quantity, reason, effective time, and atomic safety notice.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-a6b4059a4a397bcacf9b46104e69372d14dba5b7%2Fdoc-monetization-038-change-reservation.jpg?alt=media)

*A change uses the current reservation version. A stale or conflicting request cannot overwrite a newer state.*

Do not submit the old form again. A new reservation or change must use the current version shown by the page.

## Resolve an expired reservation

An expired soft reservation no longer protects supply. An expired forecast is also not a valid basis for a new booking.

1. Confirm that the reservation is expired and not a guaranteed commitment.
2. Check the current Flight schedule and Inventory package.
3. Calculate a new forecast.
4. Select the new forecast.
5. Create a new reservation with the correct booking type.
6. Confirm the new protection end and version.

Refreshing a forecast does not extend an active reservation. A guaranteed commitment ends with its Flight schedule unless you release or replace it.

## Change or partially release protected capacity

Use **Change reservation** when the commercial plan needs less protected supply:

1. Open the current reservation.
2. Select **Change reservation**.
3. Choose **Release part of the capacity** or **Release all capacity**.
4. Enter a valid quantity for a partial release.
5. Select the reason and effective time.
6. Review the remaining protected quantity.
7. Select **Apply change**.
8. Confirm the new reservation state.

A partial release must be greater than zero and lower than the current quantity. Podigee keeps the current reservation until the change succeeds, then returns released supply to the available pool.

## Preserve or revise the commercial promise

After a conflict, compare the new forecast with the buyer commitment:

* If the goal still fits, reserve the current selected forecast.
* If the goal is lower, save a new Flight version and record the changed promise.
* If the schedule or Inventory changes, prepare a new proposal or amendment.
* If delivery cannot meet the promise, agree a make-good, renewal, or revised Campaign before you commit another reservation.

Use [Review and commit the commercial proposal](/documentation/grow-and-monetize/monetization/review-and-commit-the-commercial-proposal.md) for a changed buyer promise. Do not change a published Campaign version in place.

## Verify the result

After the correction:

1. Confirm the Flight and Inventory versions are current.
2. Confirm the forecast is selected and still valid.
3. Confirm the reservation quantity, type, state, and protection end.
4. Check that the available pool reflects any release or replacement.
5. Recheck Launch readiness when the Campaign is close to publication.
6. Confirm that no delivery or billing evidence was created by the planning correction.

The reservation protects supply, but it does not prove that an ad was delivered. Use [Monitor delivery, pacing, fill, and revenue](/documentation/grow-and-monetize/monetization/monitor-delivery-pacing-fill-and-revenue.md) after delivery starts.

## If the conflict remains

* **The forecast remains too low:** review supply, targeting, frequency, pacing, and competing reservations with the sales owner.
* **The reservation keeps changing:** open an operational issue and record the affected Flight and reservation versions.
* **A release is not reflected:** wait for the command result, then refresh. Do not release again from an old form.
* **The buyer promise cannot fit:** stop the commercial commitment and agree a corrected plan.
* **The numbers do not reconcile:** preserve the forecast and reservation receipts and use [Reconcile sources that do not agree](/documentation/grow-and-monetize/monetization/reconcile-sources-that-do-not-agree.md).

## Expected result

The Flight has a current forecast and a reservation that matches its actual commercial promise. Stale or conflicting requests do not overwrite newer state, released supply returns to the pool, and planning corrections do not create false delivery or money evidence.


---

# 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/fix-a-forecast-or-capacity-conflict.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.