> 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/scenarios/key-concepts-scenarios.md).

# Key Concepts for Scenarios

## What Is a Scenario?

An editable copy of your Main Org where you model future changes without affecting the current live data. Changes in scenarios are completely isolated from Main Org until you choose to implement them.

**Typical workflow:** Main Org (current state) → Create scenario → Model changes → Review impact → Submit for approval → Implement

## Change Types

**Addition (green outline)** - New position created; increases headcount and cost.

**Reduction (red outline)** - Existing position closed; decreases headcount and cost. Types: RIF and Exits.

**Modification (icon only, no color)** - Changed attributes on existing position (title, salary, department, manager). May increase or decrease cost.

**No Change** - Position exists in both the Main Org and scenario; no attributes modified.

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

## Before / After / Changes Views

* **Show Before** - Main Org (current reality); your baseline
* **Show After** - All scenario changes applied; the proposed future state
* **Show Changes** - Delta only; shows +/- per department; best for communicating impact

## OpEx Panel (Scenario Changes & Impact)

The OpEx Panel is the side panel where you review all scenario changes and their impact. It shows headcount additions and reductions, net headcount change, net cost impact, and breakdown by department. You can toggle between cost and headcount views, and see changes grouped by effective date. The OpEx Panel is also where you submit scenarios for approval. See [Scenario Changes & Impact](/scenarios/opex-panel.md).

## Effective Dates

Date when a planned change takes effect. Set different dates on different changes in the same scenario to model phased rollouts. Forecast shows the time-phased impact. See [Time-Based Planning](/scenarios/time-based-planning.md).

## The Bench

Holding area for employees detached from positions but not yet placed elsewhere. Useful for modeling internal transfers: detach from Position A → assign to Position B. The bench is a planning construct only.

## Scenario Views

* **Org Chart** - Visual hierarchy; drag-and-drop; best for structural changes
* **Directory** - Table view; bulk operations; best for mass edits and filtering
* **Forecast** - Time-phased projections; headcount/cost by period
* **Workforce Hub** - Analytics charts (SOC, distribution, heatmap); before/after comparison

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

## Approval States

Draft (editable) → Submitted/Pending (locked) → Approved (locked) → Rejected (editable for revisions). Once approved, scenarios lock to preserve the approved state.

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

<figure><img src="/files/7YT9o6XEWsbnAVC7o3Je" alt=""><figcaption></figcaption></figure>

## Scenario Comparisons

Compare 2 scenarios side-by-side: cost, headcount, structure, org health metrics. Create Option A and Option B and use comparisons to choose the best approach for leadership. Comparisons must be started from the homepage.

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

## Projects (Optional)

Group related scenarios under a project for larger initiatives. Example: "2026 Restructuring" project containing Engineering Reorg, Sales Consolidation, and G\&A Cost Reduction scenarios.

**Note:** Projects are being retired soon and may not be available in a future release. Avoid relying on projects for new scenario setup.

## Related Articles

* [Scenarios Overview](/scenarios/overview.md)
* [Creating Scenarios](/scenarios/creating-scenarios.md)
* [Time-Based Planning](/scenarios/time-based-planning.md)
* [Scenario Comparisons](/scenarios/comparisons.md)
* [Scenario Approvals](/scenarios/approvals.md)


---

# 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/scenarios/key-concepts-scenarios.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.