Beach width vs. pond level: what's the difference?

Two people walk the same impoundment and come back with different numbers for "how much beach we've got." One's talking about the dry tailings surface between the water's edge and the crest. The other's talking about where the pond sits relative to the decant structure. Both are right. They're just answering different questions.

What each term actually measures

Tailings beach width is the horizontal distance of exposed, deposited tailings between the edge of the supernatant pond and the embankment crest (or the upstream toe of the dam, depending on your facility's geometry). It's a measure of how much buffer you've built between standing water and the structure holding it back. A wide beach dissipates wave energy before it reaches the dam face, gives seepage somewhere to go besides straight through the embankment, and generally means your spigotting sequence is keeping tailings away from the pond edge the way it's supposed to.

Supernatant pond level is the elevation of the standing liquid sitting on top of the deposited tailings, the clarified supernatant that hasn't decanted or evaporated yet. It's a water-balance number, tied directly to freeboard: how much vertical room is left before that level reaches the spillway, the crest, or wherever your design says it can't go. Pond level moves with rainfall, with how fast the decant system is pulling it off, and with how much process flow is coming in from the mill.

They sound related because they often move together. They're not the same signal.

Why they track together, and why they sometimes don't

In a well-run cycle, as you deposit more tailings and manage the pond actively, beach width holds steady or grows and pond level stays within its band. Push more water in than you're decanting out, and the pond rises, the shoreline moves toward the crest, and beach width shrinks, not because deposition changed but because the pond ate into it.

That's the usual coupling. But beach width can also shrink for reasons that have nothing to do with pond level: a spigot sequence that's been favoring one discharge point too long, a section of beach that's eroded or slumped, or deposition simply not keeping pace with the rate the impoundment's filling. In those cases pond level might look fine on paper while the beach is quietly narrowing underneath it, which is exactly the scenario that matters for upstream-raised facilities, where a thin beach puts the pond closer to the crest and closer to the compacted tailings the next raise sits on.

The reverse happens too: pond level can climb from a storm event or a decant outage while beach width barely moves, because the rise hasn't had time to push the shoreline. Tracking only one number leaves you with half the picture, and the spreadsheet will read fine right up until it doesn't.

Reading them on the same inspection

Most inspection forms list both because GISTM and most state dam-safety frameworks expect them as separate line items, not a combined "pond status" field. That's the right call. The failure modes they feed into are different: beach width speaks to wave run-up, seepage path length, and crest stability; pond level speaks to freeboard and overtopping risk. A facility can be fine on one and marginal on the other, and the combined read tells you if it's a water-management issue, a deposition issue, or both.

The quarterly walkdowns are the only point when both numbers actually get produced by hand, and a trend can build in the weeks between them without anyone on site to see it. A beach that's narrowed six meters over two months doesn't show up in a spreadsheet until someone's standing on it with a level, and by then the pond's already closer to the crest than your last report said.

Tailings Dam Monitor pulls both readings, beach width and pond level, off weekly imagery and flags them against your own facility's baseline, so a slow narrowing shows up in week three instead of at the next scheduled walkdown.

If you're tracking these two numbers by hand between inspections, it might be worth seeing what a weekly read looks like for your facility.