NSW Council OSD Compliance: A Stage-by-Stage Guide From Design to Ongoing Maintenance

Updated 31 July 2026.

While many resources simply say “get council approval”, this usually leaves out the hardest part of the process: the compliance journey isn’t a single approval, but a sequence of 6 separate tasks, a number of which don’t happen until after you’ve been issued your Occupation Certificate. Let’s walk through this OSD sequence in chronological order: design & sizing, engineering certification, legal instrument, construction sign-off, Occupation Certificate issuance, and ongoing maintenance.

What NSW Council OSD Compliance Actually Requires: Six Stages From Design to Ongoing Compliance

NSW council OSD compliance isn’t one job but six: design & sizing, engineering certification, legal instrument (Section 88E covenant and restriction), construction sign-off, Occupation Certificate issuance, and ongoing maintenance.

This guide groups the process into five functional areas — design and sizing, engineering certification, legal instruments, Occupation Certificate deliverables and ongoing maintenance — while tracking six distinct tasks.

How much detail and council investigation this sequence demands varies by site. Where a flood, overland-flow, heritage or contamination control applies, or the proposed discharge reaches Sydney Water’s network rather than council’s, the application may require specialist review or input from a second authority. Applicable planning controls, the consent authority and the network owner determine that pathway and the required signatories. Build time for possible council delays into the programme when extra review is required. Across projects, the goal remains the same: stopping the additional runoff a new development generates from causing downstream flooding or nuisance discharge onto neighbouring properties.

Whether OSD is required depends on the applicable planning controls and consent conditions. Changes in impervious area are commonly a key design input, so a renovation or granny flat can still require a stormwater review, but the threshold and exemptions must be checked with the relevant council for the property.

Requirements vary by local government area (LGA). Homeowners comparing new builds or a duplex on an already-buildable lot should ask the relevant council whether the controls require OSD or another stormwater compliance response. That applies in Western Sydney and across Sydney, but the answer comes from site-specific controls, not a regional shortcut. Apply the same verification rule to councils across New South Wales.

Factor	Standard Case	Referral Case	Limitations / Watch-Outs
Site constraints	No flood, bushfire, heritage or contamination overlay	One or more overlays apply	Overlay status is set by the LEP/DCP map, not by visual inspection — always confirm on council’s own planning portal
Discharge authority	Discharges to council’s stormwater system	Discharges into Sydney Water’s network or a shared easement	Some sites need sign-off from both council and Sydney Water — confirm early, not at lodgement
Dwelling type	Single dwelling / minor renovation	Multi-dwelling, subdivision, or commercial	Building class and development type can change the design, declaration and approval requirements
Construction material	Product matches the certified design	A project-specific condition or specification applies	Confirm material, load and installation requirements before selecting a tank system
Assessment pathway	Standard DA/CDC assessment	Integrated development requiring referral to a concurrence authority	A referral may extend the assessment; confirm the pathway before setting a programme

Because the applicable pathway is set by planning controls and the project’s circumstances rather than a visual site check alone, the applicant or consultant should confirm it before lodgement. For regulated building work, verify the professional and design-practitioner registrations that apply to the project; for other work, confirm the engineer qualifications and certification wording required by the relevant council or authority. If the discharge authority is unclear, use Storm Manager’s NSW discharge authority finder as a starting point, then confirm the result with the relevant authority.

Stage 1, OSD Design & Sizing: DRAINS Software, SSR and PSD Explained

Permissible Site Discharge (PSD) and Site Storage Requirement (SSR) are not statewide constants. PSD is the rate at which runoff from a site may leave for the approved drainage system, while SSR is the storage volume the design must provide. Your engineer must use the value or calculation method required for the site, not a generic online range. For example, Mid-Coast Council’s published guideline adopts 75 L/s/ha in its stated context; that council-specific figure should not be treated as a NSW-wide default.

Your engineer will usually model the site’s stormwater behaviour with specialist hydrology software such as DRAINS rather than relying on a simple manual rule. Inputs can include impervious area, catchment characteristics, site levels and the approved discharge point. These are site-specific inputs for assessment by a suitably qualified civil or hydraulic engineer: how much runoff the catchment generates and how to control its release before it reaches the downstream network.

Since what DRAINS actually spits out for your specific catchment is highly site dependent, view the following as simply working our way through the possibilities as opposed to a mathematical calculation you can conduct.

Sizing needs drainage design as well as hydraulic design inputs – your site’s contour, hard surfaces (roof and driveways), soil type and catchment data all feed into the same DRAINS model your engineer builds. So why size it so accurately?

In simple terms, capturing stormwater on site and releasing it at the approved rate avoids sending a sudden runoff peak into existing drainage infrastructure. That is the condition OSD is intended to control because unmanaged peaks can contribute to downstream erosion and flooding.

Good stormwater design coordinates roof, driveway and landscape runoff with the on-site detention system and its approved discharge point. Where the design connects to council drainage or another public network, effective stormwater management limits the peak stormwater runoff that can overload downstream assets; it is not a substitute for the local DCP or Water Sensitive Urban Design (WSUD) requirements.

For a 600 m² suburban block, a statewide rule of thumb is not a safe sizing method. Site-specific modelling must apply the actual roof and paved areas, levels, catchment assumptions, discharge point and current council requirements. Two similar-looking blocks can therefore produce different approved discharge rates and storage volumes.

What Your Engineer Needs From You	Why It Matters
Roof area (m²) and driveway/paved area (m²)	Impervious surface drives runoff volume into the DRAINS model
Site plan showing the downstream waterway or drainage connection point	Documents the proposed downstream connection for authority review
Your council’s current DCP stormwater chapter (and any published PSD/SSR method)	Council-specific values or calculation methods must replace generic assumptions
Any known site constraints (flooding, contamination, easements)	Feeds directly into the Standard Case vs. Referral Case triage above

Stage 2, Engineering Certification for Council OSD Approval

Once your engineer has provided a sizing figure, the next step is to confirm who is authorised to certify or declare the relevant work. The Design and Building Practitioners (DBP) scheme applies to professional engineering work on regulated building classes, currently Class 2, certain Class 3 and Class 9c buildings. A professional engineer may also need the relevant design-practitioner registration to prepare regulated designs or make compliance declarations. Other projects remain subject to the qualifications and certification requirements specified by the council, certifier or approval authority. Before lodgement, confirm the project’s building class, the required registration or accreditation, and the exact person authorised to sign each document.

Certification commonly has pre- and post-construction stages. Before construction, the applicable approval pathway may require a chartered civil engineer to certify that the design meets the calculated PSD and SSR requirements. After construction, it may require signed Work-As-Executed (WAE) plans from a registered surveyor and a Certificate of Hydraulic Compliance. Submit the documents to the council, certifier or water authority identified in the project’s approval conditions.

Which authority reviews a particular part of the project depends on the discharge location and approval pathway. Confirm that point early rather than assuming; Storm Manager’s Approval Pathway Matrix provides a starting point, but the council and relevant water authority remain the controlling sources for the site.

Stage 3, Registering Your Section 88E Positive Covenant

One concept that often receives only brief treatment in online OSD guides is Section 88E. A missing or delayed title instrument can stall an otherwise compliant project before an Occupation Certificate. A Section 88E positive covenant is recorded against the title of a property in NSW under the Conveyancing Act 1919 and can place an ongoing maintenance obligation on the owner and subsequent owners. Unlike an informal assurance, the registered covenant remains attached to the title when ownership changes.

What Is a Positive Covenant and Restriction for a Stormwater OSD System?

For systems within its approval scope, Sydney Water’s OSD guidance says storage must accommodate runoff up to a 100-year Average Recurrence Interval (ARI) event. It also specifies a flat stainless-steel orifice plate at least 200mm by 200mm and 3mm thick, with an orifice diameter of 40mm or more, and requires the covenant agreement to be registered on the title so the obligation is not lost when ownership changes. If title registration is a consent requirement, missing evidence can prevent the relevant approval stage from being completed.

Stage 4, Construction and Occupation Certificate Compliance Deliverables

Before an Occupation Certificate can be issued, the approval conditions may require three related deliverables: Work-As-Executed (WAE) drawings prepared and signed by a registered surveyor to show what was actually built; a Certificate of Hydraulic Compliance confirming that the constructed system conforms to the certified design; and evidence that any required Section 88E positive covenant has been registered on the title, usually shown by a current title search. Check the project’s consent conditions for the exact documents and signatories.

• Work-As-Executed (WAE) drawings — prepared and signed by a registered surveyor to show the as-built system
• Certificate of Hydraulic Compliance – the build conforms to original design PSD’s / SSR’s
• Confirmation of registered Section 88E covenants – extract from title search to show the instrument is in force not just drafted

Costs at this stage depend on the council and the current fee schedule. For example, The Hills Shire Council’s published 2025–26 fees and charges lists $5,000 for an OSD Compliance Certificate for design and construction including two inspections, $664 for amended plans or modification of an application, and $454 for each additional inspection. These are council- and year-specific figures, not a statewide price guide.

Stage 5, Ongoing OSD Maintenance Obligations After Occupation

OSD duties continue after occupation. Council material references the UPRCT Handbook for the Management and Inspection of On-site Storm Water Detention as a practical maintenance framework. Keeping a simple management plan and dated log helps owners and contractors protect access points and record inspections. The handbook schedule calls for residential systems to be inspected every six months and after heavy rainfall, commercial and industrial systems every three months and after heavy rainfall, and cleaning at least annually or every six months depending on use.

Penrith City Council publishes an OSD inspection and maintenance sheet with dated fields, condition checks and post-heavy-rainfall items. Canada Bay Council states that owners of private detention and storage tanks are responsible for their management and maintenance to keep the system compliant with council requirements.

Who Is Responsible for Maintaining an OSD System After Occupation?

• Record all your service inspection dates, discoveries, repairs performed in a dated inspection logbook
• Review of the UPRCT cadence – every 6 months residential, every 3 months commercial/industrial, and after every large rain event
• Clean at least once a year – more frequently if a site has heavy leaf litter, is near construction activities or is in a large catchment
• Don’t change the system without checking the approval conditions — an altered orifice, storage volume or layout may require engineer and authority sign-off

Neglected maintenance can allow sediment, debris or damaged components to reduce system performance. It can also make it harder to demonstrate compliance during a council inspection or later building work. During a sale or later approval, a solicitor or certifier can see the registered title restriction and may ask how the obligation has been managed, so keeping records is prudent even where a specific logbook format is not prescribed.

Why OSD Compliance Requirements Differ Between NSW Councils

OSD compliance requirements differ between NSW councils because planning controls are local rather than one statewide formula. Even neighbouring councils can specify materially different PSD methods for similar blocks; the difference reflects their adopted controls and drainage context, not a value that can be transferred from one site to another.

Each NSW council applies its own stormwater planning controls alongside state and national requirements, so PSD, SSR and construction conditions can vary. In one cited Georges River Local Planning Panel determination, the conditions used a project-specific peak-discharge formula and required childproof fencing for open above-ground storage where peak design depth exceeded 300mm. A cited Hornsby Local Planning Panel determination used storage capacity sized to a 50-year ARI storm, restricted discharge to the five-year pre-development value, and added a 50 L/s limit per gutter discharge point. These are examples from individual determinations, not universal council policy values.

A council-hosted copy of the Upper Parramatta River Catchment Trust On-site Detention Handbook provides technical background for some Sydney-area OSD practice. Treat it as background, not as a substitute for the current controls, consent conditions and specifications that apply to the site.

Stormwater on-site detention is the underlying subject, but the controlling requirements still depend on the project. They may appear in the applicable DCP, a council specification or project-specific consent conditions. In practice, locate the controlling document for the property and use its PSD/SSR method rather than borrowing a value from another council or development.

The Practical NSW Council OSD Compliance Checklist (Stage by Stage)

Breaking OSD compliance into a submission-ready checklist makes it easier to track the certification, plan and PSD/SSR items shown on council on-site detention requirements pages. The table below turns each stage into practical sub-steps.

For quick reference: Mid-Coast Council’s cited guideline uses 75 L/s/ha in its stated context; Sydney Water’s cited guide specifies a flat stainless-steel orifice plate at least 200mm by 200mm and 3mm thick, with an orifice diameter of at least 40mm; the UPRCT handbook schedule calls for six-monthly residential and three-monthly commercial or industrial inspections; the cited Hornsby determination limits gutter discharge to 50 L/s per outlet point; and the 2025 revision to AS/NZS 3500.3 raised the Clause 3.6.2 valley-gutter catchment limit from 20 m² to 40 m². In the cited Georges River determination, the 300mm fencing threshold applies to that project-specific condition only.

Sourcing a Council-Compliant OSD Tank: What to Confirm Before You Order

Once your compliance parameters are locked in, choosing among the available OSD solutions is a matching exercise. Start with the certified design, then compare Storm Manager’s OSD tank range against the required storage volume, load class, access and maintenance provisions, outlet arrangement and installation constraints. Where Sydney Water’s specification applies, confirm that the outlet assembly meets its stainless-steel orifice-plate requirements. Also check every project-specific material or construction condition with the engineer and approval authority. Do not order from a generic capacity estimate: obtain engineer sign-off on the PSD/SSR design and confirm the applicable DCP and consent conditions first.

For a starting-point comparison of possible approval routes, consult the Authority Approval Pathway Matrix and review the product-level details in Storm Manager’s NSW council compliance hub. Final acceptance depends on the certified design and the relevant authority; company history is available on the Storm Manager profile.

2025-2026 Regulatory Currents: What’s Changing for NSW OSD Compliance

AS/NZS 3500.3:2025 updates stormwater-drainage clauses in the plumbing and drainage standards series. One published change to Clause 3.6.2 doubles the permissible valley-gutter catchment area from 20 m² to 40 m². At council level, Ballina Shire Council endorsed amendments across four DCP chapters on 27 November 2025. That example is evidence of DCP change activity, not proof of a particular OSD clause change.

Online tracking through the NSW Planning Portal’s DA Application Tracker makes application progress visible. These developments do not create one new statewide OSD formula, but they reinforce a practical control: verify the edition of every cited standard, the current council DCP and the project’s consent conditions before finalising design and submission documents. Current-document checks are a basic part of sustainable stormwater planning.

That valley-gutter catchment limit has doubled from 20 m² to 40 m². The change does not automatically invalidate an existing design, but it is a clear reason to confirm which edition of the standard applies before lodgement or revision. Council DCP chapters move on their own schedules, so standards checking should be a standing item on the compliance checklist rather than a one-off task.

Frequently Asked Questions

This guidance draws on publicly available material from Mid-Coast Council, Penrith Council and Canada Bay Council. The Georges River and Hornsby examples come from published Local Planning Panel business papers, not standalone council policy documents. Councils update their DCPs on independent schedules, so determine the requirements for your property before preparing a development application instead of treating the examples above as a generic standard. This article accompanies Storm Manager’s OSD Tank Compliance Guide, which adds product-selection detail and an authority pathway matrix.