T TASSCUBO
Contact Member LoginReviews
Join TASSCUBO

How to create a university capital project contingency release process

A capital project contingency is a controlled reserve, not an unallocated budget surplus. It exists to absorb defined uncertainty—such as latent site conditions, price escalation, design development, or regulatory changes—without weakening the business case or quietly expanding the project’s scope. A sound release authorisation process determines when that reserve may be used, who may approve it, and what evidence must be retained.

For Australian universities, the process must work across estates teams, finance, procurement, project control groups, executive committees and governing bodies. It should also reflect local conditions, including construction markets in Sydney and Melbourne, cyclone or flood exposure in northern Queensland, GST treatment, state procurement rules and the accountability attached to public funding.

Establish the purpose and decision boundaries

Begin by defining contingency in the project controls framework. The reserve should cover credible risks that were identified during planning but cannot be precisely costed. It should not fund an unapproved enhancement, remedy poor cost management, replace a client budget shortfall or conceal a scope change.

Separate the different reserves used in the capital programme. Design contingency, construction contingency, escalation allowance and client-held risk provision may have different owners and release rules. A project manager might recommend drawing on construction contingency for an unforeseen services conflict, while an executive sponsor may need to approve a new laboratory fit-out requirement.

Decision point Typical owner Required evidence Result
Risk occurs or forecast changes Project manager Risk register, site report or cost plan Potential draw identified
Technical and financial review Quantity surveyor and finance partner Independent estimate and funding impact Recommendation prepared
Approval within delegation Authorised officer or steering group Signed release request Contingency transferred
Scope or budget change Investment committee or governing body Revised business case and funding plan Broader approval required
Close-out and audit Project controls and finance Updated forecast, ledger and lessons learned Reserve and records reconciled

Build a tiered approval model

A tiered model keeps routine decisions moving while protecting larger or more sensitive releases. Set thresholds in Australian dollars and connect them to the university’s financial delegations. For example, a minor release may be approved by the project sponsor, a medium release by the capital steering committee, and a material or cumulative release by the executive investment committee or council.

Value alone should not determine the route. A small release may require escalation if it affects accessibility, heritage fabric, research-compliance requirements, fire safety, student accommodation or a politically sensitive site. Cumulative drawdowns should also be monitored so that several modest approvals cannot bypass a higher level of oversight.

The approval matrix should state who can recommend, review, approve and record each decision. Include segregation of duties: the person requesting a release should not be the only person validating the estimate or authorising the financial transfer. This is particularly important where a university manages multiple projects through a central capital plan.

Define an evidence-based release trigger

Every request should begin with a clear event and a quantified consequence. Suitable triggers include an unforeseen asbestos discovery, contaminated soil, a failed building-services inspection, a supplier insolvency, a documented market escalation or a design coordination error that could not reasonably have been known at the approved baseline.

Require the project team to explain why the cost belongs to contingency rather than an existing contract obligation, insurance claim, consultant liability or change in scope. A request should include the original budget, current forecast, amount already committed, proposed release, remaining contingency and the expected effect on completion date and benefits.

For Australian projects, the evidence may include a superintendent’s direction, builder quotation, quantity surveyor assessment, geotechnical report or procurement evaluation. If GST is treated differently across project components, show the basis clearly. A finance reviewer should be able to reconcile the request to the general ledger and the approved capital budget without reconstructing the calculation.

Use a consistent workflow

A practical workflow can be managed through a project management information system, controlled form or approved workflow in the university’s finance platform. The request should receive a unique reference, be linked to the relevant risk and change records, and move through review in a predictable order.

The project manager submits the request, the commercial or quantity surveying function tests the estimate, and the finance business partner checks the funding source and accounting treatment. The delegated approver then makes a decision, while project controls update the forecast, risk exposure and contingency balance. The final release should be reflected in both the project cost report and the finance ledger.

Set service standards for each stage. A low-value, well-supported request might be reviewed within five business days, while a complex release involving a heritage building in central Melbourne or a major Sydney campus redevelopment may require specialist review. Delays should be visible rather than handled through informal email approvals.

Create a strong release request

A standard form improves consistency and reduces arguments about incomplete submissions. It should identify the project, package, contractor, cost code, risk event, amount requested, currency basis, GST treatment, timing and remaining reserve. Include a concise explanation of alternatives considered and the consequence of not releasing the funds.

The request should distinguish between committed cost and forecast cost. A signed variation, for example, may represent a committed liability, while a preliminary estimate remains uncertain. Record the confidence range where appropriate, especially for volatile materials, imported equipment, specialised laboratory systems and long-lead mechanical plant.

A useful request pack contains:

Also require confirmation that the release does not create an unapproved scope change. If it does, the request should be redirected into the change control process rather than approved as a routine contingency draw.

Monitor cumulative exposure and market conditions

Contingency governance is a forecasting discipline, not a sequence of isolated approvals. At every monthly reporting cycle, compare the original reserve, approved releases, committed amounts, emerging risks and expected remaining exposure. A project can appear within budget while its residual contingency is no longer credible.

Use a contingency drawdown curve to identify unusual patterns. Early and repeated releases may indicate an unrealistic baseline, incomplete design, weak contractor pricing or inadequate risk ownership. A project with a large unused balance near completion may indicate that risks were overstated, though funds should not be released simply to improve apparent performance.

Australian market conditions deserve explicit attention. Construction costs and subcontractor availability can differ sharply between Brisbane, Perth, Adelaide and regional campuses. A university should document whether escalation is held centrally, embedded in package budgets or managed through project contingency. Where Commonwealth or state grants are involved, check whether the funding agreement permits reallocations and whether any underspend must be returned.

Make governance visible and auditable

Good records allow an internal auditor, auditor-general, finance committee or successor project team to understand the decision months later. Retain the request, supporting evidence, approval, revised budget, ledger entry, contract variation and meeting record in a controlled repository. Avoid relying on personal inboxes or undocumented verbal decisions.

Report more than the total amount released. A useful dashboard shows contingency percentage remaining, releases by cause, pending requests, forecast final cost, schedule effect and the age of unresolved risks. Highlight projects where remaining contingency falls below a defined threshold or where approved releases exceed the risk allowance for a particular category.

Professional networks can help institutions compare governance practices without copying a process that does not fit their delegations. For example, senior business officers can use TASSCUBO meetings to exchange approaches to capital governance, project assurance and financial controls with peers managing complex public-sector portfolios.

Strengthen the process through review

The process should be tested after each major project phase and formally reviewed at project close. Examine whether requests arrived early enough, whether approval levels were appropriate, and whether the original risk register predicted the issues that actually occurred. Record lessons in a central knowledge base so future business cases use better assumptions.

Before launching the procedure, agree on the measures that will show whether it is working:

Run scenario tests with the project control group. Consider a latent-condition claim, a sudden escalation in imported equipment, a safety-related change and a proposed enhancement presented as a risk response. The team should be able to identify the correct approval route, funding source, evidence and reporting treatment for each scenario.

A mature process also preserves the right to pause. If a request reveals that the project’s benefits, affordability or delivery strategy has materially changed, the appropriate response may be a reapproval of the business case rather than a contingency release. That discipline protects the university’s balance sheet and keeps decision-makers accountable for the full investment.

Adopt the process as a controlled policy, publish the approval matrix, train project sponsors and embed the request workflow into monthly capital reporting. Start with a pilot on one active project, adjust the thresholds and evidence requirements based on real transactions, then extend it across the portfolio. A clear contingency release authorisation process gives Australian universities faster decisions where the facts are sound and stronger scrutiny where public money, project scope or institutional risk is at stake.