What-If Analysis Calculator
Analyze multiple project scenarios, assess risks, and make data-driven decisions with comprehensive scenario planning
Use this when
Use this during risk identification, quantitative analysis, reserve planning, or before choosing between uncertain delivery options.
Prepare
Bring a current risk register, calibrated probability and impact estimates, response assumptions, and evidence from subject-matter experts or historical data.
Decision supported
Use the result to prioritize responses, assign owners, set escalation thresholds, or recommend contingency and management attention.
Practitioner guidance and limitations
Interpret and act
Separate inherent from residual exposure and consider threats and opportunities. The number supports—not replaces—facilitated risk judgment.
Professional caution
Avoid false precision and correlated assumptions. Document estimate ranges and revisit them when scope, schedule, cost, or external conditions change.
Common questions about this analysis
What does the What-If Analysis Calculator help a project manager decide?
Analyze multiple project scenarios, assess risks, and make data-driven decisions with comprehensive scenario planning Use the result to support a documented decision, action, threshold, or follow-up rather than treating it as a stand-alone score.
How reliable is the What-If Analysis Calculator?
Reliability depends on the quality, consistency, and status date of the inputs. Validate source data, record assumptions, and test material results against your approved baseline and expert judgment.
When should the What-If Analysis Calculator not be used on its own?
Avoid false precision and correlated assumptions. Document estimate ranges and revisit them when scope, schedule, cost, or external conditions change.
Which inputs require the most attention?
Bring a current risk register, calibrated probability and impact estimates, response assumptions, and evidence from subject-matter experts or historical data.
What should be shared with stakeholders?
Share the result together with units, status date, source data, assumptions, confidence or range, interpretation, recommended action, owner, and next review date.
Learn the topic: concept, PMP lens, and common mistakes
Core concept
Risk analysis makes uncertainty explicit by linking a cause to an uncertain event and its effect on objectives. Scores and exposure values support prioritization; they do not replace response planning.
Professional application
Compare inherent and residual exposure, assign an accountable owner, select a response, and define a trigger or review date.
PMP exam and practice lens
Separate qualitative prioritization from quantitative analysis. EMV is probability multiplied by impact; contingency addresses identified uncertainty, while management reserve is held for unknown-unknowns within governance rules.
Common mistakes
- Writing issues or vague concerns as risks
- Using uncalibrated probability and impact scales
- Calculating exposure without funding or assigning a response owner
Before you trust the result
- Confirm one status date and consistent units.
- Retain the input source, owner, and confidence.
- Sense-check the result against an independent benchmark.
- Record the decision, action owner, and review date.
Baseline Scenario
Alternative Scenarios
Best Case
Optimistic scenario with better efficiency
Worst Case
Pessimistic scenario with major delays
Add New Scenario
What is What-If Analysis?
What-if analysis is a scenario planning technique that allows project managers to explore the consequences of different assumptions and conditions on project outcomes. The PMBOK Guide references what-if scenario analysis as a tool in both the Develop Schedule and Plan Risk Responses processes. It enables teams to ask "what happens if" questions -- what if the vendor is three weeks late? What if the budget is cut by 15%? What if two key team members resign? -- and systematically evaluate the answers to make better-informed decisions.
At its core, what-if analysis constructs multiple coherent scenarios from a set of variable changes. A typical analysis includes at minimum three scenarios: the best case (optimistic assumptions), the worst case (pessimistic assumptions), and the most likely case (realistic assumptions). Each scenario adjusts project parameters -- duration, budget, team size, scope, quality, and risk -- to model a plausible future state. Probability weights are then applied to calculate a weighted average that represents the statistically expected outcome.
What-if analysis connects directly to Monte Carlo simulation and contingency planning. While Monte Carlo runs thousands of randomized simulations to produce a probability distribution, what-if analysis examines a handful of discrete, hand-crafted scenarios. This makes it faster and more accessible for decision-makers who need directional insight without the overhead of full simulation. The output -- a range of possible outcomes with probability estimates -- feeds directly into contingency reserve calculations and go/no-go decisions.
Weighted Scenario Outcome Formula Explained
Scenario Outcome is the calculated result (ROI, budget, duration) for a specific scenario after applying all variable changes to the baseline. Scenario Probability is the estimated likelihood of that scenario occurring, expressed as a percentage. The Remaining Probability is whatever percentage is left over after all explicit scenarios are accounted for, and it is assigned to the baseline as the default outcome.
For example, if your Best Case scenario has a 30% probability and your Worst Case has a 20% probability, the baseline implicitly carries the remaining 50% probability. This weighted approach produces an expected value that accounts for both upside potential and downside risk, giving stakeholders a single number that represents the most statistically probable project outcome.
Step-by-Step Guide to What-If Analysis
Establish the baseline scenario with your current project parameters: planned duration, approved budget, allocated team size, committed scope, target quality, and assessed risk level. This is your reference point for all comparisons.
Define alternative scenarios based on identified risks, opportunities, and stakeholder concerns. Each scenario should tell a coherent story -- not random variable adjustments -- such as "vendor delivers late" or "team expands with two senior hires."
Assign realistic probabilities to each scenario based on historical data, expert judgment, and current project conditions. Probabilities across all scenarios should not exceed 100%, and gaps between scenario probabilities and 100% are automatically assigned to the baseline.
Calculate outcomes for each scenario -- ROI, efficiency, success probability -- and compare against the baseline. Identify which scenarios cross critical thresholds such as budget limits, deadline commitments, or minimum acceptable quality levels.
Develop contingency plans for the worst-case scenario and opportunity plans for the best case. Present the full scenario comparison to stakeholders with a recommendation that accounts for both expected value and risk tolerance.
Real-World Example
Scenario: A software project with 180-day baseline, $100,000 budget, 8-person team
• Baseline: 180 days, $100K budget, ROI 95%, success probability 85%
• Best Case (30% probability): 160 days, $85K budget, ROI 135%, success 92%
• Worst Case (20% probability): 252 days, $135K budget, ROI -5%, success 35%
• Weighted Average ROI: (30% x 135%) + (50% x 95%) + (20% x -5%) = 89%
Result: The weighted average ROI of 89% is healthy, but the worst-case scenario shows a negative ROI with only 35% success probability. The project manager recommends establishing a contingency reserve of $35K (the worst-case budget overrun) and setting a management reserve for the 72-day schedule risk.
Common Mistakes to Avoid
- Only modeling extreme scenarios -- If your only scenarios are wildly optimistic and catastrophically pessimistic, the analysis provides little actionable guidance. Always include a realistic most-likely scenario grounded in current project data.
- Assigning equal probability to all scenarios -- Not all scenarios are equally likely. A vendor being one week late is far more probable than a natural disaster shutting down operations. Use calibrated probability estimates based on data, not guesswork.
- Creating scenarios that ignore dependencies -- If your worst case assumes both budget overruns and team attrition, make sure those events are plausibly correlated. Randomly combining independent extreme events produces scenarios with vanishingly small probabilities.
- Failing to update scenarios -- What-if analysis is a living tool, not a one-time exercise. As the project progresses and actuals replace estimates, update your scenarios to reflect new information. Stale scenarios lead to stale decisions.
PMP Exam Tips
The PMP exam references what-if scenario analysis primarily in the context of schedule management and risk management. In schedule management, what-if analysis is used to assess the feasibility of schedule targets under different conditions -- for example, "what if Activity A takes twice as long as planned?" In risk management, it supports contingency planning by quantifying the range of possible outcomes and their associated probabilities.
Know the distinction between what-if analysis, sensitivity analysis, and Monte Carlo simulation. What-if analysis examines discrete, hand-crafted scenarios. Sensitivity analysis varies one variable at a time to identify which variables matter most. Monte Carlo simulation runs thousands of randomized iterations to produce a full probability distribution. On the exam, if the question describes a few named scenarios with probability weights, the answer is what-if analysis. If it describes varying one variable at a time, the answer is sensitivity analysis. If it mentions running thousands of iterations, the answer is Monte Carlo.
Also remember that what-if analysis outputs feed directly into contingency reserve planning. The expected value of the worst-case scenario (probability times impact) tells you how much contingency reserve to allocate. This connection between scenario analysis and reserve determination is a high-yield exam concept that appears frequently in risk management questions.