Facility Drainage Operation Questions Checklist

Walk the whole site and list every grating, channel, cover, outlet, trap, ditch and planted feature that appears to handle water.

The list is the foundation of everything else here, and on most facilities it has never once been written down.

Mark each feature with a number on a plan of the site, including ones at the edges and in areas nobody usually goes.

A list without positions cannot be given to somebody else, and the edges are where features are forgotten.

Ask at handover what each numbered feature is and what it does, and record the answers in the words you were given.

Several features look alike and behave in opposite ways, and only the documentation separates them.

What a drainage feature is and how it works is established by a qualified drainage professional from the design records rather than from its appearance.

Note which features do not look like drainage at all, such as a shallow planted hollow, a grassed channel or a gravel strip.

A feature that looks like landscape is maintained like landscape, which is how it stops working.

Note which surfaces are built to let water through and which shed it, and ask which features receive water from each area.

Knowing what arrives where explains most of what an operator will later observe.

Ask what exists below ground that has no visible feature at all, and how anybody would locate it in future.

A buried vessel or void with nothing at the surface is a facility's most invisible dependency.

Ask whether any part of the drainage is shared with, or crosses into, neighbouring land, and who else depends on it working.

A shared arrangement is one the facility cannot alter alone and cannot assume is being maintained by anybody in particular.

Walk to every numbered feature and note what you had to move, cross or unlock to get there, and how long it took.

A route that is awkward on a dry afternoon becomes impractical in the conditions that make it necessary.

Note who is able to open or lift each access point and with what, recording where the answer is nobody currently on site.

Access points get specified without anyone asking who would be holding them, which decides whether routine work happens.

Lifting covers exposes open drainage and gases. Who may do it and with what equipment is a matter for qualified professionals.

Ask what equipment each feature needs for clearing or emptying, and check whether that equipment can physically reach it.

Emptying something is a different access requirement from looking at it, and only one of the two is usually considered.

Note any feature that planting, storage, a container, parking or a later structure now sits over, against or in front of.

Features are lost to ordinary site development within a couple of years of opening.

Ask whether there is a flow control, where it sits and how it is reached, and record the answer even if it is not reachable.

It is the component most often built in behind something else and the one nobody can locate afterwards.

Write down the access limitations you found, not only the arrangements, since the limitations are what the operation has to work around.

Operations records list what exists and rarely list what is awkward, which is the part that governs whether anything is done.

Write a name or a role against every feature on the list, including the ones everybody assumes are somebody else's responsibility.

Features on the boundary between a grounds contractor and a caretaker are reliably cleared by neither.

Ask which features need a specialist contractor rather than site staff, and mark those separately on the list from the routine ones.

Separating arranged work from routine work early stops a specialist task quietly becoming somebody's Friday afternoon.

Ask what the design assumes about how often each feature is cleared, and record the answer rather than deciding it yourself.

Frequency is a design assumption on many of these features and cannot be guessed from looking at them.

Maintenance regimes for a drainage feature are set by the designer and supplier for that installation; nothing here sets an interval.

Ask what equipment, methods and materials are ruled out on each feature, and keep that note where the equipment is stored.

Restrictions filed in an inbox never reach the person holding the machine, which is where the damage is done.

Ask where material removed from each feature goes once it is out, and confirm locally what may be done with it.

Silt and debris removed from drainage is not always ordinary waste, and the question is better asked in advance.

What may be done with material removed from drainage, and where any washings may go, is confirmed with the local authority and the drainage undertaker.

Keep a simple dated log of what was cleared and when, including the visits on which nothing at all needed doing.

The visits where nothing was needed are the ones that establish what normal looks like on this site.

Note which features sit under or downwind of trees, when leaf fall happens, and how quickly a feature fills at that time of year.

A single autumn week frequently accounts for most of a year's clearing on some features.

Note which surfaces shed silt, grit or loose material into a feature, and whether anything can be done at the source instead.

Dealing with the source is usually cheaper than clearing the consequence, and nobody looks at it that way.

Note what users, vehicles and equipment carry onto the site, and where that material ends up once it has rained.

Material walked and driven in becomes the facility's drainage problem a few weeks later.

Note whether anything arrives from beyond the boundary, including from a road, a track, a field or a neighbouring property.

Water and material arriving is a different problem from water not leaving, and the two are constantly confused.

Responsibility for water crossing a boundary is a matter for the relevant authority and the parties involved rather than for the operator to settle.

Write out the year and mark when each feature needs most attention, so the work can be planned rather than reacted to.

Almost all of this is predictable, which is what makes an annual plan worth more than a reactive one.

Note any change on or around the site that alters what arrives, including new paving, a rerouted downpipe or work next door.

The load on a drainage system changes without anything buried being touched, and the operator is the one who notices.

Agree who is called when water appears somewhere it should not, and who is called if that person cannot be reached.

Unagreed, the call is made by whoever is present to whoever they happen to have a number for.

Agree that whoever finds it photographs and dates what they can see before anything is moved, cleared or mopped up.

The evidence is cleared away instinctively, and with it goes the only record of where water actually went.

Agree what site staff never attempt themselves, including lifting covers, rodding, clearing a blockage, opening a chamber or entering standing water.

The instinct to fix it is exactly the response that turns an operational problem into a safety one.

Open drainage, chambers and standing water present real hazards; clearing and investigation are work for qualified professionals with the right equipment.

Agree who is able to close part of the site, on what observation, and how users and bookings are told.

A decision nobody owns is taken by whoever arrives first, differently each time.

Ask at handover what an operator might notice that would suggest something has stopped working, and write that answer down verbatim.

This is a question only the designer can answer usefully, and it takes a minute while they are still engaged.

Keep a dated record of every occasion water has appeared where it should not, with photographs, however minor it seemed.

A pattern across several small events is the evidence a professional wants and the thing nobody keeps.

Bring the plan, the numbered list, the responsibilities and the clearing log together into one document rather than several separate ones.

Split records get partially handed on, and the half that goes missing is usually the plan.

Keep the answers given at handover with the operating record rather than in a project file that nobody ever opens again.

Project files are archived; operating records are used, and the answers need to be in the second one.

Record how each feature behaves while everything is still new, including how long each area takes to clear after rain.

Later change cannot be distinguished from how it always was unless somebody wrote down how it always was.

Make the drainage record part of what any new member of staff or committee is shown, rather than something they find.

The features that look like landscape are only protected by somebody being told about them.

Go through the list once a year and note what changed, what was cleared, and any feature that has become harder to reach.

Access degrades quietly as a site develops, and an annual walk is what catches it.

Keep the record with the facility rather than with the person who assembled it, and tell whoever comes next where it is.

The duty attaches to the site, so the record has to travel with the site rather than with a person.

Where no handover record exists at all, write that down as the starting position and ask what could be established without opening ground.

Most operators inherit nothing, and recording the absence is what turns it into a question somebody can eventually answer.