Development budgets: separate cost, escalation and contingency

Define what the budget is buying

Begin with the project scope and a cost breakdown that can be matched to the physical proposal. State whether the total includes land, enabling works, buildings, external works, utilities, professional fees, owner costs, finance and tax. A construction estimate and a complete development budget can both be correct while covering different things.

ICMS provides an international reporting framework for construction costs and related lifecycle information. A consistent classification helps explain comparisons, but it does not make two projects equivalent. Keep the area definition, specification, location, date and exclusions visible beside any rate or benchmark used.

The GAO cost guide links reliable estimates to scope, schedule, a technical baseline, assumptions, data, risk analysis and subsequent updates. Its programme-costing context is broader than property development, but the discipline is useful: a budget number needs an explanation of what supports it.

Sources: RICS: ICMS: International Cost Management Standards; US Government Accountability Office: Cost Estimating and Assessment Guide, GAO-20-195G

Give every estimate a price date and timing basis

An estimate at today's prices is different from the cash expected to be paid over the delivery programme. Record the price base and identify the packages still exposed to change. A genuinely fixed future payment should not receive another inflation allowance simply because it sits beside an uncommitted package.

UK government cost estimating guidance separates base estimates, escalation and uncertainty and calls for a clear base date and an evidenced inflation mechanism. That is useful methodological guidance, not a universal construction inflation forecast. Use a suitable index, quotation basis or supported assumption for the actual scope and market.

When a quotation already includes an escalation allowance, identify that amount before applying a project-level adjustment. Exchange-rate exposure also needs its own basis if costs and funding use different currencies. A schedule change can alter the amount exposed and the period over which prices may move.

Sources: UK Infrastructure and Projects Authority: Cost Estimating Guidance: base estimates, escalation and uncertainty

Build an outturn budget from explicit assumptions

Consider an invented budget in millions of one currency, with a price base of 15 September 2026. Building works are 10 million, including 0.40 million of known ground treatment. External works are 1 million and a fixed fee is 1 million. The base estimate is therefore 12 million. Land, finance and tax are outside this construction-and-fees example.

Assume half the building expenditure is priced for payment one year after the base date and half two years after it. For this simplified calculation, apply a chosen 4% annual compound escalation rate at those dates. The first 5 million increases by 0.20 million; the second by 0.408 million. External works paid after one year increase by 0.04 million. The fixed fee receives no escalation.

Add three separately identified risk allowances: 0.30 million for unresolved design, 0.25 million for ground conditions beyond the known treatment and 0.10 million for utility-related delay costs. These allowances are already expressed in future payment amounts and do not receive the price uplift again. They are illustrative provisions, not probability-calibrated estimates.

Do not confuse an allowance with measured confidence

The 0.65 million risk total identifies where this example still lacks certainty. It does not establish an 80% chance of completing within 13.298 million. A confidence statement needs a defensible uncertainty model, including the way risks may occur together. Adding arbitrary percentages and naming the result P80 does not supply that evidence.

Ask what each allowance covers, what it excludes, who owns the risk and what event releases or consumes it. Design growth, contractor pricing uncertainty and a known client change may need different treatment. Once work is confirmed, include it as defined scope rather than keeping it hidden within a general buffer.

A delay allowance should also state its boundary. If it covers only temporary site facilities and supervision, additional finance or price escalation may still sit elsewhere in the development appraisal. Map the same delay through those lines explicitly so that one consequence is neither omitted nor duplicated.

Update the forecast when a risk becomes defined work

Suppose a ground investigation resolves the additional ground risk. The confirmed extra work costs 0.18 million at its expected payment date. It is separate from the original known 0.40 million treatment. Add 0.18 million to the defined outturn forecast and remove the old 0.25 million allowance for that specific risk.

Defined outturn cost increases from 12.648 to 12.828 million. Remaining risk allowances fall from 0.65 to 0.40 million. The revised total is 13.228 million, a net reduction of 0.07 million. Keeping both the confirmed work and the full old ground allowance would instead overstate the current forecast by 0.25 million.

Record this as a forecast reconciliation. It is not automatic permission to spend the released amount on additional scope. Budget authority, procurement commitments and the latest expected cost are different records, and their differences should be visible to the person approving a change.

Review the changes, not just the latest total

At each review, reconcile the previous forecast to changes in quantity, specification, rates, timing, scope and remaining risks. Separate actual payments from commitments and expenditure still to procure. An unchanged total can hide a growing defined cost that has quietly consumed the allowance.

For an international portfolio, agree a common reporting structure while retaining local procurement, currency and tax assumptions. Use ranges where the design or evidence is immature, and explain which investigation or procurement result will narrow them. The purpose of contingency is to make uncertainty visible enough to manage, not to disguise a missing estimate.