A runoff model can look credible and still fail the approval process, construction review or post-event investigation. The difference is usually not the software. It is whether the model represents how water will actually move across, through and away from a developed site. Knowing how to model development runoff means building a defensible hydrologic and hydraulic case from surveyed conditions, applicable planning controls and clearly documented assumptions.
For developers, asset managers and project teams, the objective is not simply to produce a peak flow. It is to demonstrate that the proposed development manages quantity, quality, flood risk and downstream impacts over its operating life.
Define the decision the model must support
Start with the approval, design or risk question. A concept-stage model may test whether onsite detention is likely to be required and establish preliminary storage footprints. A detailed design model must demonstrate pipe capacities, surcharge behaviour, overland flow paths, pit performance and detention outlet operation. A forensic assessment may need to determine whether an asset failed because of design capacity, construction variation, blockage, inadequate maintenance or an event beyond the adopted standard.
These are different modelling tasks. Applying a simple rational method calculation to a constrained urban drainage network, for example, may not answer whether water backs up through pits or enters a building during a critical storm. Conversely, a highly detailed hydraulic model is not always proportionate for an early feasibility assessment.
Confirm the governing authority requirements before selecting the method. In NSW and Queensland, council criteria, state guidance, flood studies, development controls and catchment-specific requirements can materially affect adopted storm events, climate change allowances, detention targets and acceptable discharge points. The model basis should identify these requirements early, rather than retrofitting them after a design is developed.
Establish existing and developed catchments
Development runoff modelling begins with a reliable representation of the existing site and contributing catchment. Survey data, cadastral information, contours, drainage plans, aerial imagery and site inspection should be reconciled before catchment boundaries are fixed. Water does not always respect title boundaries. Upstream overland flow, cross-lot drainage, road runoff and informal flow paths can all influence the design condition.
Map flow paths, not just areas
Delineate each catchment according to where water drains under both minor and major storm conditions. A roof connected to tanks and pipes behaves differently from a landscaped area that sheds water across a paved courtyard. Hardstand drainage can be intercepted by grated inlets, while an intense storm may bypass those inlets and follow a separate surface route.
For each sub-catchment, document area, slope, surface type, flow length, inlet points and downstream connection. Imperviousness should reflect the proposed finished development, including roofs, driveways, accessways, podiums, loading areas and paved external works. Do not assume landscaped areas are fully pervious. Compaction, shallow soils, retaining walls and subsoil drainage can significantly alter their runoff response.
Existing drainage assets need the same level of scrutiny. Confirm pipe sizes, levels, material, condition, legal point of discharge and downstream capacity where data is available. A proposed system cannot be assessed reliably against an assumed outlet that is undersized, blocked, disconnected or subject to tailwater.
Treat upstream and downstream conditions as model inputs
A site-only model can understate risk where upstream catchments discharge through or toward the property. It can also overstate the available capacity of the receiving system if downstream flooding causes tailwater at the outlet. Include external contributing flows and receiving conditions where they influence design performance.
This is particularly relevant in established industrial areas, infill developments and low-lying urban catchments. The legal discharge point may be clear on plans, but hydraulic capacity during a major event may be constrained by a downstream network, creek, basin or road crossing.
Select rainfall, losses and temporal patterns carefully
Rainfall inputs should align with the applicable Australian rainfall data, authority requirements and project location. The adopted average recurrence interval, storm duration, temporal pattern and climate change treatment must be recorded in the modelling report. These inputs are not administrative details. They directly control storage requirements, pipe sizing and flood extent.
The critical storm duration is rarely obvious. Short-duration storms may govern local pit and pipe performance, while longer events can govern onsite detention storage, downstream flooding or saturated catchment response. Test a suitable range of durations and temporal patterns rather than relying on one convenient storm.
Loss parameters and routing assumptions should be selected for the catchment condition and model purpose. Use values that can be explained and, where relevant, are consistent with local guidance or established catchment studies. An assumption that reduces predicted runoff may appear attractive at concept stage, but it creates approval and delivery risk if it cannot be justified later.
For large, complex or high-consequence sites, sensitivity testing is valuable. Test the influence of impermeable area, initial losses, tailwater levels, blockage assumptions and rainfall patterns on the result. This shows decision-makers where the design has limited tolerance and where additional investigation has the greatest value.
Build separate models for quantity and quality where required
Hydrologic and hydraulic modelling addresses runoff quantity and conveyance. Water quality modelling addresses pollutant generation, treatment performance and the effect of WSUD measures. They are connected, but they should not be treated as interchangeable exercises.
A drainage model may use DRAINS or another suitable hydraulic platform to assess detention, pipe networks, pits, surcharge and overland flow. A MUSIC model may be used to assess pollutant reduction from treatment measures such as bioretention, rainwater harvesting, proprietary treatment devices or vegetated systems. Each model needs inputs suited to its purpose.
Where an OSD system is proposed, model the storage volume, outlet configuration, bypass arrangement, overflow route and maintenance access as a functioning system. The outlet is often the controlling component. A detention tank that has sufficient theoretical volume but an impractical or blockage-prone outlet may not achieve its nominated discharge rate in service.
Modelled WSUD performance also needs to reflect realistic treatment areas, filter media, hydraulic loading, bypass conditions and maintenance regime. A treatment train is only defensible if it can be built, accessed and maintained by the asset owner.
Test the minor system and major system together
The minor drainage system is typically designed to capture and convey more frequent events through pits, pipes and formal drainage infrastructure. The major system manages exceedance flows when the underground network is at capacity or partially obstructed. Both must be understood before the development layout is finalised.
Assess whether surcharge remains within acceptable limits, whether surface flow routes avoid buildings and critical infrastructure, and whether low points create unacceptable ponding. Finished floor levels, driveway grades, retaining walls, basement entries and electrical infrastructure should be checked against the predicted flow paths, not considered separately after drainage design is complete.
Blockage assumptions deserve practical attention. Grated inlets in leaf-prone areas, sediment-exposed construction zones or industrial loading areas do not perform like clean, laboratory conditions. The appropriate blockage scenario depends on the authority standard, inlet type, location and consequence of failure. State the adopted assumption and show how exceedance water is safely directed.
Quality-assure the model before it becomes a design commitment
A technically sound model should be easy for another competent practitioner to review. That requires clear model files, an assumptions register, input data sources, catchment plans, hydraulic long sections, calculation outputs and concise interpretation. Version control matters when civil design, architectural levels and landscape plans are changing concurrently.
Before issuing the model, check that sub-catchment areas reconcile with the site plan, invert levels follow gravity, pipe directions are correct, detention outlets are represented accurately and no hidden defaults are driving the result. Review peak flows, hydraulic grade lines, storage levels and flood extents for engineering sense. A result may be mathematically valid while still being physically implausible.
Independent review is particularly valuable for constrained sites, major developments, disputed drainage performance and projects subject to compliance auditing. It identifies whether a stated result is supported by the underlying model or relies on assumptions that require redesign, additional evidence or stakeholder agreement.
Convert the model into an operable asset
The best runoff model does not end with approval. Its outputs should inform construction set-out, inspection hold points, as-built verification and ongoing maintenance. Detention chambers, pits, filters, trash screens, pumps and treatment devices need documented access, inspection intervals and asset records. If these requirements are omitted, the completed system can progressively depart from the modelled condition.
For high-risk projects, Stormwater Services Australia applies modelling as part of an integrated pathway from flood and drainage assessment through design, construction, compliance auditing and long-term asset management. That continuity reduces the gap between what was approved, what was built and what continues to perform.
A defensible development runoff model is therefore not a report appendix. It is the technical evidence behind safer levels, buildable drainage, compliant discharge and an asset that can be maintained with confidence long after practical completion.
