> 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/amend-campaign-terms-or-schedule.md).

# Amend Campaign terms or schedule

Change a committed Campaign Flight, review the exact business and delivery impact, and keep the current live version safe until the amended Campaign is ready and published.

Use an amendment when a committed Campaign must change. You can change the schedule, delivery goal, rate, budget, audience, pacing, frequency limit, priority, or other Flight terms in the Podigee Audio Video Ad Server.

An amendment creates a new Flight version. It does not edit the earlier version and it does not change live delivery when you save or commit it. The current publication stays active until the amended Campaign passes its readiness checks and is published.

## Prerequisites

Before you start, make sure that you have these items:

* Permission to edit and commit Campaign Flights in Monetization.
* A committed Campaign with at least one Flight.
* The confirmed change from the buyer or commercial owner.
* A short reason for the change.
* A current workspace review rule.

## Create the amendment

1. Open **Monetization**.
2. Select **Campaigns**.
3. Open the committed Campaign.
4. Find the Flight that must change.
5. Select **Adjust flight**.
6. Change only the values that must be different.
7. Enter the business reason for the change.
8. Select **Save new flight version**.

The Campaign page now shows the Flight as proposed. Open **Review amendment** to continue.

## Review what changed

The amendment page shows only the values that differ from the earlier version. Check the **Before** and **Proposed** columns for every changed value.

![The One Podigee amendment page shows a proposed end date change, the protected live delivery notice, a fresh capacity forecast, and the reservation impact.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-77b29bc4d8693962a16b8f962cc6c28a97c6aefe%2Fdoc-monetization-040-amendment-impact-review.jpg?alt=media)

*Compare the earlier value with the proposed value before you continue.*

Check these areas:

| Area     | What to check                                                                         |
| -------- | ------------------------------------------------------------------------------------- |
| Terms    | The goal, budget, rate, price model, and guarantee match the updated agreement.       |
| Schedule | The start and end dates match the buyer commitment and the Campaign plan.             |
| Audience | The markets, content categories, and other targeting values are correct.              |
| Delivery | The inventory, media, measurement, pacing, priority, and frequency limit are correct. |
| Reason   | The reason explains why the new version is necessary.                                 |

Select **Adjust again** when a proposed value is wrong. Saving again creates another proposed version. It does not change the earlier committed record.

## Calculate a fresh forecast

A forecast from the earlier version does not cover the amendment. Select **Calculate forecast**. When a forecast is already present but is no longer current, select **Refresh forecast**.

Check these values:

* **Requested** is the delivery goal for the proposed Flight.
* **Available** is the capacity that the current plan can use.
* **Expected range** shows the delivery range for the current inputs.
* **Valid until** shows when you must refresh the forecast.

Do not use an expired forecast to make a commercial decision. Correct the schedule, audience, goal, or inventory when the forecast shows a shortfall.

## Check reservation impact

A reservation belongs to one exact Flight version. It never moves to a changed version without an explicit action.

* The current live version keeps its existing reservation.
* The proposed version needs its own reservation after the amendment is committed.
* A prior reservation does not prove that the changed dates or terms have capacity.

This rule prevents a schedule or targeting change from consuming capacity that was reserved for a different promise.

## Select the review rule and effective time

Your workspace controls how the amendment is reviewed.

| Review rule        | What happens                                                                        |
| ------------------ | ----------------------------------------------------------------------------------- |
| Solo confirmation  | You confirm and apply the exact amendment yourself.                                 |
| Optional review    | You can ask a teammate for advice, but an open review does not block the amendment. |
| Independent review | A different authorized person must approve the exact amendment.                     |

A one-person operation can use Solo confirmation. A team can require an independent reviewer for material commercial changes.

Set **Effective time** to the time when the committed amendment may take effect. This value becomes part of an independent review request. Create a new amendment when the approved effective time must change.

![The One Podigee amendment page shows the fresh capacity forecast, reservation impact, Solo confirmation rule, effective time, Confirm and apply action, and safe restoration action.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-4c5be80df65cb418fe8a891946cf5beed4709b62%2Fdoc-monetization-040-amendment-forecast.jpg?alt=media)

*Confirm the forecast, review rule, and effective time for the same proposed version.*

## Apply the amendment yourself

Use this flow when the workspace uses Solo confirmation.

1. Check the changed values.
2. Check the fresh forecast and reservation impact.
3. Set the effective time.
4. Select **Confirm and apply**.
5. Return to the Campaign.
6. Complete any new reservation, creative, readiness, or publication action.

The Flight amendment is committed. Live delivery still uses the current publication until the amended Campaign is ready and published.

## Complete an independent review

Use this flow when the workspace requires another reviewer.

1. Check the changed values, forecast, reservation impact, and effective time.
2. Select **Send for review**.
3. Ask a different authorized person to open the request in **Approvals**.
4. The reviewer checks the exact amendment, forecast, reservation effect, and effective time.
5. The reviewer approves the request or asks for changes.
6. Return to the amendment after approval.
7. Select **Apply approved amendment**.

Changing the amendment or its effective time invalidates the earlier review. Send the new exact version through the review rule again.

## Restore the earlier values

Select **Prepare restoration** when the proposal should return to the earlier values. Restoration creates another proposed version from the previous record. It does not delete the amendment or rewrite history.

Review and publish the restoration like any other amendment. Until then, live delivery remains on the current published version.

## Solve common problems

| Problem                                 | Cause                                                                                    | Safe action                                                              |
| --------------------------------------- | ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| The amendment action is not available   | You do not have edit permission, or the Campaign is not in a state that allows a change. | Ask an administrator for the correct role or resolve the Campaign state. |
| The forecast action is not available    | You do not have forecast permission.                                                     | Ask an administrator for permission to calculate forecasts.              |
| The forecast is missing or expired      | The proposed version has no current forecast.                                            | Select **Calculate forecast** or **Refresh forecast**.                   |
| The forecast shows a shortfall          | The proposed promise is larger than the available capacity.                              | Change the plan or resolve capacity before publication.                  |
| A prior reservation does not apply      | The reservation belongs to the earlier Flight version.                                   | Commit the amendment, then reserve capacity for the exact new version.   |
| The amendment is waiting for review     | The workspace requires an independent reviewer.                                          | Ask a different authorized person to decide the exact request.           |
| The earlier approval does not apply     | A material value or effective time changed.                                              | Send the current exact version through the review rule again.            |
| The amendment is committed but not live | Readiness or publication work is still incomplete.                                       | Complete the current blockers and publish the amended Campaign.          |

## Expected result

The changed Flight exists as a new committed version with a current forecast and the required review decision. The earlier version remains in history. Live delivery changes only after the amended Campaign has the required capacity, creative, readiness, and publication authority.

Next, create a make-good or renewal Campaign when a completed delivery promise needs follow-up work.


---

# 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/amend-campaign-terms-or-schedule.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.