Blog·
Field notes: the week the beach narrowed and nobody wanted to say why

The first time I noticed it, I almost didn't. Q2 walkdown had the beach at 38 meters off the spigot line on the north cell, down from 44 in Q1. Six meters. The report that quarter blamed it on the deposition rotation, we'd shifted more tonnage to the east cell for three weeks to keep the south spigots from icing over, and that was a fine explanation. Rotations do that. Beach width breathes with the schedule.
Q3 came in at 33. Another report, another reason: a wet spring, more runoff reaching the pond than modeled, pond encroaching a little further up the beach than usual. Also fine. Also true, probably. Nobody in that room was lying.
Q4 was 29 meters. And this time the explanation in the report was tonnage, we'd run above plan for two months to catch up on a stripping delay upstream, more slurry out, more beach consumed per rotation. Still plausible. Still, on its own, nothing anyone would flag to the engineer of record.
Here's what nobody said in any of the three reports, because nobody was looking at all three at once: the beach had lost fifteen meters in nine months. Each quarter's excuse held up when you read it alone, because each walkdown sits in its own little box, disconnected from the one before it. The person writing the Q3 report hadn't read the Q2 one closely enough to ask whether this was now a trend instead of a season. The person writing Q4 was three sites deep into a busy travel month and took the operator's word on the tonnage story because it matched the number on the page.
The walkdown format is the real issue here, not any one engineer's judgment call. A quarterly inspection answers "is this facility okay right now," and it answers that question well. Answering "has this indicator been sliding for three straight cycles under three different cover stories" takes a different kind of check: someone, or something, holding last quarter's number next to this quarter's number next to the quarter before that, every time, without getting talked out of it by a plausible local explanation. A rotation shift is a fine reason for one narrow reading. It stops being a fine reason the third time in a row.
What finally caught it was a maintenance tech who'd been on site long enough to remember the beach used to run past the old access ramp marker, and now it didn't, not even at low pond. That's institutional memory doing a job the inspection cadence wasn't built to do. Most sites run on turnover, consultants rotating through, and reports that each stand alone, so that kind of memory rarely sticks around long enough to catch the slide before it's three quarters deep.
A beach narrows because the deposition plan, the pond level, and the tonnage all shift a little at once, and the shoreline is just where those three things settle out. That's exactly why it's so easy to explain away one reading at a time and so hard to catch the slide until the freeboard margin you were counting on has quietly halved. A weekly read against your own baseline catches that kind of drift between the walkdowns that actually get written up, instead of waiting for someone with a long memory to notice the ramp marker's gone.
If your beach has been "explained" three quarters running, it might be worth a weekly look instead of another plausible reason.