> For the complete documentation index, see [llms.txt](https://help.modelreef.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.modelreef.io/syntax/understanding-the-interface/scenario-selector.md).

# Scenario Selector

This article explains the **Scenario Selector** pattern in Model Reef.

You will learn:

* How scenarios are represented as separate models.
* How the interface helps you move between them.
* How scenario context affects dashboards and reports.

In Model Reef, each scenario is its own model. The Scenario Selector is a navigation aid that helps you switch quickly between those models while keeping a consistent view.

***

## Scenarios as separate models

Unlike some tools, Model Reef does not store scenarios as states inside a single model. Instead:

* Each scenario is a standalone model with its own branches, variables and Data Library.
* For example you might have `Client X - Group Forecast - Base`, `Client X - Group Forecast - Downside`, `Client X - Group Forecast - Upside`.
* These models are related by naming and structure, not by internal links.

The Scenario Selector relies on these naming patterns and relationships.

***

## Where you see the Scenario Selector pattern

In some views, especially dashboards and reporting, you may see a scenario selector or quick switcher that lets you:

* Jump from one scenario model to another while keeping the same high level dashboard or report open.
* Compare common layouts across Base, Downside and Upside builds.

Behind the scenes, switching scenario is really switching to a different model that shares the same layout or template.

***

## What changes when you switch scenario

When you move from one scenario model to another:

* All calculations are taken from the new model.
* P\&L, Balance Sheet, Cashflow and Cash Waterfall change to reflect that model's assumptions.
* Dashboard charts and KPIs update.
* Valuation outputs such as NPV, IRR and money multiple update.

The structure of the report or dashboard stays constant. The underlying data source (the model) changes.

***

## Working with scenarios

{% stepper %}
{% step %}

### Create a scenario model

Duplicate a base model to create a new scenario model.
{% endstep %}

{% step %}

### Update assumptions

Change assumptions in the new model (growth, margins, capex, financing and so on).
{% endstep %}

{% step %}

### Switch between scenarios

Use the Scenario Selector pattern in dashboards or reports to move between scenarios quickly.
{% endstep %}

{% step %}

### Review and discuss

Discuss differences in outputs with stakeholders.

Because scenarios are separate models, changes in one do not affect the others.
{% endstep %}
{% endstepper %}

***

## Related articles

* [Viewing Scenario Differences](/syntax/scenario-syntax/viewing-scenario-differences.md)
* [Selecting Series for Charts](/syntax/chart-and-table-syntax/selecting-series-for-charts.md)
* [Model Periodicity](/help/drivers-variables-and-timing/model-periodicity.md)
* [Build a Discount Rate Scenario Model](/how-tos/valuation/build-a-discount-rate-scenario-model.md)