Chlorophyll-a vs phycocyanin: what each pigment tells you about a bloom

If you've sat through a watershed committee meeting where someone asks why the utility doesn't just test for chlorophyll-a instead of phycocyanin, the two pigments measure different things: chlorophyll-a tracks total algal biomass across every photosynthetic group in the reservoir, and phycocyanin tracks the pigment specific to cyanobacteria. Neither one alone tells the committee what it actually wants to know before a bloom call gets made.
Chlorophyll-a: the general algae signal
Chlorophyll-a is the pigment every photosynthetic organism in your reservoir carries, from diatoms to green algae to cyanobacteria. It's been the standard trophic-state indicator for decades because labs know how to measure it, state programs have decades of baseline data built around it, and it correlates reasonably well with total algal biomass.
The catch for a cyanobacteria program specifically: chlorophyll-a can't tell you which organisms are driving that biomass number. A reservoir can read high on chlorophyll-a during a dense diatom bloom that poses zero toxin risk, or read moderate during a smaller but toxin-producing cyanobacteria bloom that chlorophyll-a alone would underweight. If your operations team is trying to decide whether to shift intake depth or hold a public notice, "total algae went up" isn't the number that drives that call.
Phycocyanin: the cyanobacteria-specific marker
Phycocyanin is a phycobiliprotein, part of the light-harvesting apparatus specific to cyanobacteria, with limited crossover in a few other groups. That specificity is why phycocyanin monitoring has become the go-to add-on for utilities that need to flag the organism group that produces microcystin, cylindrospermopsin, and the other toxins on your watch list.
The tradeoff: phycocyanin readings are noisier. Concentration per cell varies with light adaptation, nutrient status, and even time of day, so a probe reading taken at 7am and one taken at 2pm on the same bloom can diverge more than most operators expect. It's a better identifier of "cyanobacteria are present" than a precise biomass count, and most programs that rely on it pair it with microscopy or qPCR before making a treatment-level decision.
What this means for a sampling program
Most reservoir monitoring plans that take cyanobacteria seriously run both: chlorophyll-a as the long-term trophic baseline, phycocyanin as the trigger that tells you when to pull a sample for taxonomic ID or toxin analysis. Neither pigment, on its own, gives you the lead time to reposition an intake or draft a notice before a bloom patch has already drifted over the raw water line. That lead time depends on catching the bloom forming, not waiting for a grab sample result to come back from the lab days after the water's already moved.
That's the gap satellite-based spectral monitoring is built to close. A daily-in-season pass over the reservoir reads the water's spectral signature and flags where bloom-like signal is forming, before anyone's out in a boat with a sample bottle. It doesn't replace the lab work that distinguishes phycocyanin from chlorophyll-a at the cellular level. It gives your team an earlier flag on where to point that lab work, and on how fast the extent is changing week to week. If your current workflow is "wait for the weekly grab sample, then react," a daily read on bloom extent across the whole reservoir is the piece that's missing between sampling events.
A practical takeaway
If you're choosing one pigment indicator to build a program around, chlorophyll-a reservoir sampling gives you the long-term trend and the cheaper, more established lab method. Phycocyanin monitoring gives you the cyanobacteria-specific flag that matters for toxin risk. Running both, alongside something that tells you where on the reservoir to look between sampling runs, is how most utilities end up covering the gap either pigment leaves on its own.
None of this changes what the state lab tells you about toxin concentration on a given day. It changes how much warning you get before that sample needs to be pulled. If bloom formation timing is the piece your current program is missing, that's the specific gap Algal Bloom Warning is built to flag.