Skip to content
All solutions

Solutions / Water infrastructure investment

Water Infrastructure Investment Support & Exchange

Connecting capital to water infrastructure.

Proof of concept

WIISE is a project marketplace connecting capital to water infrastructure through a common, verifiable record of baseline, delivery and outcomes. It supports outcomes-based finance for non-revenue water, water reuse and treatment projects, with verified outcomes, transparent reporting and supporting evidence. Water Ledger Global is preparing a proof of concept focused on South Africa.

How it works / WIISE

List the project. Connect investment. Track delivery.

Explore the process

Reading the model

  1. 01 · ListThe network asset and document form a project dossier: what needs to change, the starting point and the proposed work.
Connected evidence
Project, baseline & intended outcomes
01 / 03

Select a step to explore

One connected record

Project baseline · funding terms · delivery evidence

Illustrative · not live data

Project examples

Different projects.
Evidence of the outcome.

Explore how a project could connect its funding, delivery and measured results. WIISE is at proof-of-concept stage; these examples illustrate the approach.

Non-revenue water

Connect investment in a water network to evidence of reduced losses. Start with the water balance, define the intervention and assess the measured change.

Intended outcomeA sustained reduction in water losses, assessed against an agreed baseline.

How it works / WIISE / Non-revenue water

Reduce losses. Account for the water recovered.

Explore the process

Reading the model

  1. 01 · ListThe supply tank, network and record represent the starting water balance. Input and consumption evidence establish what is known about losses.
Connected evidence
Network boundary & starting water balance
01 / 03

Select a step to explore

One connected record

Water balance · funded intervention · measured reduction

Illustrative · not live data

Questions behind the project

Where is water being lost?

Define the network boundary and compare input, consumption and loss records to establish a credible baseline.

What work needs funding?

Set out the proposed intervention, its cost, delivery responsibilities and intended reduction in losses.

How will improvement be measured?

Agree the measurement period, comparison method and evidence needed to assess change against the baseline.

What reduction has been verified?

Review measured performance and supporting records, keeping verified results separate from forecast savings.

Different responsibilities.
Shared facts.

WIISE is preparing a proof of concept focused on South Africa. An engagement begins with the project owner, a defined intervention and the evidence needed to assess its baseline and outcomes. Funding arrangements and connections to operational systems are agreed for each implementation.

Project proponents

Define the project, establish its baseline and set out the work to be funded.

Solution providers

Connect delivery milestones and interventions to supporting evidence.

Investors

Assess the project basis, agree responsibilities and follow evidence of delivery.

Regulators

Review project requirements and evidence of outcomes against the relevant rules.

WIISE questions, answered.

What to know before taking the next step.

Questions about working with us
Is WIISE suitable for our infrastructure project?

WIISE is at proof-of-concept stage and is designed to connect investable water infrastructure projects with capital through outcomes-based finance. Project examples include reducing non-revenue water and putting water back to use. Start with a defined project, its baseline, funding needs and the evidence required for verified outcomes and transparent reporting.

How does WIISE help with non-revenue water?

WIISE follows List, Invest, Track. A project owner lists an intervention with its baseline and intended outcomes; potential funders assess that evidence and agree terms with the participants; delivery and measured performance are then tracked against the starting point. Water-balance and consumption records support this process, rather than replace the project and investment decisions.

How could WIISE support a water reuse project?

Define the recoverable source and intended use, including the required volume, quality and delivery conditions. Connect the infrastructure plan and funding terms to delivery milestones, then keep delivered volumes, quality checks and review records together. The outcome is assessed against agreed project requirements; finance and performance are not guaranteed.

What information is needed to start a WIISE project?

Start with the project owner, location, intended outcome, baseline evidence, proposed infrastructure, estimated costs and delivery responsibilities. A non-revenue water project needs network and water-balance records; a reuse project needs a defined source, intended use, and volume and quality requirements. Data gaps are assessed during project scoping.

Discuss your project
How are investment decisions and outcomes assessed?

Project evidence gives participants a shared basis for assessing investment and measured outcomes, such as reduced losses or water put back to use. Funding depends on the project and agreed terms; outcomes depend on delivery and measured performance. Forecast benefits remain separate from verified results, and neither funding nor performance is guaranteed.

Who should be involved in an initial WIISE discussion?

Start with the project owner and people responsible for infrastructure delivery and operational evidence. For reuse, include the source provider and intended water user. Potential funders and relevant public agencies can then review the project basis, intended outcomes and evidence needed to evaluate progress.

Explore WIISE in your context.

WIISE is preparing a proof of concept focused on South Africa. An engagement begins with the project owner, a defined intervention and the evidence needed to assess its baseline and outcomes. Funding arrangements and connections to operational systems are agreed for each implementation.