Photo: SiteLogic editorial imageClause 66
Referral Triggers in Clause 66: When a Planning Permit Leaves Council Control
Clause 66 separates determining referrals, recommending referrals and notice requirements. Only some external responses bind the responsible authority, but each can change programme and permit conditions.
A council planner may support a proposal and still be unable to issue the permit on those terms. The reason is often a determining referral authority: an external body whose objection or required conditions bind the responsible authority under Victoria's referral system.
That is the sharp end of Clause 66, but it is not the whole clause. Some referral authorities are recommending only. Some bodies receive notice rather than a referral. Those categories have different legal effects, and a feasibility that groups them together will misstate both decision risk and programme.
What Clause 66 does
The current Clause 66 referral and notice provisions identify applications that must be referred under section 55 of the Planning and Environment Act 1987 and applications for which notice must be given under section 52(1)(c). The clause also deals with referral of plans under the Subdivision Act 1988.
The structure matters:
- Clause 66.01 covers specified subdivision referrals.
- Clause 66.02 covers specified use and development referrals.
- Clause 66.03 covers referrals triggered by other state-standard provisions.
- Clause 66.04 and its local schedule can add referrals under local provisions.
- Clause 66.05 specifies notice to persons or bodies under state-standard provisions.
- Clause 66.06 and its local schedule can add notice requirements under local provisions.
That means a search limited to the word "referral" in the zone or overlay is not enough. The trigger may sit in the state table, another provision or the local schedule to Clause 66.04. A notice requirement may sit separately in Clause 66.05 or 66.06.
Clause 66 also states that a referral requirement can be displaced in specified circumstances. One example is where, in the responsible authority's opinion, a proposal satisfies requirements or conditions previously agreed in writing with the referral authority. Another is where the referral authority considered the same proposal within the previous three months and stated in writing that it did not object. Those are narrow pathways based on actual written material, not a general discretion to skip referral because informal advice was favourable.
Determining is not the same as recommending
Planning Victoria's practitioner guidance on referral and notice provisions separates two types of referral authority.
A determining referral authority can object, decide not to object or specify conditions. If it objects, the responsible authority must refuse the permit. If it specifies conditions, those conditions must be included in any permit granted. This is the point at which council loses control over that part of the outcome.
A recommending referral authority can take the same three positions, but its response does not bind council in the same way. The responsible authority may refuse following an objection and may include recommended conditions, but it retains the decision-making choice. Recommending does not mean irrelevant; specialist advice can still be persuasive and can shape the final assessment. It means the statutory consequence is different.
The type is stated in the applicable Clause 66 table or local schedule. It should be recorded against each trigger. The name of the authority alone does not tell you whether its role is determining or recommending for this particular application.
Notice is a third category
Clause 66.05 is a notice provision, not a referral table. A person or body given notice under section 52(1)(c) has the rights and obligations of a person notified of the application. It does not acquire the binding powers of a determining referral authority merely because it is a government body or infrastructure operator.
This distinction is easy to lose in a permit programme because both processes involve an external party. The questions are different. For a referral, ask what type of referral authority applies and what its response can require. For notice, ask whether the notified body may make a submission and what that could mean for assessment or review rights.
Describing every external authority as having a veto is wrong. Assuming none of them can direct the result is also wrong.
How to model it
Build a referral matrix before the programme is fixed. For each potential trigger, record the clause, kind of application, authority, determining or recommending status, information required, whether a written agreement removes the need for referral, and the design issue the authority will assess.
The trigger needs to match the proposal. Clause 66.01 contains subdivision categories and exceptions. Clause 66.03 operates where the planning scheme includes the specified state-standard provision. Local referrals depend on the relevant municipal schedule. A generic authority list does not establish that a particular application must be referred.
Carry time for a complete referral package and response. Planning Victoria's permit guidance states the response period, which should be checked in the current guidance when the programme is prepared. That period is not the entire programme allowance. Council first needs an application that can be referred, and missing technical information can create further work or redesign. Early written advice may reduce that risk, but it should not be treated as the formal response unless the statutory exception in Clause 66 is actually satisfied.
Carry the condition risk separately from refusal risk. A determining authority may not object but may require conditions that affect access, drainage, servicing, easements, construction management or design. The permit can therefore remain obtainable while the commercially useful scheme changes.
For subdivision, do not stop at the planning-permit referral. Clause 66 also states when a plan must be referred under section 8(1)(a) of the Subdivision Act 1988. The path from permit to certification and statement of compliance can involve service authorities and easement requirements that need their own programme line.
What to check before exchange
Read the current Clause 66 tables and both local schedules for the municipality. Then read every zone, overlay and particular provision that applies to the proposed use, development and subdivision. The trigger is defined by the kind of application, so a change in access, lot layout, use or building form can add or remove a referral.
Identify the status of each authority in writing. If it is determining, test the scheme against that authority's published requirements before the permit strategy is settled. If it is recommending, decide how its technical advice may influence council even though the legal effect is not binding. If it is a notice body, keep it in the notification pathway rather than the referral matrix.
Ask whether council and the authority have a written agreement containing standard requirements or conditions. Clause 66 recognises those agreements as a way of avoiding unnecessary referrals where the proposal satisfies them, but the responsible authority must form that opinion. Do not assume compliance without confirmation.
Finally, price the authority's likely conditions rather than allowing only for a response date. A site can pass the headline planning test and lose value through a crossover change, drainage requirement, servicing corridor or subdivision condition imposed later.
Clause 66 does not hand every application to another agency. It allocates defined roles. The commercial task is to identify which role applies before council support is mistaken for control of the final permit.
Published by the SiteLogic Editorial desk. Every fact traces to a primary source. See our standards and corrections register.
Fact-checked: 5 October 2026 · Review by: 27 July 2027
Sources: planning-schemes.app.planning.vic.gov.au · planning-schemes.app.planning.vic.gov.au · planning-schemes.app.planning.vic.gov.au · planning-schemes.app.planning.vic.gov.au · planning.vic.gov.au · planning.vic.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.