Auditing SuDS: Knowing What’s Built, and What’s Working

Date 14.04.2026
Category Auditing SuDS: Knowing What’s Built, and What’s Working
Author Conor Holgate

Sustainable Drainage Systems are now a routine part of new developments across the UK.

They are designed, approved, and expected to manage surface water in a more sustainable way; slowing flow, providing storage, and reducing pressure on traditional drainage networks. On paper, their role is clear, but that clarity often fades once construction begins.

From Design to Delivery

Across many authorities, there is a growing gap between what is designed and what is ultimately delivered on site. Changes during construction, variations in interpretation, and limited oversight mean that SuDS are not always built exactly as intended. Even where they are, the detail of what has been delivered is not always clearly recorded or retained.

By the time assets are handed over, responsibility has often passed through multiple parties. Developers, contractors, planning teams, and operational teams all play a role, but information does not always move with the same consistency. What was approved at planning is not always what is understood by the teams responsible for long-term management.

This creates a familiar position for many authorities. SuDS exist, but there is limited visibility of what has actually been built, whether it has been tested, and how it is expected to perform over time.

The Visibility Gap

This lack of clarity has practical consequences. Maintenance teams are asked to manage assets without a full understanding of their design or condition. Flood risk teams are expected to rely on infrastructure without clear evidence of how those assets were delivered or assessed. When issues arise, it is difficult to determine whether they stem from design, construction, or ongoing management.

In each case, the underlying problem is the same: there is no clear, structured record linking design intent to real-world delivery.

A Clear, Verifiable Record

Addressing this requires more than simply recording that an asset exists. Authorities need a way to evidence what has been built, how it aligns with approved designs, and what testing or validation has been carried out.

Rather than treating SuDS as static assets, auditing introduces a structured layer of verification. It allows teams to capture what has been delivered on site, record whether it aligns with specification, and attach supporting evidence such as inspection outcomes or stress test results where these have been carried out. Over time, this builds a consistent and traceable history for each asset or site.

KaarbonTech’s SuDS auditing capabilities are designed to support this in practice. Authorities can record whether assets have been built to specification, attach evidence of testing or validation, and maintain a verified record that sits alongside the wider drainage network. This does not replace physical testing or inspection, but ensures that the outcomes of those activities are captured, structured and accessible.

Instead of relying on assumptions about what should be in place, authorities can understand what actually exists. Instead of reacting to issues as they arise, they can identify where risks may sit earlier. Instead of fragmented information across teams, there is a single, consistent record that can be referenced over time.

From Uncertainty to Accountability

This supports stronger accountability across the lifecycle of SuDS and provides greater confidence that the infrastructure being relied upon to manage water has been delivered and evidenced as intended.

As SuDS become more widely adopted, and with increasing focus on standards, adoption and long-term performance, that confidence becomes increasingly important.

Knowing what has been built is one step. Knowing what has been evidenced is another. Bringing those together supports a clearer understanding of how SuDS contribute to managing risk within a wider, connected drainage network.

This moves SuDS management away from assumption and towards evidence, supporting:

  • Operational confidence: Maintenance and operational teams can work from a clear understanding of what exists, how it was built, and how it is expected to perform.

  • Risk identification: Gaps between design, construction and performance can be identified earlier, before they lead to failure or reactive intervention.

  • Accountability across the lifecycle: Clear records of delivery, testing and condition help define responsibility between developers, contractors and authorities.

  • Evidence for compliance and investment: Structured, verifiable records support adoption processes, regulatory requirements and future funding or improvement programmes.