Integrated Risk Using Risk Drivers & Monte Carlo (CPM)

What integrated cost-schedule risk analysis is

This is the most sophisticated method in the module, pioneered by David Hulett. Earlier approaches put a range directly on each activity's duration or each cost item. The risk-driver method instead starts from the risk register — the actual things that could go wrong — and models how each one ripples through the schedule and, through the schedule, into cost. It mirrors reality: risks cause delays, and delays cause cost.

What a risk driver is

A risk driver is a discrete, real-world risk from your register, defined by two things: a probability it occurs, and a multiplicative impact on the duration of the activities it's assigned to (e.g., "if it happens, affected activities take 1.1× to 1.4× as long"). Crucially, one driver can be assigned to many activities — and many drivers can pile onto one activity.

How the analysis runs

• Build a sound CPM schedule with cost loading — Start from a logic-driven critical-path schedule whose activities carry their time-dependent costs.
• Define risk drivers from the register — For each significant risk, set its probability and its multiplicative duration impact (e.g. 1.1×–1.4×).
• Assign drivers to activities — Map each driver to every activity it would affect — one driver can touch many activities.
• Simulate the network thousands of times — Each iteration fires drivers by probability, lengthens affected activities, recomputes the critical path, and tallies the resulting cost and finish date.
• Read joint cost and schedule results — Get confidence curves for both completion date and total cost — and see which drivers matter most.

Using the risk-driver method well

It demands a genuinely sound CPM schedule (garbage logic produces garbage risk results), a well-built risk register, and specialist software. Reserve it for large, schedule-sensitive projects where the integration of cost and time risk justifies the effort. Define drivers from real risks, assign them thoughtfully to activities, and use the prioritized driver list to drive your risk responses — not just to set a number.

Nine things to remember

1. Integrated analysis models cost and schedule risk together.
2. Big cost overruns often come from schedule slips — model them linked.
3. A risk driver = a real risk with a probability and a duration impact.
4. Model the cause, not just the symptom — one driver, many activities.
5. Shared drivers create correlation honestly — no fudged coefficients.
6. Each iteration fires drivers, lengthens activities, recomputes the path.
7. Output: joint cost and finish-date confidence curves.
8. It ranks the drivers — telling you which risks to attack first.
9. It's only as good as the CPM schedule it runs on.