
Public reporting on lake cleanup usually starts with a spending total, and the total invites a plain expectation: money goes in, the water gets cleaner, and the trend follows. Circle of Blue's report on Lake Champlain, titled Vermont's nearly billion-dollar effort on Lake Champlain, puts that mismatch in the headline itself. The title frames the algae problem as one that persists, describing how the "Green Slime Keeps Coming Back" despite the work. For a utility, lab, or consultant reading a story like this, the useful question is not whether the spending was large. It is which pool of phosphorus the spending was aimed at.
Phosphorus that reaches a lake does not leave on a schedule. Part of it settles into bottom sediment, where it can bind to iron and other particles. Whether it stays bound depends on the chemistry at the boundary between sediment and water. When bottom water loses oxygen, which often happens in stratified water during warm months, some of that bound phosphorus can return to the water column. Limnologists call this internal loading. It means a lake can keep supplying nutrients to algae after inflows drop, and the sediment can hold older deposits for years. How long that lasts varies from lake to lake, and surface readings alone rarely reveal how large the reserve is.
This is why external controls and in-lake controls answer different questions. Watershed practices reduce what arrives from the land and the streams. They do not remove what has already settled on the bottom. Some in-lake approaches target the release directly, including oxygenation and sediment treatments, but each carries its own cost, physical footprint, and uncertainty about how long the effect holds. A program that funds only the first category can perform exactly as its reports describe while the bloom record responds to a different source. Neither result is a failure of the program. They are a mismatch between the program and the question being asked of it.
What to record before reading a trend
A trend line built only from surface samples mixes these pools together. Before anyone interprets a season of bloom data, the record should include bottom water dissolved oxygen measured by depth and by date, not only at the surface. It should include the timing of thermal stratification, since that timing sets when the bottom water is most likely to go anoxic. It should include sediment phosphorus measurements from cores, with sampling dates, locations, and the fraction of phosphorus being reported, because total values do not show how much is mobile. Inflow loads belong in a separate column from in-lake concentrations so that the two are not averaged into one number. Bloom observations need the same dates and sites as the chemistry, or they cannot be matched to the conditions that produced them.
Who owns the sediment line
Budget documents usually list projects, not pools. A line that reads as watershed work may or may not address internal release, and the document rarely says which. Ask which project targets bottom-water conditions, who collects the oxygen and core data, how often those measurements are taken, and what result would show that the sediment reserve is shrinking rather than simply being sampled. Those questions matter because the answers determine whether a bloom season can distinguish a funded watershed program from a stalled one.
The defensible reading of a multi-year lake program is that some outcomes appear in the inflow records, and others appear only in the bottom water. The two may move on different calendars, and the timing of any recovery remains uncertain. A record that says so, and that keeps each pool on its own line, will hold up better in a later review than a headline total that promises a clean result by a fixed date.