Scenarios Fundamentals

What scenarios are and when to use them

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

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.

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.

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.

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