Back to Journal
The Development Plan Overlay: Clause 43.04 and what it defersPhoto: SiteLogic editorial image

planning

The Development Plan Overlay: Clause 43.04 and what it defers

How Clause 43.04 blocks a permit application until a development plan is agreed with council, what that sequencing means for programme, and the notice and review exemption an approved plan can trigger.

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

A Development Plan Overlay is not a design control in the way a Design and Development Overlay is. It is a sequencing control. It tells a developer that a permit for the site cannot be sought at all until a separate document, the development plan, has been prepared and agreed with the responsible authority. That step change in process, more than any single numeric standard, is what a DPO defers, and it needs to be identified early, well before the first concept plan is drawn.

The provision

VPP Clause 43.04 allows a planning scheme to identify land where development depends on a coordinated development plan rather than a single site-by-site assessment. Its purpose is to identify areas which require the form and conditions of future development to be shown on a development plan before a permit can be granted, and to allow the requirements of that plan to be carried into subsequent permits. It is most often used over larger sites, growth-area precincts or fragmented ownership, where piecemeal permits would work against an integrated outcome for roads, drainage, open space or staging.

What it requires

Where a DPO applies, the clause generally prevents the responsible authority from granting a permit to use or subdivide the land, or to construct a building or construct or carry out works, until a development plan has been prepared to its satisfaction and, where the schedule requires it, generally in accordance with any specified requirements. The schedule sets out what the development plan itself must show and address, which can include the pattern of subdivision, the road and movement network, the open space and drainage strategy, staging, and interfaces with adjoining land.

The consequence that most affects a project is the notice and review outcome the schedule can attach once a development plan is approved. A schedule may provide that a permit application which is generally in accordance with an approved development plan is exempt from the notice requirements of the Act and from third-party review rights. That materially changes how the subsequent permit stage runs, since it removes the objection and appeal risk that would otherwise sit over every stage of a staged project. It only applies, however, once the development plan itself has been through its own approval process, and only to applications that stay within it.

How to model it

Build the development plan step into the programme as its own gate, separate from and prior to the design and permit programme, because a DPO changes when design certainty can be relied upon, not just how the design is assessed. Where a site is subject to a DPO, avoid carrying a permit-ready timeline that assumes concept design can proceed without reference to what the development plan will need to demonstrate, since the plan will fix the road layout, lot pattern, open space location and staging that any later permit application has to sit inside.

The following figures are illustrative. They demonstrate the method and will vary by site, council and timing. A feasibility on a DPO-affected growth-area parcel might otherwise assume a twelve-month path from acquisition to a permit-ready subdivision layout. If the schedule requires council agreement to an area-wide development plan covering drainage and a collector road alignment shared with adjoining ownerships, the realistic programme could run to two years or more before a subdivision permit application is even lodged, driven by negotiation with adjoining owners, servicing authorities and the responsible authority rather than by the applicant's own design pace. Carrying only the shorter timeline in a feasibility understates holding costs and can misstate the return on a site that is otherwise sound.

Where the site sits within a larger DPO precinct and a development plan already exists or is in preparation by others, check whether that existing or draft plan already fixes the constraints the site will need to work within. A later entrant to a precinct can have far less scope to influence road or lot layout than an owner negotiating the plan from the outset.

Interaction with other controls

A DPO frequently sits alongside a Precinct Structure Plan, a Comprehensive Development Plan or a Development Contributions Plan over the same growth-area land, and the schedule may cross-reference those instruments rather than restate their content. Reading the DPO schedule in isolation, without the precinct-level documents it points to, will understate the coordination task. Where the site also carries an infrastructure or open space contribution obligation tied to the same precinct, that obligation is usually resolved through the development plan process rather than at the permit stage, which is another reason to bring it forward in the programme.

What to check before exchange

Confirm whether a development plan for the site or the broader DPO precinct has already been approved, is in preparation, or does not yet exist, since each position carries a materially different programme and cost. Where a plan exists, obtain it and check whether the concept can genuinely be generally in accordance with it, rather than assuming compliance from the zone and overlay maps alone.

Identify who else needs to agree the plan, since a DPO covering multiple ownerships can mean the programme depends on a landowner group, a precinct-level process, or another party's timeline as much as on council. Check the schedule for any requirement to fund or contribute to shared infrastructure, such as roads, drainage or open space, as a condition of development plan approval, and carry that as a cost line rather than an assumption.

Check whether the schedule specifies referral authorities for the development plan itself, since servicing authorities can add both time and design constraints before a permit application is even considered. Finally, confirm that the exemption from notice and review the schedule may attach to an approved plan is still available for the specific application contemplated, since some schedules limit the exemption to applications that closely match the plan, and a materially different later application can fall back into the ordinary notice and appeal process. Planning Victoria's guides and resources page is a useful entry point for how overlay-driven processes like this are administered, though the schedule and any precinct documents it references remain the operative record.

Record keeping

Keep the approved development plan, and any council correspondence about what "generally in accordance" is taken to mean for the site, in the project file alongside the eventual permit application. Where a later stage of a staged project departs from the plan in any material respect, treat that stage as requiring a fresh assessment of whether the notice and review exemption still applies, rather than assuming it carries forward automatically. Revisit the development plan if a precinct-level document it relies on, such as an infrastructure or open space contributions arrangement, is itself amended during the life of the project.


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.