Framework library · Risk management and assessment
Monte Carlo simulation
A single estimate hides how uncertain it is. Monte Carlo simulation gives each uncertain quantity a range, draws from those ranges thousands of times, and adds them up each time, so the answer is a distribution: how likely the project is to come in under budget, and how much contingency it really needs.
Use it when
- A budget, schedule or forecast is the sum of several uncertain pieces and you need to know how much contingency to hold.
- A board asks "how confident are you?" and a single number cannot answer.
- You want to know which uncertainty drives the spread, so the effort to reduce it goes to the right place.
Avoid it when
- You cannot give honest ranges. A simulation of guesses is a precise-looking guess.
- The pieces move together (for example, every cost rises with one contractor's rates). This tool draws them independently, which understates the spread. Model the common driver as its own quantity instead.
- The risk is a single event, not a spread of outcomes. Put it in the risk register.
How to run it
Break the total into pieces
Five to fifteen pieces, each one that someone can estimate: civil works, equipment, labour, permits.
Give each piece three numbers
The lowest it could plausibly be, the most likely, and the highest it could plausibly be. Plausible means a one-in-twenty chance of being outside, not the worst imaginable.
Ask the people who know
Ranges from the engineer who has built it before are worth more than ranges from the spreadsheet. Ask for the highest number first; people anchor on the most likely.
Set the target
The budget or deadline you are testing against.
Read the distribution
P50 is the median; P80 or P90 is what most organisations budget to. The chance of exceeding the target is the number the board wants.
Work on the drivers
The chart of what drives the spread shows which ranges matter. Narrow those with better information, or carry the contingency.
Work through it
Answer the questions below, or load the worked example to see a finished one. The drawing updates as you type. Export the result as a PowerPoint deck, a Word document, an Excel workbook, a PDF or plain text.
What you type stays in this browser, so you can close the page and come back to it. It is not sent to Blue Prysm or anyone else, and the exports are made here, on your device. Privacy policy.
Mistakes to avoid
- Ranges that are too narrow. People are overconfident. Widen anything that has never been done before.
- Adding the "most likely" values and calling it the estimate. The sum of most-likely values is usually below the P50.
- Treating the output as fact. It is only as good as the ranges, and it ignores anything you did not list.
Where it comes from
Developed at Los Alamos in the 1940s by Stanislaw Ulam, John von Neumann and Nicholas Metropolis, and named in Metropolis and Ulam, "The Monte Carlo Method", Journal of the American Statistical Association 44(247), 1949. Brought into business investment decisions by David B. Hertz, "Risk Analysis in Capital Investment", Harvard Business Review, January to February 1964. Source.
Use it with
Work through it with us
The frameworks here are free to use as they stand. If you would rather work through the question behind this one with us, these are the ways an engagement starts.