Photo: SiteLogic editorial imagePlanning Law
The Development Facilitation Program: the Minister as authority
Under the Development Facilitation Program the Minister for Planning, not the council, assesses and decides eligible applications. What that pathway trades away, what it buys, and how to model it.
Some Victorian projects never go near their local council's planning department. Under the Development Facilitation Program, the Minister for Planning can step into the role the council would normally play, becoming the authority that assesses and decides the application directly. For a developer with an eligible project, that is a genuinely different process, distinct from a faster version of the same one, and it needs to be understood as a trade rather than a straightforward shortcut.
The provision
The Development Facilitation Program sits within the broader planning framework under the Planning and Environment Act 1987, which gives the Minister for Planning powers to act as the planning or responsible authority in defined circumstances. The Planning Victoria program page describes the current settings for which projects can be brought into the program and how applications are lodged and assessed.
The premise of the program is straightforward. Certain categories of development, particularly larger or more complex projects that would otherwise move through a standard council assessment, can instead be assessed through a dedicated state-level process with the Minister as the decision maker. The precise eligibility settings, including any project type or scale threshold, are administrative settings that are reviewed and adjusted over time, so they should always be confirmed against the current program page rather than assumed from an earlier version of the guidance or from a colleague's experience with a different project.
What applies
Where a project is accepted into the program, the Minister effectively displaces the council as the authority responsible for assessing the application. Referral arrangements, notice steps, and the pathway to a decision are all run under the program's own settings rather than under the ordinary permit process a council would apply to the same site.
That does not mean technical standards disappear. Referral authorities such as water corporations, transport agencies, and other statutory bodies with a direct interest in the site still have a role, and the application still has to satisfy the substantive planning scheme controls that apply to the land, including the zone, any overlays, and relevant policy. What changes is who makes the decision and how the process around that decision runs. The underlying planning scheme itself stays the same.
What it trades away
The most consequential difference for anyone assessing risk is what happens to third-party rights. Standard council-run applications usually carry notice requirements and objection rights, with a review pathway to VCAT if an objector is dissatisfied with the outcome or a permit is refused. A program built to fast-track eligible projects is built specifically to compress or remove that layer, on the basis that the state-level process substitutes its own scrutiny for the standard local one.
For a developer, that is a genuine trade. Removing broad third-party notice and review rights lowers the risk of delay from formal objections, but it does not remove community or political attention from a project. A development assessed through a ministerial pathway can still attract scrutiny through other channels, including local advocacy directed at the Minister or the department rather than at a tribunal.
What it buys
The other side of the trade is programme certainty. A project moving through a dedicated state-level pathway is not competing for attention inside an ordinary council queue, and the assessment steps are structured around defined program settings rather than a general permit process that can be slowed by unrelated council workload.
For projects where holding costs are large relative to the value that additional months of a standard process would protect, that certainty can be worth more than the objection rights that are traded away. The calculation is different for a project that is genuinely contentious locally, where the removal of a review pathway can also remove a mechanism that would otherwise have tested a marginal design before it was built.
Interaction with other approvals
A decision made under the program does not replace every other approval a project needs. Building permits, works approvals under environmental legislation, cultural heritage requirements, and the requirements of individual referral authorities still apply in the normal way, regardless of who granted the planning approval. The program changes the planning decision-making pathway. It does not fold every other regulatory step into the same process, and treating it as though it did is a common programming mistake.
That distinction matters for sequencing. A developer who assumes the entire approval chain compresses to match the planning decision can be caught out when a downstream approval, unrelated to the planning pathway, still runs on its own ordinary timetable regardless of how the rezoning or permit was obtained. Utility connection approvals in particular tend to run on the utility's own program rather than the planning authority's, and that program does not accelerate just because the planning decision did.
The realistic programme benefit of this pathway sits in the planning decision itself. It should be modelled there, quantified against what a comparable council-run assessment would likely take, rather than assumed to flow through every subsequent approval step in the same proportion.
How to model it
Do not model an application under the program as simply the same permit process running faster. Model it as a different process with a different risk profile. The upside is a defined and generally shorter path to a decision. The downside, if the project attracts strong local opposition, is that the usual mechanism for resolving that opposition through formal objection and review is not available in the same way.
Confirm eligibility early, against the current program settings, rather than assuming a project that might have qualified previously still does. Because those settings are administrative and reviewed over time, a project's eligibility should be checked directly with the department rather than relied on from a prior deal.
What to check before exchange
Confirm, in writing from the department, whether the specific project is eligible for the program under its current settings, rather than proceeding on an assumption. Map out what referral authorities will still need to be consulted, since their requirements do not disappear just because the Minister is the decision maker.
Consider the local political context around the site honestly. A program that removes formal objection rights does not remove the underlying community sentiment, and a contentious site can still generate delay through other means even where a tribunal review is not part of the pathway. Build a realistic view of programme timing from the department's published settings instead of the fastest case study available, and treat the trade between speed and third-party rights as a genuine commercial decision rather than an automatic win.
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.vic.gov.au · legislation.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.