02 - Risk how-to
How to use Monte Carlo
Use this guide to operate the native Monte Carlo module: the risk register, uncertainty bands, simulation results, driver analysis, and the cross-update burn-down.
Quick Start
- Open a project and go to its Monte Carlo module.
- Add risk events in the Risk Register tab, and duration bands in Uncertainty Bands.
- Run the simulation.
- Review Results, Drivers, and Burn-down, and check the Calculation Glossary for methodology.
01
Risk Register
- Click Add Risk to create a discrete risk event.
- Set its probability percent and a min/likely/max day impact and cost impact (sampled from a triangular distribution).
- Use Targets to pick which activities the risk applies to, or leave it as "Whole project (serial)" to extend the finish directly.
- Set a Correlation group (e.g. "weather") so multiple risks that should occur together share one occurrence draw per simulation run.
- Save or load a named register to reuse a risk set across runs.
02
Uncertainty Bands
- Set the default Min/Likely/Max percent range applied to every activity's remaining duration (before any risk events are added).
- Add an override for a specific activity code (format "Type:Value", e.g. "Phase:Construction") when part of the schedule needs a different band.
- Completed work and milestones are not resampled.
03
Run the simulation
- Confirm the risk register and uncertainty bands are ready, then run the simulation.
- The engine runs a full CPM-per-iteration simulation over the parsed activity network (up to 10,000 iterations), calendar-aware, deterministic by default so identical inputs reproduce identical results.
- Re-run after editing risks or bands to see updated results.
04
Use Results
- Open the Results tab after a run completes.
- Read the Finish Date Risk Curve for how many days beyond the deterministic finish each percentile lands.
- Check the Milestone Forecast table for each milestone's deterministic, P50, and P80 dates.
05
Use Drivers
- Open the Drivers tab.
- Read the tornado chart for which risks and activities most affect total duration.
- Check the Criticality Index table for the percent of iterations each activity sat on the driving path.
06
Use Burn-down and the Glossary
- Open Burn-down to see the P50/P80 finish trend across schedule updates, once the project has more than one run.
- Open Calculation Glossary for the exact formula behind every metric on this page.