Monthly qualitative updates and quarterly water-volume and uptime KPIs across the Water for Health portfolio. Draft format for agreement with Bridges.
Of — projects, — are on track and — are on watch. Asili DR Congo needs a decision on its three excluded kiosks.
Monitoring and audits run once a year, so the monthly signal is movement through these six stages and whether the next milestone is still on schedule.
| Project | Stage | Status | This month | Next milestone |
|---|
People served, end of September. School enrolment updates each term; July and August are school holidays.
People served, end of September, estimated from monthly meter readings at the age-weighted 3.15 L/person/day.
| Date | Project | Area | Status | Update |
|---|
— of — volume-tested projects delivered enough water to cover their Gold Standard consumption cap. Systems were functional — of system-days across the portfolio.
Quarter volume ÷ (people claimed × 92 days). A project at or above its cap (QPW, SDWS V2.0) has enough metered water to support every person it claims, so credits are not volume-limited.
| Project | Q3 m³ | vs Q2 | People claimed | L/p/d | Cap | Of cap | Result |
|---|
Not volume-tested this quarter: .
m³ per month. Each project on its own scale; Q3 months in colour.
From maintenance and operator logs, or Lume sensors where installed. Gold Standard accepts functionality above 95% only with sensor evidence, so log-based figures are capped at 95% for crediting.
| Project | Systems | Uptime | For crediting | Breakdowns | Fixed | Median days to fix | Open 30 Sep |
|---|
Most carbon milestones happen once a year, so the monthly report tracks progress toward them in words, and the quarterly report carries the operational numbers that do move: water delivered and systems kept running.
Due by the 15th of the following month. Stage in the credit cycle and status per project, key events (monitoring data collected, analysis started, audit questions answered, issuance requests), and the next milestone. People served is reported monthly where it updates monthly: Amazi Meza Rwanda and Amazi Water Burundi.
Due within 30 days of quarter end. Metered water volume against the Gold Standard per-person cap, system uptime, and breakdowns with time to repair.
Field data arrives monthly at best, so a weekly report would repeat itself. If Bridges wants a weekly signal, the lightest option is an automated count of mWater submissions received, with no narrative.
| KPI | Cadence | Definition | Evidence | Threshold |
|---|---|---|---|---|
| Credit-cycle stage | Monthly | Which of the six stages each project is in, from data collection to issuance. | Project tracker, auditor and GS correspondence | Next milestone named for every project |
| Project status | Monthly | On track, watch or at risk, with the reason when not on track. | Weekly partner calls | Any "at risk" comes with a recovery plan |
| People served | Monthly (Amazi), annual (others) | People with access to project water at month end. | mWater registry, enrolment records, meter readings | Trend reported; no monthly target |
| Water delivered vs GS cap | Quarterly | Metered volume ÷ (people claimed × days), against the project's QPW in litres per person per day (SDWS V2.0 Table 9 defaults or age-weighted). | Meter readings in mWater | At or above QPW |
| Uptime | Quarterly | Functional system-days ÷ total system-days. | Maintenance and operator logs; Lume sensors where installed | At least 90%; above 95% creditable only with sensor evidence |
| Breakdowns fixed | Quarterly | Breakdowns fixed in the quarter ÷ breakdowns reported, with the median days to fix. | Maintenance logs | Median days to fix reported; no fixed target |