Back to Journal
VicSmart, objections and the limits of the fast trackPhoto: SiteLogic editorial image

Planning Law

VicSmart, objections and the limits of the fast track

What qualifies a Victorian planning application for the VicSmart fast track under Clause 71.06, what the pathway removes in notice and appeal rights, and where projects misjudge eligibility.

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

What VicSmart is for

VicSmart is a streamlined permit pathway built into Clause 71.06 of the Victoria Planning Provisions for classes of application the scheme treats as straightforward: proposals with limited off-site impact where a fast, largely administrative assessment is considered appropriate. The pathway's accelerated decision timeframe is set by the VicSmart provisions of the Planning and Environment Act 1987 and the Planning and Environment Regulations, with the eligible classes prescribed in Clause 71.06.

The premise is straightforward: an application that fits a defined VicSmart class is assessed against a short, specific checklist rather than the full range of decision guidelines that apply to a standard application, and the responsible authority works to a shorter statutory clock. For a developer running a program of small, repeatable works, correctly identifying which applications genuinely qualify for VicSmart can materially compress a project timeline.

What qualifies

Clause 71.06 sets out specific classes of application eligible for the VicSmart pathway, together with the checklist of requirements each class must meet. The classes cover a defined range of relatively contained proposals, commonly including things such as minor extensions to an existing dwelling, straightforward subdivisions of existing lots, certain fencing, signage and use changes, and other applications the scheme has assessed as suited to abbreviated processing. Each class carries its own eligibility checklist in the clause, and an application only qualifies for VicSmart if it fits within one of those defined classes and meets the checklist for that class.

Confirm the current class list and every threshold attached to it directly against Clause 71.06 before assuming a proposal qualifies, because the classes and their checklists are amended from time to time, and a proposal that qualified under an earlier version of the clause may not fit the current one.

What VicSmart removes

The trade-off for speed is that VicSmart applications are generally not required to go through public notice in the way a standard application is, and the statutory review rights attached to the decision are correspondingly narrower. Where a standard application gives adjoining owners and other affected parties a right to receive notice, lodge an objection, and seek review at VCAT if a permit issues over their objection, VicSmart applications are assessed without that notice and objection step built in, and with more limited third-party review rights.

This matters in both directions. For an applicant, the absence of a notice and objection period removes a major source of delay and uncertainty. For a neighbour who might otherwise object to a proposal, VicSmart means less opportunity to have input before a decision is made, and a narrower path to challenge it afterward. A developer relying on VicSmart to sidestep an anticipated objection should understand that this is only lawful where the application genuinely fits a defined class, not a strategy for avoiding notice on a borderline proposal.

Where projects misjudge eligibility

The recurring mistake is treating VicSmart eligibility as a matter of degree rather than a strict class fit. A proposal that seems basically minor but does not actually satisfy every element of a class's checklist, for example because it affects a heritage-overlaid property, exceeds a size or scale element of the class definition, or sits in a zone the class excludes, is not eligible for VicSmart no matter how modest it appears in practice. Lodging it as a VicSmart application when it does not meet the checklist risks the responsible authority rejecting the application as invalid for that pathway, which costs more time than lodging it correctly as a standard application from the outset.

A second common error is assuming that because a class of works is eligible for VicSmart in one zone or overlay context, the same works are eligible everywhere. Overlay controls in particular can pull an otherwise eligible proposal out of a VicSmart class, because the checklist for many classes expressly excludes land affected by specified overlays, or requires the absence of an overlay to qualify.

How to model VicSmart into a project timeline

Where a program includes a series of small works across multiple sites or stages, build the feasibility program around confirmed class eligibility for each application rather than assuming the whole program will run on the VicSmart clock. Get a planning consultant or the responsible authority's duty planner to confirm eligibility against the current Clause 71.06 checklist for each distinct application before committing a delivery date to it.

Where eligibility is genuinely marginal, price the downside scenario, standard-track assessment with notice and potential objection, into the program rather than assuming the best case. The cost of assuming VicSmart and being wrong extends beyond the extra assessment time: it includes the cost of re-lodging correctly and any delay that flows through the rest of the program.

What to check before lodging

Check the current version of Clause 71.06 directly for the specific class the application is intended to fit, including every element of that class's checklist, since informal summaries of what qualifies for VicSmart can lag behind the current clause. Confirm whether any overlay affecting the site excludes the application from the class, and check the zone provisions for the same reason.

Ask the responsible authority's planning department to confirm eligibility before lodgement where there is any doubt, because an authority that receives an invalid VicSmart application will generally need to redirect it to standard processing, and catching that before lodgement avoids losing time in the process. Keep a record of the eligibility checklist assessment for each application lodged under VicSmart, in case the pathway used is later questioned by an objector or on review.

Practical steps for a program of small works

Treat VicSmart eligibility screening as its own step in the pre-lodgement process, sitting before, not folded into, the drafting of the application material. A short written eligibility note for each application, referencing the specific class and checklist item relied on, gives the applicant a defensible record if the responsible authority later disputes the pathway, and it forces the discipline of checking the overlay and zone position for every site rather than assuming consistency across a portfolio.

Where a portfolio includes sites in more than one municipality, do not assume a class that was straightforward in one council area behaves the same way in another, because local policy and schedule variations can affect how a checklist item, such as a heritage or vegetation overlay exclusion, applies to a given site. Confirming eligibility site by site, rather than pathway by pathway, is the discipline that keeps a fast-track program actually fast.


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: planning-schemes.app.planning.vic.gov.au · legislation.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.