Need to talk? Call 07503 558323
Back to articles
Flow Restored Journal

SEPA drainage regulations Scotland: a forensic, design-led compliance guide

Flow Restored
SEPA drainage regulation in Scotland hinges on protecting the water environment: select lawful discharge routes (often infiltration, then watercourse, then sewer by agreement), control construction pollution, and prove capacity with site-specific evidence. For compliance, combine soil testing (BRE 365-style soakage assessment), runoff rate/volume checks, treatment trains, and maintenance plans. Document decisions, consult SEPA/Local Authority early, and retain records to defend flood, pollution, and enforcement risks. (Source: SEPA)

SEPA drainage regulations Scotland: a forensic, design-led compliance guide

This article provides a practical, evidence-first approach to meeting drainage requirements in Scotland where the Scottish Environment Protection Agency (SEPA) is a key regulator of activities that may affect the water environment. It is written for engineers, developers, surveyors, and property stakeholders who need to justify drainage decisions, address failures, or prevent enforcement risk while aligning with Scottish policy and technical standards. (Source: SEPA)

What SEPA regulates (and what it typically expects to see)

SEPA’s remit includes protecting the water environment from pollution and physical impacts, including those arising from surface water drainage, construction activities, and discharges to groundwater or surface waters. Depending on the activity, requirements may arise via the Water Environment (Controlled Activities) (Scotland) Regulations (CAR) and pollution prevention expectations during construction. (Source: SEPA)

In practice, when drainage is being designed, altered, or investigated, SEPA and/or the Local Authority (as Flood Authority) commonly expect:

  • Clear destination for surface water (infiltration, watercourse, or sewer with agreement) supported by evidence. (Source: SEPA)
  • Appropriate SuDS selection and siting, including treatment and attenuation where required. (Source: CIRIA)
  • Demonstration that infiltration is viable and safe (ground conditions, groundwater level, separation distances). (Source: BRE)
  • Construction-phase controls (silt control, spill response, temporary drainage, wheel wash). (Source: SEPA)
  • Long-term maintenance plan with inspection frequencies and responsible party identified. (Source: CIRIA)

Regulatory landscape in Scotland (SEPA, Local Authorities, and standards)

CAR licensing/registration and controlled activities

Discharges to surface water or groundwater, abstractions, engineering works in inland waters, and other controlled activities may require authorisation under CAR. Whether a proposed drainage outfall, infiltration discharge, or dewatering arrangement needs authorisation depends on the activity type, location sensitivity, and scale. Always confirm the correct authorisation route early. (Source: SEPA)

Flood risk, roads drainage, and planning conditions

Local Authorities (often through Flood Risk Management and Roads/Transport teams) typically assess surface water drainage proposals through planning and roads construction consent processes. This is especially relevant where new development increases impermeable area, changes flow routes, or interacts with culverts and ordinary watercourses. (Source: Scottish Government)

Technical guidance commonly relied upon in Scotland

While project-specific requirements vary, commonly referenced technical sources include:

  • SuDS manuals and guidance for treatment trains and maintenance principles. (Source: CIRIA)
  • Soakaway and infiltration assessment methods for sizing and performance verification. (Source: BRE)
  • Scottish water policy and flood risk guidance for sustainable surface water management. (Source: Scottish Government)
  • Ground condition and hydrogeological data to support infiltration feasibility and contaminant pathways. (Source: British Geological Survey)

Design hierarchy: proving your drainage destination is compliant

1) Infiltration to ground (often preferred, but must be proven)

Infiltration-based systems (soakaways, infiltration basins, permeable pavement sub-bases) can reduce runoff volumes and mimic natural drainage. However, they must be supported by soil permeability evidence, groundwater depth assessment, and pollutant risk management to protect groundwater. (Source: SEPA)

A defensible submission typically includes:

  • Site investigation logs: strata, permeability indicators, made ground, and contamination screening. (Source: British Geological Survey)
  • Infiltration testing at representative depths and locations. (Source: BRE)
  • Seasonal groundwater considerations and separation distances to buildings and boundaries. (Source: BRE)
  • SuDS treatment where runoff may carry pollutants (e.g., parking areas) before infiltration. (Source: CIRIA)

2) Discharge to watercourse

Where infiltration is unsuitable, controlled discharge to a watercourse may be appropriate, typically with attenuation to manage peak flows and SuDS treatment to manage water quality. Outfalls, bank protection, and works near watercourses can trigger CAR considerations and require careful ecological and geomorphological assessment. (Source: SEPA)

3) Discharge to public sewer

Connection to the public sewer network is generally by agreement with the sewerage undertaker and may be limited by capacity or policy constraints. Documentation usually needs evidence that infiltration and watercourse discharge were not viable, plus confirmation of connection approval. (Source: Scottish Water)

Technical data: infiltration performance and indicative risk bands

The table below is an engineering screening tool used to frame early feasibility and forensic diagnostics. It does not replace site testing, but it helps explain why certain ground conditions repeatedly correlate with drainage failure, surcharge, or non-compliance when infiltration is assumed without evidence. (Source: BRE)

Ground / soil type (typical) Indicative infiltration capacity (Vp band, s/m) Typical drainage behaviour Failure likelihood if infiltration is relied upon without field tests Forensic flags to verify
Coarse sand / gravel (often glaciofluvial deposits) ~1×10-5 to 1×10-3 Generally good infiltration; storage sizing dominates Low–Medium High groundwater, preferential pathways, clogging from fines (Source: British Geological Survey)
Medium–fine sand / sandy till ~1×10-6 to 1×10-5 Often workable with larger footprint and robust pre-treatment Medium Seasonal perched water, variable strata, construction compaction (Source: BRE)
Silty clay / clayey till / lacustrine clays ~1×10-8 to 1×10-6 Poor infiltration; attenuation and controlled discharge usually required High Slow drainage, groundwater mounding, soakaway “never empties” (Source: BRE)
Made ground (heterogeneous fills) Highly variable; test-specific Unreliable; risk of settlement, clogging, and pollutant pathways High Unmapped services, contamination, fines migration, collapse voiding (Source: SEPA)

Forensic methodology: how to evidence compliance (or diagnose non-compliance)

Common failure modes seen in Scottish drainage investigations

Drainage non-performance is often not caused by a single “broken pipe” but by a chain of assumptions: untested infiltration rates, unaccounted contributing areas, missing flow controls, inadequate silt management during construction, or lack of maintenance leading to blocked inlets and reduced storage. (Source: CIRIA)

Minimum evidence pack for a defensible SEPA-facing position

A robust file typically includes: drawings (as-designed and as-built), calculations for runoff and attenuation, infiltration test results with locations and depths, CCTV/drainage survey outputs, and a maintenance and monitoring plan. The goal is traceability: a reviewer should be able to follow how you selected a discharge route and how you ensured water quality and flood risk controls. (Source: SEPA)

Decision logic (diagnostic blocks)

If infiltration is proposed then provide soil infiltration test results, groundwater observations, and demonstrate separation distances; else justify why infiltration is not feasible and proceed to watercourse/sewer options with evidence. (Source: BRE)

If runoff drains from parking/trafficked areas then include a treatment train (e.g., source control + filter + basin) before discharge/infiltration; else document why pollution risk is low (e.g., roofs only) and confirm treatment rationale. (Source: CIRIA)

If there is a history of flooding, surcharge, or ponding then undertake capacity checks, exceedance routing review, and investigate blockage/siltation; else confirm inspection records and demonstrate design storm resilience. (Source: Scottish Government)

If works occur in/near a watercourse (outfall, culvert, bank works) then screen CAR requirements and ecological/geomorphology impacts; else retain a written screening note for the project file. (Source: SEPA)

If construction is ongoing then implement pollution prevention controls (silt fences, settlement tanks, spill kits) and document inspections; else verify legacy controls were removed safely and permanent SuDS commissioned. (Source: SEPA)

Forensic checklist: site survey steps (8–10)

  • Confirm drainage ownership, responsibilities, and legal outfall rights (wayleaves/servitudes where relevant). (Source: Scottish Government)
  • Collate as-built drawings, planning conditions, CAR authorisations/registrations, and maintenance records. (Source: SEPA)
  • Map contributing areas and verify impermeable extents against current site use and aerial imagery. (Source: Ordnance Survey)
  • Undertake manhole schedule and connectivity testing (dye testing where appropriate) to validate flow routes. (Source: CIRIA)
  • CCTV survey critical pipe runs to identify fractures, deformation, siltation, and misconnections. (Source: WRC)
  • Inspect SuDS assets for sediment loading, vegetation condition, inlet/outlet blockage, and short-circuiting. (Source: CIRIA)
  • Perform infiltration testing at proposed invert depth(s) and multiple locations to capture variability. (Source: BRE)
  • Record groundwater indicators (trial pits/boreholes), seasonal constraints, and nearby abstractions/springs. (Source: British Geological Survey)
  • Check exceedance routing for extreme storms and confirm no uncontrolled flow paths to sensitive receptors. (Source: Scottish Government)
  • Produce a photographic record and chain-of-custody log for samples, survey files, and field notes. (Source: SEPA)

Case studies (Scotland): defensible outcomes and recurring pitfalls

Case study A: soakaway failure in clayey till due to untested Vp

A small development relied on soakaways specified generically, but residents reported persistent ponding after moderate rainfall. Forensic trial pits showed clayey till at shallow depth and evidence of perched water. Retrospective infiltration tests indicated very low permeability, meaning the storage never fully recovered between events. Remediation involved redirecting flows to a lined attenuation feature with controlled discharge (subject to approvals) and adding a treatment stage. (Source: BRE)

Case study B: pollution risk from construction runoff entering a burn

During earthworks, fine sediments were transported via temporary overland flow to a nearby burn. The corrective action plan implemented settlement control, check dams, and a defined temporary drainage route, supported by inspection logs and trigger levels following rainfall. This reduced turbidity incidents and created a defensible audit trail demonstrating reasonable measures. (Source: SEPA)

Case study C: “blocked” system that was actually under-sized with no exceedance plan

A site experienced flooding at a low point despite clear pipes on CCTV. The analysis found the contributing impermeable area had increased (additional paving) and the flow control had been omitted during construction, causing peak flows to exceed the downstream capacity. A retrofit throttle and upstream storage, plus a formal exceedance route away from buildings, resolved the issue. (Source: CIRIA)

Documentation that reduces regulatory and dispute risk

For SEPA-facing drainage scrutiny, disputes most often arise when the design intent cannot be evidenced. Maintain a controlled document set:

  • Basis of design note: hierarchy decision (infiltration vs watercourse vs sewer) and constraints. (Source: SEPA)
  • Calculations: runoff rates/volumes, storage sizing, control device settings, and sensitivity checks. (Source: CIRIA)
  • Ground model: logs, groundwater observations, and infiltration test reports with coordinates. (Source: British Geological Survey)
  • Commissioning records: sediment removal, as-built levels, flow control installation photos. (Source: CIRIA)
  • Maintenance plan: inspection frequency, sediment trigger levels, and responsibility assignment. (Source: CIRIA)

Internal resources (related guidance)

To support implementation, see our related guides:

Frequently asked questions (SEPA drainage regulations Scotland)

Do I always need a CAR authorisation for surface water drainage?

Not always. It depends on whether the activity is a controlled activity (e.g., certain discharges, engineering works in inland water, or groundwater interactions) and the scale/sensitivity of the receiving environment. Screen early and retain the rationale in writing. (Source: SEPA)

What is the single most common reason drainage proposals are challenged?

Insufficient evidence: no infiltration test results, unclear outfall details, missing treatment rationale, or absent maintenance commitments. A clear audit trail that ties calculations, site data, and drawings together is usually decisive. (Source: SEPA)

How do I defend an infiltration proposal on variable Scottish glacial deposits?

Test multiple locations and depths, build a simple ground model, and design with conservative parameters and clogging resilience (pre-treatment and maintainability). Avoid relying on a single trial pit result for an entire site. (Source: British Geological Survey)

Conclusion: compliance is an evidence trail, not a statement

Meeting SEPA drainage expectations in Scotland is less about asserting that a system is “SuDS compliant” and more about proving—through test data, calculations, drawings, and maintenance controls—that the chosen drainage route protects the water environment and manages flood risk. Where failures occur, a structured forensic method quickly isolates whether the cause is ground infeasibility, missing controls, misconnections, or maintenance breakdown. (Source: SEPA)