Design Rainfall in South Africa: TR102, RLMA&SI, and How Estimates Are Made

Every design flood estimate in South Africa starts from the same question: how much rain should the design assume? Whether the method is the Rational Method, SCS-SA, or a full rainfall–runoff model, a “1:100-year flood” is built on a “1:100-year rainfall” — and that number has to come from somewhere. This explainer covers where South African design rainfall estimates come from, and what to check when you see one quoted.

What “design rainfall” means

Design rainfall is the rainfall depth (mm) expected at a location for a given duration (say 15 minutes, 1 hour, or 1 day) and return period (say 1:50 or 1:100 year — see return periods explained). Divide depth by duration and you get the average intensity (mm/h) used directly in peak-flow formulas. The full set of depth–duration–frequency values for a site is often presented as IDF (intensity–duration–frequency) curves.

Design rainfall is a statistical estimate extracted from long rainfall records — which is why the quality, length, and density of the underlying rain-gauge network sets the ceiling on how good any flood estimate can be.

TR102 — the long-serving reference

For decades, the standard reference was TR102 (Southern African Storm Rainfall, Adamson, 1981), published by the then Department of Environment Affairs. TR102 tabulated design rainfall depths for durations from 1 to 7 days across return periods up to 1:200 years, for hundreds of stations across the region, and generations of floodline and drainage reports cite it. Shorter-than-daily durations were typically derived from the daily values using published depth–duration relationships, since most of the historical gauge network recorded daily totals only.

TR102’s limitation is its vintage: it reflects the records available in the late 1970s. Records have lengthened by more than four decades since — and at many stations the additional data materially changes the estimates.

RLMA&SI — the modern regionalised approach

The current benchmark is the RLMA&SI approach — Regional L-Moment Algorithm with Scale Invariance — developed by Smithers and Schulze (published in the early 2000s through the Water Research Commission). Two ideas drive it:

• Regionalisation. Instead of fitting a statistical distribution to each rain gauge in isolation — noisy for rare events, since even an 80-year record contains few genuinely extreme storms — stations are grouped into statistically homogeneous clusters, and data is effectively pooled across each region using L-moment statistics. Rare-event estimates become far more stable.
• Scale invariance. Observed scaling relationships link short-duration behaviour to daily rainfall statistics, allowing defensible estimates for durations from 5 minutes to 7 days even where only daily gauges exist nearby.

The result is a consistent national coverage of design rainfall estimates for return periods from 1:2 to 1:200 years, available at fine spatial resolution across South Africa — the dataset behind most modern flood studies, accessed through dedicated software utilities and grids rather than a printed report.

How the estimate flows into a flood number

A typical chain for a small-catchment design flood looks like this:

1. Establish the site’s design rainfall (depth or intensity) for the required return period.
2. Determine the critical storm duration — for peak-flow methods, the catchment’s time of concentration.
3. Read the design intensity or depth for that duration.
4. Convert rainfall to runoff via the chosen method (Rational, SCS-SA, or a hydraulic model’s inflow hydrograph).

Notice that an error at step 1 scales everything after it. Two studies of the same site can differ simply because one used TR102-era values and the other current regionalised estimates — worth checking before concluding that the hydrology itself disagrees.

What to look for when reviewing a report

• Source stated. The report should name its design rainfall source (regionalised RLMA&SI estimates, TR102, or a drainage-manual IDF relationship) — not just present a rainfall table.
• Appropriate durations. Short-duration urban drainage design needs sub-hourly design rainfall; quoting only 1-day depths for a 20-minute catchment is a red flag.
• Consistency across methods. Where several flood estimation methods are compared, they should share the same underlying design rainfall, otherwise the comparison confounds method differences with input differences.
• Climate context. Standard design rainfall datasets describe the historical record. For long-lived infrastructure, it is increasingly common — and in some jurisdictions expected — to test sensitivity to rainfall intensification.

Design rainfall extraction, duration analysis, and method-consistent application are part of every hydrological study and stormwater management plan we produce — if you need a defensible design rainfall basis for a site, that is the natural starting point.