Surface Water Destination Enquiry Preparation Checklist

Write down that a surface water arrangement is worked out from its discharge point backwards, so the destination has to be settled first.

What the receiving point will accept is the limit, and everything upstream of it follows from that rather than the other way round.

Note that the destination is not something to establish once the layout is fixed, because it is one of the things that fixes the layout.

Levels have to be able to reach the discharge point, which constrains where things can go far more than most owners expect.

Record that the answer changes what the surfaces can be, whether storage is needed, and whether any feature would be lined or open.

The same visible feature does entirely different things depending on this answer, which is why it cannot be deferred.

Consider making these enquiries before you appoint anybody, or ask at appointment whose job it is to make them.

Whether the designer or the owner makes the enquiries is a reasonable thing to settle at the start rather than assume.

Write down plainly what you are proposing that would change how water leaves the site, including added roof area or hard surfacing.

The enquiry is about a change, and describing the change accurately is what makes it answerable.

Note the ground as one candidate, and record that whether it will accept water is established by investigation rather than by assumption.

Giving water to the ground depends on what the ground does, which is a separate question from whether it is permitted.

How a given ground accepts water is established by investigation on that site by qualified professionals, and permission is a separate question.

Note any watercourse, ditch or channel on or near the site as a candidate, and record who appears to own or manage it.

A ditch running along a boundary is a destination with an owner, and that ownership is part of the enquiry.

Note any piped system belonging to somebody else as a candidate, and record what you know about what it currently takes.

Discharging into somebody else's system is a matter of permission before it is a matter of engineering.

Discharge into a system belonging to somebody else requires permission determined by the relevant authority or its owner; confirm locally.

Record where water from the site currently goes, as far as you can establish it, and how you established that.

The existing arrangement is the starting point for any enquiry, and it is frequently less well understood than owners assume.

Note that different parts of a site may drain to different places, and record what you believe applies to each part.

Treating a plot as having one destination is a common simplification that falls apart during the first enquiry.

Record whether foul and surface water on the site are separate, and whether that has been confirmed rather than assumed.

Keeping them apart is a question the receiving body will ask about, and the honest answer is often that nobody has checked.

Establish which bodies are responsible locally for each candidate destination, and write their roles down rather than their names alone.

Responsibilities are arranged differently in different places, and the role is what tells you which question to put where.

Identify who is responsible for any public drainage system serving the area, and what they require before answering an enquiry.

Their process is usually published, and following it is considerably faster than approaching them informally.

Identify the body responsible locally for surface water and flood risk matters, and find out what part they play in enquiries like yours.

Which body holds this role varies, and establishing it early avoids an enquiry going to the wrong place and waiting.

Where anything drains to or from a road, identify who is responsible for the highway and what applies at that boundary.

The road is a common destination and a common source, and it is somebody else's ground in both directions.

Anything draining to or from a highway is a matter for the highway authority and must be confirmed locally before it is relied on.

Where a watercourse or ditch is involved, establish who owns it and whether any neighbouring owner has an interest.

A private ditch has private obligations attached to it, and those sit with whoever owns the land it crosses.

Rights and obligations relating to watercourses and neighbouring land are legal matters and should be confirmed with a suitably qualified adviser.

Ask each body you approach whether anybody else would need to be consulted, and add them to your list rather than assuming.

Each body knows its neighbours, and asking the question is the quickest way to complete the list.

Start by establishing what already exists and what it connects to, since the first question every body asks is what happens now.

An enquiry that cannot describe the existing arrangement tends to come back asking for it rather than answering.

Approach first whichever body is most likely to hold the answer for your most probable destination, and record what they say.

One clear answer often removes several other enquiries, so the order matters for how long the whole exercise takes.

Where the destinations are genuinely alternatives, consider making the enquiries in parallel rather than waiting for each in turn.

Sequential enquiries to slow-moving bodies can take a long time, and parallel ones are often perfectly acceptable.

Ask each body how long a response usually takes, and note that alongside the enquiry so your planning reflects it.

Owners frequently discover the timescale after committing to a programme, and asking is a single extra sentence.

Make sure every enquiry describes the same proposal, so that answers can be compared rather than reflecting different descriptions.

Inconsistent descriptions produce inconsistent answers, and it is rarely obvious afterwards which description caused which reply.

Have the property address and a plan showing the boundary, and mark on it what you are proposing to change.

Almost every enquiry begins by needing to know exactly which piece of ground is being asked about.

Describe what you understand of the existing arrangement, including where covers are and what you have been told each serves.

Even an incomplete description is useful, provided you say which parts are established and which are believed.

Describe the change in terms of areas and surfaces rather than intentions, including roof area, hard surfacing and anything being removed.

A change described as a new patio is not answerable, whereas a change described as added surface and where it drains is.

Gather any drainage record, search result or developer information you hold, and send what is relevant rather than everything.

Relevant material speeds an enquiry and a folder of everything slows it, so a short covering description helps.

Include what you have observed about where water goes on the site during heavy rain, marked on the plan.

Observations from somebody who lives there are genuinely useful and are not available to anybody else.

State plainly what you are asking for, which is whether discharge to that destination is permitted and on what terms.

A clear question gets a clear answer, and a general enquiry about drainage frequently gets a general reply.

Ask for answers in writing, and where something is said on the telephone, confirm your understanding of it in writing afterwards.

A drainage scheme is designed against these answers, and a recollection of a conversation is not something a designer can use.

Record who answered, in what capacity, for which body and on what date, alongside the answer itself rather than separately.

An answer without a source cannot be relied on or followed up, and both may be needed later.

Record any condition attached to a permission, including anything said about rate, connection point, level, or what has to happen upstream of it.

Conditions are the part of the answer the design actually has to satisfy, and the part most easily summarised away.

Record what the answer appears to assume about your proposal, so a later change can be recognised as needing a fresh enquiry.

An answer is given about a described proposal, and changing the proposal quietly invalidates it.

Give the whole set of answers to whoever designs the arrangement, rather than summarising them, and keep a copy yourself.

Summaries lose conditions, and the conditions are what make a scheme buildable.

Keep the answers with the property record rather than only with the project files, because they explain why the arrangement is the shape it is.

A future owner faced with an unusual arrangement has no way of knowing what constrained it unless somebody kept the answers.

Treat a refusal as information that redirects the design rather than as the end of the project, and record exactly what was refused.

A refused destination narrows the field, which is a useful outcome and a great deal better than discovering it later.

Where an answer is partial or conditional, record precisely which part remains open and who would be the one to settle it.

Partial answers get remembered as permissions, and writing down the open part is what prevents that.

Where an enquiry goes unanswered, record that you made it, when, and to whom, and follow it up in writing.

A documented unanswered enquiry is a different position from never having asked, and the record is what establishes it.

Where two bodies give answers that appear to conflict, record both and put the conflict to whoever is designing the arrangement.

Resolving a conflict between bodies is not an owner task, but noticing and reporting it is.

Once the answers are in, write down plainly which destinations remain available to this site and which of them have been ruled out.

That short list is the single most useful thing you can hand to a designer at the start of their work.

Note that a change to the proposal may require the enquiries to be made again, and record the proposal the answers were given about.

Projects change, and an answer carried forward onto a different proposal is not an answer about that proposal.