Coastal flood coverage tends to blur two drivers that a municipal operator has to keep apart. Rain fills a drainage network from above, while a high tide pushes against it from below. The Guardian's aerial video report on California flooding, headlined with the phrase "record-breaking tides", describes coastal communities preparing for days of flooding as water levels began rising. The video is a news item, not a utility record, but it raises a practical question: which assets in your system feel the tide before they feel the rain?
Why a tide loads the network differently
A gravity outfall discharges only when the water outside it sits lower than the outlet. When the receiving water rises to or above the pipe invert, flap gates close and storm flow has nowhere to go. The network then backs up from the outfall toward upstream inlets, and the pump stations that normally lift water out of low areas must run against a higher head. Pumps may run longer, wet wells may fill faster, and the margin for a separate rain event shrinks.
Groundwater can also rise during extended high water, entering sewers through cracked joints and manhole walls. That added flow shows up at the treatment plant as a wet-weather signal that can look like inflow from rain, even when no rain fell nearby. Operators who read only the plant influent record may misattribute the cause.
Keep predicted and observed levels separate
Tide predictions are calculated from astronomical constituents and describe the expected level at a station under normal conditions. Observed levels include the effects of wind, barometric pressure, and surge, which can push water above or below the forecast. Media reports that use the word record usually refer to a gauge reading or a forecast peak at a named station. Neither is necessarily the water surface elevation inside your outfall structure, and the difference can matter.
Your log should carry separate columns for predicted stage, observed stage at the gauge you use, local water level at the outfall if you measure it, and rainfall at your own gauge. Mark which entries are forecasts so that no one later treats a projection as a measurement.
Check the assets that fail first
Start with the tide-gated outfalls. Confirm that the flap gates seat fully, that hinges and seals move freely, and that debris cannot hold a gate partly open. Test the backflow preventers on critical service connections in low-lying areas. Review pump station run-time records from the last high-water event, check the standby power transfer, and confirm that high-level alarms reach an operator who can act on them outside business hours.
Walk the manhole covers and vents in the low sections, since they are the points where backed-up water tends to surface first. At the plant, confirm that influent flow monitoring is working, because an infiltration signature is only useful if the meter is trustworthy.
Accept the tradeoffs
Closing gates protects the shore side of an outfall but can trap runoff inland, raising levels in neighborhoods that drain through that point. Running pumps through a high tide keeps the network moving but draws more power and wears equipment faster, and it may still fall short if inflow exceeds rated capacity. Neither choice is universally right. The answer depends on the hydraulics of your system, the elevation of your critical structures, and the duration of the high water, which a forecast headline rarely states.
A news report about a record tide does not tell you how long your gates will stay shut or how many hours your pumps will need to run. Those answers come from your own system's records.
Write the tide triggers before the water rises
A workable operating plan names the gauge station it uses, the stage at which each action begins, and who acts. Typical actions include closing gates at a set level, staging pumps and standby generators, notifying crews and the on-call operator, increasing the frequency of wet well checks, and sampling discharge where outfall water mixes with receiving water.
Set thresholds from your own historical observations where you have them, and label them provisional where you do not. After each high-water period, compare the observed record against the triggers and revise them. The goal is a plan that can be checked after the event, not one that assumes the forecast was correct.