Skip to main content
Adaptive Planning
Last Updated: 2023-06-23
Org Design and Scenario Modeling: Headcount Reduction and Redeployment

Org Design and Scenario Modeling: Headcount Reduction and Redeployment

Preview Date: 2026-05-29. Production Date: 2026-07-03.
This feature enables organizational strategists and business leaders to model workforce reductions and worker redeployments within Org Design and Scenario Modeling scenarios. You can model the closure of existing filled or open positions, create To Be Reduced placeholders for planned reductions, and move workers between positions to optimize organizational structures. The system now systematically handles calculations based on action types, ensuring that Headcount, FTE, and Cost of Workforce metrics accurately reflect the impact of planned closures and reductions.

Business Benefits

This feature provides you with:
  • Strategic agility. You can model complex reduction and redeployment scenarios to align with changing business goals without affecting live production data.
  • Enhanced decision support. You can gain instant visibility into the cost and structural impacts of workforce reductions through dynamic KPIs and updated organizational health analytics.
  • Streamlined execution. This feature links the planning of workforce movements and closures to downstream execution in HCM, reducing manual reconciliation efforts.

Changes

Modeling Actions
We add these new related actions that you can access when you launch and edit org model scenarios:
  • Reduce Headcount
    on active orgs, which enables you to create To Be Reduced placeholder records, including planned new orgs.
  • Close
    on positions with a
    Staffing Status
    of
    Open
    or
    Filled.
    When you close a filled position, we automatically notify you that the worker will be removed.
  • Reopen
    on closed positions, which enables you to revert planned closed positions back to
    Open
    status within the same scenario.
  • Transfer Worker
    on filled positions, which enables you to move a worker from a source position to a proposed open or To Be Hired position within the scenario using a new form.
We change the
Planning Staffing Status
field so that it:
  • Is now read-only.
  • Updates automatically based on modeling actions, such as
    Reopen
    , C
    lose
    , or
    Assign Roles
    .
We update the calculation engine to treat metrics based on the specific modeling action. While edits and adds remain positive, we now treat a closed position as $0, 0 Headcount, and 0 FTE. For To Be Reduced placeholders, we use the value from your
Cost Estimate By Calc
field but treat it as a negative value in all rollups and analytics.
User Interface and Visualizations
We update the formatting and icons on position cards to distinguish between these statuses:
  • New (TBH)
  • Moved
  • Edited
  • TBR
  • Closed
We also update the cards for To Be Hired positions with an assigned worker to now display the worker's profile image with a dotted circle.
We rename the
Model Variance
section in the
Summary
tab to
Org Health
. In the
Org Health
section, we also add a new
Orgs with negative metrics
row that appears when reductions cause negative headcount or cost values.
We now include warning messages or specific groupings to handle orgs or layers with negative total headcount on these charts:
  • Span of Control
  • Org Structure
  • Position Distribution
We add a new
To Be Reduced
tab to the
Review Changes
task which displays closed positions and worker transfers within the
Edited
section.
Reporting
We deliver these new report fields on the Headcount Plan Lines Details business object (secured to the
Public Reporting Items
domain):
  • Closed Headcount
    . You can use this report field to identify plan lines with closed headcount.
  • Reduce Headcount
    . You can use this report field to identify plan lines with reduced headcount.
We update the
Positions
report data source to return negative values for these org model metrics when you reduce headcount to negative amounts:
  • Cost of Workforce.
  • FTE.
  • Headcount.

What Do I Need to Do?

If you already configured Org Design and Scenario Modeling, you don't need to do anything. To configure Org Design and Scenario Modeling, see Steps: Set Up Org Design and Scenario Modeling.

What Happens if I do Nothing?

If you do nothing and already configured Org Design and Scenario Modeling, we automatically display the new related actions for modeling headcount reductions, closures, and redeployments. Your existing analytics will continue to function and will reflect negative headcount or cost impacts from potential reductions.
If you do nothing and didn't configure Org Design and Scenario Modeling, the Org Design & Scenario Modeling features will not be accessible to your users. Existing workforce planning functionality will remain unchanged.

Test Scenarios

We recommend that you check the
Cost Estimate By Calc
field on your org model to ensure that it returns the expected values.

Change Log

Org Design and Scenario Modeling: Headcount Reduction and Redeployment
We now deliver this feature to your Preview tenant and update the Release Note Type from Coming Soon to Feature.
Preview Date: 2026-05-29. Production Date: 2026-07-03.