An OSD tank can appear to be functioning right up until a major rainfall event exposes the loss of storage beneath the surface. Sediment, litter, organic matter and construction debris gradually reduce effective detention volume, obstruct outlet controls and compromise the asset’s intended hydraulic performance. For owners corporations, strata OSD tank cleaning is therefore not a cosmetic maintenance task. It is a risk-control measure that protects property, supports compliance and creates a defensible record of asset stewardship.
OSD, or on-site detention, systems are designed to temporarily detain stormwater and release it at a controlled rate. In dense strata developments, that function is often delivered through underground tanks, pits, pipe networks, weirs, orifice plates and associated access structures. These assets are commonly out of sight, but their condition can have direct consequences for flood exposure, downstream drainage performance and the corporation’s ability to demonstrate reasonable maintenance.
What strata OSD tank cleaning must achieve
Effective cleaning is not simply the removal of visible rubbish from an access point. The objective is to restore the tank’s operational capacity while confirming that its critical hydraulic components remain consistent with the approved design intent.
A maintenance contractor should identify accumulated sediment and waste, remove material without damaging the structure or fittings, and inspect accessible elements such as screens, grates, baffles, outlet pits and flow-control devices. The work should also establish whether the tank is suffering from defects that cleaning alone will not resolve, including damaged pipework, displaced components, root ingress, joint failure or unauthorised modifications.
The distinction matters. A tank may be emptied of sediment but still fail to restrict discharge correctly because an orifice has been enlarged, bypassed or obstructed. Conversely, a functioning outlet cannot compensate for storage volume lost to years of deposits. Asset managers need evidence of both capacity and control.
Cleaning protects more than tank volume
The immediate benefit of sediment removal is recovered detention volume. However, the broader value is operational certainty. A properly maintained OSD system reduces the prospect of water backing up through car parks, driveways, landscaped areas or lower-level drainage during intense rainfall.
It can also prevent accumulated pollutants from being mobilised into downstream infrastructure. Depending on the development and catchment, tank deposits may contain fine sediments, hydrocarbons, organic material and litter. Their removal and lawful disposal require appropriate controls, particularly where water quality assets or trade-related activities connect to the broader drainage network.
For strata committees, the commercial issue is straightforward: deferred maintenance can turn a predictable programme of inspection and cleaning into a much larger rectification project. Once deterioration, blockage or hydraulic non-compliance is identified, the response may require engineering review, specialist access arrangements, repairs and updated documentation.
Why strata OSD tank cleaning is often missed
Many OSD assets sit beneath basements, courtyards, communal open space or driveways. They may have limited access points and little visual indication of their condition. Maintenance schedules can focus heavily on pumps, lifts, fire systems and visible common property, while stormwater infrastructure is addressed only after water ingress, flooding or a compliance request.
Documentation is another common issue. Older schemes may have incomplete approved drainage drawings, unclear maintenance responsibilities or records that do not reflect later building works. A contractor cannot reliably verify an OSD system from surface observations alone. The relevant design levels, discharge-control arrangements and access configuration must be understood before conclusions are drawn about performance.
Newer developments are not exempt. Construction-phase sediment can remain in tanks after practical completion, and landscaping, hardscaping or drainage alterations can change how runoff reaches the system. A maintenance plan should begin with the installed asset rather than assumptions based on its age.
A defensible cleaning and inspection process
The appropriate scope depends on tank size, access, sediment load, the presence of connected treatment measures and the available design information. It should nevertheless follow a disciplined sequence that links site work with asset records.
First, available plans, approvals, previous inspection reports and maintenance records should be reviewed. This establishes what the system is intended to do and identifies components that must be located or verified. Where records are incomplete, an engineering-led inspection can help reconcile the constructed asset with its likely design function.
The tank and associated structures are then inspected using suitable access and safety controls. Underground OSD assets can present confined-space hazards, poor air quality, unstable surfaces and difficult entry conditions. Works must be planned and undertaken by competent personnel with an appropriate safety system, rather than treating the tank as a routine pit-cleaning exercise.
Cleaning generally involves removing sediment, debris and standing residues using equipment suited to the site and material. The team should avoid dislodging or damaging internal components, particularly calibrated outlet devices. Waste classification, transport and disposal must be managed in accordance with the nature of the material and applicable requirements.
Finally, the condition and function of accessible components should be documented. Good records include photographs, sediment observations, identified defects, work completed, recommendations and confirmation of any items requiring engineering assessment. This information gives the owners corporation a practical basis for future budgeting and provides evidence that the asset has not been ignored.
Cleaning frequency depends on the catchment
There is no single cleaning interval that suits every strata OSD tank. A building beside a heavily trafficked road, a construction site or a landscaped area with high leaf load is likely to accumulate material faster than a stable residential site with clean upstream drainage. Tank geometry also matters. Shallow systems and structures with poor self-cleansing flow paths may retain sediment more readily.
As a starting point, owners corporations should establish a scheduled inspection regime and use actual inspection findings to set cleaning frequency. This is more reliable than committing to a fixed interval without evidence of sediment accumulation or hydraulic condition. Following major site changes, such as landscaping works, basement drainage modifications or adjacent construction activity, an additional assessment may be warranted.
A condition-based approach also helps committees allocate funds responsibly. Cleaning too frequently can create unnecessary expenditure, while waiting until an asset is visibly blocked transfers risk into the next significant storm. Inspection data allows decisions to be based on observed condition, not guesswork.
When cleaning becomes a rectification issue
Cleaning can reveal defects that require more than routine maintenance. Cracked walls, corroded steelwork, damaged access covers, pipe displacement, failed seals and altered outlet structures can all affect performance or create safety risks. So can accumulated sediment that indicates an upstream defect, such as erosion, damaged grates or ineffective pre-treatment.
In these cases, the correct response is to separate maintenance from rectification. Cleaning may make the asset accessible and allow the problem to be defined, but engineering assessment is needed to determine the appropriate repair and whether the system continues to meet its approved discharge requirements. Where liability, insurance or compliance questions arise, independent and well-documented forensic investigation may be necessary.
For complex sites, an integrated provider can connect inspection findings with drainage design review, civil repair works and an ongoing maintenance programme. This avoids the common gap between a contractor reporting a defect and a committee being left to coordinate multiple parties to diagnose and resolve it.
Practical governance for owners corporations
OSD maintenance should sit within the broader asset management plan, not as an isolated line item. The strata manager, facilities representative and committee should know where the asset is located, who can access it, what records exist and which party is responsible for arranging inspection and cleaning.
A useful file includes approved stormwater plans, inspection reports, cleaning records, photographs, defect registers and evidence of completed rectification. These records assist with committee handovers, capital works planning, property transactions and any request from a council or other authority for maintenance evidence.
Stormwater Services Australia approaches OSD assets as engineered systems rather than hidden maintenance liabilities. By linking cleaning with inspection, compliance auditing and targeted rectification where required, strata stakeholders can make decisions from reliable evidence.
The most useful time to assess an OSD tank is before its lost capacity becomes visible at the surface. A planned inspection and cleaning programme gives the owners corporation clear evidence of condition, a basis for prioritising works and greater confidence that a critical drainage asset will perform when rainfall places it under pressure.












