> 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/scenario-syntax/creating-scenarios.md).

# Creating Scenarios

This article explains how to **create scenarios** in Model Reef.

You will learn:

* How scenarios are represented as separate models.
* How to create new scenarios from an existing base case.
* How to name and organise scenario models in your workspace.

## 1. Scenarios as separate models

In Model Reef:

* Every scenario is a full model with its own branches, variables, drivers and Data Library.
* There is no scenario dropdown inside a single model file.
* You create scenarios by duplicating models and changing assumptions.

This keeps each scenario isolated and easier to audit and reason about.

## 2. Creating a scenario from a base model

Typical workflow:

{% stepper %}
{% step %}

### Build or import a base model

Start with a model that represents your base case.
{% endstep %}

{% step %}

### Duplicate the base model

In the workspace, use the Duplicate / Copy model action on the base.
{% endstep %}

{% step %}

### Name the new model as a scenario

Give the new model a scenario-style name, for example:

* `Client - FY25 - Base`
* `Client - FY25 - Upside`
* `Client - FY25 - Downside`

The new model is now an independent scenario.
{% endstep %}
{% endstepper %}

## 3. What is copied when you create a scenario

When you duplicate a model, Model Reef copies:

* Branch structure.
* All variables and timing settings.
* All drivers and Data Library entries.
* All imports (Xero, QuickBooks, PDF, Excel, CSV, ticker data).
* All dashboards and custom reports.
* All valuation settings and assumptions.

The scenario starts identical to the base at the time of duplication, then evolves independently.

## 4. Organising scenarios in the workspace

To keep scenarios manageable:

* Group related scenarios in a single folder.
* Use clear naming such as `Base`, `Downside`, `Upside`, `Stress`.
* Include the planning year or project in the name, for example `FY25` or `Project Alpha`.
* Optionally keep a separate folder for archived or superseded scenarios.

Good organisation makes it obvious which model corresponds to which scenario.

## 5. When to create a new scenario

Create a separate scenario model when:

* You want materially different assumptions (growth, pricing, cost, capex, funding).
* You are preparing clearly defined cases for stakeholders.
* You want to test structural changes without touching the base model.
* You need distinct valuation assumptions, capital structures or risk cases.

Small tweaks can be handled within one model. Larger narrative changes merit a dedicated scenario.

## Related articles

* [Cloning Scenarios](/syntax/scenario-syntax/cloning-scenarios.md)
* [Branch Assignment](/syntax/variables-syntax/branch-assignment.md)
* [Current Liabilities](/help/financial-outputs-and-valuation/current-liabilities.md)
* [Scenarios & Planning](/how-tos/scenarios-and-planning.md)