A drainage concept can look straightforward on a civil layout and still become the reason a Brisbane project stalls. Brisbane drainage approval requirements are not limited to sizing pipes and nominating a lawful point of discharge. They can involve flood behaviour, overland flow, water quality treatment, detention, downstream capacity, site levels, construction sequencing and the condition of existing assets.
For developers, asset owners and project managers, the commercial issue is clear: drainage is often resolved late, yet it can drive redesign, approval conditions, infrastructure works and ongoing maintenance liability. The most reliable approach is to establish the drainage constraints early, model the system properly and produce documentation that is defensible through assessment, construction and handover.
When does a drainage approval apply in Brisbane?
The approval pathway depends on the nature of the work, the site and the receiving drainage system. A new development, subdivision, major alteration, hardstand expansion or change in use may require stormwater matters to be addressed through development assessment. Works within, adjoining or connecting to public drainage infrastructure can also require separate consent from the relevant authority.
It is important to separate three issues that are frequently grouped together as “drainage approval”. The first is planning approval for development and its stormwater outcomes. The second is approval or consent for works affecting Council-controlled drainage assets, road reserves, easements or waterways. The third is certification and regulated plumbing and drainage work associated with a building project. These pathways can overlap, but they are not interchangeable.
A building approval does not automatically establish that site stormwater can be discharged as proposed. Likewise, a concept endorsed during planning may still need detailed design, operational works documentation or asset-owner consent before construction can proceed. The exact pathway should be confirmed against the current planning controls, development conditions, property records and proposed scope.
The drainage matters assessors will test
Brisbane projects are generally assessed against a combination of planning scheme provisions, adopted infrastructure requirements, catchment-specific constraints and accepted engineering practice. The applicable requirements will vary with location, development type and risk profile, particularly where a site is affected by flooding, waterways, tidal influence or constrained downstream infrastructure.
Lawful point of discharge and downstream capacity
Every design needs a credible answer to a basic question: where does the water go, in both frequent and major storms? A lawful point of discharge might be a kerb and channel, piped network, drainage easement, watercourse or approved on-site solution. It cannot simply be a low point at a boundary or an informal flow path across adjoining land.
The receiving system must also have adequate capacity, or the project may need to manage flows on site, stage discharge, upgrade infrastructure or revise the development outcome. Existing pit and pipe records are useful, but they should not be treated as conclusive. Site investigation can reveal altered levels, blocked structures, undocumented connections or deteriorated assets that change the feasible design response.
Flooding, overland flow and safe conveyance
Conventional pipe design is only part of the drainage case. Major storm events exceed the capacity of underground systems, so surface flow paths and finished levels need to manage exceedance flows without creating unacceptable risk to buildings, accessways or neighbouring land.
Flood modelling may be required where the development sits in a mapped flood area or where site works change flood storage, conveyance or afflux. A proposal that removes low-lying storage, obstructs an overland flow path or concentrates runoff towards a vulnerable boundary can fail even when its minor drainage system is correctly sized.
The assessment should distinguish between nuisance ponding and a material change in flood risk. That distinction depends on levels, velocities, depth, duration, warning time and the sensitivity of affected uses. For industrial facilities, critical plant locations, hazardous material areas and operational access may warrant a more conservative resilience response than a standard commercial site.
Quantity control through OSD
On-site stormwater detention, commonly called OSD, may be required to limit post-development discharge rates. Its purpose is to prevent new impervious area from shifting peak flows and downstream impacts into the public system.
An OSD system is not just a tank volume on a drawing. It needs correctly derived inflows, storage-volume calculations, outlet controls, overflow paths, maintenance access and a practical construction detail. Small errors in orifice sizing, outlet invert levels or hydraulic connections can materially alter performance.
Designers should also consider operational reality. A detention basin below a loading area, for example, may be difficult to inspect, prone to sediment accumulation and exposed to damage. A technically compliant concept that cannot be maintained is a poor long-term asset decision.
Water quality and WSUD performance
Where water quality treatment is required, the design may need to demonstrate pollutant reduction through water sensitive urban design, or WSUD, measures. Depending on the site, this could involve treatment trains incorporating source control, sedimentation, filtration, bioretention or proprietary treatment devices.
MUSIC modelling is commonly used to test whether the proposed treatment strategy achieves applicable objectives. The model is only as credible as its inputs and assumptions. Catchment areas, imperviousness, rainfall data, treatment node configuration, bypass arrangements and maintenance assumptions must align with the actual design.
A recurring failure point is treating the model as an approval document rather than a design control. If the construction drawings omit the treatment footprint, bypass detail, filter media specification, access or maintenance requirements assumed in MUSIC, the built asset may not deliver the claimed performance.
What a defensible submission should contain
The level of documentation should match the scale and risk of the project. A minor alteration may need a concise drainage plan and calculation package. A larger development or constrained site may require detailed hydraulic modelling, flood assessment, water quality modelling, construction drawings and an operational management plan.
For complex projects, the submission should establish a clear chain from survey and site constraints through to design assumptions and final outcomes. It will commonly address existing and proposed catchments, design storm events, pipe and pit capacity, surface flow routes, finished floor levels, detention calculations, water quality outcomes, downstream interface details and maintenance responsibilities.
Where public assets are involved, provide accurate plans showing tie-in points, easements, offsets, asset levels and any proposed protection, relocation or upgrade works. Ambiguity at the public-private interface is a common source of approval conditions, construction variations and later disputes.
Common causes of delay
Drainage approval delays are rarely caused by one missing calculation. More often, they result from inconsistent information across planning material, civil drawings, architectural levels and hydraulic reports. A roof plan that drains differently from the civil catchment plan, or an OSD outlet that cannot physically connect at the stated level, weakens confidence in the entire package.
Other common issues include relying on outdated survey, assuming downstream capacity without verification, overlooking overland flow, placing treatment assets where maintenance is impractical, and leaving easement or third-party consent questions unresolved. These are avoidable issues, but only if drainage is treated as an integrated design discipline rather than a late documentation task.
A practical approval strategy
Start with due diligence before locking in building pads, basements, access grades and landscape levels. Review available drainage records, survey information, flood constraints, planning overlays, easements and the likely discharge point. If the project has high consequence exposure, undertake targeted site investigations and preliminary modelling early enough to influence the masterplan.
Then develop the drainage strategy alongside the architectural and civil design. Use DRAINS or equivalent hydraulic tools to test pipe and surface-system performance where appropriate, and use flood and water quality models at a level proportionate to the risk. The objective is not to produce more reports. It is to make critical design decisions with data that can withstand review.
Before lodgement, conduct a coordination and compliance audit. Check that calculations, models, levels, plans, specifications and proposed maintenance arrangements describe the same asset. This is especially valuable for staged developments, brownfield sites and projects with multiple design consultants.
For high-risk or contested matters, an independent forensic review can identify whether a proposed solution has a hidden constructability, performance or liability issue before it becomes embedded in an approval condition or contract.
Stormwater Services Australia supports this process from drainage and flood modelling through compliance auditing, construction and long-term asset management. The value of an integrated approach is continuity: approval assumptions are carried into the built work and then into the maintenance regime needed to protect performance.
The strongest drainage submission is not the one with the most drawings. It is the one that demonstrates, with coordinated evidence, that the site can manage water safely, lawfully and maintainably for the life of the asset.
