Glossary
Contingency vs Management Reserve
Contingency covers known unknowns inside the project budget; management reserve covers unknown unknowns above it. A practitioner guide to the difference, who controls each, how drawdown works, and why conflating them obscures real performance.
Quick comparison — contingency vs management reserve at a glance.
| Contingency | Management reserve | |
|---|---|---|
| Covers | Known unknowns — risks already identified and quantified in the risk register | Unknown unknowns — scope changes that no risk analysis could have foreseen |
| Held inside the project budget? | Yes — part of the approved budget | No — held above the project budget by the sponsor |
| Owned by | Project manager | Sponsor / client / change-control board |
| Sized by | Quantitative risk analysis (typically gap between P50 and base estimate, or P80 and base, depending on policy) | Sponsor policy — typically 5–15% of project budget on UK infrastructure |
| Drawn down by | Project manager, against entries in the risk register, without formal change request | Formal change-control process; sponsor approval required |
| Visible in EVMS / VAC? | Yes — tracked as part of EAC | Generally no — sits outside the performance measurement baseline |
| Common policy reference | AACE 40R-08, HM Treasury Green Book, Class 1–5 estimate accuracy bands | PMI PMBOK 7, individual sponsor delegation rules |
Contingency and management reserve are both budget held above the base estimate, but they cover different types of uncertainty and are controlled differently. Contingency — sometimes called risk allowance or risk provision — is calculated from the quantified risk analysis. It covers the expected cost of identified risks that are likely but not certain to occur, and is typically sized at the difference between the P50 (or P80, depending on policy) and the base estimate. It is part of the project budget, owned by the project manager, and drawn down through the risk management process as risks are realised or their status changes. Management reserve, by contrast, covers genuinely unforeseen scope changes — the unknown unknowns that no risk analysis could have captured. It is held above the project budget by the sponsor or client organisation and is released only by formal change control.
The distinction matters for governance and accountability. A project manager can use contingency without a formal change request because it is already within their delegated budget — but they should still track which risks triggered the drawdown. Management reserve requires sponsor approval because it represents a change to the approved project budget. Conflating the two — raiding management reserve to cover overspend caused by poor risk management — is a governance failure that obscures the true performance of the project.
In practice, the boundary between contingency and management reserve is not always clean, particularly at early project stages when scope is still developing. Some organisations define a third tier — design development allowance (DDA) — to cover cost growth from design development between RIBA stages, which is distinct from risk contingency. The key principle is that every pound of budget held above the base estimate should have a clear definition of what it is for, who controls it, and what process governs its use. Without this, contingency becomes a slush fund that absorbs overruns without generating insight about what is going wrong.
Frequently asked
- What is the difference between contingency and management reserve?
- Contingency is held inside the project budget to cover known, quantified risks (known unknowns) and is owned by the project manager. Management reserve is held above the project budget by the sponsor to cover genuinely unforeseen scope changes (unknown unknowns) and requires formal change control to release. Contingency is sized from the QRA — typically the gap between the P50 or P80 cost and the base estimate. Management reserve is set as a policy percentage by the sponsor.
- Who controls contingency vs management reserve?
- The project manager controls contingency within their delegated budget — they can draw it down without a formal change request, although every drawdown should be tracked back to the risk register. The sponsor or client organisation controls management reserve and must approve its release through formal change control because using it represents a change to the approved project budget.
- Are management reserve risks identified?
- No. Management reserve covers risks and scope changes that have not been identified — the genuinely unforeseen events that no risk analysis could have captured. If a risk is identifiable and quantifiable enough to be in the risk register, it belongs in contingency, not management reserve. Conflating the two is a governance failure that obscures project performance.
- How much contingency vs management reserve should a project hold?
- Contingency is calculated, not chosen — it comes out of the quantitative risk analysis. The amount depends on the risks identified, their probabilities and impacts, and the confidence level the sponsor has chosen (P50 vs P80 vs P95). Management reserve is set by sponsor policy and is typically 5-15% of the project budget on UK infrastructure programmes, sized for the residual uncertainty after a thorough risk-identification exercise. Holding less than that on a complex programme suggests either confident scope or under-recognised risk.
Related terms
Putting these techniques into practice?
SOMA provides independent project controls consultancy for UK programmes. We can help you apply QRA, EVM, schedule risk analysis, and more.