5 min read ·

How Do I Run an Optimization Scenario in Profit.co?

Profit.co's Scenario Planning lets you create a named optimization scenario inside a portfolio's Optimization tab, setting target values for constraints like Budget, Resource Capacity, and Timeline against the projects currently in your plan. Each constraint you add is scored as Must Meet, Should Meet, or Optimize.

What Is an Optimization Scenario?

An optimization scenario is a named what-if plan you build inside a specific portfolio's Optimization tab, using the Scenarios sub-tab. Each scenario has a Scenario Name, optional Owner(s) and Tags, and a set of Optimization Constraints, each comparing the portfolio's Current value against a Target value you set for that scenario.

The Optimization tab is organized into three sub-tabs: Projects, which lists every project in the portfolio with an In Plan toggle; Scenarios, where scenarios are created and managed; and Optimization. Scenario Planning itself is enabled and configured organization-wide from Settings, where three default Constraint Types, Must Meet, Should Meet, and Optimize, are available to apply to any scenario.

Why Does Running an Optimization Scenario Matter?

A portfolio's summary cards show its current Budget, Resources, and Timeline as a single snapshot, for example ₹300K budget, 3 resources, and a 4-month timeline. An optimization scenario lets you test a different target for those same figures, and choose which projects are In Plan, without changing the portfolio's live data to find out whether a target is realistic.

Because each constraint carries a Type, Must Meet, Should Meet, or Optimize, you can also signal which targets are non-negotiable and which ones are flexible goals, rather than treating every constraint as equally strict.

How Do I Set Up and Run an Optimization Scenario?

Step 1

  • Navigate to Settings → Portfolios and Projects → Portfolios → Scenario Planning.
  • Enable the Scenario Planning toggle.
  • Review the three default Constraint Types under Constraint Types: Must Meet, Should Meet, and Optimize. Use the pencil icon to edit a type, or its Enabled toggle to turn it on or off.

Step 2

  • Open the portfolio and switch to the Optimization tab.
  • On the Projects sub-tab, review the portfolio's summary cards: Projects, Budget, Resources, Timeline (months), and Risk Score.
  • Use the In Plan toggle next to each project to control which projects are part of the current plan.

Step 3

  • Switch to the Scenarios sub-tab within Optimization.
  • Open the Create Scenario panel.
  • Enter a Scenario Name (required), and optionally add a Description, Owner(s), and Tags.
 

Step 4: Set Optimization Constraints

  • Under Optimization Constraints, review the Current value shown for each constraint, for example Budget, Resource Capacity, or Timeline.
  • Enter a Target value for each constraint you want the scenario to evaluate against.
  • Set the Type for each constraint to Must Meet, Should Meet, or Optimize.
  • Use + Add Constraint to add more constraints, or the X icon to remove one, then click Create.

Note

Budget, Resource Capacity, and Timeline are the constraint options shown in the Create Scenario panel, each with its own Current value drawn from the portfolio.

What Happens When You Create an Optimization Scenario?

Scenario What Happens
You set a constraint's Type to Must Meet. The constraint becomes an absolute requirement, and the scenario's optimization fails if that target is violated.
You set a constraint's Type to Should Meet. The constraint is treated as an important goal that allows violations with a penalty, at whichever flexibility level is configured for that type.
You set a constraint's Type to Optimize. The constraint is treated as a nice-to-have, with only a minimal penalty if the target isn't met.
You try to create a scenario without entering a Scenario Name. The field is marked as required in the Create Scenario panel, so a name must be entered before the scenario can be saved.

What Are the Default Constraint Types?

Constraint Type Description Priority Flexibility Setting
Must Meet Absolute requirement; optimization fails if violated. High Hard Constraint
Should Meet Important goal, allows violations with penalty. Medium Slider from Most Strict to Most Flexible (default: 45, Moderately Strict)
Optimize Nice to have, minimal penalty for violations. Low Slider from Most Strict to Most Flexible (default: 35, Strict)

What Are the Best Practices for Running Optimization Scenarios?

  • Reserve Must Meet for constraints that truly can't be violated, since the guide's own description ties this type to optimization failing outright if it's not satisfied.
  • Toggle In Plan off for projects you're testing removing before creating a scenario, so the scenario reflects the plan you actually want to evaluate.
  • Name scenarios descriptively, for example by the target you're testing, since Scenario Name is the main way you'll tell multiple saved scenarios apart later.
  • Review the default Flexibility Setting values for Should Meet and Optimize in Settings before relying on them, and adjust the slider if your organization needs stricter or looser enforcement than the defaults.

What Are Some Frequently Asked Questions About Optimization Scenarios?

Q1. Can I create more than one scenario for the same portfolio?

The Scenarios sub-tab is where scenarios are created and managed for a portfolio, and each one is saved under its own Scenario Name.

Q2. Which constraints can I set a target for in a scenario?

The Create Scenario panel shows Budget, Resource Capacity, and Timeline as constraint options, each with a Current value and a field to enter your Target.

Q3. Do I need to enable Scenario Planning for every portfolio separately?

Scenario Planning is enabled from Settings → Portfolios and Projects → Portfolios → Scenario Planning, which is an organization-level setting rather than a per-portfolio toggle.

Execute your strategy with confidence

Connect OKRs, tasks, and teams in one place with Profit.co

 
Athena

Welcome to Profit.co 👋

How can I help you today?