Why drainage and SuDS conditions get refused

The refusal grounds we see most often on London decision notices, and what to submit instead.

Trails Research·Updated 2026-07-29·6 min read
From our ongoing reading of London planning decision notices
… of the drainage discharge submissions we read are refused
… of refusals cite the single most common ground

A refusal here does not mean the scheme was rejected: permission was already granted. It means the submission meant to satisfy the condition did not pass, which stalls the start on site.

When a planning permission carries a drainage or SuDS condition, the developer has to discharge it: the detail is submitted for written approval before work begins. A material share of those submissions fail: the headline above is how often we see that happen.

The grounds below are drawn from a wider net: the refusal reasons recorded across the flood and drainage refusals we read in the capital, not the discharge stage alone, bucketed into recurring themes to show what they actually say. It is built from public records; individual schemes are not named, and we publish the pattern rather than the tally.

Why do drainage and SuDS conditions get refused?

The refusal grounds cluster into a small number of recurring themes. The live breakdown loads below; the pattern it shows is that most turn on what the submission demonstrates rather than whether the drainage can work. The exception is flood-risk refusals, which turn on the site itself.

What the refusal grounds actually say

The theme breakdown is withheld until we have read enough refusals to report it reliably: a named ground resting on a handful of cases would be neither trustworthy nor anonymous. It appears here once we have read enough.

How do I avoid a refusal?

Work backwards from the grounds above. Three things account for most of it:

  • Show the calculation, not the conclusion. A stated discharge rate with no method behind it is the most common single gap.
  • Name who maintains it. Maintenance and adoption is a recurring omission, and increasingly what the condition explicitly asks for.
  • Answer the condition as written. Where it names a verification report or as-built drawings, provide that document, not a general drainage statement that covers the topic.

Most turn on evidence that existed but was not submitted; flood-risk refusals aside, where the site rather than the paperwork is the problem. See what a SuDS condition actually requires for the full picture of what is being asked, and pre-commencement conditions for what a refusal costs in programme.

Where does this come from?

We read planning decision notices across inner- and outer-London boroughs as part of our monitoring work, and this page reports the patterns in what we have read. These are observations, not a census: our reading is deeper in some boroughs than others, and where it is still thin we hold a figure back rather than publish it. Proportions and rankings are published here; the underlying counts, and how much of each borough we have read, are on the London page. Only aggregate patterns appear here: never a scheme address, an application reference, or the wording of a refusal. See the methodology page for sources and refresh cadence, or the full London flood & drainage picture .

This is the public view. Flood and drainage consultants use Trails to see the same picture for their own patch: which live applications carry a drainage condition, and the architect behind each one.

See how Trails works for consultants →

Frequently asked questions

Why was my drainage discharge of conditions application refused?
One ground dominates everything else in what we read: insufficient detail or evidence submitted. Behind it sit an unagreed drainage strategy, unagreed runoff or attenuation rates, and maintenance or adoption gaps. Notice what that list has in common: these turn on what the submission demonstrates rather than on whether the drainage can work, so the fix is usually a better submission rather than a redesign, which is the far cheaper problem. Flood-risk refusals are the exception: they turn on the site itself, so the fix is substantive mitigation (a proper flood risk assessment, raised levels, compensatory storage), not better paperwork, and on the worst sites not achievable at all.
Is a refused discharge of conditions the same as a refused planning application?
No, and the distinction matters commercially. Planning permission has already been granted; what has been refused is the submission intended to satisfy a condition attached to that permission. The scheme is not dead. But if the condition is pre-commencement, work cannot lawfully begin until it is discharged, so a refusal at this stage converts directly into programme delay rather than into a lost project. That is why the discharge stage is worth taking as seriously as the application itself.
What should a drainage discharge submission include?
Work backwards from the refusal grounds. Show the calculation, not just the conclusion: greenfield runoff rates and attenuation volumes with the method visible. Include the maintenance and adoption arrangements, which are a recurring omission and are increasingly what the condition explicitly asks for. Where the condition names specific evidence such as a verification report or as-built drawings, provide exactly that document rather than a general drainage statement that covers the topic. In our reading, most refusals turn on evidence that was available but was not submitted; flood-risk refusals aside, where the site rather than the paperwork is the problem.

About this data

This article reports patterns in UK planning decision notices that Trails reads across London local planning authorities, recomputed daily. Every figure carries its own sample, and the London page shows how much of each borough's decisions we have read.

→ The full London flood & drainage picture→ Methodology and sources

About Trails

Trails reads London planning decision notices every morning and shows flood and drainage consultants which schemes have just picked up a drainage condition, which discharge submissions were refused, and the architect behind each one.

See how Trails works for consultants →