> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudcapital.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Scenarios and budgets

> Keep another version of your forecast, and freeze one as a budget so you can see how actuals diverge from it.

A scenario is another version of your [forecast](https://docs.cloudcapital.co/forecasting/overview.md). You change the assumptions that drive it:

* Which [initiatives](https://docs.cloudcapital.co/forecasting/initiatives.md) are included, and the impact of those initiatives
* How individual parts of the forecast are [projected](https://docs.cloudcapital.co/forecasting/projection-types.md)
* Which [metrics](https://docs.cloudcapital.co/forecasting/business-metrics.md) are used to project growth
* What the values of those metrics are

A scenario keeps updating as new actuals arrive. A budget is that forecast frozen at a point in time. It stays as it was on the day you saved it, until you re-baseline it, so you can see how actuals diverge from the forecast as of its creation. Keep one for an enterprise agreement with a cloud provider, or for a department budget.

A budget covers one integration or a set of integrations, or one vendor or several. You might save one as your AWS Private Pricing Agreement, covering your AWS integrations, or as your AI spend budget, covering the vendors in that spend.

Open **Planning** under Forecast for the **Scenarios** and **Budgets** tabs. The same controls sit in the bar at the top of Forecast, Initiatives, and Business Metrics.

***

## Scenarios

Every organization has a **Base forecast**. That is the forecast configuration itself. Any other scenario records only how its assumptions differ from base.

The bar names the scenario on screen. Its color tells you what edits will do.

| What you are viewing | What edits do |
| - | - |
| **Base forecast** | Change the forecast itself |
| **Core forecast** | The plan Forecast, Initiatives, and Business Metrics open on. Marked in green |
| Any other scenario | A what-if, marked in amber. Edits stay out of the core forecast until you adopt it |

Creating, deleting, and renaming, and [cost allocation](https://docs.cloudcapital.co/get-started/map-cloud-resources.md), happen in the base forecast. Those are shared by every scenario. The control says to switch to Base when an action is only available there.

Each difference from base is a change you can switch off. A change that is off stays in the list and is left out of that scenario's forecast.

![The scenario bar on Forecast, naming the scenario on screen and what it is compared to](https://mintcdn.com/cloudcapital/BFnczmKqOuEZ1t_W/images/scenarios-and-budgets/scenario-bar.png?fit=max\&auto=format\&n=BFnczmKqOuEZ1t_W\&q=85\&s=2b74be85b01997bede98bbbee4943c35)

Open the scenario name to create one, rename it, or go to **Manage scenarios**. **Back to core** returns you to the core forecast. **View base** shows the base forecast while a scenario is the core forecast.

### Adopt

**Adopt** makes the scenario you are viewing the core forecast. Both scenarios keep their own changes, and adopting the previous one again switches back. Only an organization admin can adopt.

Adopting changes what Forecast, Initiatives, and Business Metrics open on. Commitment buying keeps reading the base forecast.

The base forecast and the core forecast cannot be archived. Restore an archived scenario from the archive icon on the **Scenarios** tab.

![The Scenarios tab with High Growth selected, listing how it differs from the base forecast](https://mintcdn.com/cloudcapital/BFnczmKqOuEZ1t_W/images/scenarios-and-budgets/scenarios.png?fit=max\&auto=format\&n=BFnczmKqOuEZ1t_W\&q=85\&s=2a3c709964fa39f2841258456a5ecb3b)

***

## Budgets

Save a budget from the scenario you are viewing. You name it, pick a period, and choose the integrations or vendors it covers. Later edits to the scenario do not move the budget, and actuals that arrive afterward are what you compare against it. An integration added later stays out of the budget until you re-baseline.

From the scenario bar, open **Compare to…** and choose **Save “…” as a budget…**. On the **Scenarios** tab, use **Save as budget**.

### Compare

**Compare to…** sets what the scenario on screen is measured against: another scenario, or a budget. Against a budget, the variance is your actuals and the current scenario versus the frozen forecast. Spending over the budget is marked over; spending under it is marked under. The Forecast chart draws the reference beside each period.

A budget only compares over the integrations it covers. Choosing one from **Compare to…** switches the page to those integrations. If the page is already showing a wider set, the bar offers **Show the budget's integrations** instead of a variance, and the comparison is drawn only after the page matches the budget.

On the **Budgets** tab, select a budget to see the comparison by cost layer and month. **Compared with** chooses the scenario measured against that budget. It starts as the core forecast.

![A budget compared with a scenario, by cost layer and month](https://mintcdn.com/cloudcapital/BFnczmKqOuEZ1t_W/images/scenarios-and-budgets/budget-comparison.png?fit=max\&auto=format\&n=BFnczmKqOuEZ1t_W\&q=85\&s=00bad80d61a1716143f76475e5ab6fcd)

### Re-baseline

**Re-baseline** freezes the same scenario again, as it stands today, over the same period and the same scope. The previous budget stays in the list as history. Re-baseline is how a budget takes in an integration added since you saved it, and drops one that is no longer enabled.

**Archive** removes a budget from the list and from **Compare to…**. Restore it from the archive icon on the **Budgets** tab.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.