Structural engineering and detailing for water and wastewater assets.

Serviceability governs, not strength

A tank or a reservoir rarely fails because it is too weak. It fails because it lets water through where it should not, which makes a water and wastewater structure a different design problem from most of the structures built around it.

• Liquid-retaining structures are designed to serviceability limits — crack width, deflection and watertightness — that are usually tighter than the strength check the same section would need to pass.
• Tanks, channels, reservoirs, digesters and pumping stations each hold or convey liquid under a slightly different condition, and each sets its own durability and exposure requirement.
• Durability and exposure class are set by what the structure holds and what it sits in, not by a general assumption, since a digester and a clean-water tank age differently.
• Watertightness and joint detailing decide whether the structure performs from day one, since a joint is the part of a liquid-retaining structure most likely to leak.
• Asset lives are long, often measured in decades under a utility's own framework standards, so the detailing record has to outlast the people who produced it.

The assets, and what each one asks for

A treatment site is a collection of structures with different jobs, and the durability requirement moves with the job rather than with the shape of the tank.

• Water treatment and clean-water storage — filters, contact tanks, service reservoirs — hold water that has to stay clean, so the specification protects the contents as much as it protects the concrete.
• Sewage and wastewater treatment puts the same concrete in a far more aggressive place. Inlet works, primary and secondary tanks, aeration lanes and sludge structures see sulphate attack and abrasion that a clean-water structure never does.
• Industrial effluent structures vary by process. The chemistry is specific to the site, so the exposure class has to come from what the structure will actually hold rather than from a municipal default.
• Recycling and reuse structures add a second water quality to the same site, and with it a second set of tightness and durability requirements on structures that often stand side by side.
• Stormwater and overflow structures — attenuation tanks, storage shafts, screening chambers — spend most of their life empty and fill fast, which makes the empty condition rather than the full one the case that governs.

The packages a treatment asset needs

Water and wastewater structures are reinforced concrete first, with a smaller steel and access-structure scope layered around them.

• Rebar detailing for tanks, reservoirs, channels, digesters and pumping station structures, with reinforcement and cover detailed to the durability class the asset requires.
• Drafting and CAD production for the construction issue set and the joint and waterstop details a watertight structure depends on.
• BIM modelling and coordination across structure, process and mechanical and electrical, where pipework penetrations through a liquid-retaining wall are a recurring coordination point.
• Steel detailing for access platforms, walkways, handrails and covers, weir plates and launder supports, pipe and duct supports, and the access bridges that cross a tank — a smaller scope than the concrete, but the part the operator touches every day.

Standards for liquid-retaining structures

The structural basis follows the country of construction — BS EN Eurocodes with the UK National Annex, or EN 1992 with the relevant National Annex elsewhere in Europe — with EN 1992-3, the Eurocode part specifically covering liquid-retaining and containment structures, governing crack width limits, tightness class and additional detailing requirements beyond the base concrete code.

Tightness class is selected for each structure depending on what it holds and what leakage consequence is acceptable, and it sets the crack width limit the reinforcement is detailed to achieve. Utility clients frequently layer their own framework standard on top of the code, covering preferred joint types, waterstop specification and design life requirements specific to that operator.

Outside Europe the equivalent is ACI 350, the American code for environmental engineering concrete structures, with ACI 350.3 covering the hydrodynamic and sloshing effects a seismic region adds to a tank full of liquid; IS 3370 covers the same ground in India. Older UK assets were built to BS 8007 and BS 8110, and a refurbishment or extension has to be detailed with that original basis understood even where the new work follows the current code.

Where a structure also has a process or mechanical function, its structural design basis is agreed with the process engineering at intake, since pipework loads and penetrations are rarely fixed until the process design is.

Cover, joints and the checks that matter

The failure modes on a liquid-retaining structure are specific, and the checks are built around them.

• Crack width — reinforcement checked against the tightness class the structure is designed to, not just against a strength limit state.
• Cover — checked continuously against the exposure class for every element, since cover on a liquid-retaining structure protects against a more aggressive environment than most concrete sees.
• Joints and waterstops — every movement and construction joint checked for waterstop continuity, since a gap in a waterstop run is a leak path that is expensive to find after the structure is in service.
• Penetrations — pipework penetrations through liquid-retaining walls and slabs reconciled between the structural, process and mechanical models before they are cast in.
• Buoyancy — every below-ground structure checked empty against the highest credible groundwater, since the condition that floats a tank is the one where it has been drained for maintenance in wet ground, not the one where it is full. Whatever resists it — ballast, anchorage or dead weight — belongs in the design rather than in a decision taken on site.

The check record is issued with the package, and a senior engineer reviews and signs it before it goes out.

Building on a plant that is still running

Most water and wastewater work happens on a site that cannot stop treating what arrives at it, and that single fact shapes the package more than any structural decision inside it.

• Structures come out of service one at a time. A tank is isolated, drained, worked on and returned while its neighbours carry the flow, and that sequence is what the drawings have to support.
• Tie-ins are the difficult detail — new concrete cast against old, a penetration cut into a wall still retaining liquid on the far side, or a slab extension where the movement joint between old and new decides whether the finished structure leaks.
• Ageing concrete is understood before it is built on. Where the original record is missing or the structure has degraded, it is surveyed and assessed first, and repair or strengthening is detailed against what was found rather than what was drawn decades ago.
• Capacity is added in phases. A site meant to be extended leaves connection points, blanked penetrations and foundation provision for the next phase, and those are worth detailing deliberately rather than leaving the next scheme to cut them in.
• Access and lifting around live plant constrain what can physically be built, so the erection and pour sequence is checked against the space actually available, not the space on the site plan.

Delivering across a utility framework

Water and wastewater work is usually delivered as one structure inside a wider utility framework or capital programme, where consistency across sites matters as much as the quality of any one structure. Repetitive elements — standard tank types, repeated pumping station layouts — are AI-driven, so a structure produced under the framework's own standard can be repeated across sites without redetailing it from scratch, and a change to the framework standard is re-checked across every affected structure before reissue.

What does not change is accountability. BuildTwin is the delivery partner for the whole scope — one delivery lead, one register, one programme, one company answerable for what is on the drawing, structure by structure across the framework.