Trash screens, blockage scenarios and sensitivity tests
A culvert that performs perfectly in the design case can flood a site when the screen clogs. Blockage scenarios are where the real risk usually sits.
A hydraulic model that only runs the design event with a clear culvert tells you very little about the risk to a site. Screens collect debris, culverts silt and the most common cause of localised flooding in an urban catchment is a blocked inlet during a storm, not an exceedance of the channel capacity. So a flood risk assessment involving a culvert or a trash screen has to model blockage as a scenario in its own right, state the assumption used, and report the upstream levels it produces alongside the design case.
Consultees ask for this routinely and applicants are still surprised by it. The screen is usually the single most sensitive component in the model.
Why blockage must be modelled
Blockage changes the hydraulics rather than just the margin. A partially blocked screen behaves as an orifice with a reduced effective area, head builds upstream, the water surface rises, and flow may leave the channel at a point the design case never identified. The consequence is often a new flow route across the site or towards a neighbour.
Two further reasons make it unavoidable. Residual risk after mitigation has to be assessed and communicated, and a culvert maintained by a third party is outside the applicant's control, so the assessment cannot rely on it being clear. National flood risk guidance expects the assessment to consider the consequences of failure of flood management infrastructure, and a screen is exactly that.
The answer is rarely that the site is undevelopable. It is usually that finished floor levels, the layout, the exceedance route or the screen design need to change.
Standard blockage assumptions
There is no single national figure, and anyone quoting one as a rule should be asked for the source. What exists is a set of conventions that consultees recognise, and the sensible approach is to test a range and state what each produces.
| Scenario | Typical representation | Purpose |
|---|---|---|
| Clear culvert, design event | Full effective area | The design case |
| Partial blockage | A stated proportion of the opening obstructed | The realistic residual risk |
| Full blockage | Inlet treated as closed, all flow leaves the channel | The worst credible case for safety |
| Blockage plus climate change allowance | Partial blockage with the uplifted flow | Lifetime risk for the development |
| Debris raft against the screen face | Reduced area with raised approach head | Where upstream land use generates debris |
The proportion used for partial blockage should be justified by the screen type, the bar spacing, the catchment land use and the maintenance regime rather than taken from a precedent model. A screen below a wooded catchment with fine bar spacing and no maintenance access deserves a harsher assumption than a coarse screen on an urban channel inspected weekly.
Agree the assumption before the model is run. The approach to representing a restricted opening in the model is set out in modelling a partially blocked flow control, and the method you choose affects the result as much as the percentage does.
Screen design and maintenance access
Screen design is mitigation, and a good design reduces the blockage assumption you have to defend. The features that matter are a face inclined to allow debris to ride up rather than pin, bar spacing matched to the debris size rather than the smallest conceivable item, a self-cleaning or curved profile where the hydraulics allow, a bypass or overflow route so that total blockage does not mean total loss of capacity, and access that lets someone clear it safely in a storm.
That last one is the practical failure. A screen reachable only by wading into a channel in spate will not be cleared when it matters, and a consultee reading the maintenance plan will see that immediately. A hard standing, a safe working platform, a handrail and a vehicle route change the plan from aspiration to procedure.
Then name who maintains it, how often, after what trigger and with what record. An obligation requiring inspection before and after storm events, with a log available on request, is the version that survives a change of ownership.
Effect on upstream water levels
Report the effect quantitatively at defined locations rather than describing it. For each scenario, give the predicted peak water level at the screen, at the site boundary and at the nearest third-party receptor, with the difference from the design case.
The numbers drive the design decisions that follow. Finished floor levels set above the blocked-scenario level with a freeboard allowance, a layout that keeps habitable accommodation out of the area affected, an exceedance route that carries overtopping flow safely to a defined receiving area, and safe access and egress that works in the blocked scenario rather than only in the design event.
Where a blocked scenario raises levels on land outside the site, that is not merely a design input. It is a potential increase in flood risk elsewhere, and the assessment has to show that the development is not the cause or that the effect is mitigated. Where that overland flow then crosses falling ground, its behaviour is covered in managing run-off on a steeply sloping site.
Choosing sensitivity scenarios
Build a scenario matrix and keep it short enough to report properly. A workable set for a site with a culverted watercourse covers the design event clear, the design event with partial blockage, the design event with climate change and partial blockage, the extreme event clear, and a full blockage case for safety assessment.
And add scenarios only where they answer a question someone will ask. A model run that varies roughness by ten per cent across six variants fills pages without changing a decision, whereas a run that tests the blockage proportion against the rainfall dataset chosen does change decisions, and the choice of dataset matters in the way set out in which rainfall dataset to cite in a drainage calculation.
An illustrative example. A site beside a 900 millimetre culverted brook with a vertical bar screen at the inlet. The design event clear gives a peak level 400 millimetres below the lowest proposed threshold. At partial blockage the level rises to 150 millimetres below. At full blockage flow leaves the channel upstream and crosses the site on a route the design case never showed. The scheme is still consentable, with thresholds raised, the exceedance route formalised as a swale and the parking court used as the flow path, but only because the scenario was run before the layout was fixed.
Reporting results alongside the design case
Put the scenarios in one table with the assumption, the modelled peak level at each reporting point and the difference from the design case, then explain in the text what each result means for the layout. Keep the design case in the same table rather than in a separate chapter, because a reviewer comparing two chapters will assume the worse figure is being hidden.
The Flood Risk Assessment should state the model software and version, the boundary conditions, the structure representation, the blockage method and the sensitivity results, with the model files available on request. A Drainage Strategy covering the site's own surface water system is a different document and should cross-refer rather than repeat the fluvial modelling.
Agreeing assumptions with the consultee
Ask the lead local flood authority and, where a main river is involved, the Environment Agency what blockage assumptions they expect, before the modelling is commissioned. Put the question in writing with the screen type, the bar spacing, the catchment description and the proposed maintenance regime, and record the answer.
That conversation is worth a fortnight of modelling. An assessment built on an assumption the consultee rejects has to be rerun, and the rerun usually lands after the layout has been fixed by the architect. Where no response comes, model a range and say in the report that the assumption was offered for agreement and none was given.
This is general guidance, not legal advice. Hydraulic modelling should be carried out by a suitably qualified engineer, blockage conventions and climate change allowances are periodically updated, so check the current guidance and agree the assumptions with the relevant consultee.
PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.
Frequently asked questions
Why does a flood model need a blockage scenario?
Because a blocked screen or silted culvert behaves as a restricted opening, head builds upstream and flow can leave the channel on a route the design case never identified. Localised urban flooding is more often caused by a blocked inlet during a storm than by the channel exceeding its capacity, so residual risk has to be assessed.
What blockage percentage should be used?
There is no single national figure. The proportion should be justified by the screen type, bar spacing, the debris the catchment generates and the maintenance regime, and a range should be tested and reported. Ask the lead local flood authority or the Environment Agency what they expect before the modelling is commissioned.
Can good screen design reduce the blockage assumption?
Yes. An inclined face that lets debris ride up, bar spacing matched to the debris size, a self-cleaning profile, a bypass route so total blockage does not mean total loss of capacity, and safe access for clearing in a storm all support a less severe assumption, provided the maintenance regime is named and recorded.
What do blockage results change in the design?
Finished floor levels and freeboard, the position of habitable accommodation, the exceedance flow route and the safe access and egress strategy. Running the scenarios before the layout is fixed turns a difficult result into a design adjustment, whereas running them afterwards usually means redesigning after permission.
How should the scenarios be reported?
In a single table listing each scenario, the assumption applied, the predicted peak level at each reporting point and the difference from the design case, with the implications explained in the text. Keeping the design case in the same table matters, because separating them reads as though the worse result is being downplayed.
Sources and further reading
This article is general guidance about the planning system in England and, where stated, the rest of the UK. It is not legal or professional advice. Check your local planning authority’s validation requirements and take professional advice for your specific site.