A credible water claim lets another person understand what changed, where and how it was measured. Terms such as water positive become ambiguous when withdrawals, reuse, rainwater capture and recharge are added without a defined method. Corporate teams need a statement that survives scrutiny from operations, communities and report readers. This guide proposes an evidence review before publication. It distinguishes routine water accounting from programme-specific positive-impact frameworks and explains why volume alone cannot establish an environmental outcome.
“Freshwater targets are basin-specific”
Science Based Targets Network, Freshwater Targets
Write the claim boundary first
Define the organisation, facility, activity and reporting period covered. Specify whether it concerns direct operations, a supplier, community project or wider catchment. Explain which sources are included and where water returns after use. A site result should not become a company-wide claim unless the wider boundary has been assessed. State exclusions that materially affect interpretation.
Include the geographic relationship between an intervention and the pressure it addresses. Benefits in one location do not automatically compensate for depletion elsewhere. Timing matters: a seasonal intervention may not address a shortage in another period. Put these limits in the claim or a linked methodology where readers can find them without requesting a private presentation.
Keep the accounting terms distinct
Withdrawal is water taken from a source. Consumption and discharge describe different outcomes and must follow the selected reporting framework’s definitions. Internal recycling describes water used again within the system. It can reduce new demand, but counting each recirculation as new water created exaggerates the result. A clear facility balance prevents these categories from being mixed.
Rainfall on a roof is not equivalent to harvested water, usable water or verified aquifer recharge. Collection losses, overflow, storage, treatment and destination affect the reported quantity. Keep potential separate from measured delivery. For modelled impacts, identify the model, inputs, uncertainty and validation. Avoid presenting a design calculation as a commissioned result, even when it is based on a recognised engineering method.
Choose a baseline that can be explained
Use a documented comparison period reflecting the activity assessed. Record production, occupancy, operating hours, rainfall and other material conditions. Explain exceptional shutdowns or changes in boundaries. A low-demand year can make subsequent consumption appear worse even when efficiency improves. Reduced production can create an apparent saving without an intervention. The comparison needs enough context to distinguish these effects.
Retain absolute and intensity measures where they answer different questions. Define the intensity denominator, such as tonnes of a specified product, and keep it consistent. If a baseline is adjusted, document the original, reason and revised method. Management should be able to reproduce the result. A favourable percentage without a stable denominator is difficult to defend or compare with later performance.
Evaluate benefits in their local context
GRI 303 addresses water-related impacts and emphasises the local context of a shared resource. SBTN freshwater methods set basin-level targets. Discuss availability, quality and competing users before choosing a headline target. Consult credible catchment information and people responsible for local water management. Record uncertainty where the information is incomplete or outdated.
For recharge or replenishment projects, assess source-water quality, hydrogeology, access, maintenance and the expected benefit pathway. Describe who benefits and whether another user could be affected. Increasing storage needs a different evidence plan from improving water quality. Use the relevant framework’s current methods rather than assuming that every positive outcome can be reduced to one interchangeable volume.
Prevent double counting and unsupported attribution
List partners, funding shares and the allocation method for a claimed benefit. If several organisations fund one intervention, each should not automatically claim its entire result exclusively. Record whether the claim concerns delivery, financial support or a quantified outcome. Each can be useful when described accurately and attributed to the correct contributor.
Ask what would happen without the intervention and whether improvement is additional to the baseline. Document assumptions about continued operation, maintenance and future benefit. Check whether a volume appears in another project or category. An evidence register with unique identifiers, locations, years and claim owners can reveal overlaps before publication. Retain the agreement on shared claims with the underlying project records.
Build a reviewable evidence file
For each metric, retain measurement source, units, dates, calibration, calculation method and responsible person. Attach commissioning records, laboratory reports and operating logs where relevant. Photos show infrastructure exists; they do not independently establish annual benefits. Consider consent and privacy when publishing community images or beneficiary information. Link evidence to the specific period reported.
Separate measured values, estimates and qualitative outcomes in the reporting table. Record limitations and independent review where it exists. If verification has not occurred, say so. Positive Water Impact and other frameworks have their own definitions and validation expectations. An internal workbook does not confer recognition under them. Use framework names only when the methodology and participation status support the wording.
Publish precise progress and revisit it
Prefer a measured reduction at a named facility over a defined period, with the comparison method linked. Where evidence is incomplete, communicate the intervention and monitoring plan. Avoid extending a one-year result indefinitely or describing installed capacity as sustained annual benefit. Keep a correction process for errors found after publication and a record of revised statements.
Create an annual review involving operations, sustainability and the person approving external communications. Reassess whether boundaries, data and local context still support the statement. Expansion, changing groundwater conditions or an idle project can alter the result. Readers should see progress, understand its limits and compare future updates consistently. A precise, modest claim with accessible evidence can be more useful than an expansive statement whose meaning changes between reports.
Questions for your next review
Before communicating an outcome, ask a colleague who was not involved in the project to trace one number from the proposed claim back to its source. They should be able to identify the place, reporting period, baseline, measurement method, assumptions and responsible reviewer without relying on a verbal explanation. If the trail ends at a presentation slide, the evidence pack is incomplete. Repeat the exercise for the attribution statement: which organisation funded, implemented or operates the activity, and what portion is being claimed? Record exclusions as carefully as included benefits. An honest limitation can make a result more useful to a reader than an impressive aggregate. Keep the approved wording with the evidence version so later edits do not expand the original claim.
Key takeaways
- Define site, period, source and catchment.
- Separate potential, delivery and verified outcomes.
- Avoid double counting reuse or shared benefits.
- Link claims to reproducible evidence.
Free tools for this topic
Sources and further reading
Calculation examples are illustrative planning calculations, not reported project results. Confirm current Indian and site-specific requirements before applying international guidance.