> For the complete documentation index, see [llms.txt](https://docs.fabricplan.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fabricplan.com/planning-sheets/how-tos/measure-and-row-based-planning/row-based-modeling/perform-scenario-analysis-in-row-model.md). # Perform scenario analysis in row model Use scenarios with a row model to evaluate different assumptions without changing the base plan or forecast. A scenario can contain a single driver or multiple drivers simulated at the same time. Use the **tree layout** to visualize how simulated driver values flow through the row model and affect dependent rows. Each scenario provides a separate simulation layer, so changes in one scenario don't affect the base plan, forecast, or other scenarios. In this example, use ***Forecast*** as the baseline series and ***PY Actuals*** as the comparison series to generate and assess different forecast assumptions against the previous year's actuals. You'll create three scenarios in the **tree layout** to evaluate upside, downside, and balanced business conditions. Then, you simulate different combinations of drivers in each scenario and compare their potential impact on the forecast. ### Prerequisites Before you create a scenario, make sure that: * You have a planning sheet with a [configured row model](/planning-sheets/how-tos/measure-and-row-based-planning/row-based-modeling/create-a-row-model.md). * Ensure that you have [created a forecast](/planning-sheets/how-tos/measure-and-row-based-planning/row-based-modeling/create-forecasts-using-row-model.md) or have another series available to use as the **baseline** for scenario analysis. * The row model includes the required measures and dimensions for the scenario. ### Create scenarios using tree layout In this section, you create and configure the tree layout to structure your data and simulate different scenarios by adjusting driver values. #### Enable tree layout 1. In the planning sheet, go to **Layout** > **Tree**.

2. Select the **Baseline** and **Comparison** series. To create three forecasting scenarios for 2026, select *Forecast* as the baseline series and *PY Actuals* as the comparison series to compare against 2025 actuals.

3. Select **Save**. The tree view appears as shown in the following image. This is the base scenario.

The tree layout aggregates values across the entire period available in the planning sheet. Use the **time period selector** to select the year or period you want to include in the tree.

#### Create a scenario 1. To create a scenario, select **Base** > **Create New Scenario**.

2. Enter a name for the scenario and choose the series to simulate. To simulate forecast values, select *Forecast* and then select **Create**.

### Create the best-case scenario Create a scenario by following the steps above. Name the scenario *Best Case* and configure the driver values to simulate favorable business conditions. 1. Increase the **Revenue** values for the forecast by using the slider or by entering the simulation percentage (e.g., 10%) in the text box. 2. Similarly, simulate a decrease in the **Purchase** values. 3. Review the resulting changes to **Profit**.

The row model recalculates dependent values as you change the drivers, so you can see the cascading impact of the assumptions in the tree layout. ### Create the worst-case scenario Create another scenario named *Worst Case* to evaluate unfavorable business conditions.

1. Decrease the **Revenue** values. 2. Increase one or more **Expense** drivers such as **Purchase** and **Salaries**. 3. Review how the changes affect profit.

The worst-case scenario remains separate from the best-case scenario and the base plan. ### Create a balanced-case scenario Create a *Balanced Case* scenario by applying moderate changes to **Revenue** and **Expense** drivers to review their impact on the profit.

### Analyze simulation impact In the tree layout, select a node to analyze the impact of the simulation on that node. Use the available **Graph** and **Table** views to review the **trend**, **simulation** **details**, **simulation impact**, **variance**, and **dependents** for the selected node.

### Compare scenarios After creating the scenarios, compare their outcomes to understand how the different assumptions affect the forecast. 1. Select **Compare scenario**.

2. In the **Scenario Comparison** screen, select the scenarios that you want to compare and analyze. You can select a scenario and compare it against one or more scenarios. Consider a scenario that focuses on cost optimization, and you name it *Cost Optimized.* The following image compares the *Cost Optimized* scenario with the *Balanced Case* and *Best Case* scenarios.

3. Review the differences in drivers and KPIs across the selected periods. The comparison displays the values for the selected scenarios and the variance between them. Positive and negative variances help you identify how the assumptions change the forecast outcome. ### Copy to base scenario After evaluating different scenarios, you can copy the assumptions and simulations from a specific scenario to the **base scenario**. This makes the selected scenario the new baseline, so you continue to simulate additional changes from it. To set a simulated scenario as the new baseline, select the vertical ellipsis next to the scenario name, and then select **Copy to Base**. This copies the selected scenario's simulations to the base scenario.

### How scenario analysis helps in row model Scenario analysis in the row model makes you understand how different assumptions influence overall business outcomes. By simulating driver changes and tracing their impact through the row hierarchy, you can evaluate potential outcomes, compare alternatives, and make informed planning decisions without affecting the underlying plan. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.fabricplan.com/planning-sheets/how-tos/measure-and-row-based-planning/row-based-modeling/perform-scenario-analysis-in-row-model.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.