An OSD system can sit out of sight for years, right up until a heavy rain event exposes a blocked outlet, failed pump or altered site level. OSD compliance is not simply a box to tick at handover. It is the ongoing process of confirming that your detention system still performs as approved and does not create avoidable risk for your property or neighbouring sites.

For homeowners, strata committees, developers and facilities teams, the practical challenge is knowing what needs attention, when it needs attention and what evidence to keep. A specialist inspection turns that uncertainty into a clear plan for maintenance, repairs and reporting.

What OSD compliance means in practice

OSD systems are designed to temporarily detain runoff and release it at a controlled rate. They may include a tank, chamber, pit, orifice, filter screen, pipework, access points, overflow provisions and, on some sites, a pump or mechanical control device.

The approved design is specific to the property. Its storage volume, outlet arrangement, levels and discharge control are not optional features. They are the elements that allow the system to manage runoff as intended during a major rain event.

In practical terms, OSD compliance means the system remains accessible, structurally sound, clear of obstructions and consistent with the approved plans and relevant council conditions. It also means any maintenance, alteration or remedial work is properly documented.

A system can look tidy from the surface and still be non-compliant. Silt, leaf litter and rubbish often collect inside pits and chambers. Screens can clog. A small outlet can be blocked or modified. Covers may be damaged, unsecured or buried under landscaping. Each issue can reduce storage capacity or affect the controlled release of runoff.

Why OSD systems fall out of compliance

Most OSD failures develop gradually. They are rarely caused by one obvious event. Regular inspection matters because the early signs are often hidden below ground or behind access covers.

Common causes include poor access for maintenance, debris accumulation, damaged grates and covers, settlement around pits, cracked pipes, unauthorised site works and changes to landscaping or paving. Renovations can also create a problem when new surfaces direct more runoff into a system that was designed for an earlier layout.

For strata properties, responsibility can become unclear when an OSD asset sits beneath common grounds, a driveway or an area used exclusively by one lot. That uncertainty should not delay inspection. The approved plans, strata records and a site assessment can help establish where the asset is located and what work is required.

Older systems deserve particular attention. Original drawings may be incomplete, access points may have been concealed, and components may no longer be operating as intended. The right response is not to guess. It is to inspect the system, assess its condition and develop a staged remediation plan where necessary.

The risks of leaving defects unresolved

A poorly maintained OSD system can contribute to ponding, overflows, property damage and unsafe conditions around pits or covers. It can also create problems during a sale, development application, building upgrade or council review, especially where records are missing.

The financial impact is often greater when routine maintenance has been deferred. Cleaning a blocked component is usually straightforward. Locating a buried chamber, repairing a failed structure or rectifying unauthorised alterations can be more disruptive and costly.

There is also a liability issue. Owners and managers are expected to maintain critical drainage infrastructure under their control. If a known defect is ignored, the consequences can extend beyond the immediate repair bill. For facilities managers and strata committees, clear reporting and a documented maintenance programme provide a far stronger basis for decision-making.

What a proper OSD inspection should assess

An effective inspection does more than lift a grate and take a photograph. It should consider the system as a complete asset and compare site conditions with available approved documentation.

The inspection scope will depend on the property, access and system type, but it should generally address the following:

  • the location, condition and safe access to pits, tanks, chambers and covers;
  • sediment, leaf litter, rubbish and other obstructions that reduce capacity;
  • the outlet control, including whether the orifice or control point is clear and unaltered;
  • pipework, overflow paths, grates and surrounding surfaces for damage, settlement or blockage; and
  • pumps, alarms or mechanical components where they form part of the approved system.

A useful compliance report should identify defects in plain language, include supporting photographs, set out recommended actions and distinguish between urgent safety issues, maintenance items and longer-term upgrades. If the original plans are available, the report should also identify material differences between the approved arrangement and the installed asset.

That distinction matters. Not every defect requires full reconstruction, but some changes cannot be resolved with cleaning alone. A damaged outlet control, inadequate access point or altered site level may require remedial works designed around the approved performance requirements.

How often should OSD maintenance be organised?

There is no single interval that suits every property. The right frequency depends on the system design, surrounding trees, roof and pavement areas, site use, age of the asset and conditions attached to the development approval.

As a practical baseline, many property owners benefit from a professional inspection and clean at least annually, with additional attention after significant rain, construction activity or visible drainage issues. Properties with dense vegetation, shared grounds, basement areas or frequent debris buildup may need a more regular programme.

A maintenance schedule should be based on actual site conditions rather than a generic calendar reminder. If inspections repeatedly find heavy sediment or blocked screens, shortening the interval is usually more cost-effective than waiting for a failure.

For strata and commercial sites, recurring maintenance also creates a consistent record. This helps incoming committee members, building managers and contractors understand what has been done, what remains outstanding and whether defects are worsening over time.

Records that support compliance

Good records are often the difference between a manageable maintenance issue and a difficult compliance dispute. Keep the approved OSD plans and relevant consent conditions with inspection reports, photographs, invoices, cleaning records and details of any repair work.

When works are completed, the record should state what was found, what was done and whether further action is recommended. If access could not be obtained to part of the system, that should be recorded too. A report that identifies limitations is more useful than one that assumes everything is satisfactory.

If you are buying a property, taking over a strata role or planning a renovation, request the OSD documentation early. It is far easier to account for access, maintenance and possible upgrades before plans are finalised than after new hard surfaces, landscaping or structures have been installed.

When cleaning is not enough

Cleaning is essential, but it does not resolve every compliance issue. Specialist remedial works may be needed where pits have deteriorated, pipes are damaged, outlet controls are missing, access is unsafe, levels have changed or the system no longer matches its approved configuration.

The best approach is to start with inspection and evidence, then prioritise work based on risk. Immediate hazards and active failures should be addressed first. Lower-risk improvements can often be scheduled as part of planned property maintenance, provided the system continues to operate safely and as required.

For more complex sites, engaging one specialist provider for inspection, reporting, maintenance and remedial works reduces the risk of gaps between diagnosis and delivery. It also means the people completing the works understand the compliance outcome they are working towards.

Do not wait for visible flooding or a council notice to investigate an ageing OSD system. Organising a clear inspection now gives you a practical record of its condition and a realistic path to keeping the asset serviceable, accessible and compliant.

Stormwater Sydney