EMV Calculator
From the probability of a risk and its financial impact, compute the expected monetary value of a project risk or decision.
Input Data
Results
At a glance:The Expected Monetary Value (EMV) Calculator converts an uncertain risk or opportunity into a comparable amount: EMV = probability × impact. Positive impact = opportunity/gain, negative = threat/loss. EMV is central to project risk management and decision-tree analysis, letting risks be ranked, compared and summed on a common money scale to size a contingency reserve. It is a long-run average, of limited use for a one-off major event, and excludes risk tolerance and tail risk — pair with scenario and sensitivity analysis.
Formula
EMV = probability × impact.
EMV_total = Σ (p_i × impact_i).
$$EMV = Probability \\times Impact$$$$EMV_{total} = \\sum_{i} (p_i \\times Impact_i)$$How to Use
- Enter the probability the risk or event occurs.
- Enter the financial impact (positive for gain, negative for loss).
- View the computed expected monetary value.
EMV at different probability and impact combinations
| Probability | Impact (HK$) | EMV (HK$) | Type |
|---|---|---|---|
| 30% | +100,000 | +30,000 | Opportunity |
| 30% | −100,000 | −30,000 | Threat |
| 60% | +200,000 | +120,000 | Opportunity |
| 10% | −500,000 | −50,000 | Threat (low prob, high impact) |
Case Studies
Case 1: Convert a project risk into money
A project identifies a risk: 30% chance of a weather delay triggering a penalty, costing HK$100,000 if it occurs. Convert this uncertain threat into a comparable amount.
EMV = 30% × (−100,000) = −HK$30,000. Negative means an expected-cost threat.
Similarly, a 40% chance of early completion worth HK$50,000 gives EMV = 40% × (+50,000) = +HK$20,000. Netting threat (−30,000) and opportunity (+20,000) gives net EMV −HK$10,000, suggesting about HK$10k contingency buffer for these two.
Case 2: Same EMV, totally different risk
Risk A: 50% chance of HK$20,000 loss, EMV = −10,000. Risk B: 2% chance of HK$500,000 loss, EMV = −10,000. Identical EMV.
But nature differs vastly: A is a likely small loss, bearable, almost a cost of doing business; B is a rare catastrophe that could cripple the project or firm. Judging both as '−10,000' is the expectation trap — it averages away tail-risk damage.
Practice: (1) EMV depends heavily on subjective probability/impact estimates; (2) it is a long-run average, not what a one-off decision experiences; (3) for B-type low-prob high-impact risks, use scenario analysis and consider transfer (insurance), avoidance or a larger buffer, not EMV alone. EMV is the building block of decision trees. Pair with EVM and business-valuation calculators for project/investment assessment. Estimation only.
FAQ
What do positive and negative EMV mean?
The sign shows whether the event is an opportunity or a threat. Positive impact (gain) gives positive EMV — an opportunity, e.g. an early-completion bonus. Negative impact (loss) gives negative EMV — a threat, e.g. delay penalty, price rise, breakdown. In practice list all identified risks, compute each EMV, then sum: opportunities and threats net off to the project's net risk exposure. That net guides whether to reserve contingency, how much, and which high-EMV risks (either sign) to handle first.
EMV is just 'probability × impact' — what are its limits?
Simple but with key limits. First, it heavily depends on the probability and impact estimates, which are often subjective and poorly supported — wrong inputs mislead. Second, EMV is a long-run average: if the same situation repeated infinitely, the average tends to EMV; but for a one-off major decision you actually experience either 'occurs' or 'not', never the average. Third, it ignores risk tolerance and tail risk: a 5% chance of a HK$10M ruinous loss may have a small EMV yet bankrupt a firm — do not judge by expectation alone. So EMV is good for ranking and screening; major decisions need scenario and sensitivity analysis plus judgement.
How is EMV related to decision-tree analysis?
EMV is the basic operation of decision-tree analysis. A decision tree evaluates a chain of linked decisions and uncertain events: decision nodes (your choices) and chance nodes (probability-driven outcomes) branch out. At each chance node, the EMV of each branch (probability × impact) is summed to its expected value; then working right-to-left you compute each path's overall EMV and pick the highest (or lowest loss). So EMV is the building block; this calculator computes a single event's EMV, while a decision tree organises many such EMVs for multi-stage analysis.
How to estimate probability and impact? Is EMV still useful if rough?
Since EMV = probability × impact, input quality decides credibility ('garbage in, garbage out'). Estimating probability, from reliable to subjective: (1) historical data — e.g. how often this delay occurred in past similar projects; (2) expert judgement and team consensus, using bands (high/medium/low ≈ 70%/40%/10%) to reduce arbitrariness; (3) for decomposable risks, event trees. Impact should cover all consequences — not just direct loss (penalty) but knock-on effects (idle resources, reputation) — quantified in money; hard-to-quantify at least flagged qualitatively. Techniques: (1) use ranges not points (loss 80k–120k) and see the EMV range; (2) sensitivity analysis — move probability/impact and see how much EMV changes; if a conclusion is very sensitive to one input, estimate that one more carefully. Is it still useful if rough? Yes, but know its place: EMV's value is not a precise prophecy but (1) a consistent framework forcing you to break vague worries into probability and impact; (2) a common ruler to rank risks and focus on high-EMV ones; (3) support for sizing contingency. Even imperfect inputs, the structured thinking helps. But it is a reference and starting point, not the sole basis — pair with scenario analysis and judgement. Estimation only.
After EMV per risk, how to set the contingency reserve?
Summing risk EMVs is a common start for the project's contingency reserve, but 'sum = reserve' is the crudest step; in practice add adjustments so you neither under- nor over-reserve. Logic: contingency is a buffer for identified risks (distinct from management reserve for unknown risks). The direct way is to sum all identified EMVs — net of threats' negative and opportunities' positive — giving a baseline of 'expected buffer needed'. E.g. three threats at −30k, −20k, −10k need about 60k. But corrections: (1) EMV is an average; risks are either-or, so if several hit together (worst case) the needed buffer far exceeds the sum — for high-risk projects use scenario analysis or Monte Carlo to see '90% confidence max needed', not just the mean; (2) tail risk (low prob, high impact) looks small in EMV but is devastating if it hits — for such risks consider transfer (insurance) or avoidance, not just reserve; (3) reserve should be reviewed dynamically as the project moves — risks pass or new ones appear, release unused buffer. Healthy approach: start from the EMV sum, calibrate the worst case with scenario analysis, arrange separately for tail risk, and review periodically. EMV gives the quantitative base; the final amount needs risk tolerance and management judgement. Estimation only.
Related Tools
References
Content review: Calculatorism Finance Team. Results are for reference only; please refer to the relevant authorities for the official figures.