Back to Journal
VicSmart: the fast-track permit pathway (Clause 71.06)Photo: SiteLogic editorial image

planning

VicSmart: the fast-track permit pathway (Clause 71.06)

VicSmart lets a defined list of straightforward applications be decided within a short statutory timeframe. This piece explains what qualifies, what a complete application needs, and where the pathway helps or hurts a development programme.

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

Most permit programmes are built around the standard 60-statutory-day assessment clock, plus whatever notice, referral and further-information time gets added on top. A smaller class of applications runs on a different clock entirely. VicSmart exists to decide genuinely straightforward proposals quickly, and it rewards an applicant who treats "straightforward" as a technical test, not a general impression of the site.

The provision

Clause 71.06 (VicSmart) sets out how the VicSmart process operates once an application falls into a class the scheme identifies as eligible. It does not itself list every eligible class. The classes, together with the specific information requirements and decision guidelines for each one, sit in the relevant zone, overlay, particular provision or Clause 59, with a table directly under the ordinary permit requirement flagging where VicSmart is available for that trigger. Clause 71.06 is the operating mechanism that ties those scattered eligibility tables together into a single, consistent process.

The headline feature is timing. The clause sets a statutory decision period measured in a small number of business days, materially shorter than the standard assessment timeframe, and there is no public notice step built into the pathway. Because the class list and the specific information requirements attached to it are refined through periodic amendment, the current wording of Clause 71.06 and the applicable eligibility table should be confirmed directly before an application is prepared, rather than assumed from a previous project or an older summary.

What applies

Eligibility is defined narrowly and by class, not by a general sense that a proposal is minor. Typical VicSmart classes include specified categories of single dwelling development in particular zones or overlays, minor extensions or alterations, some subdivisions of land into a small number of lots, certain classes of signage, and defined thresholds for native vegetation removal or other particular provisions where the scheme has specifically flagged VicSmart availability. Planning Victoria's VicSmart guidance sets out the current list of eligible classes and how they map to the zone and overlay tables, and is the more current reference point than any list reproduced in a guide that predates the most recent amendment.

The defining feature of the pathway is that the application must be complete, against the specific information requirements for that class, at the point of lodgement. There is no scope within VicSmart for the kind of iterative further-information request that extends a standard application's clock. An application missing a required plan, report or piece of supporting information for its class does not get the benefit of the short timeframe; many councils will not treat it as a valid VicSmart application until the missing information is supplied, which can mean the application effectively restarts its clock rather than pausing it.

Because there is no public notice step, VicSmart applications do not carry third-party objection rights in the way a standard application with notice does. That is part of why eligibility is confined to classes the scheme has judged unlikely to raise the kind of amenity or character issue that notice and objection rights exist to manage. It also means the assessment is typically made by a council officer under delegation against the specific decision guidelines for the class, rather than through a broader planning merits assessment against the full range of policy that might apply to a more complex proposal.

How to model it

For a developer choosing between the standard pathway and VicSmart where an application straddles the line, the modelling question is not simply which pathway is faster on paper. It is whether the proposal actually fits the class as defined, because a VicSmart application lodged against the wrong class, or lodged incomplete, loses the timing benefit and can cost more calendar time than starting on the standard pathway from day one.

Build the programme around the specific class's information requirements, not a generic application checklist. Where a subdivision, use or development could plausibly be structured to fit a VicSmart class, for example a two-lot subdivision that meets the class threshold rather than a larger subdivision that does not, weigh the design and yield trade-off against the timing benefit deliberately, rather than defaulting to the larger scheme and assuming VicSmart is unavailable without checking. Where native vegetation removal, signage, or a minor building class is the actual trigger on an otherwise larger project, consider whether that specific element can be lodged and decided separately under VicSmart while the balance of the project proceeds on its own track, since the two need not be bundled into a single application if the scheme does not require it.

Because there is no further-information mechanism within the pathway itself, build the pre-lodgement diligence into the programme rather than the post-lodgement stage. The time saved by VicSmart is realised only if the application is right the first time.

What to check before you lodge

Confirm the specific class the proposal falls into, quoting the exact zone, overlay or particular provision clause and table that identifies VicSmart availability for that trigger, rather than relying on a general description of the proposal as "minor." Obtain the current, class-specific information requirements and decision guidelines directly from the applicable clause or from the current VicSmart guidance, since these are drafted per class and a checklist for one class will not cover another. Confirm the current statutory decision timeframe against Clause 71.06 itself, since the class list and requirements are the elements most often refined by amendment.

Check whether any other application affecting the same site, such as a separate planning permit for works not covered by the VicSmart class, will need to run in parallel, and confirm the two applications will not create a conflict where one process moves faster than an interdependent approval it relies on. Finally, confirm with the responsible authority's planning department how it treats an incomplete VicSmart lodgement in practice, since councils vary in whether they return the application, request the missing item under a short administrative process, or decline to accept it as valid until it is complete, and that variance affects how tightly a programme can be built around the fast-track timeframe.

Where VicSmart does not help

VicSmart is not a substitute for a genuinely contested proposal simply because a developer would prefer a faster decision. A class boundary is a class boundary, and an application that does not actually meet the eligibility criteria for information, use, or threshold gains nothing by being lodged as if it does, beyond the risk of an invalid lodgement and lost time. The pathway is most useful where it was designed to be useful: a defined, low-impact trigger that genuinely does not need public notice or an extended assessment to be decided well.


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 · 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.