Which rainfall dataset the drainage model should use

The rainfall dataset drainage model question gets settled too late on most schemes. Design rainfall depth is the single input that decides attenuation volume, and successive national rainfall studies give materially different depths for the same grid reference. Change the dataset and the storage requirement moves. Change the hydraulic software and, for a simple attenuation system with a fixed outflow, almost nothing moves at all.

So the first page of a drainage calculation should say which dataset was used, at what grid reference, extracted on what date. Reviewers look for that before they look at anything else.

Why the rainfall input changes the answer more than the model

For a small site the hydraulics are not complicated. Water falls on an impermeable area, is routed to a storage volume, and leaves at a controlled rate. The volume needed is the difference between what arrives and what leaves, integrated over the critical duration.

That makes the calculation sensitive to two numbers: the design rainfall depth for the chosen return period and duration, and the permitted discharge rate. The second is usually fixed by the authority at the greenfield rate. The first comes from the dataset. Everything else, including the choice of modelling package, is detail by comparison.

Which is why a reviewer who disagrees with your storage volume will almost always be disagreeing about rainfall, catchment area or discharge rate, and not about routing.

The older rainfall study and the later flood estimation handbook datasets

Three generations of national rainfall data are still in circulation.

The oldest derives from the 1975 flood studies work, and models built on it typically use an index rainfall depth for a five-year return period over sixty minutes together with a ratio describing the local rainfall profile. You still meet it in older drainage calculations, in some adoption agreements and occasionally in the wording of an old planning condition.

The flood estimation handbook introduced a depth duration frequency model in the late 1990s, fitted to a much larger gauge network and extracted per catchment or per grid point rather than from a national map.

That model was revised in 2013 with a reworked fitting approach. For many locations the revision raised short-duration design depths, and in some areas it lowered longer-duration depths. The direction and the magnitude are location-specific, which is exactly why you cannot carry an assumption from one site to the next.

Treat the newest published depth duration frequency model as the default, extract it for the site grid reference rather than for a nearby town, and record the version. Our companion note on which rainfall dataset to cite in a drainage calculation covers the citation itself in more detail.

How the choice affects storage volumes

The mechanism is worth spelling out because it explains why small sites are the most exposed.

A tight permitted discharge rate means storage has to hold most of the volume that arrives. The critical duration, which is the storm length that produces the largest storage requirement, lengthens as the outflow falls. On a site with a very low greenfield rate the critical duration can run to many hours, and the dataset's treatment of long-duration depths then governs. On a site with a generous outflow the critical duration is short, and short-duration depths govern instead.

So a dataset revision that raises short-duration depths hits sites with a relatively free outfall, while one that changes long-duration depths hits sites with a restricted one. Two schemes on the same street can respond differently.

An illustrative sensitivity

Take a hypothetical 0.3 hectare site with 0.18 hectares impermeable and a restricted outflow. The figures below are illustrative only and exist to show the shape of the result.

The point is not the numbers. It is that both the volume and the critical duration can move, and a design fixed around the wrong critical duration will underperform in the storm that matters.

Agreeing the dataset with the authority in advance

Lead local flood authorities publish local guidance of varying detail. Some name the dataset, the return periods, the climate change epoch and the allowable discharge method. Some say very little and comment at consultation stage instead.

Where guidance exists, follow it and cite it. Where it does not, write and ask before the final model run. A one-line email confirmation that the authority is content with the dataset, the discharge rate and the return periods saves a round of consultation comments, and the confirmation belongs in the appendix of the Drainage Strategy.

Ask about three things together: the rainfall dataset, the allowable discharge rate and its basis, and the climate change allowance to apply. Those three settle most of the argument.

Documenting the version and the point of extraction

A drainage appendix that cannot be reproduced will be queried. Record, as a minimum, the grid reference used for extraction, the dataset name and model version, the date of extraction, the return periods and durations assessed, whether an areal reduction factor was applied and on what basis, the storm profiles used for summer and winter, the climate change allowance with its management catchment and epoch, and the permitted discharge rate with the calculation or correspondence behind it.

Extract at the site, not at the postcode centroid. On a small site the difference is usually trivial, in upland catchments it is not, and the habit of extracting at the right point removes an easy criticism.

Keep the raw extraction output. Not a screenshot pasted into a report, the output itself.

Sensitivity between datasets

Where the dataset choice is contested, or where a legacy model forces an older dataset, run both and present both. A short table comparing storage volume and critical duration across datasets does more to close an argument than a paragraph asserting that the difference is immaterial.

Sensitivity also helps on sites where the design is marginal. If the scheme works on the current dataset with a 10 per cent margin and fails on a plausible alternative, the design is too tight and the layout needs more space for storage. Better to know at planning stage than at the technical approval stage, when the layout is fixed and the only remaining option is a deeper tank.

What a reviewer checks first in the output

In rough order: the dataset and extraction details, the impermeable area against the layout drawing, the discharge rate against the greenfield calculation, the climate change allowance, the critical duration, and only then the storage volume and the half-drain time.

Two recurring failures. The impermeable area in the model does not match the area on the drawing, usually because the layout changed after the model was run. And the discharge rate in the model is not the rate in the greenfield calculation, usually because a minimum practical value was substituted without comment. Both are easy to catch and both get picked up.

Where surface water interacts with flood risk from rivers or the sea, the drainage work feeds the Flood Risk Assessment rather than standing apart from it, and the two documents should use the same climate change epoch. Our note on modelling a partially blocked flow control covers the related blockage scenarios a reviewer will expect to see.

This is general guidance rather than legal advice. Confirm the dataset, discharge rate and allowances with the lead local flood authority before relying on them, and treat the climate change allowances as subject to revision.

Browse the PlanScope report types to see which drainage and flood documents a site is likely to need. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.