> For the complete documentation index, see [llms.txt](https://greenstarresources.gbca.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://greenstarresources.gbca.au/greenstarresources.gbca.au_ratingtools/current-green-star-rating-tools/green-star-buildings/v1.1/categories-and-credits/nature-2/42-or-waterway-protection.md).

# 42 | Waterway Protection

Points: 2

## <mark style="color:$primary;">Outcome</mark>

Local waterways are protected, and the impacts of flooding and drought are reduced.

## <mark style="color:$primary;">Criteria</mark>

<mark style="color:$success;">**Credit Achievement — 2 points**</mark>

* [#id-42.1.1-pollutant-reduction-targets](#id-42.1.1-pollutant-reduction-targets "mention"): Specified pollution reduction targets are met.
* [#id-42.1.2-stormwater-volume-management](#id-42.1.2-stormwater-volume-management "mention"): The project demonstrates an appropriate level of stormwater volume management as determined by a site and water catchment assessment.

***

## <mark style="color:$primary;">Additional information</mark>

#### Scope of credit

All areas within the Green Star project boundary. If the project is part of a shared sitewide stormwater strategy where the site boundary is beyond the Green Star project boundary, the project's site boundary may be used.

#### Stage implementation

**Strategy** | **Brief** | **Concept** | **Design** | **Tender** | **Construction** | **Handover** | **Use**

#### Synergies with other credits

* Nature Connectivity
* Biodiversity Enhancement
* Water Use
* Climate Resilience
* Operations Resilience

#### Sustainable Development Goals

* **Goal 13:** Climate Action
* **Goal 14:** Life Below Water

#### Relevant reporting initiatives

* GRESB
* Task Force on Nature-related Financial Disclosure **(TNFD)**

***

## <mark style="color:$primary;">Requirements</mark>

### <mark style="color:$success;">Credit Achievement</mark>

The project must comply with **both** of the following criteria:

* Pollution Reduction Targets
* Stormwater Volume Management

#### 42.1.1 Pollutant Reduction Targets

All stormwater discharged from site meets specified pollution reduction targets listed in the table below.

| Pollutant                     | Reduction Target (% of the post development annual average load) |
| ----------------------------- | ---------------------------------------------------------------- |
| Total Suspended Solids (TSS)1 | 85%                                                              |
| Gross Pollutants              | 90%                                                              |
| Total Nitrogen (TN)2          | 45%                                                              |
| Total Phosphorus (TP)2        | 65%                                                              |

1 Load based on the following particulate size distribution (by mass): 20% <20 μm; 20% 20-60 μm; 20% 60-150 μm; 20% 150-400 μm; 20% 400-2000 μm.

2 Load includes particulate and dissolved fraction.

#### *Environmental Management*

The risk of chemical pollutants and other toxicants entering the stormwater system is minimised by the following:

* Chemical storage, loading, refuelling or work areas have installed bunding, with any spills draining to trade waste or appropriate treatment devices. These areas also have roofing to separately divert rainfall into the stormwater system.
* If a site has more than 200m² of uncovered areas where vehicles are likely to transit and/or park, these areas drain to a Water Sensitive Urban Design (WSUD) treatments that meet the above pollution reduction targets for pollutant reduction. Electric vehicle only parking areas do not contribute towards the total suspended solids, gross pollutants, total nitrogen and total phosphorus.
* During construction, the construction environmental management plan (EMP) addresses sediment and erosion control.

#### 42.1.2 Stormwater Volume Management

The project conducts a site and water catchment assessment to determine if stormwater volume management is required for the site.

#### *Site and Water Catchment Assessment*

An assessment of the project site and the needs of the local waterways is completed by the project team with input from a qualified ecologist and a qualified civil engineer.

As a minimum, the assessment identifies:

* **The local catchment ecological context:** Locate and describe high value waterways, sensitive receiving environments, or priority areas for conservation. Identify sites in the downstream catchment that have high ecological value.
* Local council, water authority and state government targets, policies and guidelines that apply to the site.
* **Local precinct approaches** to stormwater volume management including any water sensitive urban design (WSUD) infrastructure.
* **Opportunities and constraints on site**: Describe if there are opportunities for the site for managing and controlling stormwater runoff by infiltrating, evaporating, storing, treating and detaining it and/or describe constraints that are preventing the site from reducing high volumes of stormwater runoff.

Where the project can demonstrate one or more of the following is relevant, they are exempt from meeting the requirements in *Stormwater Volume:*

* A coastal site where the project stormwater outflows are directly into tidal areas or the ocean.
* A site where groundwater infiltration is not appropriate due to soil or topographical conditions (refer Guidance for examples) and the project has insufficient demand for harvested water.
* In a tropical region (as per NCC climate zones) where retention of high intensity flows on larger sites is not feasible. Sub-tropical sites are required to meet volume criterion.
* Downstream stormwater harvesting or recycling.
* A site where runoff is to be maximised for ecological reasons (e.g., to help flush a stagnant or saline wetland in an arid climate).

#### *Stormwater Volume*

Where stormwater volume reduction is required, it is shown to be reduced by demonstrating one of the following:

* A reduction in average annual stormwater discharge (ML/yr) of 30% against a Reference case. The reference case is the proposed project without any stormwater volume reduction strategies.
* The runoff volume at the site discharge point is equal pre- and post-development for a 50% Annual Exceedance Probability (AEP) storm.

The project team provides a plan documenting how appropriate evaluation, monitoring, and maintenance of stormwater control measures (and associated reporting of their condition) will be undertaken to enhance their design stormwater treatment function. The plan is included in the operations and maintenance information provided to the building owner.

***

## <mark style="color:$primary;">Alternative pathways</mark>&#x20;

Where there are alternative pathways that a project can follow to achieve the credit, or sector specific alternatives.&#x20;

These were previously referred to as *Frequently Asked Questions*.&#x20;

<details>

<summary>Alternative pathways</summary>

Existing FAQs are currently located [*here*](https://www.gbca.org.au/greenstar-manager/faqs/). GBCA are working on bringing them across to this site. New FAQs will be published here under the relevant credit and type.

</details>

***

## <mark style="color:$primary;">Clarifications</mark>

Where GBCA have clarified any requirements of the credit criteria. This information is additional and it is not complusory to apply.

These were previously referred to as *Frequently Asked Questions*.&#x20;

<details>

<summary>Clarifications</summary>

Existing FAQs are currently located [*here*](https://www.gbca.org.au/greenstar-manager/faqs/). GBCA are working on bringing them across to this site. New FAQs will be published here under the relevant credit and type.

</details>

***

## <mark style="color:$primary;">Definitions</mark>

Definitions provided here must be applied to Requirements unless agreed with GBCA via a Technical Question.

[Glossary](https://greenstarresources.gbca.au/greenstarresources.gbca.au_ratingtools/current-green-star-rating-tools/all-definitions.md#pre-development)

[Glossary](https://greenstarresources.gbca.au/greenstarresources.gbca.au_ratingtools/current-green-star-rating-tools/all-definitions.md#project-boundary)

[Glossary](https://greenstarresources.gbca.au/greenstarresources.gbca.au_ratingtools/current-green-star-rating-tools/all-definitions.md#qualified-civil-engineer)

[Glossary](https://greenstarresources.gbca.au/greenstarresources.gbca.au_ratingtools/current-green-star-rating-tools/all-definitions.md#qualified-ecologist)

[Glossary](https://greenstarresources.gbca.au/greenstarresources.gbca.au_ratingtools/current-green-star-rating-tools/all-definitions.md#site-boundary)

[Glossary](https://greenstarresources.gbca.au/greenstarresources.gbca.au_ratingtools/current-green-star-rating-tools/all-definitions.md#water-sensitive-urban-design-wsud)

***

## <mark style="color:$primary;">Guidance</mark>

Guidance is supporting information for the credit requirements and is not mandatory to apply.

**Pollutant reduction**\
A reduction in average annual stormwater pollutant loads refers to the average annual reduction in stormwater pollutant loads discharged from the development, with treatment, compared with the stormwater pollutant loads that would be discharged without treatment.

*Modelling*\
Pollutant export modelling using computer programs such as MUSIC, STORM etc. can be used to predict the discharge pollutant loads for the total site area. The results of the simulation must show a comparison against the relevant reduction targets for offsite reductions.

**Site and water catchment assessment**\
*Local catchment ecological context*\
Downstream catchment sites that have high ecological value may include water catchments, protected wetlands, swimming beaches, streams and rivers with high biodiversity, platypus populations or sensitive fish, insect or amphibian species.

*Exemption scenarios*\
The listed scenarios where a project is exempt from meeting the [Stormwater Volume](#stormwater-volume) requirements are examples where for ecological reasons, stormwater volume reduction is not relevant. If the project is in a scenario that is not listed and can justify that stormwater volume reduction is not relevant for ecological reasons, a Technical Question can be submitted.

**Stormwater volume reduction**\
The aim of stormwater volume reduction is to reduce hydrologic and flooding impacts on downstream ecosystems. There are two methods available to account of location-based challenges including rainfall and site area.

**Average annual stormwater discharge reduction**\
This approach encourages projects to reduce the average annual stormwater discharge leaving the project's site in comparison to a version of the project without any volume reduction strategies.

Pre- and post-development runoff\
This approach recognises projects that aim to mimic the natural flows of the site. This approach may be better suited for projects that do not have a high water use demand or have limited site area that can be pervious.

**Modelling**\
Typical urban annual load reductions can be estimated using continuous simulation modelling software such as MUSIC, SWMM, XPSWMM, or InSite. Where available, relevant guideline values for pollutant concentrations for the catchment land use and surface type should be used. In areas where there are no specific guidelines, reference can be made to sources such as Australian Runoff Quality (ARQ, 2006).

**Volume management strategies**\
The strategies to consider for both approaches may include a combination of harvesting, detention for slow release, infiltration and/or other Water Sensitive Urban Design practices. Further guidance is available in the Australian Rainfall & Runoff Guidelines (AR\&R 2019).

*Harvesting*\
Stormwater can be harvested, stored and treated for reuse in the project. For projects where the building footprint covers the whole site, projects may use the Water Use calculator to demonstrate that the building captures and reuses the required stormwater volume to meet the requirements. The annual average stormwater volume can be based on the average rainfall volume for the whole site, using an impervious area coefficient of runoff of 0.9.

*Slow-release devices*\
This is a method of detaining water and releasing is slowly over the catchment time of concentration (considered to be 6 hours for this credit) to mimic the more natural flow regimes of undeveloped catchments.

*Infiltration*\
In most cases groundwater infiltrated into the ground is deemed to treat water pollution (TSS, TN, TP, and Gross pollutants) (refer CSIRO & Government of Western Australia guidance linked below). The % of stormwater infiltrated is counted towards volume and pollution reduction targets. Usually soil microbes will bio-attenuate the low concentration pollutants found in stormwater. Infiltration systems should be designed with sediment control in mind to prevent them being blocked by fine silts.

Groundwater infiltration has many benefits such as providing water for trees, recharging local aquifers, and encouraging more natural flow regimes in local waterways. Soil filters and purifies stormwater and soil microbes will usually remove most nutrients. Infiltration approaches require designers to consider interaction with soil properties, capacity of aquifers, urban form and local authority guidelines (refer AR\&R Book 9, Chapter 3).

Infiltration is not suitable where industrial pollution, hydrocarbon or chemical risks could cause groundwater contamination.

Infiltration will not be appropriate in certain areas including shallow saline aquifers, unstable slopes, capped contaminated soil, impervious soils, sites with existing groundwater contamination, unconsolidated fill and highly reactive impervious clays close to building footings. It is recommended to coordinate with the geotechnical engineer and the structural engineer if there is any doubt about soil suitability for infiltration.

*On site detention*\
For some sites, local councils may require limitation of post-development peak event discharge from the site. This is commonly called On Site Detention (OSD). OSD is not an integrated water management solution for Green Star purposes, but relevant local council requirements should also be integrated and included in the design and submission documentation for consistency and buildability.

**Pre-determined infrastructure**\
It is noted that some local governments may provide pre-determined infrastructure solutions that are 'deemed to comply' with the aim of this credit criterion. Some sites may also be 'not applicable' for the volume control target if for example they are in an area of downstream stormwater harvesting and wish to maximise stormwater from the site. If this is the case the project team should submit a Technical Question to have this approach approved.

***

## <mark style="color:$primary;">Submission content</mark>

Submissions for this credit must contain:

* **Submission form** through Green Star Online
* **Evidence** to support claims made in the submission

#### Recommended evidence

The following list of evidence serves as a guide for the Certified submission and is not exhaustive. Project teams are not required to provide all of the listed items and alternate forms of documentation can be used to demonstrate compliance. The key requirement is that evidence is provided to support each claim.

**Pollution Reduction Targets**

* Site plans showing the total areas of uncovered areas where vehicles are likely to transit and/or park (e.g., roads, loading docks, refuelling bays, and car parking, etc).
* As built civil, hydraulic and landscape drawings showing the stormwater collection, storage, infiltration, and treatment facilities and detailing their functional elements.
* Independently verified performance certification for each manufactured stormwater treatment device, proving its ability to achieve the pollution reduction targets.
* Calculation report by a suitably qualified professional describing how the water quality objectives will be achieved referencing calculations, and listing assumptions made.

**Stormwater Volume Management**

* Site and catchment assessment.
* Calculation report by a suitably qualified professional describing the strategies implemented.
* As built civil and landscape drawings showing the stormwater collection, storage and treatment facilities and detailing their functional elements.
* As built hydraulics drawings showing all the capture, storage, re-use piping and discharge route.
* Evaluation, monitoring and maintenance plan.

Refer to the [Guidance for Submitting for Designed Assessments](https://greenstarresources.gbca.au/greenstarresources.gbca.au_ratingtools/current-green-star-rating-tools/other-useful-resources/guidance-for-submitting-for-designed-assessments.md) for further information on submitting evidence for the Designed assessment.

***

## <mark style="color:$primary;">Supporting information</mark>

The following resource(s) are referenced in this credit:

* Commonwealth of Australia (Geoscience Australia) - [Australian Rainfall & Runoff](https://arr.ga.gov.au/arr-guideline)
* CSIRO - [WSUD Engineering Procedures: Stormwater](https://www.publish.csiro.au/book/4974/)
* Department of Water and Environmental Regulation, Government of Western Australia – [Stormwater management manual for Western Australia: Chapter 9 Structural controls](https://www.wa.gov.au/government/publications/stormwater-management-manual-western-australia-chapter-9-structural-controls)
* EPA Victoria - [Urban stormwater management guidance](https://www.epa.vic.gov.au/urban-stormwater-management-guidance)
* WALGA and IPWEA – [Code of Practice – Urban and peri-urban drainage modelling](https://www.engineersaustralia.org.au/sites/default/files/2023-12/code-practice-urban-peri-urban-drainage-modelling-western-australia.pdf)
* Wong, T H F – Australian Runoff Quality


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://greenstarresources.gbca.au/greenstarresources.gbca.au_ratingtools/current-green-star-rating-tools/green-star-buildings/v1.1/categories-and-credits/nature-2/42-or-waterway-protection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
