The UPRCT OSD Handbook: Why Western Sydney Councils Use It

Why a decades-old handbook still shapes your DA

If you build in western Sydney, the on-site detention requirements in your development consent trace back to one document: the Upper Parramatta River Catchment Trust (UPRCT) On-Site Stormwater Detention Handbook. The Trust itself no longer exists, yet councils across the region still reference its handbook, apply its methodology, and assess OSD designs against the framework it established. Understanding where it came from explains a lot about why Sydney OSD works the way it does.

The problem: a flood-prone catchment filling up with development

The Upper Parramatta River catchment — taking in areas around Parramatta, Blacktown, The Hills and the former Holroyd council area — has a long history of flooding. Through the late twentieth century, the catchment urbanised rapidly. Every new roof, driveway and car park pushed runoff into the river system faster, and downstream flooding got worse with each wave of development.

The Upper Parramatta River Catchment Trust was established as a dedicated catchment management body to tackle the flood problem. Big structural works were part of the answer, but the Trust recognised something important: flood mitigation spending would be undone if thousands of individual developments kept increasing peak runoff. The catchment needed a way to stop the problem growing at the source — one development at a time.

The solution: a uniform, catchment-wide OSD policy

The Trust’s answer was a catchment-wide on-site detention policy, documented in its On-Site Stormwater Detention Handbook and refined over several editions. The handbook gave councils, engineers and certifiers a single consistent framework, built around concepts that will be familiar to anyone who’s done an OSD design since:

• Permissible site discharge (PSD) — a capped rate of outflow from each developed site, set so development doesn’t worsen catchment peak flows.
• Site storage requirement (SSR) — the detention volume each site must provide to hold back the difference.
• Standard hardware and details — orifice plates, discharge control pits, trash screens, surcharge and overflow provisions, and access for maintenance.
• Certification and ongoing protection — works-as-executed documentation and positive covenants on title so the system survives changes of ownership.

What made the handbook powerful was uniformity. An engineer could design OSD the same way across multiple council areas within the catchment, councils could assess designs against a common benchmark, and the cumulative effect across thousands of lots genuinely protected the downstream flood mitigation investment.

What happened to the Trust

Having largely delivered its flood mitigation program, the Trust was eventually wound up and its functions absorbed into other government bodies and the councils themselves. But the handbook outlived its author. The member councils — and a number of neighbouring councils that saw the framework working — carried the methodology into their own DCPs and engineering specifications. Some adopted the handbook by direct reference; others rebadged its methods with local adjustments to the numbers.

Why this matters to builders today

Three practical consequences flow from this history:

1. Western Sydney OSD requirements are unusually consistent — but not identical

Because so many councils built on the same foundation, OSD design across western Sydney follows a recognisable pattern. But councils have amended their requirements independently over the years — discharge rates, storage methods, drainage system standards and exemption thresholds vary. Never assume one council’s numbers apply next door. Always check the current DCP and any adopted handbook for the specific LGA.

2. Catchment-based requirements aren’t bureaucracy for its own sake

When a council insists on a seemingly conservative PSD, it’s usually protecting a known downstream constraint — often one identified in catchment studies dating back to the Trust era. Designs that respect this logic get approved faster than ones that argue with it.

3. Modern standards now sit alongside the legacy framework

Today’s OSD designs also need to align with Australian Rainfall & Runoff 2019 design rainfall and methods, AS/NZS 3500.3 for property drainage, and each council’s current engineering specifications. A good stormwater engineer reconciles the legacy handbook methodology with current standards — and knows when a council has updated its position.

The bottom line

The UPRCT handbook is one of the quiet success stories of Australian urban drainage: a regional flood problem tackled by making every development part of the solution. If your site is in western Sydney, its legacy is written into your consent conditions — and designing with that framework, rather than against it, is the fastest route through council.

Contrive Consultants designs council-ready OSD and stormwater systems across Sydney and NSW. See our services, call +61 497 848 111, email info@contriveconsultants.com.au or contact us — we work with the OSD handbooks and DCPs of councils right across the region.