A drainage strategy report earns planning approval when it proves a site can manage surface water through the SuDS hierarchy, secures an agreed foul water route, and backs both with calculations, drawings and a maintenance plan the Lead Local Flood Authority (LLFA) can sign off. Miss any one of those pillars and the application either stalls at validation or picks up a raft of pre-commencement conditions. Get the LLFA and water company talking to you before submission, not after.
TL;DR:
- A drainage strategy must include a clear executive summary, site description, existing infrastructure review, and supporting calculations and drawings for quick approval.
- The surface water plan should prioritize infiltration first, only escalating to surface watercourses or sewers with justified reasons, and include details on water quality and landscape integration.
- The foul water strategy depends on existing sewer capacity, with off-site reinforcement, pumping, or phased connections, and should document water company communication and requisition status.
- Hydrological calculations need to present pre- and post-development runoff, attenuation volumes, climate change allowances, and modelling software used, with raw output files attached.
- Successful reports require documented consultations, clear ownership and maintenance arrangements, and detailed appendices to avoid delays or rejection.
Table of Contents
- What must a drainage strategy report contain?
- Surface water strategy and SuDS: hierarchy, options and design principles
- Foul water strategy: sewer capacity, requisition and phasing
- Hydrological calculations and modelling: attenuation, Qbar and climate change
- Consultation, consents and approvals: who has to sign off
- Drawings, surveys and appendices to include
- Operation, maintenance and adoption arrangements
- Recommended report template and example section titles
- Practical pitfalls and how Xponexus Engineering approaches these reports
- An engineer’s view on when to commission a full strategy
- How Xponexus Engineering supports planning-ready drainage submissions
- Sources
What must a drainage strategy report contain?
Planning officers and LLFA reviewers work through submissions against a fairly fixed mental checklist, so a report that mirrors that structure moves faster through validation. Most rejected or heavily-conditioned reports fail not because the engineering is wrong, but because a required section is thin, missing, or buried without a clear heading.
A submission-ready report typically includes:
- An executive summary stating the SuDS hierarchy position, proposed discharge point and headline attenuation volume in plain language a case officer can quote directly in their report.
- A site description covering topography, geology, existing watercourses, historic flooding and any known groundwater or contamination constraints.
- A review of existing drainage infrastructure, including any records obtained from the water company or LLFA on downstream capacity.
- A surface water strategy statement setting out the preferred SuDS route and why alternatives higher up the hierarchy were ruled out.
- A foul water strategy describing the proposed connection or requisition route.
- Supporting appendices: infiltration test data, hydraulic calculations, drawings and a maintenance and management plan.
Local validation lists vary slightly between authorities, and some LLFAs, such as Tower Hamlets, publish their own drainage strategy checklist. Check the specific authority’s list before drafting, because a report built purely to a generic template will still get bounced back for a missing local requirement.
Surface water strategy and SuDS: hierarchy, options and design principles
Every credible surface water strategy starts by working down the SuDS hierarchy set out in CIRIA’s C753 manual: infiltration first, then discharge to a surface watercourse, then a surface water sewer, and combined sewers only as a last resort with clear justification. The report needs to show this working, not just assert a conclusion. If infiltration is dismissed, say why: high groundwater table, contamination risk, or a percolation test result outside acceptable ranges.
Site constraints usually decide which SuDS features make the shortlist; practical options are well illustrated in Backyard Landscape Drainage Solutions That Actually Work. Free-draining ground with a deep water table and no contamination history points towards soakaways or infiltration basins. Clay-heavy or urban sites with limited land take tend to favour permeable paving, filter drains, or below-ground attenuation crates feeding a flow control device. Larger greenfield or mixed-use sites with room to spare can use swales and attenuation ponds, which double as landscape and biodiversity features rather than purely functional tanks.
Design decisions worth spelling out in the report:
- Whether infiltration testing supports full or partial infiltration, and what happens to the balance of flow if it doesn’t.
- How water quality treatment is achieved through the management train (vegetated swales, filter strips, permeable paving) rather than relying on a single end-of-line device.
- Whether the chosen SuDS features can realistically be adopted by the LLFA, water company or a management company, since unadoptable assets create long-term liability questions that reviewers will flag.
- How the drainage layout integrates with landscaping so ponds and swales read as amenity space, not leftover land.
Pro Tip: Sketch the SuDS management train on the same drawing as the landscape masterplan before finalising either. Reviewers spot bolted-on drainage immediately, and integrated schemes get through committee with far fewer objections.
Multi-functional SuDS also tend to score better with planning officers on design merit, not just technical compliance, because green infrastructure delivers biodiversity and amenity value that a buried attenuation tank never will.
Foul water strategy: sewer capacity, requisition and phasing
The foul water section gets far less attention than surface water in most draft reports, yet it causes just as many delays when the local sewer network is already stretched. Start by establishing whether the existing network downstream of the site has spare capacity, which usually means requesting sewer records and a capacity check from the statutory water company, such as Thames Water in much of the South East, rather than guessing from an old drawing.
Where capacity exists, a straightforward gravity connection to the public sewer is the default and the easiest to defend in a report. Where it doesn’t, the strategy needs to address one of three routes:
- Off-site network reinforcement, funded by the developer, where the water company confirms upgrade works would restore capacity.
- Pumped foul drainage, where gravity connection isn’t feasible due to levels, requiring a pumping station with agreed adoption arrangements and a clear power resilience statement.
- Phased connection, where later phases of a development are timed to coincide with planned network upgrades, which needs explicit cross-referencing to the phasing plan elsewhere in the application.
On-site treatment, such as a package treatment plant discharging to a watercourse, should only appear in a report as a fallback where no connection is remotely viable, and it carries its own Environment Agency permitting burden that the report must flag rather than gloss over.
Requisition under the Water Industry Act can take several months once formally submitted, so the report should state the current status of that application, even if it’s still “pending”, rather than leaving the foul strategy looking unresolved. A report that says “connection to be agreed” without evidence of contact with the water company reads as unfinished to a case officer, and it usually is.
Hydrological calculations and modelling: attenuation, Qbar and climate change
Reviewers want to see the numbers, not just the narrative, and they want them presented in a way that lets them check the logic in minutes rather than reverse-engineering a spreadsheet. The calculation appendix should present:
- Pre-development runoff rates, calculated using the greenfield method to establish the Qbar baseline, alongside the 1-in-30 and 1-in-100 year equivalents.
- Post-development runoff rates for the same return periods, demonstrating how far above greenfield the site would sit without attenuation.
- Proposed discharge (flow control) rate, ideally matching or bettering the Qbar figure, since demonstrating betterment against greenfield rates is often the decisive factor in LLFA acceptance rather than merely replicating the site’s existing discharge.
- Required attenuation volume, typically driven by the 1-in-100 year plus climate change event, with the 100-year 6-hour storm volume commonly requested by drainage boards.
- Climate change allowance applied, referencing current national guidance rather than a fixed historic percentage, since allowances are periodically revised and the NPPF expects local policy to reflect the latest position.
- Modelling software and assumptions, naming the package used (MicroDrainage and Causeway Flow are the two most widely accepted across UK LLFAs) and stating the design storm profile, urban creep allowance and any blockage factor applied to outfalls.
Attach the raw model output files, not just summary tables, because several drainage boards explicitly request MicroDrainage or Causeway Flow outputs as supporting evidence rather than accepting a narrative summary on trust. Include a sensitivity check showing what happens if infiltration rates are lower than tested, since a single percolation test result presented without a safety margin is one of the more common reasons LLFAs ask for resubmission.
Consultation, consents and approvals: who has to sign off
Planning permission and drainage consent are two separate legal processes, and conflating them in a report is a recurring source of confusion. Planning permission covers whether the development itself is acceptable in principle; Land Drainage Consent is a distinct statutory approval required for any works affecting a watercourse, and it sits with the relevant drainage board or the Environment Agency, not the local planning authority.
Where a site sits within 9 metres of a board-maintained watercourse, most boards apply a byelaw buffer requiring separate consent for any structure, culvert or discharge within that zone, regardless of what planning permission allows. This catches out more schemes than any other single drainage issue, usually because the byelaw distance was checked against the wrong watercourse or ignored altogether at concept stage.
The report should evidence consultation clearly rather than simply asserting it happened. LLFAs and drainage boards typically want to see:
- Dated correspondence or meeting minutes confirming the agreed discharge point and rate.
- Written confirmation from the water company on sewer capacity or requisition status.
- Any pre-application advice received, quoted or appended rather than paraphrased.
- Evidence that LLFAs, as statutory consultees on major development, were engaged before submission rather than only at the formal consultation stage.
Pro Tip: Appendix your LLFA pre-application email chain in full, not summarised. A reviewer who sees the agreed discharge rate in the LLFA’s own words moves straight to sign-off; a reviewer who has to take your word for it asks for confirmation, and that alone can add weeks.
Water company requisition follows its own timetable, often running to several months from formal application to adoption agreement, so state where that process stands honestly rather than implying it’s already resolved.
Drawings, surveys and appendices to include
A drainage strategy report is only as credible as the evidence behind it, and reviewers routinely flag reports where the narrative claims are strong but the appendices are thin. A well-packaged submission includes:
- A topographical survey showing existing levels, watercourses and drainage runs across the whole site, not just the developable footprint.
- A drainage layout drawing showing pipe runs, manholes, invert levels, flow control chambers and the final discharge point.
- Infiltration test reports, including raw test data and the calculated infiltration coefficient, not just a headline pass or fail.
- Hydraulic model output files (MicroDrainage or Causeway Flow), matching the summary figures quoted in the report body.
- A management and maintenance plan setting out inspection frequency and ownership.
- Signed or dated LLFA and water company consultation records, as referenced in the consents section above.
One real-world example of this structure, drawn from a recent parcel drainage and SuDS strategy submission, shows how signed LLFA consultation minutes and Qbar-based discharge limits sit alongside attenuation pond design and landscape integration, giving a working template for what “complete” actually looks like in practice.
Name files consistently when uploading to a planning portal, using a clear prefix (Drainage_Layout, Drainage_Calcs, Drainage_Infiltration) so reviewers aren’t hunting through a folder of ambiguously titled PDFs. It sounds trivial until a case officer’s report cites the wrong drawing revision because two files had near-identical names.
Operation, maintenance and adoption arrangements
A drainage system without a credible long-term owner is a drainage system LLFAs will query, however well the calculations stack up. The maintenance plan needs to answer three practical questions: who inspects the system, how often, and who pays when something needs clearing or repairing.
A workable plan sets out:
- Inspection frequency for each SuDS component, typically quarterly for silt traps and flow controls, and after major storm events for attenuation basins.
- Access arrangements and any easements required over private land to reach below-ground infrastructure.
- Clear identification of maintenance responsibility for each asset, whether that’s the LLFA, the water company, a management company, or individual plot owners.
Adoption routes vary by asset type. Conventional pipework discharging to a public sewer usually follows the water company’s standard adoption agreement (Section 104 in England and Wales). Above-ground SuDS features such as ponds and swales are less consistently adopted, and many LLFAs still expect a private management company to hold long-term responsibility, funded through a service charge or a commuted sum paid at handover.
Whichever route applies, the report should state it plainly rather than leaving it open. “To be confirmed” on a maintenance and adoption question is one of the most common triggers for a holding objection, because it signals the developer hasn’t yet resolved who’s liable once the site is occupied.
Recommended report template and example section titles
A logically ordered report reads faster and gets fewer queries, because the reviewer can find the answer to their question without hunting across three appendices. A structure that works consistently across UK planning submissions runs roughly as follows:
- Executive summary – headline SuDS hierarchy position, discharge point and attenuation volume in two or three sentences.
- Site description – location, topography, geology, existing watercourses and any flood history.
- Policy context – relevant national guidance (NPPF) and local LLFA policy references.
- Existing drainage arrangements – current site drainage, downstream capacity and any known constraints.
- Surface water strategy – the SuDS hierarchy statement and justification, with the proposed feature mix.
- Foul water strategy – proposed connection, requisition status, or pumping arrangement.
- Hydraulic calculations summary – headline figures, with full workings in the calculations appendix.
- Consultation record – summarised LLFA and water company engagement, with full correspondence appended.
- Maintenance and adoption plan – ownership, inspection regime and adoption route.
- Appendices – topographical survey, infiltration test data, drainage layout, model output files and consultation minutes.
Place the SuDS hierarchy statement and any agreed LLFA discharge rate early in the surface water section, since that’s the first thing most reviewers look for and burying it in an appendix only invites a query that a clearer structure would have avoided.
Practical pitfalls and how Xponexus Engineering approaches these reports
The most common reason a drainage strategy report bounces back isn’t bad engineering. It’s a report that asserts conclusions the appendices don’t fully support, or one that treats LLFA consultation as a formality rather than evidence to be documented.
Reports that replicate existing discharge rates without demonstrating betterment against greenfield Qbar figures routinely draw LLFA objections, even when the underlying calculations are technically sound. The failure is almost always presentation and evidencing, not the maths itself.
Pro Tip: Draft the maintenance plan alongside the calculations, not after. LLFAs increasingly read the two together, and a strong technical case undermined by a vague ownership statement still gets held up.
Specialist embedded engineering capacity can produce calculation packages, drawings and BIM coordination that sit behind reports like this. When engineers integrate directly into a client’s existing workflow rather than working at arm’s length, revisions during LLFA consultation get turned around fast, which matters when a discharge rate needs recalculating overnight ahead of a committee date.
An engineer’s view on when to commission a full strategy
I have seen enough drainage submissions to know that the workflow behind a good one is unglamorous: agree the discharge point with the LLFA early, model it properly, and document every conversation. A full drainage strategy report earns its cost on anything beyond a handful of units or a site with any flood or infiltration uncertainty; an outline drainage statement suffices for smaller, low-risk applications where detailed design can follow at the reserved matters stage. Outsourced embedded engineering support exists precisely to keep that workflow moving without adding permanent headcount to a consultancy’s books.
— Mohammed
How Xponexus Engineering supports planning-ready drainage submissions
Specialist embedded engineering support can be an alternative to hiring another permanent drainage engineer when a consultancy needs a review-ready drainage strategy report on a deadline.
Offerings can cover the outputs this article has walked through: hydraulic calculations, drainage layout drawings, CAD/BIM coordination and appendix packages structured to LLFA and water company expectations. Projects may kick off quickly after engagement, with the client supplying necessary starting information. Outputs are produced to UK standards and Eurocodes, ready for a reviewing engineer to check and stamp rather than rebuild.
If a drainage strategy report is sitting on the critical path for a submission deadline, the services page sets out how an embedded engineer can be brought into the project this week.
Sources
For anything in this report beyond the basics, go to the primary documents. CIRIA’s SuDS Manual C753 sets the design hierarchy every LLFA measures against. The NPPF and Gov frame national policy expectations, while individual LLFA validation lists, such as Tower Hamlets’, set out local submission requirements that vary by authority.
Leave a Reply