A development can satisfy architectural, planning and commercial objectives yet still stall at approval if its drainage strategy is incomplete, unmodelled or impossible to maintain. Stormwater approval requirements are not a documentation exercise at the end of design. They are a set of technical obligations that must be resolved early enough to influence site layout, levels, servicing corridors, construction sequencing and long-term asset ownership.
For developers, asset owners and project managers, the objective is clear: establish a drainage solution that meets the relevant authority criteria, works within real site constraints, and can be substantiated with reliable calculations, drawings and construction evidence. That is how teams reduce approval risk rather than simply responding to review comments late in the programme.
What authorities are assessing
Approval pathways differ between councils, state agencies, water authorities and private-certification arrangements. The applicable requirements also vary by location, development type, downstream catchment, receiving environment and whether works affect public drainage infrastructure. A site in Sydney may need to address local OSD requirements and council drainage standards, while projects in Queensland may be assessed against a different local planning scheme, flood overlay and water quality framework.
Despite those differences, reviewers are generally testing the same core question: will the proposed development avoid worsening flooding, drainage capacity, water quality or maintenance risk on and beyond the site?
That assessment commonly extends to the legal point of discharge, existing downstream network capacity, major and minor storm performance, overland flow paths, finished floor levels, detention performance, water quality treatment and access for inspection and maintenance. Where a proposal connects to, modifies or builds assets intended for public ownership, asset standards and handover evidence can become as significant as hydraulic performance.
The practical implication is that no single drawing can carry an approval. A credible package aligns survey information, civil design, hydraulic modelling, water quality modelling, architectural levels, landscape treatment and construction details.
Establish constraints before selecting a solution
The most costly stormwater redesigns usually begin with an assumed outlet, unverified pipe level or simplified flood condition. Before detention tanks, pits or WSUD devices are selected, the project team needs a defensible picture of the site and its catchment context.
Confirm the drainage and flood baseline
Start with current survey, title information, services records, available council drainage plans and relevant flood mapping. These sources identify obvious constraints, but they are not always complete or current. Existing pipes may differ from records. Private inter-allotment drainage may be poorly documented. A site can also receive significant external overland flow that is not apparent from its local topography alone.
For complex sites, flood modelling should test both the development’s internal drainage and its interaction with the broader catchment. This is particularly relevant where filling is proposed, the site is low-lying, adjacent development relies on shared flow paths, or a new basement changes the consequence of surcharge. The correct model scope depends on risk. A simple compliant connection may only need targeted hydraulic assessment; a constrained redevelopment near mapped flooding may require integrated flood modelling.
Identify the lawful discharge pathway
An approval authority will expect a clear, feasible discharge strategy. This may involve connection to a public system, discharge to a kerb and gutter where permitted, a controlled inter-allotment drainage route, or a site-specific arrangement approved by the relevant authority. The proposed route must account for levels, capacity, easements, downstream constraints and the ownership of each asset.
Do not treat a notional connection point as an approval outcome. If a design depends on a downstream asset with limited capacity, a third-party easement or works outside the site boundary, that dependency needs to be investigated early. It can materially alter cost, programme and consent conditions.
Design for quantity, quality and safe exceedance
A compliant stormwater system manages more than the pipe network. It must operate under routine rainfall, control peak discharge where required, convey exceedance flows safely and limit pollutant loads to the standard expected by the receiving environment.
Detention and drainage performance
On-site detention is frequently required where development increases impervious area or changes runoff characteristics. The design needs to demonstrate the nominated storage volume, permissible site discharge, outlet control and overflow behaviour under the adopted design storms. It must also be buildable, accessible and capable of being maintained over its service life.
In NSW, OSD systems are often assessed against detailed local authority criteria. DRAINS modelling may be used to demonstrate hydrologic and hydraulic performance, but software output is only as reliable as the adopted parameters, catchment definition and outlet assumptions. Reviewers need to be able to follow the calculation trail from design inputs through to the final system shown on the plans.
Major drainage is equally critical. When rainfall exceeds the capacity of the underground system, water will move across the surface. Finished levels, driveway profiles, landscaped grades and pit locations must direct that flow away from buildings and towards a safe route. A system that meets minor-pipe capacity yet ponds against a loading dock, electrical room or basement ramp has not adequately managed project risk.
Water quality and WSUD
Water quality requirements may apply through development controls, environmental conditions or receiving-water objectives. Typical pollutants include sediment, gross pollutants, hydrocarbons, nutrients and litter, but the treatment train should respond to the actual land use. An industrial hardstand, mixed-use podium and low-density subdivision do not create the same runoff risk or demand the same solution.
MUSIC modelling is commonly used to assess WSUD performance. Its value lies in testing whether the proposed treatment measures meet nominated reduction targets, not in producing a report for its own sake. Model inputs should reflect the real catchment areas, treatment device configuration, rainfall data and maintenance assumptions. If a biofiltration system cannot be safely accessed, or its filter media and drainage layers are not detailed correctly, an apparently compliant model result will not protect long-term performance.
Prepare an approval package that can withstand review
The strongest applications present a coherent engineering position rather than a collection of disconnected attachments. The reviewer should be able to see what exists, what is proposed, why the design complies and how it will be delivered.
A typical package may include a stormwater management report, civil design plans, catchment plans, drainage calculations, OSD or detention details, flood assessment, water quality report, MUSIC files or outputs, erosion and sediment controls, and maintenance documentation. The exact list depends on the authority and project risk. Where connection, encroachment or public-asset works are involved, additional approvals, specifications and inspection requirements may apply.
Design drawings should show more than pipe sizes and pit labels. They need clear levels, grades, invert information, overflow routes, detention outlet details, access provisions and interfaces with architectural and landscape works. Inconsistent levels between disciplines are a common source of review comments and site failures.
For higher-risk sites, independent compliance auditing before lodgement can be commercially worthwhile. A targeted review may identify unverified discharge assumptions, missing overflow protection, non-compliant detention details or water quality devices that have no practical maintenance access. Resolving those matters before submission is generally less disruptive than redesigning after conditions are issued or works have commenced.
Approval conditions continue into construction
Securing consent is not the end of compliance. Conditions may require inspections, certified works-as-executed information, CCTV investigation, testing, operation and maintenance manuals, or evidence that an OSD system and water quality assets were built to the approved design.
Construction changes need disciplined control. A substituted pit, altered outlet level or revised landscape grade can change hydraulic behaviour materially. Site teams should use approved drawings, record variations promptly and obtain engineering review before changes become permanent. This is especially important for concealed infrastructure, where incomplete records create future maintenance, sale and liability issues.
At practical completion, documentation should establish what was built, who is responsible for each asset, how it is accessed and what maintenance is required. For privately owned detention and treatment systems, this handover is essential. An asset that is approved but never inspected, cleaned or repaired will eventually become an operational and compliance exposure.
Common causes of avoidable delay
Approval delays are rarely caused by one dramatic error. More often, they arise from small unresolved issues: out-of-date survey data, a missing downstream capacity check, an OSD system without maintainable access, flood levels that do not align with architectural levels, or water quality modelling that does not match the civil plans.
The remedy is integrated delivery. Engage drainage, flood and water quality expertise while the layout can still change, then carry those decisions through detailed design, construction verification and asset handover. Stormwater Services Australia applies this lifecycle approach across modelling, design, compliance auditing, construction and long-term asset management, helping project teams maintain technical accountability from feasibility to operation.
A well-prepared stormwater strategy does more than satisfy an approval condition. It gives the owner a documented, maintainable system that protects buildings, supports future decisions and performs when the site is under pressure.
