Back to Journal
Unreasonable permit conditions and how VCAT tests themPhoto: SiteLogic editorial image

VCAT

Unreasonable permit conditions and how VCAT tests them

A planning permit condition is not valid just because a council imposed it. This article explains the general tests a condition must meet and the practical path for challenging a condition that undermines a project's feasibility.

·Written and fact-checked . Published .·6 min read

Not every condition attached to a planning permit is one the developer has to simply accept. A council or referral authority can attach a wide range of conditions when a permit is granted, but the power to impose conditions is not unlimited. A condition that has nothing to do with the planning purpose of the permit, or that in substance defeats the project the permit was meant to allow, is the kind of condition an applicant can put to the test.

For a project team, this matters because a poorly considered condition can do more damage to a feasibility than an outright refusal. A refusal is a clear stop. A permit issued with an unworkable condition can look like a win on paper while quietly removing the yield, the built form, or the staging the numbers were built around.

The provision

The Planning and Environment Act 1987 is the framework instrument for how permits are granted, what a responsible authority may require as a condition, and how a permit decision, including its conditions, can be reviewed. Conditions are not an unconstrained discretion. They exist to give effect to the planning scheme and to manage the impact of the specific proposal, not to achieve outcomes that sit outside the purpose of the permit power altogether.

An applicant who accepts a permit still has the right to seek a review of specific conditions attached to it, distinct from a review of an outright refusal. That right exists precisely because the two problems, a refusal and an unworkable condition, are not treated as the same thing procedurally, even though commercially they can produce a similar result. Anyone relying on the current procedural mechanics of that review right should check the relevant provisions directly in the Planning and Environment Act 1987 rather than assume they are unchanged from a past project.

What applies

The general tests that Victorian planning law and tribunal practice apply to conditions are consistent with the broader administrative law principle that a condition must serve the purpose for which the power to impose it exists. In practice, that has been distilled into a small number of questions decision-makers and reviewers ask of any contested condition.

Does the condition relate to the planning scheme and the permit it is attached to, rather than to an unrelated public purpose the council might want to achieve through some other mechanism. Is the condition connected to the specific proposal being permitted, rather than a general policy preference applied without regard to the site. Would a reasonable decision-maker, properly applying their mind to the planning merits, have imposed it. And, importantly for feasibility, does the condition leave the permit holder with a permit that can actually be acted on, or does it in effect prevent the approved development from proceeding at all.

That last question is where feasibility and planning law intersect most directly. A condition that is lawful in form but commercially fatal, for example one that removes so many car spaces or so much yield that the approved building can no longer be built as designed, sits close to the boundary of what a condition is allowed to do. Because whether any specific condition crosses that boundary depends on the wording of the condition, the planning scheme, and the site, this is a fact-specific question. It is not something this article resolves in the abstract, and it is not something to decide without a planning lawyer or town planner reviewing the actual permit and conditions in question.

How to model it

The feasibility discipline here is to treat every draft condition, as well as every draft decision, as a line item with a cost or yield consequence, before the permit is accepted.

When conditions are foreshadowed during assessment, whether through a request for further information, a notice of decision, or informal correspondence from the planning department, run each proposed condition against the design and the numbers rather than only against the planning scheme. A landscaping condition might be immaterial to yield. A condition altering setbacks, private open space, car parking ratios, or a staging sequence can move the numbers materially, and should be flagged to the design team and the financial model at the same time it is flagged to the planning consultant.

Where a condition looks like it could be commercially fatal rather than merely inconvenient, get advice on whether it is open to challenge before the permit is accepted, not after. Accepting a permit and then trying to renegotiate a condition later is a much weaker position than raising the objection while the decision is still under review.

What to check before exchange

Before a site is priced on the assumption that a permit, existing or anticipated, delivers a particular yield, check the conditions attached to any current permit line by line against the feasibility as well as against the planning scheme. Identify any condition that touches car parking, private open space, setbacks, height, staging, or contributions, since these are the categories most likely to move numbers.

Confirm whether the permit as issued, including its conditions, is actually capable of being built as approved, or whether a further amendment will be needed before the approved development matches the feasibility. Check whether any condition purports to require something outside the planning purpose of the permit, since that is the category most likely to be open to challenge.

Finally, build in time for a conditions review as a discrete due diligence step, separate from the headline question of whether a permit exists. A permit that exists but cannot be built as priced is not the same asset as a permit that delivers the modelled yield.

Practical steps if a condition looks unworkable

Where a specific condition appears to defeat the purpose of an otherwise workable permit, the general path is to seek a review of that condition, rather than the permit decision as a whole, so the parts of the approval that work are not put at risk along with the part that does not.

Because the tests a tribunal applies to a contested condition depend heavily on the specific wording of the condition, the planning scheme provisions in play, and the site context, this is squarely a fact-specific area. This article sets out how the general framework operates. It does not set out how any particular condition would be assessed, and it does not summarise past tribunal decisions, because doing so without the full facts of a matter risks giving a false sense of certainty. Anyone facing a condition that threatens a project's feasibility should get advice from a planning lawyer who can review the actual permit, the actual scheme, and the actual site before forming a view on prospects.

Record keeping

Keep a clear record of every version of a condition as it moves through assessment, from any request for further information through to the final notice of decision. Note the date each version was received and who from the responsible authority or referral authority proposed it. That record is what makes a later review, if one is needed, a matter of comparing documents rather than reconstructing history from memory.


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: legislation.vic.gov.au · vcat.vic.gov.au

Our standards·

Share this article

Get new articles by email

Weekly digest of new articles. No spam. Unsubscribe any time.

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.

See Pro pricingFree tier stays free.