# Scenario Toggle Behaviour

This article explains **scenario toggle behaviour** in Model Reef.

You will learn:

* What scenario toggling means when each scenario is a separate model.
* How to move between scenarios in practice.
* How to design dashboards so they compare cleanly across scenarios.

{% stepper %}
{% step %}

### Scenario toggling as model switching

In Model Reef:

* Each scenario is a separate model.
* Toggling scenarios means opening a different model that shares the same structure.
* Dashboards, charts and tables then show the data for that model only.

From the user's point of view you move between scenarios by moving between models.
{% endstep %}

{% step %}

### Making scenario switching feel consistent

To make scenario switching feel like a toggle rather than a rebuild:

* Clone dashboards and custom reports from the base model into each scenario model.
* Keep chart series, layouts and naming consistent.
* Only change underlying variables and drivers per scenario, not the report structures.

When you open Base, Upside or Downside models, you then see the same pages with different numbers.
{% endstep %}

{% step %}

### Scenario aware labelling

Because scenario context lives at model level:

* Make scenario names explicit, for example `Client - FY25 - Base`, `Client - FY25 - Downside`.
* Label exports and screenshots with the scenario name.
* In presentations, clearly state which scenario each chart or table is drawn from.

This prevents confusion when multiple scenario outputs circulate at once.
{% endstep %}

{% step %}

### Combining branch toggles and scenarios

You can combine two concepts:

* **Branch toggles** within a model to turn parts of the business on or off.
* **Scenario models** across the workspace to represent different futures.

For example, you might have a Base model with optional branches, plus a separate Stress model where assumptions are more conservative.
{% endstep %}

{% step %}

### Scenario toggling in external tools

If you export data into BI tools or static reports:

* Treat each scenario model as a separate data source or input file.
* Implement scenario filters or toggles in those tools based on file or scenario labels.

From Model Reef's point of view, it remains responsible for producing clean, comparable outputs for each scenario.
{% endstep %}
{% endstepper %}

***

## Related articles

* [Scenario Toggle Rules](/syntax/chart-and-table-syntax/scenario-toggle-rules.md)
* [Dropdown Field Behaviour](/syntax/how-input-fields-work/dropdown-field-behaviour.md)
* [Refresh Engine Behaviour](/help/xero-integration/refresh-engine-behaviour.md)
* [Build Scenario Aware Data Overrides](/how-tos/data-workflows-and-automation/build-scenario-aware-data-overrides.md)


---

# Agent Instructions: 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:

```
GET https://help.modelreef.io/syntax/scenario-syntax/scenario-toggle-behaviour.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.