Back to Journal
What section 60 requires a responsible authority to considerPhoto: SiteLogic editorial image

Planning Law

What section 60 requires a responsible authority to consider

The mandatory and discretionary considerations under section 60 of the Planning and Environment Act 1987, how Clause 65 operationalises them, and how to write a permit application to those tests.

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

What section 60 does

Every planning permit decision in Victoria, whether made by a council, a delegate, or ultimately VCAT on review, works through a specific list of matters set by section 60 of the Planning and Environment Act 1987. Section 60 is the backbone of permit decision-making. It tells the responsible authority what it must have regard to, and what it may have regard to, before deciding whether to grant a permit and on what conditions.

Applicants who treat a permit application as a technical exercise, satisfy the numeric standards in a clause and expect approval, often misjudge how much of the decision actually turns on section 60's broader considerations rather than compliance with a single control. A responsible authority can refuse an application, or impose conditions, based on matters section 60 requires it to weigh even where the proposal technically meets a specific numeric standard elsewhere in the scheme.

The mandatory considerations

Section 60 separates matters the responsible authority must consider from matters it may consider. The mandatory list generally includes the relevant planning scheme, including its state and local planning policy framework, any objections and submissions received, and any decision guidelines specified in the scheme itself, which is where Clause 65 does its work. It also directs the authority to consider the orderly planning of the area, the effect on the environment, and any significant social and economic effects of the proposal.

These considerations are deliberately open-textured. Orderly planning is not defined by a checklist, and a responsible authority, or VCAT on review, has genuine discretion in how it weighs a proposal against the surrounding pattern of development, existing approvals in the vicinity, and the trajectory the planning scheme's policy framework sets for the area.

The reference to objections and submissions in the mandatory list means the content of what neighbours and other interested parties actually raise becomes part of the statutory record the authority must work through, not merely a courtesy step before the real decision. A well-argued objection that identifies a specific, provable off-site effect counts for more in this framework than a general statement of opposition, because the authority is required to grapple with the substance of what has been put to it.

The discretionary considerations

Beyond the mandatory list, section 60 allows the authority to have regard to further matters where relevant, such as whether the site is affected by any relevant agreement under the Act, or any other matter the authority considers relevant and appropriate. This discretionary tail matters in practice because it gives a responsible authority, and VCAT, room to weigh site-specific factors that do not fit neatly into the mandatory categories, such as a history of related approvals on the same land or a relevant agreed outcome from an earlier panel process.

How Clause 65 sits alongside section 60

Clause 65 of the Victoria Planning Provisions operationalises part of section 60 by setting out the decision guidelines a responsible authority must consider for particular permit types, covering matters such as neighbourhood character, siting, the pattern of subdivision, off-site effects, and whether the proposal makes efficient use of the site. Clause 65 does not replace section 60; it sits inside the planning scheme limb of it, giving concrete guidance on how the broader statutory considerations translate into an assessment of a specific application.

Different permit triggers draw on different parts of Clause 65. A single dwelling application is assessed against a narrower set of guidelines than a multi-dwelling proposal, which pulls in additional matters such as the pattern of development in the wider area and the capacity of infrastructure to service the increased density. Reading the correct subset of Clause 65 for the specific trigger, rather than the clause as a whole, is a basic step that is nonetheless commonly missed in a rushed application.

Because Clause 65's guidelines are themselves broad, matters such as the pattern of development rather than a numeric test, an application can comply with every applicable numeric standard in Clause 55 or a zone schedule and still face a considered, lawful refusal if the responsible authority forms the view that the proposal fails the broader Clause 65 and section 60 tests.

How to write an application to these considerations

A strong application addresses section 60 and Clause 65 considerations directly in the planning report, rather than leaving the responsible authority to infer how the proposal measures up. That means explicitly addressing neighbourhood character, the relevant policy framework in the scheme, orderly planning of the surrounding area, and the environmental and any significant social or economic effects, alongside demonstrating compliance with the numeric standards.

Where an application departs from a numeric standard, for example seeking a variation under Clause 55's decision guidelines, the justification should engage with why the departure still achieves the purpose of the relevant objective, and not simply that the departure is minor. A responsible authority weighing section 60 considerations is assessing the proposal's fit with the scheme's intent, and an application that only argues numeric proximity to a standard, without addressing that intent, gives the authority less to work with in supporting an approval.

What to check before lodging

Read the local planning policy framework for the specific municipality, not just the state-wide provisions, because section 60 directs the authority to the planning scheme as a whole, and local policy can materially affect how orderly planning gets interpreted for that area. Check whether any decision guidelines in Clause 65 apply specifically to the permit trigger being relied on, since different permit triggers pull in different parts of Clause 65.

Review recent permit decisions and, where available, VCAT outcomes for comparable proposals in the same municipality to understand how that responsible authority has weighed similar considerations previously, while keeping in mind that each decision turns on its own facts and policy context can shift between amendments. Confirm whether any relevant agreement or notice affecting the land exists, since these fall within the matters section 60 requires the authority to take into account and can materially affect how a proposal is assessed.

Record keeping and review

Keep the planning report, the decision notice, and any conditions imposed together as part of the site's permanent record, because a future application on the same land, whether an amendment to the existing permit or a fresh proposal, will be assessed against the same section 60 framework and the responsible authority's own file will typically be referred back to. A well-documented history of how a site's section 60 considerations were previously addressed can shorten the assessment of a later application on the same land, while a thin or inconsistent record tends to invite closer scrutiny the second time around.


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 · planning-schemes.app.planning.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.