A site can meet every architectural, leasing and traffic requirement on paper and still stall at stormwater approval. That usually happens when runoff leaves the property faster than the downstream network can handle. If you are asking what is OSD design, you are really asking how a development can control discharge at source, satisfy consent conditions and avoid shifting flood risk onto neighbouring assets.
OSD stands for on-site detention. OSD design is the engineering process used to temporarily store stormwater within a development and release it at a controlled rate. In practical terms, it is a throttling system. Rather than allowing post-development runoff to spike immediately into the public drainage network, an OSD system attenuates peak flow so the site behaves more like it did before development, or at least within the limits set by the relevant authority.
What is OSD design and why does it matter?
In dense urban catchments, hard surfaces increase runoff volume and speed. Roofs, driveways, loading areas and pavements reduce infiltration and shorten the time it takes for water to reach pits and pipes. Without detention, redevelopment can overload downstream infrastructure, worsen local flooding and trigger non-compliance with council or authority requirements.
That is why OSD design matters beyond a single block. It is not just a box-ticking exercise for DA or CC conditions. It is part of a broader drainage risk management strategy. Done properly, it helps de-risk your project with data, protects the receiving system from avoidable peak flows and creates a defensible basis for approval, construction and future asset management.
The exact performance target depends on the jurisdiction and the consent framework. Some councils require discharge to be limited to a site storage requirement and permitted site discharge calculated under adopted policy. Others may reference specific hydrologic methods, hydraulic grade constraints or integrated stormwater outcomes alongside WSUD measures. The principle stays the same - temporary storage, controlled release, verified performance.
How OSD design works in practice
An OSD system has three core functions. It collects runoff, stores part of it for a short period and releases water through a flow control device at a restricted rate. The system may be above ground, below ground or integrated into built form, depending on space, levels, access and maintenance requirements.
Typical storage elements include tanks, oversized pipes, basement detention zones, car park detention areas, rooftop systems or purpose-built chambers. The flow control is often achieved through an orifice plate, outlet pit, weir arrangement or proprietary device, although proprietary products still need to be checked against actual hydraulic behaviour rather than accepted at face value.
During a design storm event, inflow to the system exceeds the allowed outflow. Water backs up within the storage volume, then drains down after the peak has passed. Emergency overflow provisions are critical because no detention system should rely on ideal conditions alone. Major storm exceedance, blockage, surcharge and overland flow paths all need to be considered as part of the design logic.
This is where poor assumptions can become expensive. A detention system that works in a spreadsheet but ignores tailwater, debris risk, surcharge interaction or realistic maintenance access can create operational problems well after practical completion.
The inputs that shape an OSD design
Good OSD design starts with site-specific hydrology and a clear reading of the applicable approval framework. The required inputs usually include catchment area, impervious proportions, site grading, inlet locations, downstream connection levels, overland flow paths, soil behaviour, existing pipe capacity and the governing design standard or council policy.
Survey quality matters. So does an accurate understanding of existing services and downstream constraints. If the outlet level is wrong, or if the receiving system is already compromised, the detention design may need to be reconsidered early rather than patched late.
Hydrologic and hydraulic modelling then translates those inputs into detention sizing and discharge control requirements. Depending on the authority and project complexity, that may involve rational method calculations, hydrograph routing, DRAINS modelling, MUSIC inputs where water quality is also in play, and supporting engineering documentation that can stand up under audit. On more constrained sites, the design may also need to interface with flood modelling, pump systems or basement drainage strategies.
What an OSD design must resolve
A compliant detention concept is only one part of the task. The design also needs to be buildable, maintainable and capable of performing over time.
Hydraulic performance
The system must achieve the required discharge limit for the nominated storm events while preserving storage volume and safe overflow behaviour. That sounds straightforward, but outlet control sensitivity can be high. Small changes in orifice diameter, blockage allowance or tailwater condition can materially alter performance.
Structural and civil integration
The detention system has to fit with the actual project. Tank footprints, slab levels, trafficable loads, retaining interfaces, waterproofing and service clashes all affect feasibility. On industrial or institutional sites, vehicle access and operational continuity can be just as important as hydraulic efficiency.
Access and maintenance
An OSD asset that cannot be inspected or cleaned is a future defect. Sediment accumulation, debris blockage and outlet fouling are common causes of underperformance. Access covers, pit geometry, confined space implications and maintenance frequency should be addressed at design stage, not left to facilities teams after handover.
Certification and evidence
Authorities and certifiers generally require formal design documentation, calculations, plans and in some cases work-as-executed verification. For high-value or contested assets, the quality of that record matters. If performance is later questioned in a compliance, insurance or legal context, defensible documentation is often the difference between a manageable issue and a prolonged dispute.
Common OSD design mistakes
Most OSD failures do not come from the concept itself. They come from gaps between modelling, detailing, construction and maintenance.
One common problem is underestimating effective impervious area. Another is treating the downstream network as a simple connection point rather than a hydraulic constraint. There are also frequent issues with outlet installations that do not match the approved drawings, detention volumes reduced by later fitout changes, and systems commissioned without proper as-built verification.
Maintenance is often the quiet failure point. A well-designed system can still underperform if sediment is not removed, grates are blocked or access is too difficult for routine servicing. For property owners and asset managers, that means OSD is not only a design matter. It is an operational responsibility.
OSD design versus broader stormwater strategy
It is worth separating OSD from the wider drainage and water quality framework. OSD manages peak discharge. It does not automatically solve water quality, flood immunity, erosion control or legal point of discharge issues. Those elements may require separate WSUD measures, flood assessments, drainage upgrades or negotiated authority outcomes.
That distinction matters during project planning. A site may satisfy OSD requirements and still face approval risk because overland flow is unresolved, basement ingress risk remains, or the legal discharge path is deficient. Conversely, a project that focuses only on WSUD treatment without addressing detention may still increase downstream peak flows.
The best results come from integrating OSD into the broader stormwater design from the start. That reduces redesign, improves approval certainty and helps avoid fragmented decisions between civil, structural, hydraulic and facilities stakeholders.
When OSD design becomes more complex
Some projects carry straightforward detention requirements. Others do not. Complexity increases when the site sits in a flood-affected catchment, has limited level difference to the point of discharge, includes basement development, adjoins sensitive assets, or forms part of a staged precinct where upstream and downstream assumptions are still moving.
There is also a different level of scrutiny when stormwater performance becomes part of an insurance claim, defect matter or expert determination. In those cases, OSD design is no longer just about satisfying a planning condition. It becomes evidence. The calculations, assumptions, as-built condition and maintenance history may all be examined to establish whether the system was adequate, compliant and properly managed.
That is why experienced delivery matters. A technically correct concept can still fail commercially if it is difficult to construct, impossible to maintain or poorly documented for downstream stakeholders.
What decision-makers should ask before approving an OSD approach
For developers, asset owners and project managers, the useful question is not simply whether detention has been included. It is whether the proposed OSD design is coordinated across the asset lifecycle.
Ask whether the discharge target has been confirmed against the governing authority requirements. Ask whether the storage volume survives structural coordination and service routing. Ask how the outlet will be protected from blockage, how the system will overflow safely, and who will maintain it once the project is operational. If the answers are vague, the risk has probably just been pushed down the line.
On more complex sites, it is also worth asking whether the OSD solution has been reviewed alongside flood modelling, forensic drainage issues or known downstream constraints. A narrow compliance lens can miss wider operational exposures.
For clients managing approvals, construction and long-term performance, that integrated view is where a specialist partner adds value. Stormwater Services Australia approaches OSD as part of a full-lifecycle infrastructure outcome, not an isolated design line item.
OSD design is simple in principle and exacting in execution. When it is grounded in sound modelling, coordinated detailing and realistic maintenance planning, it does more than satisfy a condition of consent. It gives the site a controlled, defensible way to manage runoff without exporting avoidable risk downstream.
