Photo: SiteLogic editorial imageFeasibility
Feasibility contingency: how much, and where to put it
A single blended contingency percentage hides where risk actually sits in a Victorian development. How to split contingency across construction, planning, sales and finance.
Most feasibility models carry a single contingency line, expressed as a flat percentage of construction cost, and call it done. That approach treats every risk in a development as if it were the same risk, arriving at the same point in the project, and it is one of the more common reasons a feasibility survives the acquisition decision but fails to survive the project.
Why one contingency line is not enough
Construction cost overrun is only one of several risks that erode a development's margin. Planning risk, sales risk and finance risk each behave differently: they crystallise at different points in the timeline, and they respond to different mitigations, so inflating the construction contingency line does nothing to reduce them. A developer who folds every risk into one construction contingency figure is implicitly assuming that a delayed permit and a soft sales market can be absorbed by the same buffer that covers a trade cost blowout, which is not how any of those risks actually behave.
A blended contingency also makes a feasibility harder to defend to a lender or an equity partner, because a single percentage gives no basis for a conversation about which risk it is meant to cover. Separating the allowance by category turns contingency from an arbitrary buffer into a set of specific, checkable assumptions, each of which can be tested against the actual state of the design, the permit and the market at the time the feasibility is reviewed.
Construction contingency
Construction contingency covers the gap between the cost plan prepared at the time of the feasibility and the final, contracted cost of the build. It should scale with the level of design certainty behind the cost plan: a concept-stage cost plan with no development approval carries materially more uncertainty than a cost plan based on a fully documented, tendered construction contract. Broader movement in construction activity, visible in data such as the ABS building approvals series, can also signal periods where trade pricing is under more upward pressure than usual, which is a reason to review the construction contingency assumption rather than carry forward the same figure used on the previous project regardless of market conditions.
Planning and approvals contingency
Planning risk is a timing risk as much as a cost risk. A permit that takes longer than expected to issue, or that is granted with conditions requiring design changes, delays the start of construction and extends the holding period, which flows through to finance cost. Where a site sits within a growth area subject to a precinct structure plan or a development contributions plan, the contribution schedule itself can also be varied before a permit issues; the VPA's infrastructure contributions plans page sets out how these schedules are structured and reviewed. A separate planning contingency, covering both the cost of design changes required by conditions and the holding cost of delay, is more useful than folding this risk into the construction line, because the mitigation for planning risk, a stronger pre-application strategy, for instance, is entirely different from the mitigation for a construction cost overrun.
Sales and revenue contingency
Sales risk covers the gap between the achievable sale prices assumed at feasibility stage and what the market actually delivers when the product is complete and ready to settle. This risk behaves differently to construction risk: it can move against the developer even if construction runs exactly to budget and program, because it depends on demand conditions at completion rather than on anything within the project team's control. A sales contingency, sometimes expressed as a haircut applied to the assumed sale rate rather than as a percentage of cost, gives a feasibility a more honest read of what happens if the market softens between the time a site is acquired and the time the product settles.
Finance contingency
Finance contingency covers the risk that facility terms, drawdown timing or a covenant position change the cost of capital across the life of the project. A project that runs longer than programmed, for whatever reason, incurs additional interest that a static finance cost line does not capture. A separate allowance for extended holding periods, distinct from the construction contingency, gives a more realistic picture of what a delay actually costs across the whole capital stack rather than only the construction budget.
An illustrative allocation
The following figures are illustrative. They demonstrate the method and will vary by site, council and timing. On a $10 million total development cost project, instead of a single blended contingency of $700,000, the allowance might be split as follows: construction contingency of $400,000 against a well-documented cost plan, planning and approvals contingency of $150,000 reflecting a moderately contested site, sales contingency of $100,000 reflecting a softening but not distressed market, and finance contingency of $50,000 covering a modest program extension. The total is close to the blended figure, but the allocation tells the developer where the risk actually sits and which mitigation to prioritise, rather than leaving every risk hidden inside one number attached to the building cost alone.
Reviewing contingency through the project
Contingency is not a number set once at acquisition and left untouched. As the design is documented, the permit progresses and presales are achieved, each contingency line should be revisited: a fully tendered construction contract can release most of the construction contingency, while a permit still working through objections should keep the planning contingency fully intact. Treating contingency as a single static figure, reviewed once, misses the fact that risk in a development project is retired at different points for different reasons, and a feasibility that is never updated after acquisition stops being useful the moment the first real piece of information arrives.
Practical steps
Build the feasibility with four contingency lines rather than one, even if the sales and finance lines start conservative and get refined as the project matures. Document the basis for each line, the design certainty behind construction, the planning pathway and any objections behind approvals, the depth of the comparable sales evidence behind sales, and the facility terms behind finance, so the assumption can be tested rather than taken on faith. Revisit all four at each major milestone, because a contingency line that is never reviewed after the acquisition decision is a static number pretending to manage a moving risk.
Published by the SiteLogic Editorial desk. Every fact traces to a primary source. See our standards and corrections register.
Fact-checked: 19 July 2026 · Review by: 19 July 2027
Sources: vpa.vic.gov.au · abs.gov.au
Was this useful? Try the tool this post is based on:
Pro on SiteLogic. Logi: up to 60 messages a day. Logi also stops at US$15 of model cost in a Melbourne calendar month. The Developer Comms Kit and unlimited saved projects. The Strategy Lab simulator runs without Pro. Saving a scenario needs a signed-in account. $60/month or $600/year, ex GST. First 3 months are $30/month, ex GST, on monthly Pro.