For Council Development Engineers, the pressure is constant. You are facing a tsunami of Development Applications (DAs), tight turnaround targets, and increasing density requirements. In this environment, it is tempting to treat the stormwater report as a “tick-box” exercise.
If the MUSIC model hits the targets and the DRAINS file shows no flooding, it gets approved.
But a compliant model on a screen often translates to a liability in the ground. When a developer moves on, Council is often left holding the baby—inheriting “public” assets that are expensive to maintain, prone to failure, or functionally useless.
Effective peer review is not just about checking the maths; it’s about protecting your future Operational Budget (OPEX). Here is a guide to looking beyond the compliance certificate and stress-testing the reality of a developer’s submission.
1. The “Desktop vs. Reality” Gap (Hydrology)
Developers are incentivised to maximise yield. This often leads to “optimistic” hydrological assumptions to minimise the size of On-Site Detention (OSD) or basins.
What to Audit:
- Impervious Area Fractions: Check the claimed “pervious” (grass/landscape) zones. In medium-density designs, “landscaped” areas often end up being paved by future residents or are too small to absorb real rainfall. If the model assumes 40% green space but the plans show 90% hardstand, the OSD is undersized.
- Tailwater Assumptions: Does the model assume the receiving creek or pipe is empty? In a major storm, the downstream network is likely full (backwater effect). A robust review demands sensitivity testing with high tailwater levels to prove the site won’t flood when the network is stressed.
2. The MUSIC Model “Magic”
Water Quality models are notoriously easy to manipulate. A slight tweak to a filter media specification or a “treatment node” can make a failing site look compliant.
What to Audit:
- Proprietary Cartridges: Be wary of designs that rely heavily on proprietary stormwater cartridges to hit nutrient targets. These are expensive to replace. If this asset is being handed to Council, demand a Lifecycle Cost Analysis. Can your depot budget afford $15,000 every year for filter replacements?
- Bio-Basin “Optimism”: Check the “Extended Detention Depth” and filter media surface area. Developers often squeeze bio-basins into tiny, shaded corners where plants will inevitably die. A MUSIC model doesn’t know that plants need sunlight; you do.
3. The “Mower Test” (Maintenance Access)
This is the most common failure point for assets handed over to Council (dedicated assets). An asset that cannot be easily maintained will eventually fail.
The Peer Review Checklist:
- The “Suction Truck” Test: Can a 12-tonne Gross Pollutant Trap (GPT) cleaning truck legally and physically access the pit? Are there hardstands for outriggers? Is the reversing path safe?
- The “Mower” Test: Are the batter slopes on the detention basin steeper than 1:4? If so, your maintenance crew cannot safely mow them. The basin will become a weed-infested liability.
- Confined Spaces: Does the design require a Confined Space Entry team for routine inspections? If so, push back. Demand surface-level inspection points to reduce your WHS risk and inspection costs.
4. Defending the “Public Asset” List
Not every drainage line should become a Council asset. Developers often try to categorize complex inter-allotment drainage systems as “Public” to shift the maintenance burden.
The Strategy:
Enforce a strict policy on Benefited Lots. If a line serves only a specific private strata complex, it should remain private property via an easement, not become a Council main. Use your peer review to challenge the “Public” classification of infrastructure that provides no wider community benefit.
Summary
A rigorous peer review is your only line of defence against inheriting a 50-year liability.
You have the right to challenge assumptions, demand lifecycle costings, and reject designs that transfer unfair risk to the ratepayer.
Overwhelmed by complex DA submissions?
[Engage Our Advisory Team] to act as your independent peer reviewer. We assess developer designs for technical accuracy, constructability, and long-term maintenance liability, giving you the confidence to say “Approved” or “Refused.”
