GoSiteHunt
Authority guide

Residual Land Value Explained: the most you should pay for a site

A deeper guide to residual land value, the formula developers use to work backward from finished project value to a safe land price.

The formula

Residual land value is the amount left for the land after a development has paid for everything else and still kept its required margin. In plain English: gross realisation minus all development costs minus required profit equals the maximum land price. If the asking price is above that number, the deal is relying on better assumptions, lower risk or a smaller margin.

Gross realisation

Finished sales or capitalised value, based on genuine comparable evidence rather than generic optimism.

Total costs

Construction, demolition, consultants, authority costs, contingency, finance, selling costs and tax treatment.

Required margin

The developer's reward for risk, time, funding exposure and delivery complexity.

Why developers overpay

Overpayment usually comes from one of four errors: yield is too high, end value is too optimistic, build cost is too low, or the time/risk allowance is too small. Residual land value is useful because it forces every assumption to show up in the land price.

A generic worked example

If a townhouse project could sell for $4.8m, cost $3.1m excluding land and needs $650k of profit, the residual available for land is about $1.05m before acquisition costs and sensitivity. If the vendor wants $1.35m, the buyer must either prove higher end value, lower costs, more yield or accept lower margin. That is the decision GoSiteHunt is designed to surface early.

Turn the principle into an address-level test

Use the guide to understand the decision path, then run the actual address through GoSiteHunt before paying for survey, concept plans, planning advice or a full feasibility model.

Run a site report · Open the residual land value calculator · Read more development guides

Residual Land Value: Formula & Worked Example: practical development feasibility workflow

This guide is written for the point where a buyer needs to turn planning language into a commercial decision. A useful guide should not stop at definitions. It should explain what to check, why the check matters, and how the result changes the price someone can safely pay for the land.

Start with the controls

Read the zone, overlays, height, FSR/FAR or density controls, frontage, access and minimum site-area logic. If the controls do not support the intended product, the rest of the spreadsheet is theatre.

Translate to yield

Convert the planning read into a believable number of lots, dwellings, apartments or commercial floor area. Allow for setbacks, circulation, parking, open space, services and design inefficiency.

Price the risk

Work backward from end value through construction, consultants, authority charges, finance, selling costs, contingency and required margin to a maximum residual land value.

Why this matters

The most expensive mistake is not missing a site; it is buying a site at the wrong number because one part of the feasibility chain was assumed. GoSiteHunt exists to run those checks earlier.

Run an address through GoSiteHunt or start with the residual land value calculator before you commit due diligence spend.

Due-diligence checklist before acting on this page

Before relying on any first-pass development signal, confirm the address against the live planning source, the title and easements, survey dimensions, tree and heritage controls, infrastructure capacity, stormwater, access geometry, parking, open-space requirements and any recent or pending planning amendments. Then test the commercial side: realistic end values, selling time, construction rate, demolition, services, consultant fees, authority contributions, contingency, finance, tax treatment, delivery timeframe, holding costs and the margin required for the risk. The value of GoSiteHunt is that it keeps these checks connected. A page may help a site get onto the shortlist, but the address-level report and a professional review decide whether it deserves an offer.

For search users, this extra context matters because development feasibility is never a single-keyword answer. A useful page should explain the decision path, the assumptions and the next action, not just repeat a suburb, zone or tool name. That is why each GoSiteHunt discovery page links the topic back to a practical screening workflow. The goal is not to pad copy; it is to make the page useful enough that a buyer understands what evidence is missing, what a consultant would still need to confirm, and which next action moves the opportunity closer to or further from a genuine offer. Every page should answer a practical buyer question and point to a measurable address-level check.