The Cost of Guessing
A client asks you to accelerate the fit-out by two weeks. Your subcontractor wants to delay mobilization by five days. The structural engineer says the foundation design needs to change.
Each of these decisions changes your schedule, your costs, and your critical path. But by how much? Which downstream tasks are affected? Does the project end date move?
Most project managers answer these questions with experience and instinct. That works for simple changes on small projects. On a 100-task schedule with dependencies cascading across milestones, instinct isn't reliable enough. You need a way to simulate the impact before committing.
That's what-if analysis.
What What-If Analysis Actually Is
What-if analysis is simple in concept: make a temporary change to your project data, see the full cascading impact, and then decide whether to commit the change or discard it.
The key word is temporary. You're not modifying your live schedule. You're running a simulation on a copy of the data, reviewing the results, and only applying the change if the impact is acceptable.
What you can simulate
- Duration changes - "What if the concrete curing takes 10 days instead of 7?"
- Date shifts - "What if we start two weeks later due to permit delays?"
- Dependency additions or removals - "What if we decouple electrical from plumbing and run them in parallel?"
- Resource changes - "What if we add a second crew to the critical task?"
- Scope additions - "What if the client adds a mezzanine floor?"
What you want to see
- Impact on the project end date - does it move? By how much?
- Critical path changes - did the critical path shift to a different sequence?
- Cost impact - how does the change affect the total budget?
- Float changes - which tasks lost their buffer? Which gained buffer?
- Downstream cascade - exactly which tasks are affected and how
Why Gut Feel Fails at Scale
On a 20-task project, an experienced PM can mentally trace a change through the dependency chain and estimate the impact. It's not perfect, but it's close enough.
On a 150-task project with 60+ dependencies across 5 milestones, the cascading effects are too complex for mental modeling. A change to one task might affect 20 downstream tasks through three different dependency paths. Some effects cancel out. Others compound. The only way to know the real impact is to calculate it.
This is especially true for indirect effects. Extending a non-critical task by three days might seem harmless - it has float, after all. But what if that extension consumes all the float and makes the task critical? Now a previously safe part of your schedule is on the critical path, and any further delay there pushes the end date.
Without simulation, you won't catch this until it's too late.
The Right Way to Do What-If Analysis
Step 1: Define the scenario
Be specific about what's changing. "What if we're delayed?" is too vague. "What if Task 14 (foundation excavation) takes 12 days instead of 8?" is actionable.
Step 2: Run the simulation
Apply the change to a copy of your schedule and let the scheduling engine recalculate all dates, float values, and the critical path.
Step 3: Review the diff
Compare the simulation results against your current baseline. Focus on:
- End date impact (the headline number)
- Critical path changes (the structural impact)
- Tasks that lost float (the risk shift)
- Cost impact if applicable
Step 4: Decide
Commit the change if the impact is acceptable. Discard it if not. If partially acceptable, explore mitigations: can you offset the delay by overlapping other tasks or adding resources?
Step 5: Document the decision
Whether you commit or discard, record what you simulated and why you decided the way you did. This decision log becomes invaluable when similar questions arise later.
Common What-If Scenarios
Schedule compression: "The client wants to finish two weeks early. What do we need to change?" Simulate reducing durations on critical path tasks and see if the math works.
Risk assessment: "What if the long-lead equipment delivery is late by 10 days?" Simulate the delay and see which downstream work is affected. If the impact is severe, plan mitigation now rather than waiting for the delay to happen.
Change order evaluation: "The architect wants to add a green roof. What's the schedule and cost impact?" Simulate the additional tasks, dependencies, and costs before quoting the change order.
Resource reallocation: "If we move the second crew from Phase B to Phase A, does the overall end date improve?" Sometimes accelerating one area delays another. Simulation tells you the net effect.
How Milesto Handles What-If Analysis
Milesto's What-If feature lets you select any task or set of tasks, modify their properties (duration, dates, status, dependencies), and see the full cascading impact displayed as a visual diff against your current schedule.
The simulation runs through the same CPM engine as your live schedule, so the results are exact - not estimates. You see which tasks shift, by how many days, and whether the critical path changes.
If the results look good, you commit the changes with one click. If not, discard and your schedule is untouched.
Key Takeaways
- What-if analysis replaces guesswork with calculation, especially on projects with complex dependencies
- Simulate before committing by making temporary changes on a copy, not your live schedule
- Watch for indirect effects because a change to a non-critical task can shift the critical path
- Use it for change orders and simulate schedule and cost impact before quoting
- Document every simulation because even discarded scenarios inform future decisions
Want to simulate before you commit? Start free on Milesto.io with what-if analysis and full CPM recalculation built in.