Stormwater Quality Targets in Sydney: MUSIC Modelling Explained

Somewhere in the consent conditions or the DCP for almost every significant development in Greater Sydney sits a table of percentages: reduce gross pollutants by so much, suspended solids by so much, phosphorus and nitrogen by so much. To a builder or developer working through a DA, those numbers can feel abstract — until council refuses to accept your stormwater plans without a MUSIC model demonstrating you meet them. Then the questions start. What do the targets actually mean? Why does one council want a different report format to the next? And why is your engineer asking how big the rainwater tank is and how many toilets it flushes?

This post explains stormwater quality targets and MUSIC modelling in plain terms: where the common target numbers come from, when a development triggers a water quality assessment, how the model actually works, what MUSIC-link is, how a compliant treatment train gets put together for typical Sydney sites, and the criticisms council reviewers most often raise. If you’re a builder, developer or certifier who just wants the assessment done right the first time, this is the background that makes the process make sense.

What the pollutant reduction targets actually are

Urban development changes what washes off a site. Roofs, driveways and roads shed water fast and carry litter, sediment, nutrients and metals straight into the pipe network and out to creeks, rivers and eventually Sydney Harbour, the Hawkesbury-Nepean or Botany Bay. Stormwater quality targets exist to cap that impact. They are expressed as percentage reductions in the mean annual pollutant load leaving the developed site, compared with the same site untreated, across four indicator pollutants:

Gross pollutants (GP) — litter and debris larger than 5 mm.
Total suspended solids (TSS) — fine sediment, which smothers waterway habitat and carries other pollutants with it.
Total phosphorus (TP) — a nutrient that drives algal growth in waterways.
Total nitrogen (TN) — the hardest to remove, and usually the target that governs how much treatment your site needs.

A set of figures you will see again and again is 90 per cent gross pollutants, 85 per cent TSS, 65 per cent TP and 45 per cent TN. These are commonly adopted targets across many Sydney councils — but they are not universal law. They vary by council and catchment, some councils add flow-based or drainage-specific criteria, and sensitive catchments can carry tighter numbers. Always check the specific council’s DCP, WSUD technical guideline or MUSIC-link profile before assuming the standard set applies to your site.

Notice the gradient in those numbers. Litter is easy to trap, so the GP target is high. Nitrogen is largely dissolved and only comes out through biological processes, so the target is lower — and it is almost always nitrogen that determines whether your treatment train is big enough. If a proposed design meets TN, it usually meets everything else comfortably.

When does a DA trigger a MUSIC assessment?

Not every development needs a water quality model. Councils set thresholds in their DCPs — commonly framed around development type, site area, or the amount of new impervious surface created. A single dwelling alteration may be exempt; a dual occupancy, multi-dwelling, industrial or commercial development, or subdivision very often is not. The thresholds genuinely vary across Sydney’s councils, and they change as DCPs are updated, so the safe move is to check the relevant DCP early — at concept design, not after the architect has locked in the site layout. Discovering at lodgement that you need a raingarden, and that there’s nowhere to put one, is an expensive way to learn about WSUD.

For certifiers, the trigger question cuts the other way: consent conditions frequently require the approved WSUD measures to be constructed and certified before an occupation certificate, so the MUSIC model and the drawings it validates become documents you’ll rely on well after the DA stage.

How MUSIC works, in plain terms

MUSIC — the Model for Urban Stormwater Improvement Conceptualisation, developed by eWater — is the standard tool most Sydney councils require for these assessments. Strip away the interface and it does something conceptually simple: it runs years of local rainfall over a digital version of your site and counts the pollutants coming out, with and without your proposed treatment.

Source nodes: the site, by surface type

The engineer breaks the site into source nodes by surface type — roof, road and paved areas, landscape — because each surface generates runoff and pollutants differently. Roofs are relatively clean but shed almost everything that lands on them; roads carry sediment and metals; landscaped areas absorb most small events. Each node carries pollutant export parameters, and here is a critical practice point: where the council specifies rainfall templates and pollutant parameters, those must be used. Councils publish them precisely so every applicant models on the same basis, and substituting softer parameters is one of the fastest ways to get a model rejected.

Climate template and continuous simulation

Rather than modelling a single design storm the way a flood study does, MUSIC runs a continuous simulation — typically years of rainfall at short timesteps from a council-nominated template. That matters because water quality is a long-run game: most annual pollutant load is carried by the frequent small and medium storms, not the rare big one. The outputs are mean annual loads — kilograms of sediment and nutrients per year — for the untreated and treated cases, and the percentage difference between them is what gets compared against the targets.

Treatment nodes and the train

Between the sources and the outlet, the engineer inserts treatment nodes representing physical devices — a gross pollutant trap, a rainwater tank with re-use, a bioretention system, permeable paving. MUSIC routes flows through them in sequence, which is why the arrangement is called a treatment train: each carriage removes what it’s good at and passes the rest along. The model then reports whether the whole train, working together across the full simulated record, achieves the required reductions.

MUSIC-link: the council’s parameters, built in

MUSIC-link is an eWater feature that embeds individual councils’ modelling parameters and targets as council-specific profiles within the software. Instead of the engineer manually assembling rainfall data and pollutant parameters from a PDF guideline, the profile applies them, and the model is validated directly against that council’s requirements. The output is a compliance report that states, in the council’s own terms, whether the model passes.

Many — though not all — Sydney councils maintain MUSIC-link profiles, and those that do generally expect the compliance report lodged with the DA. For applicants, this is good news: it standardises the review, reduces argument about assumptions, and makes it obvious early whether a proposed treatment train stacks up. Where a council has no profile, the engineer works from the DCP and WSUD guideline directly, and the reporting burden is a little higher because every assumption needs to be documented and justified.

Building a compliant treatment train for typical Sydney sites

So what does compliance actually look like on the ground? The recipe varies with site type, but the logic is consistent: trap the coarse material first, intercept and re-use what you can, then treat the remainder biologically.

Residential and duplex sites

For a dual occupancy or small multi-dwelling site, a typical train is a rainwater tank on each dwelling with re-use plumbed to toilets, laundry and irrigation, pit inserts or a small GPT on the paved area drainage, and a bioretention raingarden — often a few square metres in the front setback — treating the balance before discharge. The tank matters more than people expect: every kilolitre of roof water re-used is runoff and pollutant load that never leaves the site. But the re-use demand must be realistic and justified by the number of occupants and connected fixtures, which is exactly why your engineer asks about toilets.

Commercial and industrial sites

Larger hardstand-dominated sites usually lean on a proprietary GPT at the pipe network low point, tanks where there is genuine re-use demand, and either bioretention or proprietary cartridge filter devices where landscape area is scarce. A note of caution on proprietary devices: some councils restrict their use or require field-verified performance data before accepting the manufacturer’s claimed removal rates. If your site strategy depends on a cartridge system, confirm the council’s position before the design is locked in.

Subdivisions

Subdivision-scale development typically consolidates treatment — streetscape raingardens or an end-of-line bioretention basin with a sediment forebay — sized in MUSIC against the whole catchment and handed over with a maintenance framework. The same modelling rules apply; the stakes and the maintenance obligations are just bigger.

What council reviewers push back on

Council stormwater engineers review MUSIC models constantly, and they check the same things every time: node parameters against the council’s specified values, treatment sizes against the design guidelines, and performance claims against reality. The recurring criticisms:

Fudged source parameters — pollutant export or rainfall inputs that don’t match the council’s specification, conveniently reducing the untreated load.
Oversized re-use demand — a rainwater tank modelled with implausible daily demand so it never spills. Reviewers sanity-check demand against dwelling occupancy and connected uses.
Optimistic proprietary device claims — treatment nodes reflecting brochure numbers rather than verified performance, particularly where the council requires field data.
Model-drawing mismatch — a bioretention node with 15 square metres of filter area where the drawings show 8, or an extended detention depth that doesn’t exist on the section. Every node parameter should trace to the drawings.
Unrealistic overall performance — treatment trains claiming removal rates beyond what the guidelines say the measures can achieve, which invites a line-by-line audit of the whole model.

None of these tricks save money. They convert a two-week assessment into a months-long correspondence, and they mark the application as one to scrutinise.

Modelled compliance is not real-world performance

One more distinction worth understanding: a passing MUSIC report describes how the treatment train performs if it is built to specification and maintained. The model assumes the GPT gets cleaned, the raingarden media stays permeable, the plants survive and the tank pump keeps working. Neglect any of those and real performance degrades quietly while the paperwork still says compliant.

That is why councils increasingly condition consents on maintenance schedules, and on private sites often a positive covenant on title obliging owners to keep the systems functioning. For builders, the practical implication is at handover: the owner or strata needs to know these devices exist and what looking after them involves. For certifiers, it means checking that what was modelled is what was installed — media certificates, device sizes, plumbing of the re-use connection — before signing off.

What to give your stormwater engineer

A MUSIC assessment goes fastest when the engineer has the right inputs from day one. If you’re commissioning one, have ready:

The site survey and the current architectural site plan, with roof, driveway and landscape areas resolved as far as possible.
The council and, if you have them, any pre-DA advice or consent conditions referencing water quality.
Proposed rainwater tank size and what it will supply — toilets, laundry, irrigation — since re-use demand drives the modelling.
The drainage concept: where the site legally discharges, and any OSD requirements that will share space with the quality measures.
Landscape intentions, because raingardens have to live somewhere and integrate far better when the landscape designer knows about them early.

Get those settled and the model, the WSUD plans and the MUSIC-link compliance report typically come together as a single tidy package — one that a council reviewer can approve without a second round of questions.

Frequently Asked Questions

Are the 90/85/65/45 reduction targets the same for every Sydney council?

No. Reducing gross pollutants by 90 per cent, TSS by 85 per cent, TP by 65 per cent and TN by 45 per cent is a commonly adopted set across many Sydney councils, but targets vary by council and catchment, and some add extra criteria. Always check the specific council’s DCP or MUSIC-link profile for your site.

Does my development need a MUSIC model?

It depends on the council and the development type. Thresholds are typically framed around development category, site area or new impervious area, and they differ between DCPs. Dual occupancies, multi-dwelling housing, commercial and industrial development and subdivisions commonly trigger an assessment. Check the DCP early or ask a stormwater engineer to confirm.

What is a MUSIC-link report and why does council want it?

MUSIC-link embeds a council’s own modelling parameters and targets in the MUSIC software and validates your model against them, producing a standardised compliance report. Councils with profiles want it because it confirms the model used their required assumptions — which shortens review and removes argument about inputs.

If the MUSIC model passes, is the job done?

Not quite. The model demonstrates compliance for a system that is built to the documented specification and maintained. Councils typically require the measures to be constructed, certified and covered by a maintenance schedule — often with a positive covenant on private land — so the model, the drawings and the built result all need to line up.

Need a MUSIC model and WSUD strategy that clears council review? Contrive Consultants prepares MUSIC and MUSIC-link assessments, treatment train designs and stormwater documentation for builders, developers and certifiers across Greater Sydney and NSW. Explore our stormwater engineering services or get in touch to discuss your site — call +61 497 848 111 or email info@contriveconsultants.com.au.