M1
Project registry
Master records for climate projects: actors, locations, lifecycle status, documents, and public change logs.
Problem & Solution
Climate finance without accountability fails the people who need it most
Rising hazards and larger portfolios mean little if communities cannot see projects, track money, or safely report failures. Climate Fund Watch closes that loop.
The problem
Delivery fails for universal reasons
From SIDS to large economies, adaptation and mitigation portfolios share the same governance gaps. Mauritius faces frequent floods and cyclones while mobilizing domestic and international climate finance — making transparent, community-checked delivery urgent.
| Failure mode | Citizen impact |
|---|---|
| Fragmented reporting | No single source of truth for projects, budgets, and status. |
| Weak budget-to-site traceability | Money disappears between approval and community-visible works. |
| Limited local authority visibility | Delays and mis-prioritization at the places most at risk. |
| Unsafe or absent integrity channels | Corruption and greenwashing go unreported. |
| Closed data | Media and NGOs cannot audit independently. |
| Language & connectivity barriers | Excluded communities cannot participate in oversight. |
Theory of change
If governments and partners publish climate projects and budget flows, communities can submit field evidence, and whistleblowers can report integrity risks safely — and local and national actors act under clear SLAs — then delays and misuse are detected earlier, trust rises, and adaptation resources reach vulnerable communities more fairly.
The solution
Modular platform, two security zones
Climate Fund Watch ships as pluggable modules on a multi-tenant core. Public transparency data is open by default. Integrity reports live in a separate vault with no identity join keys to the public zone.
M2
Budget & fund flows
Source → instrument → appropriation → disbursement → expenditure → remaining, with co-financing fields.
M3
Map & milestones
MapLibre/OSM explorer with filters by hazard, status, funder, and admin unit; plan vs actual milestones.
M4
Community evidence
Guided reports for delay, quality, non-delivery, exclusion, environmental harm, and greenwashing signals.
M5
Integrity safe channel
Anonymous intake, case codes, encrypted attachments, handler workflow — hard-isolated from public identity data.
M6
Government ops consoles
Local and national dashboards for portfolio health, inboxes, SLAs, and controlled contributor updates.
M7
Open data & API
REST/CSV/GeoJSON exports, data dictionary, open license for public datasets.
M8+
Scorecards & green integrity
Delay alerts, monthly public scorecards, and checklist-based anti-greenwashing scores.
How it works
A continuous loop from funding decision to community verification and public accountability.
- 1Fund approved / project listed
- 2Budget chain & milestones published
- 3Citizens submit geotagged field evidence
- 4Issues flagged and escalated under SLAs
- 5Officials respond; status updated publicly
- 6Scorecards & open data for independent audit
What you can use now
- • Public narrative site (mission, problem, solution)
- • Demo project registry, map, and open CSV/JSON
- • Product build plan and Mauritius research pack in the repo
What comes next
- • Community evidence form (delivery issues)
- • Official data-sharing and live council updates
- • Integrity vault & council consoles after legal/security gates
Ready to pilot, fund, or co-design a country pack?
Get involved