A blocked outlet, a modified storage area or missing maintenance records can turn an otherwise functional OSD asset into a compliance risk. If you are asking, is your strata’s OSD system council-compliant, the right answer cannot be based on a quick visual check alone. It depends on the approved design, the condition of the installed assets and whether the system is being maintained as required.
For strata committees, building managers and owners corporations, an OSD system is not an optional site feature. It is engineered infrastructure intended to temporarily hold runoff during heavy rainfall and release it at a controlled rate. When its capacity or outlet control is compromised, the consequences can include site flooding, damage to common property, neighbour complaints, insurance complications and action from the relevant council.
What council-compliant means for an OSD system
Council compliance generally means the system continues to operate in accordance with the development approval, approved drainage plans and any conditions or legal instruments attached to the property. The exact requirements vary between councils and developments, particularly across older apartment sites where records may be incomplete or the site has been altered over time.
A compliant system is not simply one that looks tidy or drains after rainfall. Its storage volume, outlet configuration, overflow route, access points and associated pits must perform as designed. The system also needs to remain accessible for inspection and maintenance.
For example, a below-ground tank may appear sound, but it may no longer comply if sediment has reduced its effective capacity, an orifice has been enlarged during an earlier repair, or a control pit has been covered by landscaping. These are operational issues, but they can also be departures from the approved arrangement.
Compliance is specific to your site
There is no single checklist that confirms every strata OSD system is compliant. The original approval may nominate a required detention volume, outlet size, maximum permissible site discharge, maintenance frequency or reporting requirement. Some sites also carry a positive covenant or restriction that establishes ongoing obligations for present and future owners.
This is why generic maintenance advice has limits. A suitable assessment starts with the approved documents where available, then compares them against what is actually installed on site. If documents cannot be located, a specialist inspection can establish the existing configuration and identify what needs further investigation.
Is your strata’s OSD system council-compliant? Start with evidence
A strata committee should be able to produce clear evidence that its OSD system has been inspected, maintained and kept operational. When records are missing, it becomes difficult to demonstrate reasonable asset management after a complaint or incident.
The most useful starting point is to gather the development consent, approved civil or hydraulic plans, any covenant documents, previous inspection reports, maintenance records and records of past remedial works. These documents reveal what the council expected the asset to do and whether past contractors identified unresolved issues.
Then arrange an inspection that assesses condition and performance, rather than simply clearing visible debris. The inspection should identify each accessible component, check that control structures have not been altered and document defects with photos and practical recommendations.
For strata sites, the assessment commonly considers:
- storage tanks, chambers and detention areas for sediment build-up, deterioration and available capacity
- pits, grates and access covers for blockages, damage, unsafe access and unauthorised alterations
- outlet controls, including orifices, weirs and pipes, for correct sizing, obstructions and deterioration
- overflow paths and downstream drainage assets for signs of surcharge, erosion or restricted flow
- pumps, alarms and electrical controls where these form part of the approved system
A formal report matters because it separates observed facts from assumptions. It gives the committee a documented basis for budgeting, prioritising works and responding to questions from owners, insurers or council officers.
Common reasons OSD systems fall out of compliance
Most compliance issues develop gradually. They are often the result of normal ageing, deferred maintenance or well-intended site changes completed without considering the OSD design.
Sediment and rubbish are a common issue. Over time, build-up in a detention chamber can substantially reduce the volume available during a storm. A system may still appear to drain on an ordinary day, yet have far less capacity when it is most needed.
Alterations are another frequent cause. Landscaping, storage cages, paving, renovations and replacement covers can obstruct access to pits or detention areas. Changes to grates, outlet pipes or control structures can also affect hydraulic performance. Even a small alteration to an outlet opening can change the rate at which runoff leaves the site.
Ageing components require attention as well. Cracked pits, corroded grates, damaged covers and degraded pipe connections can create both performance and safety risks. Where a system relies on a pump, poor servicing, failed alarms or unsuitable controls can prevent the asset from operating as intended.
The trade-off is straightforward: minor maintenance completed early is usually more economical and less disruptive than waiting for a major failure. However, not every defect needs full replacement. A condition assessment should distinguish between routine cleaning, targeted repair and a broader upgrade.
Maintenance is necessary, but it may not be enough
Regular cleaning and inspection are fundamental, particularly before periods of heavier rainfall. But maintenance does not correct a system that was altered, undersized, poorly accessible or materially different from its approved design.
If an inspection identifies a compliance departure, the next step is to determine whether remedial works can restore the original design intent. This may involve cleaning accumulated material, repairing damaged pits or pipes, reinstating a restricted outlet, improving access or removing obstructions from storage areas.
In more complex cases, the strata may need a technical review and updated documentation before works proceed. This is particularly relevant where the building has undergone additions, hardstand areas have increased, or original plans are unavailable. A staged approach is often sensible: make immediate safety and operational repairs, investigate the approved requirements, then plan permanent remediation with a clear scope and budget.
Give the committee a clear compliance pathway
Strata decisions are easier when the committee receives a report that answers practical questions. What is the current condition? What presents an immediate risk? What work is required to restore performance? What can be planned as part of future capital works?
A useful compliance report should include asset findings, photographs, observed defects, maintenance requirements, recommended remedial works and a priority rating. It should also identify any limitations, such as inaccessible areas or unavailable approval records. Transparent reporting prevents committees from spending on unnecessary works while ensuring genuine defects are not left unresolved.
For larger or more complex strata schemes, recurring inspections provide stronger long-term control. They create a maintenance history, help identify gradual deterioration and allow the owners corporation to forecast expenditure rather than react after a failure. They also make handovers between strata managers far more reliable.
Council compliance is not achieved by filing away an old plan or arranging a one-off clean. It comes from keeping the OSD system accessible, maintained, documented and aligned with its approved purpose. If there is uncertainty about your site, a specialist inspection gives the committee the facts needed to act with confidence and do the work right the first time.
