Project budgets commonly include a contingency amount. The number can create false comfort if nobody has defined the uncertainty it addresses or the authority needed to spend it. A disciplined reserve should connect known estimation limits with a process for responding when the actual cost becomes clearer.
Separate uncertainty from omitted scope
A contingency is a poor substitute for items that management already knows the project requires. Installation, commissioning and working capital should appear explicitly where they form part of the plan. The reserve can then address uncertainty around defined work. An illustrative equipment budget might include a range for ground conditions while separately costing the electrical connection. Combining both under a single contingency percentage makes it harder to see whether the project is complete and whether the allowance is sufficient for the uncertainty it is meant to carry.
Build the allowance from the risk register
The budget team should connect important cost risks with supporting estimates and potential responses. Some exposures depend on technical design; others involve schedule, supplier pricing or operating assumptions. The method should avoid counting the same risk in several places without explanation. A clear link between the risk register and the cost model allows reviewers to examine the largest uncertainties first. It also helps management distinguish a risk that has been resolved from one that simply has not yet produced an invoice.
Set release and escalation rules
Routine cost adjustments may fit within management authority, while material changes require a fresh approval. The reserve policy should state who can authorise use, what evidence accompanies the request and when the overall business case needs reconsideration. A contingency should not quietly finance a larger project. If management adds capacity or changes the specification, the decision should be evaluated as scope change. Keeping these routes separate preserves the meaning of the original investment approval and makes subsequent reporting more informative.
Show the reserve movement in reporting
The board should see the opening allowance, approved uses, remaining exposure and closing balance. A low remaining balance may be acceptable when the main uncertainties have been resolved, and concerning when substantial work remains. ALFA's whitepaper describes programmes with different stages of preparation, so no universal contingency figure follows from the ecosystem narrative. Each project needs a reserve appropriate to its evidence and scope. The reporting goal is to show how uncertainty has changed, rather than celebrate an unspent balance without considering the risks still ahead. A supplier saving should not automatically replenish contingency unless management has confirmed that it reduces the relevant exposure; otherwise the report may count the same favourable change twice.
