A drainage package can look complete and still fail assessment because its calculations, plans and reports do not describe the same system. A pit level changes on the civil drawings, but not in the hydraulic model. An OSD tank is sized for a concept layout that has since moved. A water quality claim is made without the MUSIC inputs to support it. Knowing how to prepare drainage approval documentation means controlling these interfaces before they become a condition, a redesign or an avoidable delay.
For developers, asset owners and project managers, approval documentation is not simply a set of drawings to submit. It is the technical evidence that demonstrates a proposed development will manage stormwater without transferring flood, drainage, water quality or maintenance risk to the public network, adjoining land or future operators.
Start with the approval pathway and design basis
The first task is to identify the actual approval pathway. Requirements vary between councils, water authorities, state agencies and consent conditions. In NSW, this may involve development consent requirements, local drainage policy, flood planning controls, legal point-of-discharge constraints and separate approvals for works within public land. Queensland projects may be assessed against a different set of planning schemes, nominated design storms and water quality targets.
Do not begin by selecting a proprietary treatment device or sizing a detention system from a previous job. Establish the design basis first. It should state the site catchments, proposed impervious areas, adopted rainfall data, minor and major storm criteria, tailwater assumptions, allowable site discharge, flood level references and applicable water quality objectives.
This basis should also identify what is known and what remains to be verified. Existing pipe locations, invert levels, downstream capacity, easements and legal discharge points are often treated as settled facts when they are not. A site survey and Dial Before You Dig information are starting points, not proof of asset condition, capacity or connection suitability. Where risk is material, targeted investigation can prevent a report from being built on an untested assumption.
Build drainage approval documentation around one coordinated model
The strongest submissions work from a single, controlled engineering position. The civil layout, drainage design, OSD calculations, flood assessment, WSUD strategy and maintenance information must be coordinated, rather than prepared as separate documents that happen to use similar site plans.
A practical approach is to establish an approval register at the outset. This records each required deliverable, the governing standard or policy, responsibility, input status and review date. It is particularly useful where architects, civil designers, landscape architects, environmental consultants and structural engineers are changing the design in parallel.
The drainage design should reflect the final grading strategy. Surface flow paths, pit locations, pipe grades and overland escape routes must be achievable after considering driveway thresholds, accessible paths, retaining walls, basement entries, finished floor levels and landscaping. In constrained urban sites, the design may need to trade off pipe cover, service clashes, detention volume and maintenance access. These trade-offs should be resolved in the design, not left for the contractor to interpret on site.
Hydraulic calculations must match the drawings
Hydraulic calculations are only defensible when an assessor can trace the numbers to the plans. Catchment areas, runoff coefficients or loss parameters, pipe sizes, pit capacities, storage volumes and outlet controls should all be clearly identifiable. If the system relies on an orifice, weir, pump or proprietary flow-control device, show its location, level, capacity and maintenance requirements.
For OSD, document both the storage and the discharge control. The assessment needs to demonstrate that post-development flows comply with the allowable discharge condition across the nominated storm events, while the detention volume can physically fit within the proposed structure or landscape area. Include storage level relationships, overflow arrangements, emergency spill paths and the consequences of downstream tailwater where relevant.
A common weakness is demonstrating a compliant theoretical OSD volume without proving that the tank can be constructed, accessed and maintained. Slab depths, internal walls, structural constraints, traffic loading, access covers and sediment accumulation all affect the usable volume and long-term function.
Address major flows, not just the pipe network
Minor drainage systems are designed to convey frequent rainfall events through pits and pipes. Major storm events will exceed that capacity. Approval documentation must show where excess water goes and whether it remains away from buildings, basements, electrical infrastructure and neighbouring properties.
This is where flood modelling or detailed surface flow assessment may be required. The level of analysis depends on site risk, catchment scale, downstream constraints and local authority requirements. A small infill project on a well-drained street may need a focused overland flow check. A redevelopment beside a known flood path, culvert or constrained trunk system may require a more detailed hydraulic model and a broader assessment of off-site impacts.
The key question is not whether water can leave the site under normal conditions. It is whether the development creates a safe, controlled outcome when the drainage network is surcharged or blocked.
Demonstrate water quality performance with transparent inputs
Where WSUD targets apply, water quality documentation should identify the treatment train and demonstrate its performance using an accepted methodology, commonly MUSIC modelling. The model is only as reliable as its inputs. Roof, driveway, landscape and external catchments need to be allocated correctly, and treatment assets must reflect their actual contributing area, bypass arrangements, hydraulic loading and maintenance regime.
Do not use generic model results without checking whether the final layout can support the claimed treatment. A bioretention system needs suitable area, filter media depth, drainage configuration, overflow provisions and access for renewal. Gross pollutant treatment needs practical access for cleaning. Rainwater reuse assumptions need to account for actual demand, tank size and operational controls.
Include the model assumptions and results in a form an assessor can audit. Where targets are not fully achievable due to site constraints, explain the constraint, quantify the residual gap and document the alternative measures considered. A transparent, technically reasoned position is more credible than an unsupported assertion of compliance.
Make construction and maintenance part of the submission
Approvals assess design intent, but the asset owner carries the consequences of poor construction and neglected maintenance. For that reason, drainage approval documentation should include enough information for the system to be built correctly and operated safely.
Plans should specify pipe materials, classes, bedding where relevant, pit types, grate requirements, levels, slopes, detention details, treatment device details and connection arrangements. Sections are valuable wherever pipes cross retaining walls, enter a tank, pass beneath pavement or interact with basement structures. Ambiguous notes create a direct pathway to variations, defects and later disputes.
A concise operation and maintenance schedule should identify each asset, inspection frequency, cleaning triggers, access requirements and responsible party. This is particularly relevant for OSD systems, pump stations, proprietary treatment devices and bioretention assets. If a system cannot be safely inspected or cleaned with available access, it is not a complete design solution.
Quality-assure the package before lodgement
The final review should be a technical coordination exercise, not an administrative check. Compare every reported level and dimension against the latest drawings. Confirm that roof areas match the architectural plans, hardstand areas match the civil plans, modelled catchments match the drainage layout, and the nominated discharge point is both physically and legally available.
Before lodgement, test the package against four practical questions:
- Can an assessor identify the governing criteria and verify compliance?
- Can a contractor build the shown system without resolving core design decisions?
- Can the future owner access, inspect and maintain every critical asset?
- Does the proposed development remain safe when the minor drainage system is exceeded?
This review is also the right time to check document control. Superseded plans, inconsistent revision numbers and calculations prepared for an earlier layout can undermine an otherwise sound submission.
When a standard report is not enough
Some projects need more than a conventional stormwater concept report. Sites with a history of flooding, disputed drainage responsibility, ageing private networks, industrial contamination risks or complex downstream interfaces may require forensic investigation, CCTV condition assessment, survey validation, detailed flood modelling or compliance auditing before a credible approval position can be formed.
The additional work has a cost, but it can materially reduce exposure to conditions that cannot be satisfied, redesign after approval, construction variations and future liability. For high-risk assets, data is not an optional extra. It is the basis for a defensible decision.
A well-prepared drainage submission gives decision-makers confidence that the design is not merely compliant on paper. It shows that the system can be constructed, maintained and relied upon over its service life – the standard that protects both project approval and long-term asset performance.
