Skip to main content
All CollectionsBest practices
Scenarios - Budgeting and Termination Workflows
Scenarios - Budgeting and Termination Workflows
Jeff Von Ward avatar
Written by Jeff Von Ward
Updated over 2 weeks ago

Scenarios are a powerful, private and secure way to visualize fiscal and organizational changes at your company by emulating any potential new headcount or terminations in order to see the associated cost increase or savings.

Understanding the Budgeted Column

The "Budgeted" column in Scenarios serves different purposes depending on the plan type:

  • In new plans, all headcount should be marked as "Budgeted" as they are part of the original planning.

  • In modify plans, the "Budgeted" flag helps distinguish incremental headcount that wasn't part of the original plan. In these cases, additions to the plan should be marked as "Not budgeted".

Termination Process in Scenarios

When initiating a termination within a Scenario, there are a few things to keep in mind:

  • The action remains contained within TeamOhana and does not automatically flow to your HRIS.

  • The system displays immediate cost savings from the proposed termination.

  • Upon scenario approval and merger, the termination is recorded in TeamOhana.

  • Final reconciliation occurs once your HRIS is updated with the actual termination date.

Note: System integration with your HRIS is designed to maintain data integrity through reconciliation rather than direct real-time updates.

Reporting Manager Assignment

When adding a new headcount request to your scenario, the current functionality for reporting manager is as follows:

  • Default assignment is set to the person adding the headcount.

  • Admins can view and select from all managers in the organization.

  • Limited Editors invited to collaborate in your Scenario can only view and select managers from their assigned department.

Best Practices

  • Always mark headcount as "Budgeted" in new plan Scenarios.

  • For role redundancy and budget re-allocation, use the termination feature to reflect cost savings before adding new positions.

  • When creating new headcount, you can invite the reporting manager to collaborate as a limited editor and they will have access to their direct report positions within the same scenario.

Did this answer your question?