Making Your Water Stewardship Claim Count: How VWBA 2.0 Works and Where Practitioners Are Going Further

If your organization has set a water replenishment target, pursued Alliance for Water Stewardship certification, or reported through CDP Water, you have almost certainly encountered Volumetric Water Benefit Accounting. VWBA 2.0, published by WRI, LimnoTech, Bluerisk, and Bonneville Environmental Foundation and launched at World Water Week in 2024, is the framework most companies now use to count, track, and communicate the water benefits generated by their stewardship investments.

The 2.0 revision is a genuine step forward from the 2019 original. It introduced explicit project eligibility criteria, a formal additionality test requiring that claimed benefits would not have occurred without the stewardship investment, and specific guidance on what it actually means to make a credible claim rather than simply a calculated one. For practitioners who use the framework regularly, these improvements are meaningful.

What VWBA does well is give the field a consistent, auditable methodology for quantifying stewardship outputs. What the best programs are now exploring is how to connect those outputs more directly to verifiable watershed outcomes. This article walks through where that conversation is heading, and what it looks like in practice.

Three Questions Worth Asking Before You Finalize Your Program Design

VWBA is transparent about its own scope. The framework explicitly states that volumetric water benefits are outputs, not outcomes, and that meeting a volumetric goal does not guarantee shared water challenges are reduced. This is not a flaw in the framework; it is an honest statement of what accounting can and cannot do. The more interesting question for practitioners is what additional steps bring a program closer to the outcome side of that equation.

In our experience working on the infrastructure and engineering side of these programs, three questions consistently separate stewardship investments that can withstand independent review from those that might face closer scrutiny as disclosure expectations tighten.

1. Will you be able to show that source abstraction actually changed?

Non-revenue water reduction is the most common corporate stewardship project type: funding leak detection and repair in a municipal distribution system, then counting the metered reduction as a volumetric water benefit. VWBA 2.0 provides a sound framework for this, distinguishing between withdrawal and consumption reduction methods and requiring practitioners to select whichever reflects whether the saved water stayed in the source or was reallocated to meet other demand.

The question worth raising before an NRW program is structured is whether the stewardship agreement will include a contractual requirement to monitor source abstraction at the intake, over a sufficient period to detect the intervention's effect, before and after the project. Distribution loss data tells you what happened inside the pipe network. Source abstraction data tells you what happened in the catchment. For a claim about water returned to the environment, the second measurement is the one that matters most, and it is the one most often left out of program design.

Building abstraction monitoring in as a contractual deliverable, with a named measurement point and comparison period, is standard practice in infrastructure project commissioning. Applying that same standard to stewardship agreements is a natural extension of good engineering discipline.

2. How defensible is your without-project baseline?

Every VWB calculation rests on a comparison between a with-project condition and a without-project baseline. VWBA 2.0's additionality test asks whether the benefits would have occurred without the stewardship investment, which is exactly the right question. What gives the answer its durability is the quality of the baseline documentation.

The most robust baselines are established by a qualified independent party before the project begins, with the specific evidence base recorded and available for later review. This is worth thinking through early in program design rather than late, because a baseline assembled retrospectively to support a claim looks different to an external reviewer than one that was documented as a deliberate methodological choice from the outset. The standard is not technically difficult; it mostly requires doing the work in the right order.

3. If your project is in a different catchment, what documents the hydrological connection?

VWBA 2.0 allows companies to generate volumetric benefits in catchments other than where their operational impact occurs, which is a practical necessity for organizations managing water risk across multiple basins. The flexibility makes sense; the question is what supports the geographic pairing.

A facility facing water stress in one sub-basin is exposed to a specific catchment's hydrology, recharge dynamics, and seasonal flow regime. A stewardship project elsewhere addresses a different physical system unless there is a demonstrable hydrological connection, whether through a shared aquifer, connected surface flow, or common river basin. Documenting that connection through a hydrological connectivity assessment is the step that converts a geographically flexible claim into a geographically grounded one. It is not currently a universal requirement, but it is increasingly what sophisticated reviewers look for.

Why These Questions Are Worth Addressing Now

The regulatory and investor environment around water claims is maturing, and the direction of travel is consistent across jurisdictions.

CSRD Article 29b requires material environmental claims in sustainability reports to be supported with evidence equivalent in standard to financial disclosures. For companies reporting under CSRD, a VWB claim is subject to third-party assurance that goes beyond methodology review to include evidentiary support for the underlying impact.

The European Green Claims Directive, expected to come into force by 2026, will require substantiation of water-related claims in consumer-facing communications. Claims like 'water positive' and 'we restore more water than we use' will need documentation comparable to what regulators are already applying to carbon claims in the Netherlands, Germany, and the UK.

Institutional investors with technical ESG capacity are increasingly able to distinguish between a VWB that reflects metered, independently verified source-level impact and one that reflects a calculated output from a modeled counterfactual. That distinction is becoming material to how stewardship claims are weighted in portfolio-level water risk assessment.

Organizations that have built genuine stewardship programs are well-positioned to navigate this environment. The additional steps described above are not remedial; they are the natural evolution of rigorous programs that are already doing the hard work of stewardship investment.

What a More Complete Program Looks Like in Practice

At HydraLink, we work on the infrastructure side of water stewardship: hydraulic modelling, field-based verification, water balance analysis, and the engineering assessment of whether an intervention actually delivered the hydrological change it was designed to produce. This work sits adjacent to, and complements, the accounting methodology that VWBA provides.

The programs we find most defensible share a few consistent features.

Before the project: the baseline is established with an independent party, the monitoring protocol is specified in the agreement, and the measurement point is the one the claim actually depends on. For NRW programs, this means source intake abstraction data alongside distribution system loss figures.

During the project: monitoring captures the variable that the VWB depends on, not just the variable that is easiest to measure. Leak volume is straightforward to meter. Source abstraction requires coordination with the utility's operations team and a data-sharing protocol. Agricultural efficiency savings are calculable from irrigation records; return flow to groundwater requires field instrumentation. Distinguishing between these levels of evidence is part of characterizing the claim accurately.

After the project: independent verification that asks whether the source-level impact actually occurred is more valuable than verification that confirms the calculation was correctly performed. Both matter. The first is what positions a program to answer the questions regulators and investors are increasingly prepared to ask.

VWBA 2.0 gives practitioners a consistent, well-documented methodology for quantifying stewardship outputs. The most forward-looking programs are building on that foundation by asking what additional evidence would make their claims independently verifiable at the catchment level. That is not a critique of the framework; it is the natural next step for stewardship investment that takes its own commitments seriously.

The organizations best positioned for where disclosure expectations are heading are the ones already treating their stewardship programs with the same engineering discipline they would apply to any other piece of water infrastructure: a real baseline, monitored through commissioning, and verified against what it was actually designed to achieve.