Water stewardship, explained.

Stormwater runoff is a leading source of water pollution in urban areas. As rain moves across roofs, streets, and pavement, it picks up oil, metals, sediment, nutrients, and debris before entering local waterways.

Green stormwater infrastructure helps capture, slow, and filter that runoff. Shoalwater makes that impact measurable and scalable.

Examples include rain gardens, permeable pavement, cisterns, bioretention systems, and other green stormwater infrastructure that captures, infiltrates, stores, or slows runoff.

Water challenges are local. Basin-level accounting connects action to the watershed where risk, pollution, habitat pressure, and community outcomes actually occur.

Shoalwater follows a six-step sequence:

• Define the basin and local water context
• Establish the project baseline and accounting boundary
• Classify the relevant benefit pathway
• Select the strongest available calculation method
• Apply eligibility, consent, attribution, and double-counting controls
• Report the result with evidence level, assumptions, uncertainty, and claim-safe language

This structure keeps infrastructure documentation separate from any later determination that an outcome is eligible for corporate replenishment or another external claim.

No. Shoalwater first documents what a system physically does or is designed to do—such as capture, store, delay, infiltrate, reuse, or filter rainwater.

A reportable replenishment or volumetric benefit requires additional review of the baseline, project boundary, basin relevance, additionality, operating condition, evidence quality, funding contribution, attribution, and applicable accounting framework.

Shoalwater’s methodology is informed by:

• Alliance for Water Stewardship Standard 3.0: catchment context, shared water challenges, governance, stakeholder engagement, water balance, water quality, and freshwater ecosystems
• Volumetric Water Benefit Accounting 2.0: project goals, baselines, boundaries, conservative estimation, benefit evaluation, tracking, and double-counting controls
• Water Quality Benefit Accounting: a separate pathway for evaluating and communicating water-quality benefits

References to these frameworks do not imply AWS certification, independent verification, or assurance unless the applicable external process has been completed.

It depends on the available evidence. Shoalwater uses an evidence hierarchy:

• Measured: meters, sensors, calibrated flow data, or monitored performance
• Engineered: approved design records, inspections, and site-specific calculations
• Documented: photos, dimensions, drainage area, specifications, or installation records
• Registered: owner-submitted system identity and location

Measured and modeled results remain clearly distinguished in external reporting.

Water-performance estimates may be affected by rainfall variability, system capacity, overflow, soil conditions, maintenance, downtime, data completeness, and model selection.

Shoalwater records material assumptions, uses conservative estimates where appropriate, assigns an evidence tier, and updates calculations when stronger information becomes available.

Capture, storage, delay, infiltration, reuse, and water-quality benefits remain separately labeled when adding them would count the same water more than once.

Attribution is assigned only through explicit authorization and a defined program or funding agreement. The same incremental benefit should not be attributed to multiple funders for the same reporting period.

Verified implementation means project installation or operating evidence has passed Shoalwater’s documented review controls.

Independently assured means a qualified external party has reviewed the defined methodology, supporting evidence, and reported outcome. Shoalwater does not use these terms interchangeably.

Shoalwater can help organizations document basin-specific water context, stewardship actions, implementation evidence, project boundaries, and modeled or measured outcomes.

These outputs may support disclosure preparation, but Shoalwater does not replace company-level reporting judgments, legal review, or the current CDP questionnaire and scoring guidance.

Shoalwater’s basin-first approach is informed by AWS Standard 3.0 concepts, including catchment context, shared water challenges, stakeholder participation, water balance, water quality, governance, and transparent action.

Shoalwater participation is not the same as AWS certification. Certification requires the formal AWS process and independent conformity assessment.

VWBA 2.0 provides a recognized structure for implementing, evaluating, tracking, and communicating volumetric water benefits.

Shoalwater uses its principles to strengthen project goals, baselines, accounting boundaries, conservative calculations, benefit eligibility, reporting periods, and double-counting controls.

Stormwater projects may reduce pollutant transport, improve filtration, or create other water-quality benefits that are not fully represented by gallons alone.

Where sufficient evidence exists, Shoalwater treats these outcomes as a separate benefit pathway informed by Water Quality Benefit Accounting. Water-quality benefits are not automatically converted into replenishment volume.

Depending on the project and evidence available, outputs may include basin assignment, asset type, reporting period, data source, evidence tier, calculation method, modeled or measured performance, assumptions, uncertainty, attribution status, and approved claims language.

Shoalwater is built for companies pursuing place-based water stewardship, property owners with eligible infrastructure, contractors and providers seeking persistent project records, and municipal or watershed partners seeking better visibility into distributed systems.

Property owners with green stormwater infrastructure, organizations pursuing basin-level water impact, and partners working in watershed restoration or stewardship can all participate in different ways.

Property owners may register existing systems such as rain gardens, cisterns, bioswales, green roofs, and permeable surfaces. Registration creates an infrastructure record; it does not automatically create a replenishment claim or enroll the property in a corporate program.

Typically: property address, system type, approximate dimensions or drainage area, installation or inspection records where available, current photos, and information about operating or maintenance status. Stronger documentation supports a higher evidence tier.

System data may be used to document the asset, assign basin context, evaluate its intended water-management function, assess evidence quality, and determine whether it may be eligible for future stewardship programs. Ownership remains with the property owner, and attribution or public-facing use should require clear consent.