Expected Monetary Value: price uncertainty without hiding it

What Expected Monetary Value means

Expected Monetary Value, or EMV, is a probability-weighted view of an uncertain event. It asks what monetary result the event would contribute on average if similar circumstances could occur many times. The calculator uses probability and full impact, then returns the weighted amount for one risk. A threat has a negative impact; an opportunity has a positive one.

EMV is different from the amount you lose or gain if the event happens. A 30% chance of a 50,000 cost has a full impact of 50,000 and an EMV of negative 15,000. If the event fires, the project does not receive a 15,000 invoice. It experiences the full 50,000 consequence. The weighted value helps compare exposures and size a portfolio reserve; it does not cap one event’s outcome.

The calculation

EMV = Probability × Impact
EMV = (Probability ÷ 100) × Impact

The calculator expects probability as a percentage, so enter 30 for 30%, not 0.30. Enter the full financial consequence in the impact field. Use a negative number for a threat such as a delay cost and a positive number for an opportunity such as a saving. Keep currency, time horizon and valuation boundary consistent. If a probability came from a qualitative scale, document how the scale was translated before presenting the money.

Worked threat and opportunity readings

For a supplier delay, enter probability 30 and impact -50,000. EMV is 30 ÷ 100 × -50,000, which equals -15,000. As a portfolio planning signal, the project may carry 15,000 of expected exposure or spend up to that amount on a response if the response can materially reduce the risk. A response costing 8,000 may be attractive if it lowers probability or removes the event. A response costing more may still be justified if the deadline, safety or customer consequence is severe.

For an automation opportunity, enter probability 40 and impact 20,000. EMV is +8,000. That is average upside, not permission to subtract 8,000 from the approved budget before anyone captures it. The opportunity may need an owner, a decision window and investment. Compare the cost of pursuing it with the probability-weighted gain and with the work it would displace.

EMV and contingency reserve

When a risk register contains several known-unknowns, their probability-weighted impacts can inform contingency reserve. Threats are negative and opportunities positive, so net EMV may be negative when threats dominate. Some organisations express the reserve as a positive funding amount by taking the magnitude of negative exposure while retaining signed values in the register.

Do not confuse contingency reserve with management reserve. Contingency is tied to identified uncertainty within approved scope and is generally managed by the project manager. Management reserve is outside the cost baseline and covers unforeseen work under organisational governance. The exact authority and accounting treatment vary, but the conceptual boundary should stay clear.

Summing EMV does not claim that every risk will occur, and it does not describe the worst case. A group of threats may be correlated by one supplier, market shock or design decision. In that situation, adding individual EMVs can hide a combined scenario. For material decisions, use scenario analysis or simulation that can represent dependencies and show both the average exposure and the plausible downside.

Turn the value into a risk conversation

Start with the event statement, cause, consequence and time window. Probability without a defined event is not comparable. Ask whether impact is gross or residual, one-time or recurring, and whether schedule, quality or reputation effects have been monetised. Record whether the number is evidence-based, a workshop estimate or a conservative planning value.

Then compare the response with the avoided exposure. If a threat has an initial EMV of -15,000 and a 5,000 response reduces probability from 30% to 5%, residual EMV is -2,500. The response avoids 12,500 of expected exposure before secondary effects. But a low EMV event can still deserve urgent attention when its full impact threatens safety, compliance, a hard launch date or the project’s licence to operate.

Limits of probability-weighted money

EMV is a long-run average, not a prediction of what must happen on this project. It works best when probabilities are meaningful, impacts use a common monetary basis and the decision-maker accepts averaging across outcomes. It is not a sufficient sole rule for one-shot, irreversible or catastrophic choices. Show the full impact, time to detect, recovery path and risk appetite as well.

Probability estimates can create false precision. A team may agree that an event is possible, but “possible” is not automatically 30%. Define organisational anchors, use observed data where available and test sensitivity with plausible low and high values. If a small probability change flips the recommendation, improving the evidence may be more valuable than arguing over a decimal.

Mistakes to avoid

• Entering a decimal. The field expects 30 for 30% and performs the conversion.
• Entering EMV as impact. Impact is the full consequence if the event occurs.
• Dropping the sign. Negative threats and positive opportunities must remain distinguishable.
• Budgeting the worst case as reserve. Reserve is a portfolio planning decision; one event can still consume its full impact.
• Hiding non-monetary harm. Keep safety, trust, compliance and strategic effects visible.

Keep the register alive

Review the reserve as the risk register changes. When a threat expires without occurring, release its expected value rather than leaving an unexplained cushion in the forecast. When a response reduces probability or impact, recalculate from the residual exposure and record both the before-response and after-response values. If a new correlated threat appears, do not simply add it as though every event were independent. Discuss the common cause, maximum combined consequence and whether a scenario allowance is more honest than a row-by-row sum. This reconciliation keeps the reserve connected to named uncertainty and gives governance bodies a defensible explanation for movements between reporting periods.

For each EMV entry, store the event wording, probability source, impact basis, owner, response, residual reading and review date. Recalculate when evidence changes rather than overwriting the old number. At closeout, compare the estimate with what occurred and ask whether the miss came from probability, impact, correlation or an omitted event. Used that way, EMV becomes a repeatable bridge from uncertainty to proportionate funding and action.