A drainage model is often treated as an approval deliverable: run the software, produce plans, submit the package. That approach can leave substantial risk embedded in a development, industrial site or public asset. A capable DRAINS model consultant uses the model to test whether the proposed drainage system can perform under defined storm events, comply with authority requirements and remain practical to construct and maintain.
For asset owners and project teams, the distinction matters. A model can produce a result without being based on sound assumptions, accurate survey information or a constructible drainage concept. Where flood exposure, constrained discharge, downstream capacity or compliance conditions are material, the modelling process must be technically defensible from initial inputs through to final documentation.
What a DRAINS model consultant actually does
DRAINS is widely used in Australia for urban stormwater drainage analysis and design. It enables engineers to assess hydrology and hydraulic behaviour across catchments, pits, pipes, overland flow paths, detention systems and outlet conditions. The software is valuable, but it does not replace engineering judgement.
A DRAINS model consultant establishes the basis on which the model will be relied upon. This starts with defining the catchment boundaries, existing and proposed surfaces, design rainfall, storm duration, losses, pipe network configuration, inlet capacity, tailwater levels and allowable discharge conditions. Each input has consequences. An overlooked upstream catchment, an assumed outlet level or an overly simplified overland flow path can materially alter the predicted outcome.
The work then extends beyond a model file. A reliable engagement should translate results into drainage layouts, hydraulic grade line information, detention sizing, water quality treatment interfaces and clear approval documentation. If the model identifies a problem, the consultant needs to develop a practical response – not merely record a non-compliance.
Why modelling quality affects approvals and project risk
Stormwater conditions attached to development approvals are not administrative details. They can govern finished floor levels, site access, basement protection, on-site detention (OSD), pipe upgrades, lawful points of discharge and ongoing maintenance obligations. A late change to any of these items can affect cost, programme and design coordination across civil, structural, architectural and landscape disciplines.
Poorly coordinated modelling commonly creates problems in three areas. The first is approval risk. Councils and reviewing authorities may reject or query reports where inputs, methodology or assumptions do not align with local requirements. The second is delivery risk. A theoretically compliant design may not fit around services, retaining walls, building footprints or existing assets once construction documentation develops. The third is operational risk. An asset that meets a narrow calculation but has inadequate access, sediment management or maintenance provisions can deteriorate rapidly.
The right level of analysis depends on the site. A straightforward low-density development with a confirmed legal discharge point may require a relatively contained model. A constrained infill site, industrial facility, transport-adjacent project or asset with a history of flooding needs more detailed investigation. In those cases, a DRAINS model should be considered alongside survey, flood information, site observations, authority standards and, where relevant, broader flood modelling.
Inputs determine whether the result is defensible
The strongest drainage models are built on evidence rather than convenience. Before modelling begins, the consultant should understand what the available information proves and what still needs verification.
Survey, levels and the real drainage network
Drainage modelling is highly sensitive to levels. Invert levels, pit depths, pipe grades, kerb lines, threshold levels and outlet conditions determine where water can travel when the underground system reaches capacity. Desktop records are useful, but they may not reflect alterations, damaged assets, undocumented connections or changes in surrounding development.
For existing sites, targeted investigation may be required to confirm asset condition and connectivity. This is especially relevant where drainage performance is disputed, where an older system is being retained, or where a proposed connection depends on downstream infrastructure. A model built on unverified assumptions can appear precise while failing to represent the actual network.
Hydrology and design storm selection
Rainfall intensity, storm duration, temporal patterns, catchment response and losses must suit the applicable design framework and authority requirements. The critical storm duration is not necessarily obvious. A short, intense event may govern inlet capacity, while a longer event may control detention storage or downstream surcharge.
A consultant should test the scenarios that matter to the design decision rather than selecting a single convenient event. This does not mean modelling every conceivable condition. It means applying a proportionate, documented methodology that demonstrates why the adopted design is appropriate.
Major and minor drainage systems
A piped network is the minor drainage system. It is designed to collect and convey frequent rainfall events within defined limits. The major system is the planned overland route taken by water once pits and pipes surcharge. Both require design attention.
A common weakness is treating surface flow as an afterthought. Water will move across driveways, pavements, landscaped areas and access routes when underground capacity is exceeded. If those routes direct water towards buildings, electrical infrastructure, loading areas or neighbouring land, the risk is not resolved by a satisfactory pipe calculation. The surface response needs to be understood and designed.
DRAINS modelling and OSD design
For many development projects in NSW, on-site detention is central to the stormwater strategy. OSD is intended to manage the rate at which post-development runoff leaves a site, often by temporarily storing water and releasing it through a controlled outlet.
A DRAINS model consultant can assess the required storage volume, allowable discharge rate, outlet control performance and system behaviour across relevant storm events. However, successful OSD design is more than selecting a tank size. The detention system must be accessible for inspection, protected from blockage, coordinated with levels and able to be maintained over its service life.
Above-ground and below-ground solutions each involve trade-offs. An above-ground basin or landscaped storage area can provide visible flow paths and straightforward inspection, but may consume valuable site area. Below-ground tanks preserve usable space, yet can complicate access, cleaning and long-term asset management. The appropriate solution depends on site constraints, the development type, operational responsibilities and authority expectations.
Where OSD interfaces with WSUD measures, the hydraulic sequence must also be clear. Treatment devices, rain gardens and detention assets perform different functions. Combining them without considering bypass flows, drawdown, maintenance access and hydraulic controls can compromise both water quality and flood performance.
From model output to a buildable stormwater solution
A drainage report should make decisions easier for the wider project team. It should identify the adopted criteria, explain key assumptions, show the proposed drainage concept, document model outcomes and clearly state any limitations. Outputs need to be legible to reviewers, designers, constructors and future asset managers – not only to the engineer who prepared the model.
Coordination is where many drainage concepts succeed or fail. Pipe grades may conflict with structural beams. Detention storage may interfere with foundations or services. A lawful discharge point may require easement confirmation. Surface flow paths may need changes to finished levels, landscape design or vehicle access. Resolving these matters early reduces the likelihood of redesign after approvals or during construction.
For complex projects, it is often more effective to engage an engineering partner that can carry the work through advisory, drainage design, construction support, compliance auditing and long-term maintenance. This creates clearer accountability between what was modelled, what was built and how the asset is expected to perform.
When forensic review is required
Not every DRAINS engagement concerns a new design. Existing drainage failures can require independent review where flooding, recurrent surcharge, water ingress or asset damage has led to disagreement about cause and responsibility.
In this setting, the model is one component of a forensic investigation. The consultant may need to assess original documentation, approval conditions, rainfall records, survey data, CCTV findings, maintenance history, site modifications and downstream conditions. The purpose is not to force a preferred narrative. It is to establish whether the system was appropriately designed, constructed, maintained and operated for the event or condition in question.
This distinction is particularly important in insurance and legal matters. A model that is transparent about inputs, limitations and sensitivity testing is more useful than one that presents a single conclusion without evidentiary support. Defensible documentation protects decision-makers by showing how conclusions were reached.
Selecting the right DRAINS modelling support
The best consultant is not necessarily the one offering the quickest model turnaround. Ask how the proposed drainage strategy will be validated against survey, authority requirements and constructability. Confirm who will coordinate OSD, WSUD, civil levels and downstream connection issues. For existing assets, ask whether investigation of the physical system is needed before modelling assumptions are finalised.
It is also worth establishing the intended use of the model from the outset. An approval model, detailed design model, construction verification model and forensic model may require different levels of information and checking. Treating them as interchangeable can create gaps in accountability.
Stormwater Services Australia approaches DRAINS modelling as part of an asset-performance decision, not a standalone software exercise. The objective is to de-risk projects with data, establish compliance pathways that can withstand review, and deliver drainage assets that remain manageable after handover.
The most useful question to take into a drainage discussion is simple: what decision must this model support? When that decision is clear, the right investigation, modelling scope and design response can be defined before risk becomes a costly site constraint.
