Half of the questions we field from developers come down to one thing: does my project need Melbourne Water approval, and if so, when in the planning process does that happen? The honest answer is that the rules sit in a clause most planning consultants never read in detail — Clause 66.04 of the Victorian Planning Provisions — and the practical effect catches a lot of projects by surprise.
This is a plain-English guide to Melbourne Water referral for stormwater management plans. What triggers it, what the review actually covers, how long it takes, and what tends to go wrong.
What Clause 66.04 actually says
Clause 66.04 is the part of the Victorian Planning Provisions that lists which planning permit applications must be referred to Melbourne Water as a referral authority. It is not a clause about stormwater specifically — it is a procedural clause about which referrals the council has to make before deciding on a permit. Stormwater happens to be the largest category Melbourne Water gets referred for.
The triggers fall into three groups:
- Sites within a Melbourne Water declared drainage scheme. Most of Melbourne’s outer-growth corridor councils — Wyndham, Whittlesea, Hume, Casey, Melton, Cardinia — sit within Melbourne Water’s Port Phillip and Westernport Drainage Schemes. Subdivisions and many larger developments inside these scheme areas must be referred.
- Sites near a designated waterway or floodway. Properties adjacent to or within a Land Subject to Inundation Overlay (LSIO), Special Building Overlay (SBO), or other flood-related overlay typically trigger Melbourne Water referral on flood-compatibility grounds.
- Sites above a defined scale or impact threshold. Larger developments — typically subdivisions above a certain lot count, or commercial sites with significant impervious area increase — are referred on a project-by-project basis where the council’s local scheme requires it.
If your site is none of those three, Melbourne Water is unlikely to be a referral authority for the project. If it is any of them, plan for it from the start.
What the Melbourne Water review actually covers
Melbourne Water’s review is not a duplicate council review. They are looking at a narrower set of questions:
- Is the proposed treatment train consistent with the scheme drainage strategy for the catchment? (Where one applies.)
- Does the post-development discharge match what the downstream scheme infrastructure was sized to receive?
- Where the site sits in or near a flood overlay, is the development flood-compatible?
- Are the WSUD treatment measures sized correctly against EPA Publication 1739.1, and in particular against the STORM or MUSIC modelling tool the scheme expects?
The questions are technical, the documentation expectations are specific, and the response Melbourne Water sends back is usually short. They will either issue a “no objection” letter, attach conditions to the permit, or request further information.
Typical timeframes
The clock starts when the council formally refers the application — not when you lodge with the council. From there:
- A clean referral with documentation that aligns with what the scheme expects: typically two to four weeks.
- A referral that triggers a request for further information: add another two to four weeks per round.
- Referrals on flood-compatibility grounds where finished-floor levels or outlet configurations are in question: longer, often six weeks or more.
The biggest variable is documentation quality at first submission. Referrals that arrive with the right modelling, the right scheme-coordination, and the right flood compatibility check typically clear without an RFI. Referrals that arrive with mismatched scheme assumptions or generic WSUD treatments often go two or three rounds.
What tends to go wrong
Three patterns we see repeatedly:
Treatment train designed against the wrong scheme. A treatment train sized for a generic STORM ≥100% target may not match what the local Melbourne Water drainage scheme expects. The scheme often anticipates lot-scale measures plus an estate-scale wetland — design only the lot-scale and you get an RFI asking where the wetland integration sits.
Legal Point of Discharge confirmed late. Melbourne Water expects the Legal Point of Discharge to be identified, agreed, and shown on the documentation before they assess. Projects that submit with “Legal Point of Discharge to be confirmed” tend to come back with a request to confirm it before further review.
Flood compatibility treated as a separate exercise. Where the site sits within or adjacent to LSIO or SBO coverage, Melbourne Water expects flood compatibility to be addressed in the same package as the stormwater management plan — finished-floor levels, outlet configurations, and detention storage all factored in together. Treating flood compatibility as a separate report that lands later is a common cause of delay.
What to do about it
If your project is in any of the three trigger categories, three things help:
- Confirm referral status before lodgement. A 15-minute check at the start of the project is cheaper than a four-week RFI loop later. Send the project address to your stormwater consultant and have them confirm whether Clause 66.04 referral applies.
- Design against the local scheme, not a generic target. If the site sits within a Melbourne Water drainage scheme, the treatment train has to coordinate with that scheme. The lot-scale STORM score is necessary but not sufficient.
- Package flood compatibility, Legal Point of Discharge, and treatment train as a single document. Melbourne Water reviews them together; submit them together.
Get those three right and the referral is usually a non-event. Skip them and the referral becomes the longest part of the planning timeline.
If you have a project in a Melbourne Water drainage scheme area or near a flood overlay, send your project address and we’ll confirm referral status and what the review will look like. For related scope and quote inputs, see the Stormwater Management Plan service path.