The next time a stakeholder asks, “When will it really finish?”, do not point to the P6 finish date. Open Pertmaster, run 10,000 iterations, and say: “There is an 80% chance we finish by July 20th, and here are the three things that could still blow that up.”

In a mining project, the deterministic critical path was ore processing equipment. Pertmaster revealed that the environmental permit (variance of 0–200 days) was the true risk driver, even though it had 90 days of total float in P6. Chapter 3: Risk Register Integration – The Missing Link Most organizations manage risks in Excel. Pertmaster bridges the gap between qualitative risk registers and quantitative schedule impact.

You can define (e.g., “Strike at port” with 15% probability) and attach them to activities. Pertmaster does not just vary durations; it triggers discrete events. If the random number generator lands on 0.15, the activity duration multiplies by 1.5 and a resource cost is added.

That is not fear-mongering. That is professional risk management. This article is based on Oracle Primavera Risk Analysis (formerly Pertmaster) v14+ and Primavera P6 v20+. All case study data is representative and anonymized.

A histogram (probability distribution) showing that the P6 date of June 1st actually has only a 15% chance of being met. The P80 date (80% confidence) is July 20th. Chapter 2: The Secret Weapon – Risk Drivers and Tornado Graphs Pertmaster’s true genius is not simulation—it is sensitivity analysis .