
A 2026 report from Circle of Blue on Lake Champlain carries a headline that gets to the center of nutrient management: Vermont has spent nearly a billion dollars on cleanup, but the problem "keeps coming back." The report is useful for anyone who works with source water because it separates two things that planning documents often merge, the money spent on a watershed and the condition of the water that leaves it. Circle of Blue's Lake Champlain report is the source for the spending figure and the recurrence described here. This article does not add detail beyond that report. It explains the mechanisms that make the distinction matter.
Why a Lake Responds Slowly
Phosphorus is commonly the nutrient that limits algal growth in many temperate freshwater lakes, which is why reducing its entry is a central lever in many management plans. A lake is not a pipe, however. Phosphorus arrives from runoff in pulses that follow storms and snowmelt, settles into bottom sediments, and can return to the water column under some conditions, particularly when bottom waters lose oxygen. That return flow is often called internal loading. It means a watershed improvement may show up in the lake years later, or be partly masked by material already stored in the bed.
The practical consequence is a mismatch between clocks. A project that reduces an input can be recorded in a load estimate the year it is completed, while the lake responds on a different schedule that depends on residence time, mixing, and how much phosphorus the sediment is holding. Agricultural practices, stormwater retrofits, and wastewater upgrades each carry different costs, deliver their reductions on different timelines, and are verified in different ways. A single spending total adds them together and hides those differences.
What a Dollar Total Cannot Tell You
A budget answers one question: how much was committed. It does not answer whether loads fell, whether the fraction of loads reaching the lake fell, whether bloom frequency or extent changed, or whether the bloom signal is shifting in location or timing. Each of those is a separate measurement with its own uncertainty.
Bloom monitoring adds further complications. Results depend on where and when samples are collected. A shoreline observation during calm weather is not directly comparable to a sample drawn at a fixed intake during a windy week, and a change in station, method, or sampling frequency changes the record even if the water has not changed. Weather is a strong driver of bloom intensity, so one wet or dry season can make a program look better or worse than its underlying changes would justify. A bloom count is evidence produced by a sampling design, and its value depends on how well that design holds steady across years.
Checks Before You Cite a Trend
For utilities, laboratories, and engineers who rely on these reports, six questions help separate a trend from a tally.
Name the response variable. Load, concentration at a station, bloom extent, toxin detections, and advisory days each move on different timescales and answer different questions.
Check the sampling location and frequency. Compare like with like across years, and treat any change in station or method as a break in the record.
Separate the watershed effort from the lake outcome. Record the completion date and load estimate for each project, then look for a lag before expecting an in-lake response.
Ask whether internal loading is part of the mass balance. If sediment release is significant, a cut in external inputs may not produce the expected lake response for some time.
Keep weather and flow alongside the bloom data. Mark wet and dry years in the same table so that a favorable or unfavorable season is not read as a program result.
Log intake performance separately. An algal problem at a raw water intake is an operational question as well as a lake question. Taste, odor, filter loading, and disinfection byproduct precursors can change even when a bloom count is flat, and a count alone will not show it.
None of these checks requires a new study. They require agreement on what is being measured before the next report is written, and a record that stays consistent long enough to show change.
Reading the Recurrence
A problem that keeps coming back after heavy spending is not proof that the spending failed. It is a signal that the storage in the system, the lag between action and response, or the sampling design may not have been included in the calculation. Treat the recurrence as a prompt to ask what the lake is holding as well as what it is receiving. Plan the monitoring record before the next budget cycle, so that the next report can say what changed, by how much, and with how much confidence.