A flooded garage, overflowing pit or runoff entering a living area raises an immediate question: who is liable when stormwater backs up? The answer is rarely automatic. Liability usually turns on where the blockage or failure sits, who owns that asset, whether it was properly maintained, and whether a person or organisation failed to act reasonably after becoming aware of a risk.
For Sydney property owners, the first priority is to document the event and identify the cause. A professional inspection can establish whether the issue involves a private drain, shared strata infrastructure, an on-site stormwater detention system, a council-managed asset or a defect in building works. That evidence is far more useful than assumptions when insurers, strata committees or council teams become involved.
Who is liable when stormwater backs up?
In broad terms, the owner or party responsible for the failed asset may be liable if their neglect, damage or defective work caused the backup. But responsibility can be shared, disputed or limited by the facts. Heavy rainfall alone does not necessarily make another party liable, particularly where a system was designed for a defined capacity and an unusually severe event exceeded it.
A proper assessment should consider the asset boundary, its condition before the event, maintenance history, any recent building or landscaping work, and whether warning signs were ignored. Photos taken after the flooding matter, but CCTV inspection footage, pit levels, pipe condition and maintenance records often provide the clearer answer.
Private property assets
Homeowners are generally responsible for stormwater infrastructure within their property boundary. This can include gutters, downpipes, surface drains, pits, grates, pipes, tanks, pumps and private drainage lines leading to an approved connection point.
If leaves, sediment, construction debris or tree roots blocked a private line, the owner will usually carry responsibility for maintenance and repair. The same is often true where a damaged pipe, failed pump or poorly graded surface directs runoff towards a building.
That does not mean the owner is always at fault. A recently installed system may have been defective from the outset, or neighbouring works may have changed surface levels and concentrated runoff onto the site. In those cases, the installer, builder, neighbour or developer may need to answer questions about their work.
Strata and shared infrastructure
For apartments, townhouses and other strata schemes, the dividing line is commonly whether the affected asset is common property or part of an individual lot. Shared roofs, common pits, basement drainage, detention systems and main lines are often common property, making the owners corporation responsible for inspection, maintenance and repairs.
However, by-laws, the strata plan and the location of the asset can alter the position. A balcony drain serving one lot, for example, may not be treated the same way as a basement pit serving the whole building. Strata managers and committees should avoid making a liability decision before the system has been inspected and the relevant documents reviewed.
Where poor maintenance of common property contributed to the backup, the owners corporation may face the cost of rectification and possible claims from affected lot owners. Regular inspections and documented maintenance reduce this exposure and give the committee a defensible record of reasonable asset management.
Council-managed assets and public drainage
Councils manage many roadside pits, kerb inlets and public drainage networks. If a backup is traced to an asset outside the private boundary, council involvement may be appropriate. Even then, council liability is not guaranteed simply because a public pit appeared blocked during a storm.
The question is usually whether there was a known defect, a maintenance failure or another negligent act connected to the damage. Councils also have statutory protections and competing maintenance priorities, so a claim requires clear evidence. It is useful to record the precise location, time, rainfall conditions, visible blockage and path of runoff, then retain inspection findings that identify how the event affected the property.
A private system that is undersized, poorly maintained or incorrectly connected can still be the main cause even where nearby public assets were under pressure. Cause must be established, not presumed.
Common situations that affect liability
The circumstances behind a backup matter as much as the visible damage. These are the issues most often examined.
Neglected maintenance
Blocked pits, silted pipes, damaged grates and overflowing gutters are predictable issues. If an owner, strata scheme or facilities team knew about recurring ponding, slow drainage or debris build-up and did not arrange maintenance, that history can weigh heavily against them.
Maintenance obligations are especially relevant for on-site stormwater detention systems. These systems are designed to temporarily hold runoff and release it at a controlled rate. If screens, orifices, pumps or pits are not maintained, the system may not perform as approved. Beyond property damage, this can create compliance concerns.
Building, landscaping or excavation works
Recent works can change runoff paths quickly. New paving may remove permeable ground, retaining walls can redirect flow, and landscaping can cover or obstruct drainage points. Renovation work may also damage buried pipes or leave debris in a pit.
Where the problem follows construction, obtain records of what was changed, including approved plans, contractor scopes and photographs. An inspection should assess whether falls, levels, connections and detention measures remain fit for purpose. The party that carried out defective work may be responsible, but each case depends on contracts, approvals and evidence of causation.
Neighbouring runoff
A neighbour is not automatically liable because runoff crosses a boundary. Properties naturally sit at different levels, and some runoff during major rain is unavoidable. Liability becomes more likely where a neighbour has altered their site in a way that unnaturally concentrates, redirects or discharges runoff onto another property.
Examples may include an outlet directed towards a boundary, a new hardstand without suitable drainage, or fill that changes established flow paths. Early discussion can sometimes resolve a straightforward issue, but an independent report is valuable where the cause is contested or remedial works are likely to be significant.
Extreme rainfall and system capacity
Storm systems are designed to specified standards, not to prevent every instance of ponding under every possible rainfall event. During intense or prolonged rain, a compliant system may surcharge temporarily. That does not automatically mean the owner, builder, strata scheme or council has failed in its duty.
The key distinction is between an unavoidable capacity exceedance and a failure made worse by a blockage, defect, poor maintenance or non-compliant alteration. This is why technical findings should describe both the condition of the system and the likely cause of the event.
What to do after a stormwater backup
Act methodically. First, make the area safe and prevent further damage where this can be done without risk. Keep people away from unstable surfaces, electrical hazards, open pits and fast-moving flows. Photograph affected areas before clean-up, including the direction of runoff, debris, levels and any obvious overflow point.
Next, record the date, approximate time, weather conditions and any prior signs of trouble. Save correspondence with neighbours, contractors, strata managers or council teams. If an insurance claim may follow, notify the insurer promptly and ask what evidence they require before major rectification begins.
Arrange a specialist inspection that goes beyond clearing the immediate blockage. The scope should identify asset ownership, locate defects, assess pipe and pit condition, review the performance of detention infrastructure where relevant, and provide practical recommendations. A clear report can support insurance discussions, strata decisions, contractor rectification or a formal complaint.
Records that strengthen your position
Good records do not create liability, but they make it easier to establish what happened. Keep maintenance invoices, inspection reports, CCTV footage, compliance documentation, approved drainage plans and dated photographs. For strata and commercial sites, maintain a scheduled register showing when pits, drains, pumps and detention components were inspected and cleaned.
If you are buying a property or taking over management of a strata site, an early condition assessment is sensible. Ageing infrastructure and undocumented alterations can remain hidden until the next major storm. Finding those risks before failure is usually less disruptive and less expensive than dealing with damage afterwards.
Stormwater Sydney can inspect, report on and remediate stormwater assets across Sydney and the Central Coast, helping owners and managers move from uncertainty to a practical, evidence-based plan. When responsibility is unclear, the most useful next step is not to assign blame – it is to establish the cause properly and protect the property from a repeat event.
