Allowances, contingency and reserves: make the project budget explainable
Separate incomplete scope from uncertainty, avoid counting the same risk twice and follow a worked EUR budget through a change.
A budget with a single line called “contingency” can hide several different decisions. Some work is known but not fully specified. Some costs depend on uncertain events. The owner may also retain funding that the delivery team cannot spend without further approval. These amounts need explicit boundaries, even when the organisation uses different names for them.
GAO's Cost Estimating and Assessment Guide emphasises a documented technical baseline, assumptions, risk analysis and updates using actual information. RICS NRM 1 provides a construction cost-planning framework with separately identified risk allowances. Neither source makes an unexplained percentage a reliable estimate. GAO guide · RICS NRM.
Define the terms before adding the numbers
For the example below, an allowance is an amount already included for required work whose selection or quantity is not final. Risk contingency is separately identified funding for uncertainty within the defined project scope. An owner reserve is additional funding controlled outside this example's delivery budget.
These are the article's working definitions. Contract terms such as provisional sum, and formal management-reserve rules in particular frameworks, may carry different consequences. State the actual rules beside the budget rather than assuming everyone interprets the labels alike.
A worked budget with no double counting
Consider a fictional refurbishment, with all amounts in EUR and excluding VAT and financing:
- Defined-scope estimate: EUR 200,000. This already includes EUR 15,000 for lighting whose final selection is pending.
- Separately identified risk contingency: EUR 20,000.
- Controlled delivery budget: EUR 220,000.
- Additional owner-controlled reserve: EUR 10,000.
- Total funding provision for this example: EUR 230,000.
Adding the lighting allowance again would overstate the total by EUR 15,000. Calling all EUR 30,000 of contingency and reserve “available to the contractor” would misrepresent approval rights.
Now the lighting selection is agreed at EUR 18,000. The increase against its existing allowance is EUR 3,000, not EUR 18,000. If it is an approved development of the original requirement and the budget rules permit contingency use, record the transfer: scope allocation becomes EUR 203,000 and remaining contingency EUR 17,000. The controlled total remains EUR 220,000.
If the owner instead adds an entirely new lighting area, assess it through change control. Do not automatically disguise extra scope as the original uncertainty becoming clearer.
| Budget component | Before | After approval |
|---|---|---|
| Defined scope, including lighting | 200,000 | 203,000 |
| Lighting allowance within that scope | 15,000 | 18,000 |
| Remaining contingency | 20,000 | 17,000 |
| Controlled total (scope + contingency) | 220,000 | 220,000 |
| Owner-controlled reserve | 10,000 | 10,000 |
| Total funding provision | 230,000 | 230,000 |
The lighting row is included in the defined-scope row. Do not add it again. Figures are fictional; VAT and financing are excluded.
Connect contingency to specific uncertainties
For each material risk, record the cause, possible cost effect, timing, owner and response. Distinguish “the existing slab condition is unknown” from “the estimate is not finished”: the first may need investigation; the second may need completed estimating work.
Suppose a risk has an assessed 40% probability of a EUR 20,000 cost. Its simple expected value is EUR 8,000. That is a probability-weighted planning value, not a promise that EUR 8,000 will cover the event. If the event happens at the assumed cost, it needs EUR 20,000.
Adding expected values also does not establish an 80% confidence budget. Correlated risks, cost ranges and the chosen model matter. For an important project, use a documented risk-analysis method with competent input rather than presenting a spreadsheet sum as statistical assurance.
Manage the balance throughout the project
A drawdown record should identify the risk or approved reason, amount, decision-maker, date, affected cost line and remaining balance. Preserve the original baseline so readers can distinguish an approved budget movement from an improving forecast.
At each review, compare the remaining uncertainty with the remaining contingency. A low balance near completion can be reasonable if major risks have retired. The same balance before opening up an unknown building fabric can be a warning.
Avoid including the same price risk in supplier rates, a separate escalation line and contingency without explanation. Equally, do not omit an exposure merely because two people each assumed the other had included it. A short assumptions register is often more valuable than another decimal place.
Questions to ask at the next review
Can each allowance be tied to a defined requirement and an expected decision date? Which risks have reduced after surveys or procurement? Who can approve a transfer? Does the latest forecast include committed orders, expected final costs and the unresolved exposure?
Keep the cash-flow forecast separate: approved funding is not necessarily cash in the bank when a payment falls due. Continue with Within budget but out of cash.
Enable JavaScript to use reading progress and usefulness ratings.
