Concrete looks like the permanent answer. It is hard, it is monolithic, it does not move, and it reads as finished in a way loose stone or bagged armor does not. On the right duty it is genuinely the correct system and will outlast everything around it.
On the wrong duty it fails in a specific and well-understood way, and the failure is usually expensive because by the time it is visible the structure behind it is involved.
The undermining sequence
A rigid revetment holds its shape. The bed it sits on does not.
- Flow works at the edge of the slab — the toe, most often
- Bed material just outside the concrete is removed
- A void opens beneath the slab edge
- The slab is now spanning that void, carrying load it was not designed to span
- Water enters the void and enlarges it, working further underneath
- The slab cracks, or a section drops, or the whole panel rotates into the hole
The critical property is that steps 2 to 5 are invisible. The concrete surface looks perfect throughout. The first visible sign is usually step 6, at which point the void is large, the bed is well below design, and the repair is not a patch.
This is the same mechanism described in why scour protection fails, and rigidity is what makes a system vulnerable to it. A flexible system follows the bed down and stays in contact with it. A rigid one bridges and then fails.
The cost line that gets left out
Concrete generally needs a dry working area. Poured in place, it needs formwork and a cure. Precast panels need a prepared, graded bedding.
In water, that means dewatering: a coffer dam, diversion, or pumping arrangement, plus the permitting and schedule that come with it.
That temporary works package is frequently the largest single difference between a concrete proposal and a bagged armor proposal, and on some in-water jobs it rivals the cost of the permanent works. It also carries its own permitting path — diversion and dewatering are regulated activities in their own right, covered in permitting and agency approvals.
Rock bags are filled and placed in flowing water or fully submerged, so the project avoids that package entirely. When a comparison is run on the permanent works alone, the concrete option can look competitive while the delivered project is not.
Where concrete is the right answer
Being clear about this, because there are real duties where nothing else will do:
A trafficable surface. If vehicles, plant, or people need to drive or walk on it, concrete. Bagged armor is not a trafficable surface.
A precisely shaped hydraulic surface. A designed spillway profile, a stilling basin, an approach channel with a specified section. The geometry is the function.
A hard, defined line. Where the finished appearance and the exact position matter — an urban waterfront, a formal channel, an architectural setting.
High-abrasion, high-velocity duty at a structure. Spillway aprons and chutes take conditions that suit a hard monolithic surface.
Where the bed genuinely will not move. Founded on rock, or on a bed with no realistic degradation or scour potential, the rigidity liability does not arise. Concrete on competent rock is an excellent, extremely long-lived solution.
Where a permanent structural element is required, not armor. Retaining, load-bearing, or sealing duties are structural work.
Where the comparison goes the other way
- The bed is mobile, erodible, or already scoured
- The work has to happen wet, and dewatering is expensive or not permittable
- The geometry is irregular or fits around existing structures
- Long-term degradation is occurring in the channel, so the bed will keep lowering
- Phased or incremental work across budget years
- Local stone is available, and concrete would mean importing aggregate and cement
- Repair needs to be incremental over the asset’s life
The hybrid worth considering
The most common productive combination is concrete where its properties are needed and armor protecting the interface where it is vulnerable.
Specifically: armor at the toe of a concrete revetment. This directly removes the mechanism that ends most rigid installations. If you are designing new concrete slope protection in water, treating the toe as a separate design problem with a flexible system is a small addition that addresses the dominant failure mode.
The same applies to an existing concrete revetment showing early signs: cracking near the toe, a step at the bottom edge, settlement at one end. Armoring the toe before the void develops is a maintenance operation. After the slab has dropped, it is a reconstruction.
What to inspect on an existing concrete revetment
- The toe, at low water. A step down from the slab edge to the bed means the void is forming
- Cracks parallel to the toe, which indicate spanning
- Settlement or rotation of individual panels
- Open joints, which let flow behind the face
- The flanks, where the revetment ends against natural bank
- Behind the crest, for evidence of flow getting round the top
- Sound the slab if you suspect a void. A hollow response is the confirmation
Where to go next
- Rock bags vs articulated concrete blocks for the flexible concrete option
- Why scour protection fails for the undermining mechanism in full
- Rock bags vs gabions and riprap for the side-by-side
- Cost, procurement, and specification for what drives the installed cost
- Permitting for the dewatering approvals
Send the bed conditions, whether the site can be dewatered, and what the finished surface has to do through the quote form.