Modeler - Commit Model Scenarios

This article explains how to commit a Modeler Scenario so your approved strategic decisions are captured and made visible in your portfolio—without automatically updating live project data.

What you will accomplish
By the end of this article, you will be able to commit a Modeler Scenario and understand how committed data is stored, how conflicts are handled, and what happens after a Scenario is committed.

Requirements

Before you begin, make sure you have:

• A OnePlan account with Enterprise permissions (Edit All Data, Manager, or Admin)
• Contributor or Owner access to the Portfolio Model
• The Portfolio Modeler module enabled
• At least one saved Scenario in your Model

Background

The OnePlan Portfolio Modeler helps leaders explore what‑if scenarios—such as funding changes, timeline shifts, or prioritization options—before work begins. This allows organizations to compare options and confidently select the best path forward.

Scenario Commitments connect planning to execution by capturing approved decisions and establishing a strategic baseline. However, committing a Scenario does not automatically change live project schedules or execution data.

Instead, Scenario Commit ensures that approved decisions are clearly documented, visible, and available for controlled execution.

Important Concept: Commit Does Not Update Live Plan Fields

Committing a Modeler Scenario does not automatically update live project or plan fields such as Start Date or End Date.

When a Scenario is committed:

• Approved Scenario values are written to Committed Scenario Plan Fields
• These fields live alongside the existing live plan fields
• Live execution data remains unchanged until a user updates it manually

This design ensures that approved strategy is visible and reportable, while execution changes remain intentional and controlled.

Instructions

Note
These steps assume you already have one or more Scenarios saved in your Model.
If not, see Build Scenarios for Your Portfolio Models.

When you are ready to move forward with a Scenario, you can commit it to your Portfolio.

1. Select Save → Save & Commit Scenario.
   
2. OnePlan checks the Scenario against the current Portfolio data.
3. The Commit Scenario dialog appears, indicating whether any differences were found.
   

When Conflicts Are Found

If differences exist between your Scenario and the current Portfolio data, the Commit Scenario screen appears with a comparison table highlighting those differences.

This does not mean something is wrong. It simply allows you to review how the approved Scenario differs from the current state before committing.

Understanding the Commit Scenario Screen

Each row represents a plan included in the Scenario. The screen compares:

• Proposed – values from the Scenario you are committing
• Committed – values currently stored in committed Scenario fields

Highlighted differences show what will be captured as the new approved baseline.

Common differences include:

• IN vs OUT status
• Modeled start or end date changes
• Plans previously committed from a different Scenario

What Happens When You Commit

When you select Commit:

• OnePlan creates or updates Committed Scenario Plan Fields
• Approved Scenario values are written to those fields
• Existing live plan fields remain unchanged
• The Scenario is marked as the current committed baseline

Important
Committing a Scenario does not update live project schedules or execution data.
Live plan fields are updated only through manual user action.

Who Takes Action After Commit?

Portfolio Manager

• Commits the approved Scenario
• Establishes the strategic baseline
• Communicates approved scope, timing, and priorities

Project Manager

• Reviews Committed Scenario values
• Manually updates live Start and End Dates as appropriate
• Controls when approved strategy becomes execution reality

This separation supports governance, accountability, and change control.

Example: How Dates Flow After Commit

1. A Scenario proposes a new start date of June 1
2. The Scenario is committed
3. June 1 is written to the Committed Start Date field
4. The live Start Date remains unchanged
5. The Project Manager updates the live Start Date when ready

Approved strategy and execution remain clearly separated.

After Commitment

Once a Scenario is committed:

• Approved decisions are stored in Committed Scenario Plan Fields
• Strategy and execution data are visible side by side
• Committed fields can be used to:
  • Build Portfolio Views
    (see Save, Use, and Manage Views in the My Portfolio Area)
  • Display Scenario details on Plan Detail forms
    (see Set Up Plan Detail Forms)

Related Resources

• Build Scenarios for Your Portfolio Models
• Save, Use, and Manage Views in the My Portfolio Area
• Set Up Plan Detail Forms