Probabilistic estimating, in plain language.
Short guides on setting a risk reserve you can defend. Every example is worked out with real calculations on fictional cases, and each guide says where its numbers come from.
All guides
Quantitative cost risk analysis: a practitioner's guide
How to turn a single cost estimate into a range of outcomes with probabilities, and how to turn that range into budget decisions. With a complete worked example from a fictional road and bridge project.
Read the guideP50, P80 and P90 explained for decision makers
A P80 is not the estimate plus 20%. What each confidence level really means, how to pick the right one for a budget, and the mistakes that cost boards money.
Read the guidePoint estimates hide risk: why boards need ranges
A single number feels firm but rarely holds. On a fictional $120 million project it has a 1% chance. How a range changes the budget decision, and how to present one to a board.
Read the guideHow to calculate contingency with Monte Carlo, step by step
From estimate ranges and risk events to a P80 contingency, in plain Excel: the formulas, a worked example and the governance rules that make the number useful.
Read the guideWhy a percentage on top is not a risk budget
Ten percent on top sounds prudent. On two fictional infrastructure projects it holds in only about a third of outcomes, and each needs a different amount. A percentage cannot tell you that; a simulation can.
Read the guideHow to set a P80 contingency, step by step
From cost items and risks to a reserve your board can defend: seven steps, with a worked example from a fictional tunnel project.
Read the guideCorrelation: the setting that moves your P90
Leave correlation out and the S-curve still looks fine. It is just too narrow. In our example, the P90 reserve rises by about 70% once items move together.
Read the guideWhy the sum of EMVs is not a risk reserve
Probability times impact, added up, gives a total that almost never happens. Two reasons it makes your reserve too small, and what to do instead.
Read the guideMerge bias: why parallel paths make you late
Three teams are each 80% sure of week 40. The milestone that waits for all three has about a coin-toss chance. How merge bias works, and what to do about it.
Read the guideExcel tools, add-ins or dedicated risk software?
Three kinds of tools run a Monte Carlo risk analysis. A fair comparison, including when a dedicated product is the better choice, and five questions to ask before you pick one.
Read the guideContingency vs management reserve: what each one covers
Two reserves on top of the estimate, often treated as one pot. What each one covers, who holds it, how to size it, and the release rules that keep it from being spent too early.
Read the guideQSRA in Excel: quantitative schedule risk analysis
A schedule gives you one finish date; a QSRA tells you how likely it is and which date you can commit to. What you need, the steps, how to read the results, and when Excel is enough.
Read the guideBid/no-bid decisions and pricing a tender under risk
Whether to bid at all, and at which price: a simple bid/no-bid scorecard, then how win probability, margin and cost risk combine into the price with the highest expected profit.
Read the guideAACE 40R-08 explained: the principles of contingency estimating
AACE Recommended Practice 40R-08 sets out what any good contingency estimate should do, whatever method you use. What it covers, its principles in plain language, and what it means for your project team.
Read the guideWant to see it before you read? Run a Monte Carlo on our homepage: 10,000 futures of a small fictional project, in your browser. New to the terms? The glossary explains P80, contingency, EMV and more.