Discharge of Drainage Planning Conditions

Discharge of drainage planning conditions is the work that turns a granted permission into a start on site: producing the detail the council held back at decision stage, submitting it, and getting it approved in writing before the condition lets anything happen on the ground. The wording on your decision notice sets the whole job. Two sentences on a page decide what has to be produced, what standard it will be judged against, how long the approval takes, and which part of your programme sits still while it happens.

Unda has prepared more than 5,000 flood risk and drainage assessments across England and Wales since 2014. Our consultants are professionally qualified members of the Chartered Institution of Water and Environmental Management, including Chartered Members (MCIWEM C.WEM), and every submission is checked and signed off by a senior consultant before it goes to the council.

We take on conditions attached to schemes we advised on at planning stage, and conditions attached to schemes we have never seen, where the first job is reading what somebody else submitted alongside whatever the drainage consultee said about it. Both are ordinary work.

Permission granted with the work blocked is a different problem from a refusal, and usually a faster one to solve.

What a drainage condition actually requires

A drainage condition requires you to submit a scheme to the local planning authority and have it approved in writing before a stated point in the build. In practice that scheme is a detailed drainage strategy: drawings, calculations, and a maintenance plan for the system once it is in the ground. What the word "scheme" covers on your site is set by the sentence the council wrote, not by a standard specification.

Nearly every drainage condition is built from the same six parts, doing six different jobs. The trigger says when it bites. The deliverable names the document. The standard names what that document will be measured against, the implementation clause obliges you to build what was approved, and the maintenance clause commits somebody to looking after it once it is in. Then the reason, sitting at the bottom in smaller type and routinely skipped, carries the policy an officer will fall back on if there is ever an argument about scope. Take a condition apart along those lines and a paragraph of legal fog becomes a scope of work.

The phrases worth reading twice

• "Detailed scheme", "full details", "final detailed design". The council wants the thing that was not resolved before permission. Not another statement of principle, and not the strategy you already submitted with a new date on the cover.
• "The design must satisfy the SuDS Hierarchy." Justify where you stopped on the five-tier order, with evidence for every tier ruled out above it. Cost on its own has never been enough, as our note on the SuDS hierarchy explains.
• "The climate change adjusted critical 100 year storm." Model the full range of durations, find the one that governs, then apply the climate change allowance for that location and period. A single duration at one allowance does not answer it.
• "A management and maintenance plan for the lifetime of the development." Component by component, matched to the system on the drawing, with somebody named as responsible.
• "Notwithstanding the submitted strategy." The council has read what went in and wants it revised. Worth spotting early, because the fee and the programme are different from a first submission.
• "Approved in writing." Nothing counts until the decision notice arrives. Correspondence with a drainage officer, however encouraging, is not a discharge.

Twelve real drainage conditions, word for word

Below are twelve drainage conditions lifted from real decision notices on Unda schemes and quoted as written, with job references, site names and consultant names removed and the policy references left in, because those are what make the wording real rather than illustrative. The range is the point. Two councils asking the same question of the same kind of site can write it in thirty words or three hundred, and the difference changes what you are buying.

The first two run to a couple of sentences each. Neither says a word about what the submission has to contain, which makes them harder to scope than the prescriptive ones further down, because everything is left to whatever standard the drainage officer happens to apply. Thin conditions are not easy conditions. Where we meet one we agree the content with the officer before producing it, not after.

The eighth is worth pausing on, because it requires the discharge submission to follow the principles of a named Unda flood risk assessment and drainage strategy from the planning stage, which is exactly how a well-built strategy is meant to behave: the planning document sets the framework, the discharge submission fills it in, and nobody reopens the argument. Look at the seventh and you can also see where the numbers come from. It fixes the climate change allowances at plus 35 and plus 45 per cent, with 10 per cent for urban creep. Another condition in this set names a greenfield runoff rate of 8 litres per second per hectare. The council wrote those figures into the permission; we did not choose them, and we cannot negotiate them away at discharge stage.

The eleventh is a pair, and pairs cause more trouble than long conditions do. Cambridge splits foul and surface water across two conditions with two different triggers: surface water before anything is commenced, foul before any building is occupied. Discharge the first, forget the second, and you end up with a finished scheme you cannot hand over. Where foul and surface water sit in separate conditions we track them separately and tell you at the outset which one is on the critical path, and the foul drainage strategy page covers what the foul side involves.

Read across all twelve and the prescriptive ones ask for the same things in a different order. That recurring list is the honest answer to what a drainage condition wants:

• Runoff rates for the existing site, usually at QBar, the 1 in 30 and the 1 in 100.
• Modelling output for the proposed system, including the 1 in 100 plus climate change and an urban creep allowance. Our climate change and urban creep calculator gives a first look at what those allowances do to a storage volume.
• Detailed drawings of the whole system, commonly with levels, gradients, dimensions and pipe references.
• Infiltration test results where infiltration is proposed or has to be ruled out, to BRE Digest 365.
• Exceedance flow routing, showing where water goes when the system is full.
• Maintenance and management arrangements for the lifetime of the development.
• Third-party agreement to connect, with confirmation of capacity in the receiving system.
• Pollution prevention, both during construction and in the finished scheme, usually assessed through the CIRIA C753 Simple Index Approach.

Conditions also age, and several of these still cite the 2015 non-statutory technical standards or the Ministerial Statement alongside references to the current national standards, simply because they were drafted at different times and nobody goes back to tidy them. Above all of it the policy has been steady: the National Planning Policy Framework in force is the December 2024 version, technically amended on 7 February 2025, the Planning Practice Guidance on flood risk and coastal change was last updated on 17 September 2025, and the National Standards for Sustainable Drainage Systems were published in June 2025 and remain expressly non-statutory. We work to what the condition says as well as to what is current. Where the two point in different directions we set that out in the submission rather than quietly picking one and hoping.

Pre-commencement or pre-occupation: what your condition blocks

Read the trigger first. It decides whether you have a programme problem or a paperwork one, and those are different sizes of problem: a pre-commencement condition stops the job dead, while a pre-occupation condition lets you build and only bites when you want to hand over.

Every one of those wordings comes from the conditions quoted above, and the gaps between them are worth real money on a live programme. "Prior to commencement of groundworks (excluding site investigations and demolition)" leaves you free to get the ground investigation done, which matters, because infiltration testing is very often the thing on the critical path. "No development, other than demolition and site clearance" does the same favour for enabling works. "Before any above ground works commence" is more generous again. And "concurrently with the submission of reserved matters" pulls the work forward into the planning programme instead of parking it after the decision.

The expensive version is the plainest one: no works on site shall commence. That stops everything, including the site investigation you need in order to answer the condition.

Where the trigger is drawn that tightly, the first thing we look at is whether the council will entertain an application to vary the wording alongside the discharge submission, so that investigation and enabling works can start. It is not always available, and on a short condition it is not always worth the fee. Ask in week one, not month three.

Underneath all of this sits a principle worth knowing before you ever accept a condition. If the outstanding question is how a solution will be designed, it can usually be handled by condition; if it is whether the thing will work at all, it should have been settled before permission was granted. Our article on what drainage information is needed for planning permission takes that distinction further.

The detailed drainage strategy that discharges the condition

The condition wording sets the scope. Obvious, and skipped more often than anything else on this page, which is why submissions come back asking for items the client was never told they needed, or arrive padded with work nobody asked for and everybody paid for. The first job on every condition we take on is a line-by-line read of what the council actually wrote, checked against the drainage consultee's own technical standard.

Depending on what the condition says and what the authority expects, the submission may need:

• Sizing of attenuation storage, with the calculation output a reviewer can follow rather than a summary of it.
• Flow control specification, naming the device and the discharge rate it delivers. Our orifice and throttle sizing calculator gives a first pass at the size.
• Calculation output for the design events the condition names, at the allowances it names.
• The exceedance flow routing plan, showing flow exceedance routes and where water is held above ground.
• The maintenance plan, built component by component against the system on the drawing.
• Levels and gradients, on some schemes. Not every condition requires them, and whether yours does depends on the council's position and the words in front of you.
• Third-party evidence, where the council wants confirmation that the receiving party will accept the flows before it will determine.

Councils generally call this deliverable a detailed drainage strategy rather than a detailed design, and the choice of words is deliberate on their part. Salford's validation list, to take one example, asks for a drainage strategy at outline and a detailed drainage strategy at full and reserved matters. Using the council's own vocabulary in the submission is a small courtesy that makes an officer's job easier, and we do it as a matter of course. It also tells you what you are buying: the document that satisfies the planning condition, worked up to the level of detail that condition asks for and no further.

Where we wrote the planning-stage strategy the detail follows straight through from work already done and already agreed with the consultee. Where somebody else wrote it, we read their submission and the consultee's response before quoting, so the fee reflects what is genuinely left.

The evidence that clears each type of objection

Consultees rarely object to a scheme in general. They object to a specific, named gap, and every type of gap has a specific answer that closes it, which is why an objection that reads like a disaster in an email from your agent is usually two weeks of work rather than a redesign. Our article on LLFA objections to planning applications carries the diagnosis. This is the short version.

Most of the objections we are asked to clear sit in the bottom three rows. For an early steer on two of them, our BRE 365 infiltration rate calculator and SuDS water quality calculator will tell you roughly where a scheme stands before anyone opens a spreadsheet.

Timescales and the deemed discharge route

Councils have a set period in which to determine an application to discharge conditions, and where they miss it there is a statutory fallback: the deemed discharge provisions in Schedule 6 of the Development Management Procedure Order 2015, which in principle let a condition be treated as discharged once the authority has run out of time. In practice the exemptions catch most drainage conditions. Know about it; do not plan around it. Our guide to discharging planning conditions for drainage sets out the mechanism and the exemptions in full.

What actually moves the date is the quality of the first submission and how early the officer knows it is coming. A pack that answers every limb of the condition in the order the condition lists them, with the calculation output attached rather than summarised, is quicker to determine than one an officer has to reconcile against the wording line by line before they can even start. No trick to it. It is simply less work for the person who has to say yes.

Why first submissions get refused

The maintenance plan

Councils ask for one on almost every drainage condition, and precisely because they are asked for so routinely, this is the item most often produced from a template with the site name swapped in. An officer spots it within a minute, usually because the schedule lists a feature the scheme does not have. A plan that survives review gives every component its own entry: what it is, where it is, what has to be done to it, how often that has to happen, and who carries the responsibility for the lifetime of the development. Nobody finds maintenance controversial. The problem is that the document in front of the officer plainly belongs to another site.

Exceedance flow routing

The other item authorities most consistently ask for and most consistently do not receive. It answers the question the design calculations do not: what happens when the rain is bigger than the system was built for. We include flow exceedance routes on every drainage layout we produce, which is why this one rarely comes back on our submissions. Getting the routes right is mostly levels and kerb lines rather than pipework, so it is cheap at the right moment and awkward to retrofit.

Third-party evidence

Several of the conditions above will not be determined until somebody else has agreed in writing to take the water: a sewer undertaker confirming capacity, a riparian owner or internal drainage board accepting a rate into a watercourse under ordinary watercourse consent, a highway authority accepting a connection. That correspondence runs to its own timetable, measured in weeks, and it is nobody's priority but yours. So we start it on day one rather than when the calculations are finished. It is the commonest reason an otherwise complete submission sits waiting.

Building control and planning do not talk to each other

Approved Document H sets the building control position on drainage; the condition on your decision notice sets the planning one. Different people, different tests, and satisfying one leaves the other exactly where it was. The right to connect to a public sewer under section 106 of the Water Industry Act 1991 is a third thing again, confirmed in Barratt Homes as not depending on the undertaker's approval of the point of connection. None of it discharges a planning condition. We have written separately on whether building control and planning talk to each other, and the short answer has not changed.

Is this the right drainage document for you?

Plenty of people land here with a drainage problem that is not a condition. Unda produces all of the following, so if the label is wrong the work still gets done:

• "My permission has a drainage condition on it." This page. Post-permission work, scoped by the condition wording rather than by a standard template.
• "I am still at application stage and need to show how surface water will be managed." The discharge hierarchy, runoff rates, attenuation, water quality and exceedance flow routing, worked through for the site: surface water drainage strategy.
• "Where does the foul go?" Mains connection, off-mains treatment, pumping and water company pre-development enquiries: foul drainage strategy.
• "The council has asked for its SuDS proforma." There always has to be a strategy behind the form, so we complete the two together. Our article on SuDS proformas and when they are required covers which authorities use them.
• "I am not sure which document has been asked for." The drainage strategies hub covers thresholds, application stages and the many names councils use for the same deliverable.
• "I need a flood risk assessment as well." Often the case, and where both are required we normally write them as a single combined report: flood risk assessment for planning.

If none of those quite fits, call +44 (0) 1293 214444 or send us the exact wording the council used, and one of our experienced consultants will tell you what the application needs before any fee is involved.

How we work with you

The aim here is the same as it was at planning stage: the strongest defensible route through, without committing the scheme to something that cannot be built. What has changed is where the room to manoeuvre sits. The layout is fixed by now, so the flexibility is in the drainage design itself and in what the officer will accept, and both of those are conversations before they are documents.

• Read the condition properly, first. Every limb, against the drainage consultee's own standard, before any fee is quoted. It is the only way to price the work honestly and the only way to avoid a second submission.
• Agree the shortest defensible route with the officer. Where a condition is thin we ask what the officer wants to see rather than guess. Where it is prescriptive we answer it limb by limb, in the order it is written.
• Start the third-party correspondence on day one. Capacity confirmations and riparian agreements run to their own timetable, and it is not ours.
• Say what will not get past. Where an approach is likely to draw an objection we say so, and set out what the alternative costs in space, money or programme, so the decision is made with the full picture in view.
• Handle the response ourselves. If the consultee comes back with a query, we answer it rather than leaving you to translate it.

Where we prepared the planning-stage strategy the detail follows straight through. Where somebody else did, we pick it up, and that is a normal week here.

There is an example of the planning-stage work these conditions usually sit on top of on our surface water drainage strategy project page, and where a condition has already cost an application time, our note on applications invalidated over flood risk and drainage covers how those delays usually start.

Software and modelling

We model in Causeway Flow. Some councils and drainage consultees still ask for MicroDrainage output by name, and where a condition or a consultee does that, we settle it at the outset rather than discovering it at review. What matters to the officer reading the pack is narrower than the software question: that the calculation output is legible, complete for every event the condition names, and traceable back to the drawing it belongs to. For quick sense-checks before any of that, the drainage calculator suite runs to around twenty free tools, and our ground conditions and soakaway checker reports the underlying geology for any English postcode.

Why developers and agents bring conditions to us

• 5,000+ assessments since 2014. Residential, commercial and strategic sites across England and Wales, for developers, agents, architects and self-builders.
• Chartered, CIWEM-qualified consultants. Unda is a CIWEM Business Partner and the team includes Chartered Members (MCIWEM C.WEM), with every submission signed off by a senior consultant.
• Daily contact with drainage consultees. We work to Lead Local Flood Authority standards constantly, which is how we know what a given team will accept before anything is submitted.
• Flow exceedance routes on every layout. One of the two items authorities most often find missing; it is standard on the drainage layouts we produce.
• Conditions we did not write. Picking up somebody else's strategy is ordinary work rather than an exception, and we quote on what is left instead of starting again by default.
• Local requirements, checked per site. Our local planning authority pages set out where individual councils stand on drainage, validation and SuDS, and our note on how local planning authorities handle flood risk and SuDS explains the relationship with the drainage consultee.

Frequently asked questions

Speak to our drainage team

A condition on a decision notice, a request for further information, a consultee holding the job up: whatever has brought you here, the quickest way forward is a short conversation about the wording. Our experienced consultants will tell you what the condition requires, what evidence the council is likely to want and what it will cost, before you commit to anything.

Call +44 (0) 1293 214444 or email enquiries@unda.co.uk and one of our experienced consultants will come back to you the same working day.