A townhouse site can look straightforward on a concept plan, then become difficult once roofs, driveways, private courtyards, retaining walls and shared accessways are fitted into a tight footprint. Stormwater design for townhouse developments needs to manage runoff safely, satisfy council conditions and leave the future strata or owners with assets they can realistically inspect and maintain.
The cheapest-looking drainage layout is rarely the lowest-cost outcome over the life of a development. A system that cannot be accessed, has undersized components or relies on undocumented site changes can create ponding, property damage, disputes and costly remedial works after handover. The right approach is to resolve stormwater early, coordinate it with the whole civil and architectural design, and document the finished asset properly.
Start stormwater design before the layout is fixed
On townhouse projects, land area is usually under pressure from parking, landscaping, bins, private open space and building setbacks. That makes it tempting to treat stormwater as a service that can be fitted in later. In practice, its requirements affect finished levels, driveway grades, retaining walls, planter locations and the available area for detention or treatment measures.
A site assessment should establish the existing fall of the land, discharge point, likely runoff paths, soil and groundwater conditions where relevant, flood constraints, easements and any existing drainage infrastructure. It should also identify where runoff from adjoining properties may enter the site. These details determine whether a gravity-based system is practical or whether pumped infrastructure, additional storage or a revised site layout may be needed.
Council requirements vary across Sydney and the Central Coast. Development consent conditions, local planning controls and engineering requirements may set expectations for discharge, on-site stormwater detention (OSD), overflow paths, treatment measures and certification. Designing to a generic rule of thumb is a common mistake. The approved requirements for the specific site must guide the design.
Design for the whole site, not each dwelling in isolation
Townhouse developments combine private and common property. That distinction matters because runoff does not respect title boundaries. Roof areas may drain into a shared system, while a driveway trench drain, courtyard inlet or rear swale may protect several dwellings at once.
The design should map every major catchment area, including roofs, balconies where applicable, paved courtyards, driveways, common paths and landscaped zones. It must then establish how runoff is collected, conveyed, detained and discharged. Finished surface levels are just as important as pipe sizing. A well-sized pit cannot protect a garage or entry if surrounding paving directs runoff towards it.
Particular care is needed at low points, garage ramps and narrow accessways. These areas can collect runoff quickly during intense rainfall. Collection points need suitable capacity, but the system also needs a defined overflow route if an inlet becomes obstructed or rainfall exceeds the design event. Overflow should be directed away from buildings and not towards neighbouring land.
Roof drainage and shared lines
Roof drainage often appears simple, yet it can become a long-term liability where several downpipes connect to buried common lines without adequate inspection points. The route, grade and connection arrangement should allow blockages to be identified and cleared without removing hardscape or entering private lots unnecessarily.
Avoid placing critical junctions beneath driveways, slabs or landscaped areas that will be difficult to excavate. If this cannot be avoided, record the location accurately and specify access covers suitable for the expected load. Future owners need to know what is below the surface before they install fencing, gardens or paving.
Driveways, ramps and surface drainage
Driveways are frequently the largest shared hardstand area on a townhouse site. Their crossfall, longitudinal grade and trench drainage must work together. A trench drain at the bottom of a ramp is not a substitute for sound grading upstream.
Grates should be selected for their location and expected traffic loading. They also need practical cleaning access. Fine leaf litter, mulch and rubbish can quickly reduce inlet performance, particularly where landscaping borders paved areas. This is not merely a maintenance issue – it is a design issue when the system has no allowance for debris management.
OSD must be buildable and maintainable
OSD is commonly required to limit the rate at which runoff leaves a developed site. It may be provided through tanks, pits, pipes, underground storage or other approved arrangements. The selected solution should fit the site conditions, the consent requirements and the long-term management capability of the owners corporation.
Underground storage can preserve usable open space, but it may cost more to construct and is harder to inspect if access is poor. Surface-based solutions can be easier to observe, yet may affect landscaping and usable areas. There is no single best option. The practical choice depends on available space, required storage volume, site levels, construction sequencing and future access.
Every OSD system needs a clear path for inspection, cleaning and verification. That includes access to the storage area, control outlet, screens, pits and overflow provisions. Covers must remain reachable after landscaping and fencing are completed. A detention system hidden below a finished courtyard may technically exist, but it is not a manageable asset if no one can inspect its critical parts.
The design documentation should clearly state the approved storage volume, outlet configuration, operating levels and maintenance requirements. At completion, certification and as-built information should match what was actually installed. Small site changes made during construction can materially affect how the system performs.
Include WSUD where it serves the site
Water Sensitive Urban Design (WSUD) measures can help reduce sediment, litter and other pollutants leaving a development. Depending on the approved design, measures may include vegetated systems, filter cartridges, treatment pits or landscaped retention areas.
These measures should not be added as decorative features with no maintenance plan. Vegetated assets need appropriate plant selection, sediment management and safe access. Cartridge systems need servicing at manufacturer-specified intervals. Treatment pits need inspection and cleaning before accumulated material compromises performance.
For townhouse developments, simpler is often better if it can meet the approval requirements. A highly engineered treatment asset with difficult access may be less reliable than a well-designed, serviceable solution that the owners corporation can maintain consistently.
Coordinate the design with construction
Stormwater failures are often created during construction rather than on the engineering drawings. Pipes can be relocated around unforeseen obstructions, pits may be set at incorrect levels, or access points can be covered by finished works. These changes may seem minor at the time, but they can alter grades, reduce capacity or make routine servicing impractical.
A structured inspection process during key construction stages helps identify issues before surfaces are reinstated. Check pit levels, pipe alignment, outlet details, storage components, access covers and overflow paths against the approved design. Any approved variation should be documented promptly, not reconstructed from memory at handover.
Temporary site controls also matter. Sediment and construction debris entering unfinished pits and lines can remain in the system long after practical completion. Final cleaning and inspection should be part of the handover process, not an afterthought once residents move in.
Plan the handover for strata management
A townhouse development changes hands from developer and builder to an owners corporation, strata manager and residents. Without clear records, the incoming manager may not know where critical pits, detention controls or treatment devices are located, let alone what needs servicing.
A useful handover pack should include approved plans, as-built drawings, certification, inspection records, maintenance instructions and a site asset register. It should identify common-property components, access locations and the recommended inspection schedule. Photos of concealed assets before backfilling can also save considerable time when future works are required.
Maintenance should be scheduled around the actual site risks. A leafy site may need more frequent inlet and grate cleaning than an exposed paved site. A system serving a steep driveway may warrant inspection before the wetter months. The aim is to identify sediment, debris, damaged covers and restricted outlets before they affect drainage performance.
When a review is worth arranging
A specialist review is particularly valuable where a townhouse development has a constrained site, basement or ramp drainage, significant retaining, an ageing OSD asset, recurring ponding or incomplete handover records. It can also provide confidence before major landscaping, resurfacing or remedial works change the way runoff moves across the property.
Good stormwater design does more than obtain approval. It gives the development a system that performs under pressure, can be maintained without guesswork and remains defensible through inspections and compliance records. Before construction is locked in, make sure the design leaves the future owners with accessible, documented assets – not hidden problems beneath finished surfaces.
