Contingency management: who owns construction risk allowances
Admin · 22 October 2026
Illustrative image. Photo by LinkedIn Sales Solutions on Unsplash. Unsplash License.
A risk allowance can appear in a cost report without a clear explanation of what it represents or who may authorise its use. That ambiguity can weaken both forecasting and decisions. One team may treat the allowance as a budget for additional scope, while another regards it as part of the estimate’s treatment of uncertainty. Before discussing how much remains, the project needs a shared definition and governance arrangement.
For clients and project leadership, the practical task is to connect the allowance to the estimate basis, risk information and approval process. Appropriate cost, commercial and financial professionals should establish the method for the actual project. The management framework should explain responsibilities and evidence without implying that every project uses the same category, calculation or release rule.
Define the terms used
Agree the meaning of contingency and related terms within the project’s reporting arrangements. Identify how the estimate distinguishes base scope, uncertainty and other relevant components. The terminology may differ between organisations. A shared glossary is useful only if it reflects the actual method and is applied consistently across the cost report and decision papers.
State the scope and perspective. An allowance held by a client may serve a different purpose from a provision within a contractor’s forecast. Avoid assuming that the same label establishes the same responsibility or contractual position. Appropriate advisers should clarify the actual arrangements and their treatment before teams combine or compare figures.
Explain the estimate basis
Record what information and assumptions informed the allowance, using the project’s chosen method. Identify the date and scope of the assessment and the expertise involved. A percentage carried forward from an early stage can acquire apparent authority simply through repetition. Review whether it still reflects the current design, procurement and evidence.
The government’s Cost Estimating Guidance provides infrastructure estimating context, including attention to uncertainty and risk. It should inform appropriate professional consideration rather than be reduced to a universal percentage. The practical reporting need is a transparent explanation of what the allowance represents and how its basis changes as the project develops.
Connect risk ownership and funding decisions
A risk owner manages a defined issue or uncertainty through the project’s process. That role does not automatically give authority to approve expenditure or alter scope. Identify the relationship between risk management, estimate updates and spending approval. Keeping those responsibilities clear helps prevent an entry in a risk register from being mistaken for permission to proceed.
For consequential matters, name the person coordinating assessment and the authority required for the next commitment. The team should understand what evidence must accompany a request and which records need updating. A broadly worded instruction to manage within contingency can leave the decision route unclear and obscure the trade-offs leadership needs to consider.
Distinguish new scope from uncertainty
When a proposed cost arises, assess what has changed relative to the approved basis. The matter may concern a realised risk, clarified scope or a new client requirement. The actual contractual and financial treatment requires appropriate review. The management record should explain the facts and avoid classifying every pressure under whichever category makes the report easiest to balance.
Consider a hypothetical client request for additional operational space. The existence of an allowance does not establish whether the request belongs within the original scope or how it should be authorised. The project needs an assessment of the requirement, its consequences and the applicable decision process. The allowance is part of the financial picture, not the reasoning for approving the change.
Set a clear request process
Define the information required when a decision affects the allowance. The request may need the event or proposal, affected scope, assessment basis, options and recommendation, depending on the project. Keep the process proportionate while ensuring the decision maker understands what is being authorised. Identify unresolved information and any conditions attached to the decision.
Record the decision date, authority and references. Distinguish approval of an estimate update from an instruction to carry out work or an agreed commercial adjustment. These actions may follow different routes. Appropriate project roles should complete the necessary steps so the financial record does not imply an authorisation that the delivery arrangements have not provided.
Reconcile movements consistently
Show how the allowance moved between reporting periods and explain the basis of consequential changes. Identify the relevant decisions and updated assessments. Avoid double counting a matter in both a package forecast and an unchanged risk allowance without review. The appropriate cost professionals should establish the method and reconciliation for the project.
Retain earlier issued reports and the supporting assumptions. A later reviewer should be able to understand why the position changed. Where terminology or methodology changes, explain the effect before comparing totals. A clear movement record is more useful than a single remaining balance that conceals the decisions and evidence behind it.
Review the remaining exposure
As design and procurement develop, review which uncertainties have reduced, changed or emerged. The assessment should reflect current evidence rather than an assumption that exposure declines automatically with time. Some dependencies may become more consequential as commitments approach. Ask risk and cost specialists to explain the effect through the project’s chosen method.
Do not treat an apparently unused balance as evidence that it is available for unrelated scope without assessment and authority. Leadership needs to understand the remaining project position and the consequences of any proposed commitment. The decision should follow the applicable governance and qualified financial advice.
Make reporting decision-ready
Provide a concise summary of the allowance’s purpose, current assessment and consequential decisions required. Link to supporting detail rather than reproduce the entire risk register. Identify who can resolve missing evidence and when it is useful. The reader should be able to distinguish the estimate’s uncertainty from work already committed and proposals awaiting approval.
Where contributors disagree about treatment, record the question and refer it to the appropriate authority. Avoid resolving a substantive difference by choosing the value that fits the available budget. The report should support an honest account of the project, even when the evidence indicates a difficult decision.
Preserve the learning
At closeout, review the original basis, material movements and actual events using suitable expertise. Identify where assumptions were supported and where the process missed consequential information. The aim is to improve future assessment and governance, not to claim that one final balance proves the original allowance was universally correct.
Keep the lessons linked to context. Project type, information maturity and procurement arrangements can affect their relevance. A useful contingency process gives leadership a traceable account of uncertainty, decisions and remaining responsibilities. It connects professional estimating with controlled commitments, so the allowance supports management rather than becomes an unexplained pool of money in the report.
Challenge unsupported certainty
Ask whether the report’s presentation matches the evidence available. A single figure can be required for a particular approval while the underlying estimate remains uncertain. Appropriate professionals should explain that relationship and the limitations of the information. The management summary should preserve consequential qualifications, so leadership does not interpret a reporting convention as proof that the remaining exposure is precisely known.
Where further investigation could materially improve the assessment, identify the action and decision it supports. The project may need better survey information, a clarified requirement or a firmer supplier proposal. Assign the owner and useful date, then review whether the new evidence changes the position. This connects allowance management to practical reduction of uncertainty rather than treating every review as a negotiation about how much balance should remain in the report.
