Cloning Scenarios

This article explains how to clone scenarios in Model Reef.

You will learn:

• How to duplicate an existing model to create a new scenario.

• What is copied during cloning.

• How to use cloning for both scenario design and version control.

Cloning is the main way to create new scenarios without rebuilding structure or re-importing data.

The clone is a complete copy of the original at that moment in time. After cloning, the original and the clone no longer interact.

---

Cloning a model to create a scenario

To clone a scenario or base model, follow these steps:

1

Locate the model

In the workspace, locate the model that represents your current case.

2

Duplicate / Copy model

Use the Duplicate / Copy model function.

3

Name the new model

Name the new model to reflect its role, for example:

• Client - FY25 - Base

• Client - FY25 - Upside

• Client - FY25 - Equity raise case

---

What cloning copies

Cloning copies:

• All branches and their hierarchy

• All variables and their timing and formula settings

• All drivers and Data Library entries

• All imported data (historicals and fundamentals)

• All dashboards, charts and custom reports

• All valuation settings and assumptions

---

Using clones for scenario exploration

You can use clones to explore:

• Alternative growth, cost or capex paths

• Different funding or capital structure options

• Transaction and project cases versus base business

• Stress, downside or upside cases

Each clone can be modified independently while the base remains intact for reference.

---

Cloning for version control

Cloning can act as a simple versioning strategy:

• Clone before major structural or assumption changes

• Keep previous versions in an archive or version folder

• Use names such as Model v1.0, Model v1.1, Model v2.0

This gives you a clear trail of how the model has evolved.

---

Clean up and governance

Over time you may accumulate many clones. To keep things tidy:

• Archive models that are no longer active

• Use folders to group scenarios by client, project or planning cycle

• Periodically review and remove obsolete experimental clones

Clear governance keeps scenario sets understandable for everyone using the workspace.

---

Related articles

• Creating Scenarios

• Branch Selector

• Data Library Mapping

• Scenarios & Planning