Net alkalinity vs net acidity: what decides active or passive treatment

A concrete drainage outlet emptying into a calm, reed-lined pond with wading birds in the shallows.

If you've pulled a discharge monitoring report and seen "net alkalinity" or "net acidity" listed next to a pH that looks fine, you already know the pH alone doesn't tell you much. A stream can sit at pH 6.5 and still be hauling enough dissolved iron and aluminum to drop to pH 3 the moment it hits open air and those metals hydrolyze. Net alkalinity is the number that catches that, and it's the number that usually decides whether a site gets a lime plant or a limestone channel.

What the calculation actually measures

Net alkalinity is alkalinity minus acidity, both expressed as mg/L CaCO3 equivalent:

Net alkalinity = total alkalinity − total acidity

The acidity half of that equation is where most of the confusion lives. A simple pH-based acidity reading misses the acid that hasn't been released yet, the acid that shows up later when Fe2+ oxidizes to Fe3+ and precipitates as ferric hydroxide. That's why labs run hot acidity (Standard Methods 2310B), boiling the sample with peroxide to force that oxidation before titrating. Skip that step on a water with high dissolved iron and you'll get a net alkalinity number that looks healthier than the water actually is once it's had a chance to sit in a pond and breathe.

A positive net alkalinity means the water has enough buffering capacity to neutralize its own metal load as those metals oxidize and precipitate. A negative number, net acidic, means it doesn't, and something has to add buffering capacity from outside before the water can meet discharge limits downstream.

Where the active/passive line gets drawn

Net alkalinity is the first filter, not the only one. A net-alkaline discharge with low flow and modest iron and manganese loading is a reasonable candidate for passive treatment: an aerobic wetland, an anoxic limestone drain, a successive alkalinity-producing system, something that leans on gravity, retention time, and biology instead of a dosing pump. A net-acidic discharge, especially one carrying aluminum, usually isn't, because aluminum hydroxide armors limestone surfaces and chokes off the reaction before it gets going.

But flow matters as much as the chemistry. A small seep that's net alkaline but surges hard during snowmelt can overwhelm a passive system's retention time even though the water chemistry itself would otherwise qualify. And a legacy working with decades of sulfide exposure can produce acidity loads that would need an unreasonable footprint of wetland to handle passively, pushing the project toward active treatment regardless of what the net alkalinity number says on a calm day. Design guidance in the field generally treats net alkalinity as a screening threshold, paired with metal loading per unit area and seasonal flow variability, before anyone commits to a passive design.

Why this matters before anyone runs a titration

None of this calculation happens without a water sample, and that's the bottleneck for anyone trying to screen a watershed with dozens of workings, some active, some abandoned fifty years ago with no monitoring well in sight. You can't run net alkalinity on a pond you don't know is there.

That's the gap a wide-area spectral screen is built to narrow, not replace. Ochre staining on a streambed and a turquoise tint on a settling pond are visual proxies for exactly the iron and sulfate chemistry that drives net acidity, and they show up in satellite imagery well before anyone schedules a sampling trip. A monthly flagged-pond and plume-extent layer across a watershed won't give you a net alkalinity figure, but it tells you where to point the sampling crew first, and which sites have gone quiet versus which ones are spreading.

If you're staring down a watershed with more candidate sites than sampling budget, that's the problem Mine Water Quality is built to help you sort through first.

Start a pilot

Back to the blog