blueproof.ai starts with a defined fixture set and reporting period, preserves the connected-fixture evidence, and keeps the modeled without-project case explicit. The result carries enough context for a buyer, reviewer, or assurance practitioner to test how it was produced.
Demand reduction is a counterfactual claim: what a defined project used after installation compared with what the same use would have required without the project.
Connected fixtures make the project side more specific. The source evidence can be tied to a fixture, product, building, and period, while the without-project baseline remains a separate model supported by disclosed evidence.
That does not eliminate judgment. It makes the judgment visible and gives diligence a narrower record to test.
The unit of measurement is a connected fixture with device-level telemetry. The boundary is drawn around water leaving the source through that fixture.
Fixture activity and reported project use remain distinct from the modeled without-project case, so the reviewer can see the basis of each input.
The source references, baseline basis, method version, assumptions, exceptions, and calculation stay with the result instead of disappearing into a summary.
VWBA 2.0 is voluntary, principle-based guidance for quantifying and communicating volumetric water benefits. blueproof.ai maps the method to that guidance and keeps the project boundary, baseline, assumptions, conservativeness choices, and claim limits visible for review.
See the methodology →Drawn around water leaving the source through the fixture — so every activation, including sensor-added ones, is accounted inside it.
A modeled counterfactual, tiered by evidence, that never uses project activations as a proxy — the accounting rule that keeps the claim honest.
Structured so a verifier can test whether the reduction is real and surplus under the standard.
We can walk through the sample receipt, VWBA 2.0 mapping, chain-of-evidence design, and the questions an independent verifier would ask.