Expected monetary value is a core quantitative tool in RM8, and the July 2025 summative assessment tested it directly. Question 4, worth 20 marks, gives a construction project’s risk register and asks for the expected monetary value of each risk, the aggregated figure, and a mitigation priority. The question is described in our own words below; the answers are TheronGroup’s.
The question
A construction project team has listed five risks, each with a probability of occurring and a rand impact if it does.
| Risk | Probability | Impact if it occurs |
|---|---|---|
| Project delay | 35% | R150 000 |
| Strike | 20% | R72 000 |
| Cost variation | 45% | R110 000 |
| Fire | 12% | R430 000 |
| System failure | 25% | R56 000 |
4.1 (10 marks). Work out the average impact, or expected monetary value (EMV), of each risk on a non-aggregated basis, showing every working.
4.2 (5 marks). Work out the EMV of the five risks on an aggregated basis.
4.3 (5 marks). Say which risk the team should mitigate first, and why.
4.1 EMV for each risk, non-aggregated
Two conventions are settled before any multiplication. The impacts are all in rand, so they are already in a common unit, which is the condition for adding them later; and each percentage is converted to a decimal before it is used. The question uses “average impact” and “expected monetary value” for the same quantity, and so does the answer.
The EMV of a risk is its probability multiplied by its impact if it occurs.
EMV(i) = p(i) × I(i)
Project delay = 0,35 × R150 000 = R52 500
Strike = 0,20 × R72 000 = R14 400
Cost variation = 0,45 × R110 000 = R49 500
Fire = 0,12 × R430 000 = R51 600
System failure = 0,25 × R56 000 = R14 000
| Risk | Probability | Impact | EMV | Rank |
|---|---|---|---|---|
| Project delay | 0,35 | R150 000 | R52 500 | 1 |
| Fire | 0,12 | R430 000 | R51 600 | 2 |
| Cost variation | 0,45 | R110 000 | R49 500 | 3 |
| Strike | 0,20 | R72 000 | R14 400 | 4 |
| System failure | 0,25 | R56 000 | R14 000 | 5 |
Those five figures are the whole answer to 4.1. Non-aggregated means each risk is reported on its own, so no total belongs here; the question asks for the total separately in 4.2.
Where the marks are lost. Ten marks for five multiplications means the marks are in the workings, not the answers. A table of five EMVs with no substitution shown, or a probability left as “35” instead of 0,35, gives away most of them.
4.2 EMV on an aggregated basis
The aggregated EMV is the sum of the individual EMVs.
EMV(total) = Σ p(i) × I(i)
= R52 500 + R14 400 + R49 500 + R51 600 + R14 000
= R182 000
The aggregated EMV of the risk register is R182 000. Three points about it earn the remaining marks.
- It is an average, not a worst case. If all five risks occurred, the cost would be R150 000 + R72 000 + R110 000 + R430 000 + R56 000 = R818 000. The aggregated EMV is R182 000 ÷ R818 000 = 22,25% of that total exposure.
- It is a static figure. Adding EMVs combines single numbers; it does not combine the risks themselves, so it says nothing about how the total cost is spread.
- It belongs on top of a base cost estimate. R182 000 is the risk allowance the average project of this kind would need, an overlay on the base budget, not a substitute for a full risk model of the project.
Where the marks are lost. Presenting R182 000 as “the expected cost” without saying what it is not. A candidate who adds that the maximum exposure is R818 000, and that R182 000 is an average over outcomes, shows the marker the figure has been understood.
4.3 Which risk to mitigate first
Project delay, because at R52 500 it carries the highest EMV, and EMV is the measure that weighs likelihood and consequence together rather than either one alone.
The answer should not stop there, because the register makes the decision close.
Gap between delay and fire = R52 500 − R51 600 = R900
As a share of the leader = R900 ÷ R52 500 = 1,71%
Fire impact ÷ delay impact = R430 000 ÷ R150 000 = 2,87 times
A gap of 1,71% is well inside the precision of a probability estimated at 12% or 35%, so on EMV alone the two risks are effectively tied. Fire, though, has by far the largest single impact: R430 000 is almost three times the cost of a delay and may be more than the project’s contingency can absorb in one event, while delay costs arrive gradually and can be managed as they come. Smith and Merritt make the same point when they plot total loss against likelihood on a risk map instead of ranking on the product: ranking by expected loss alone can bury a low-likelihood, high-impact risk.
| Ranking rule | Order | What it is good for |
|---|---|---|
| EMV, p × I | Delay, fire, cost variation, strike, system failure | Allocating a mitigation budget across risks |
| Impact alone, I | Fire, delay, cost variation, strike, system failure | Identifying what the project could not survive |
| Risk map, I against p | Delay for mitigation; fire flagged on its own | Keeping both dimensions visible |
The full answer is therefore two sentences. Mitigate project delay first, because it has the highest EMV. Treat fire separately on survivability grounds, through prevention, insurance and an emergency response, because its single impact may exceed what the contingency can absorb, and its EMV is only R900 behind.
Where the marks are lost. Naming project delay and stopping. Five marks for “which and why” are not earned by one word; the marker is looking for the reason (highest EMV), and the strongest answers notice that fire is R900 behind with nearly three times the impact.
What the R182 000 hides
The question does not ask for this, but it is where an answer moves from operating the formula to interpreting it. With five independent risks that either occur or do not, there are 2⁵ = 32 possible outcomes, few enough to work out exactly.
Two of them show the method. Each outcome’s probability is the product of p for the risks that occur and (1 − p) for those that do not.
P(nothing occurs)
= 0,65 × 0,80 × 0,55 × 0,88 × 0,75
= 0,188760, or 18,88%
P(strike and cost variation only, total R72 000 + R110 000 = R182 000)
= 0,65 × 0,20 × 0,45 × 0,88 × 0,75
= 0,038610, or 3,86%
Weighting all 32 totals by their probabilities returns a mean of exactly R182 000, which confirms the aggregated EMV. The spread around that mean does not need the full table: for independent risks the variance is the sum of p(1 − p) × I² for each risk.
| Risk | p(1 − p) | I² (R²) | Contribution to variance (R²) |
|---|---|---|---|
| Project delay | 0,2275 | 22 500 000 000 | 5 118 750 000 |
| Strike | 0,1600 | 5 184 000 000 | 829 440 000 |
| Cost variation | 0,2475 | 12 100 000 000 | 2 994 750 000 |
| Fire | 0,1056 | 184 900 000 000 | 19 525 440 000 |
| System failure | 0,1875 | 3 136 000 000 | 588 000 000 |
| Total | 29 056 380 000 |
Standard deviation = √29 056 380 000 = R170 459
As a multiple of the mean = R170 459 ÷ R182 000 = 0,94
Fire's share of the variance = 19 525 440 000 ÷ 29 056 380 000 = 67,2%
Reading the cumulative distribution of the 32 outcomes gives the rest.
| What the project team might ask | Aggregated EMV | Full distribution |
|---|---|---|
| Average total cost of these risks | R182 000 | R182 000 |
| Chance that none of the risks occurs | Cannot say | 18,88% |
| Chance the total is exactly R182 000 | Implies it is typical | 3,86% |
| Chance the total exceeds R182 000 | Cannot say | 33,92% |
| Median total | Cannot say | R150 000 |
| Contingency that covers 90% of outcomes | Cannot say | R430 000, or 2,36 times the EMV |
The spread is almost as large as the mean, two-thirds of it comes from fire, and a contingency set at the R182 000 aggregate would fall short on roughly one project in three. That is the case, in numbers, for treating fire on its own and not only through the EMV ranking.
Studying RM8
RM8 has worked solutions for the summative, formative and project assessments from 2019 to 2026, each calculation set out with its substitution and interpretation in the same way. The RM8 course is R1 450 for the complete module.