# Scenarios Overview

## What Is a Scenario?

Scenarios are editable copies of your organization used for planning future changes.

Each Scenario begins as a snapshot of Main Org at the time it is created. Changes made in a Scenario do not affect Main Org.

Use Scenarios to model reorganizations, hiring plans, budget adjustments, and structural changes before implementing them.

## Three Scenario Types

When creating a Scenario, you can choose the type that matches your scope and purpose:

1. **Partial Org (recommended)** - Includes a selected portion of the organization, such as a department or reporting line. Best for focused changes within a specific team or area.
2. **Full Org** - Includes your entire accessible organization. Best for company-wide planning or large-scale restructuring.
3. **New Org** - Starts with a blank structure. Best for designing a new department from scratch.

<figure><img src="https://2094208261-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCZc46qaaBbVmMuYXPfgz%2Fuploads%2Fe23UyOWrTgMMryDB17AC%2FScreenshot%202026-03-04%20at%2010.42.38%E2%80%AFAM.png?alt=media&#x26;token=3382784a-7dc2-4b3c-ad98-858b35f56156" alt=""><figcaption></figcaption></figure>

## The Scenario Lifecycle

A Scenario typically moves through the following stages:

* **Create** - Generate a Scenario from Main Org.
* **Model** - Make structural and data changes.
* **Analyze** - Review headcount and cost impact.
* **Compare** - Evaluate alternative Scenarios.
* **Collaborate** - Share and gather feedback.
* **Approve** - Submit the Scenario for review.
* **Implement** - Apply approved changes in your Org.

## Key Features

#### OpEx Panel (Impact Tracking)

Track the impact of your changes in real time.

The OpEx Panel summarizes:

* Additions
* Reductions
* Data changes
* Headcount impact
* Cost impact

Use it to monitor the overall effect of your proposed changes.

#### Time-Based Planning

Model changes using effective dates.

Plan hires, exits, or structural updates over time and evaluate headcount and cost projections accordingly.

#### Scenario Comparison

Compare multiple Scenarios to evaluate different planning approaches.

Review differences in headcount, cost, structure, and key metrics before selecting a preferred option.

#### Approval Workflows

Submit Scenarios for formal review, including routing them through multi-level approvers while maintaining a full audit trail of all changes.&#x20;

## Scenarios vs. Main Org

| Scenarios              | Main Org         |
| ---------------------- | ---------------- |
| Future state / what-if | Current state    |
| Fully editable         | View-only        |
| Unlimited versions     | One version      |
| Manually created       | Synced from HRIS |
| Point-in-time snapshot | Real-time data   |

**When to use Main Org:** When you need to explore, search, analyze, or understand your current organization.

**When to use Scenarios:** When you need to model changes, plan reorganizations, or test different structures.

## Getting Started

1. Main Org > **Create Scenario** (top right) or Homepage > "**+"** button
2. Choose Partial Org > select scope
3. Name clearly: For example, "Engineering Q2 2026 Reorg"
4. Start editing — see [Making Position Changes](https://docs.agentnoon.com/scenarios/using-scenarios-basics/making-position-changes)
5. Check the OpEx Panel frequently for insights

## Related Articles

* [Creating Scenarios](https://docs.agentnoon.com/scenarios/creating-scenarios)
* [Using Scenarios - Basics](https://docs.agentnoon.com/scenarios/using-scenarios-basics)
* [Making Position Changes](https://docs.agentnoon.com/scenarios/using-scenarios-basics/making-position-changes)


---

# 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://docs.agentnoon.com/scenarios/overview.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.