Scenario Toggle Rules

This article explains scenario toggle rules in charts and tables, given that scenarios are implemented as separate models.

You will learn:

  • How scenario selection works in practice.

  • How charts and tables respond to scenario changes.

  • How to keep dashboards consistent across scenario models.

1

Scenario selection as model choice

Because each scenario is a separate model:

  • Selecting a scenario means opening that model.

  • Charts, tables and KPI cards then read from that model's data.

  • There is no in-model scenario drop down for a single file with multiple internal scenarios.

You instead maintain a set of scenario models with shared structure and use the workspace to navigate between them.

2

Keeping chart definitions aligned

To make scenario toggling feel like a true scenario switch:

  • Clone dashboards and reports from the base model into each scenario model.

  • Use identical series definitions, chart types and layouts.

  • Change only the underlying assumptions in each model.

This way, when you open Base, Upside or Downside models, the dashboards display comparable views with different numbers.

3

Scenario aware exports and packs

When exporting charts or reports:

  • You export from a specific scenario model.

  • Files should be labelled to indicate which scenario they represent.

In external tools or decks, you can then arrange views from different scenarios side by side.

4

Manual scenario comparison workflows

Scenario toggling can be mimicked by:

  • Opening multiple scenario models in separate browser windows or tabs.

  • Aligning dashboards to the same page and period settings.

  • Flipping between them to observe differences.

Model Reef focuses on consistent structure and calculation, leaving presentation level toggling to your workspace and reporting tools.

5

Best practice

For scenario toggling that is easy to manage:

  • Keep scenario model names clear, for example Client FY25 - Base, Client FY25 - Downside.

  • Maintain chart and table layouts via templates.

  • Use common naming and labelling on dashboards so users recognise where they are.

This makes it simple for collaborators to orient themselves when switching scenarios.

Last updated