Cost Risk — Estimate Ranging with Monte Carlo
A beginner's guide to Monte Carlo cost risk analysis — range your uncertain cost items, simulate the project thousands of times, and read the contingency straight off the resulting confidence curve. Built on AACE International RP 118R-21.
What Monte Carlo simulation is
The name comes from the casino: like spinning a roulette wheel over and over, the computer plays out the project thousands of times, each time drawing a slightly different value for every uncertain cost. One run might hit the high end on three items and the low on two; the next, the reverse. Collect all the totals and you get not a single number but the full range of what could happen — and how likely each outcome is.
How a Monte Carlo run works
- Range each uncertain item — Give every critical cost item a distribution (Lesson 11) — typically a triangular low / most-likely / high.
- Sample once from each — The computer draws a random value from each item's distribution — one plausible "version" of the project.
- Add up the total, and repeat — Sum the sampled items into one total cost. Then do it again — thousands of times (5,000+ is common).
- Read the distribution — The collected totals form a histogram and an S-curve. Pick your confidence level and read off the cost; contingency is the gap above the base.
Monte Carlo simulator
Three uncertain cost items, each with a low / likely / high range. This runs a real 5,000-iteration simulation in your browser and builds the distribution. Adjust the ranges and watch the percentiles move:
Monte Carlo cost-risk simulation
Try it yourselfEach line item is a triangular three-point estimate. 5,000 seeded iterations build the cost distribution; read the P-values and the P80 contingency.
Reading a Monte Carlo result
The output isn't one number, it's a curve — so the key decision is which confidence level to fund to. P50 means you'll overrun half the time; many organizations fund cost contingency to P70–P80 for a sensible safety margin. Choose deliberately, document it, and report contingency as "P80 = $X" rather than a bare percentage. And remember the result is only as good as the ranges you fed in — garbage ranges produce a beautifully precise wrong curve.
Ten things to remember
- Monte Carlo samples each uncertain input thousands of times.
- It builds the full distribution of total cost — not a single number.
- It needs ranged inputs (Lesson 10) with distributions (Lesson 11).
- Thousands of runs converge to a stable, dependable distribution.
- Output is a histogram and an S-curve of cumulative probability.
- Default: base $750k, mean ~$833k, P80 $889k → $139k contingency.
- Choose a confidence level to fund to — often P70–P80 for cost.
- Report "P80 = $X," not a bare percentage.
- Right-skew shows overruns are likelier than underruns.
- Precision isn't accuracy — the curve is only as good as the inputs.
Glossary
- Confidence level
- The P-value chosen to fund to.
- Convergence
- Results stabilizing as runs increase.
- Inherent risk
- The base variability of the estimate's items.
- Iteration
- One simulated version of the project.
- Monte Carlo simulation
- Sampling inputs many times to build an outcome distribution.
- P-value (e.g. P80)
- Cost with that % chance of not being exceeded.
- Right-skew
- A longer tail toward higher cost.
- S-curve
- Cumulative probability of total cost.