Planting specification for swales and wetland margins

A swale planting specification fails when it treats the whole feature as one habitat. A swale base is inundated for hours a few times a year and bone dry for the rest of it. A wetland margin is saturated most of the time. Those are different growing conditions two metres apart, and a single amenity grass mix sprayed across both will be patchy in the base, eroded on the slopes and dead in the margin by the second summer. Specify by hydrological zone, then set the maintenance regime that keeps each zone doing its job.

What the planting has to achieve

Four things, and they pull in slightly different directions.

Slowing flow, by increasing surface roughness so water takes longer to travel the length of the swale. Trapping and holding sediment, so that solids drop out before the water reaches the next component. Holding the soil together, particularly on side slopes during the establishment period when bare ground erodes in the first heavy rain. And taking up nutrients and metals through root activity, which is most of the water quality benefit a vegetated component delivers.

Amenity and biodiversity sit alongside those, and on most schemes they are what the landscape architect is actually asked about. The Drainage Strategy and the landscape drawings need to describe the same feature, which sounds obvious and is routinely not the case.

Matching species to the wet and dry cycle

Set out the zones on the drawing first, then specify into them.

The swale base sees short inundation and long dry periods, often with free-draining subsoil beneath. Species have to tolerate both. Tufted hair-grass, creeping bent, meadow foxtail and a wildflower component including yarrow, self-heal and bird's-foot trefoil handle that swing reasonably well.

The side slopes are effectively dry grassland. A standard species-rich meadow mix works, with drought tolerance mattering more than wet tolerance.

A wetland margin or the permanently wet zone of a basin is a different specification again. Soft rush, hard rush, yellow flag iris, purple loosestrife, water mint, meadowsweet and the larger sedges are the usual palette. Common reed delivers treatment performance but spreads, so specify it only where the maintenance regime will control it and the client understands what that means.

Substrate matters as much as species. Wildflower establishment needs low nutrient soil, so specifying good quality topsoil across a swale produces a dense sward of coarse grasses and very little else. On many schemes the right answer is subsoil with a thin topsoil dressing, or no topsoil at all.

Species to keep out

Some exclusions are legal rather than horticultural. Planting or otherwise causing to grow in the wild certain non-native species is an offence under the Wildlife and Countryside Act 1981, and several of them are exactly the plants that colonise wet features.

New Zealand pigmyweed, floating pennywort, parrot's feather and Himalayan balsam all belong on an exclusion list in the specification, alongside a requirement that plant stock is sourced from a supplier able to certify it is free of them. Contaminated plug stock is a recognised route for these species onto a site.

Also avoid heavy shade over the treatment zone. Trees along a swale look attractive on a visual and reduce the vegetation performing the treatment, and leaf litter adds an annual maintenance burden nobody costed.

Establishment and the first growing season

Establishment is where these features are won or lost, and the programme rarely helps.

Seed is the least costly route and the slowest to bind the surface. Turf establishes quickly and suits a swale base likely to receive flow before the vegetation is up. Plug plants at a specified density are the normal approach for marginal species, and pre-grown coir rolls or planted mats give immediate cover at the water's edge where erosion risk is highest.

Three things to write into the specification.

1. A sowing or planting window, spring or early autumn, and a requirement that the contractor does not plant outside it without agreement.
2. Biodegradable erosion control matting on slopes and in the base until the sward has knitted.
3. Watering through the first growing season, with a stated trigger rather than a vague obligation.

Also state that the drainage feature may need to be protected from construction traffic and silt until handover, because a swale used as a haul route during the build is compacted, and compacted subsoil does not infiltrate.

Mowing regimes and machinery access

The maintenance regime dictates the geometry as much as the planting does.

Side slopes intended to be mown by a ride-on machine need to be no steeper than around one in three, and gentler is better. Steeper slopes have to be strimmed by hand, which costs more and gets skipped. Provide a maintenance access point with a suitable surface, and show it on the drawing.

Regimes differ by zone and should be written out year by year.

• Amenity grass on side slopes: regular cutting through the growing season, arisings collected where a wildflower component is intended.
• Meadow areas: one or two cuts a year, with arisings removed so nutrients do not build up.
• Marginal planting: cut back on a rotation rather than all at once, leaving standing vegetation for overwintering invertebrates.
• Inlets, outlets and control structures: inspected after storm events and cleared of debris.

Name the responsible party. On most schemes that is a management company, and the maintenance schedule should be an appendix to the transfer documents rather than a page in a report that nobody reads after discharge of conditions.

Silt and the replanting nobody budgets for

Sediment kills vegetated systems slowly. It smothers the base, raises the level, reduces storage and eventually converts a functioning swale into a slightly damp lawn.

Design a pre-treatment element at every inlet, whether a forebay, a filter strip or a stone-filled trench, so that silt drops out where a machine can reach it. Then write silt removal into the maintenance schedule with an inspection frequency and a trigger depth.

Assume replanting will be needed. A realistic specification includes a defects period with a replacement obligation, and a note that marginal planting in a heavily loaded feature may need partial replacement every few years. Saying so in the submission is better than discovering it at year four.

Where the swale discharges to an ordinary watercourse, remember that the outfall structure is a separate consent, dealt with in the note on land drainage consent for works to an ordinary watercourse.

Writing the specification for the submission

A planning submission does not need a full landscape specification, but it needs enough for the drainage officer and the landscape officer to see that the feature will work.

Include a planting plan at a stated scale showing the hydrological zones. A species schedule per zone, with percentages for seed mixes and densities in plants per square metre for plugs. The substrate specification, including topsoil depth or its deliberate absence. The establishment period and the watering commitment. A maintenance schedule covering years one to five and the regime thereafter. And a named party responsible for delivering it.

Where biodiversity net gain units are being claimed from the feature, the habitat type recorded in the metric has to match what the planting plan will actually produce. A Biodiversity Net Gain Assessment claiming a species-rich habitat from a mix that will become coarse grass within three years is a condition discharge problem waiting to happen, and the metric must be completed by a competent person.

Keep the planting consistent with the wider Landscape Strategy rather than treating the drainage features as a separate drawing by a separate consultant.

Enter your postcode on PlanScope to see which drainage and landscape documents a site is likely to need.

This is general guidance, not legal advice; check the position with your lead local flood authority or a qualified professional before relying on it. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.