> For the complete documentation index, see [llms.txt](https://docs.agentnoon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agentnoon.com/start-here/agentnoon-101/scenarios-fundamentals.md).

# Scenarios Fundamentals

A scenario is an editable copy of your org where you can model changes without affecting live data. Changes in a scenario are completely isolated from the Main Org until you choose to implement them.

## When to Create a Scenario

<figure><img src="/files/g389xKZNXyAL1RX0s8Bt" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/W7FrwAMYtLQbRaq0N6XO" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/ZYpBZBCtBWzP6YirzMCS" alt=""><figcaption></figcaption></figure>

Create a scenario whenever you need to model changes to your org structure:

* Plan a reorganization or restructure
* Model headcount additions or reductions
* Explore and compare multiple approaches
* Prepare a proposal for stakeholder approval
* Run annual or quarterly planning

## Scenario Types

**Full Org** — Copy of your entire organization. Use for company-wide planning.

**Partial Org** — Copy of a subset of your organization. Faster to create and easier to work with. Most commonly used.

**New Org** — Blank canvas. Use when building a new department or team from scratch.

## What You Can Do in a Scenario

**Position actions:** Add new positions, edit details (title, salary, department), move positions to a new manager, close positions (RIF or Exit), and duplicate positions.

**Bulk actions:** Select multiple positions and change manager, edit attributes, or close them in batch.

**People actions:** Assign employees to positions, detach employees (creating vacancies), or move employees to the bench during restructuring.

## Reviewing Impact

The **OpEx Panel** shows the real-time impact of every change you make — additions, reductions, and modifications with cost and headcount impact. Check it frequently to track progress against your goals. See [Scenario Changes & Impact](/scenarios/opex-panel.md).

## Time-Based Planning

Set **effective dates** on changes to schedule when they take effect. Forecast then shows the phased impact over time — for example, 5 hires in Q1 and 3 in Q2. See [Time-Based Planning](/scenarios/time-based-planning.md).

## Approval Workflow

When your scenario is ready, submit it for approval through the OpEx Panel. Scenarios move through approval levels (Level 0 → 1 → 2 → 3) and lock once approved. See [Scenario Approvals](/scenarios/approvals.md).

## Comparing Scenarios

Create multiple versions (Option A, Option B) and compare them side-by-side on cost, headcount, and structural metrics. Comparisons are started from the homepage. See [Scenario Comparisons](/scenarios/comparisons.md).

## Scenarios vs Forecast

**Scenarios** model specific structural changes — who reports to whom, exact positions, team design.

**Forecast** projects aggregate numbers over time — headcount by quarter, cost by department, multi-year growth.

Use both together: create a Forecast for high-level targets, then build Scenarios to model the specific org structures that achieve them.


---

# 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.agentnoon.com/start-here/agentnoon-101/scenarios-fundamentals.md?ask=<question>&goal=<endgoal>
```

`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.