Scenario Approvals

Streamline multi-level approvals

Before Submitting for Approval

Before submitting perform the following checks:

• The name is clear and descriptive

• The justification explains business rationale and expected outcomes

• All changes reviewed in "Show Changes" mode

• The cost impact and headcount delta match targets

• The effective dates are set correctly

• The key views are exported for documentation

Submitting a Scenario for Approval

Scenario Approvals

Approval flows ensure scenario changes go through the necessary review process before implementation. Scenario creators can define a structured approval flow with up to two levels of approvers.

Approval Levels

There are four approval levels across two tiers:

Organization-level approvers (set by admin):

• Level 1 — Reviewers who check budget implications, org chart hygiene, and job title accuracy

• Level 2 — Decision-makers with final approval on hires

Scenario-level approvers (set by scenario creator):

• Level 0 — Optional pre-check reviewers who provide input before the standard approval chain begins

• Level 3 — Optional final reviewers who sign off after Level 2, typically used for executive or cross-functional alignment

Once approvers are added, they receive an email notification with a link to the scenario.

Setting Up Approvers

Organization-level:

1. Go to Settings → Approval Configurations

2. Search and select one or more users as approvers

3. Note: only admins can set up organization-level approvers

Scenario-level:

1. Locate the scenario and click ⋮

2. Click Configure Approvals and select approvers

Submitting a Scenario for Approval

1. Click Configure Submission in the OpEx Panel

2. Click Submit Scenario in the bottom-right corner

3. Add a justification for your changes

4. Optionally exclude any additions from the submission

5. Click Submit

Once submitted, the scenario is locked and cannot be edited unless rejected by an approver.

Approving a Scenario

Approvers can review scenario details but cannot edit them.

To review:

1. Click on the scenario to open it

2. Click Approve Roles to review changes

Available actions per change:

• Approve — The change is marked approved and moves to the next approver in the workflow. The process continues until all required approvers have approved.

• Reject — The scenario is immediately marked as rejected

Admin actions:

• Admins can un-submit an entire scenario via ⋮ → Un-submit. The scenario moves back to review status, allowing collaborators to make edits.

Revising a Submission

A scenario can only be edited and resubmitted if:

• It was un-submitted by an approver, or

• It was rejected by an approver

Once fully approved, the scenario is finalized and ready for implementation.