
Concept: carbon revenue sharing transparency communities can check

Updated: 4 days ago
Carbon revenue sharing transparency means a community can see evidence that its promised share of carbon revenue actually reached people. A percentage written into an agreement is where that starts. Standards and national laws now fix minimum shares, such as Plan Vivo's 60% and Kenya's 40% for some land-based projects. What most projects still lack is a record that people outside the developer's office can check against that promise.
Concept note: This article describes a feature we are exploring: a benefit-sharing ledger. It is not available in the CitizenClimate app today, and there is no release date or price.
Why carbon revenue sharing transparency matters now
Benefit sharing used to be a matter of good intentions. It is now increasingly a written minimum.
Plan Vivo states that "at least 60% of the revenue from the sale of each PVC goes directly to the local community". Our Plan Vivo alignment page summarises the same rule.
National law is moving the same way. Under Kenya's Climate Change (Carbon Markets) Regulations, 2024, land-based projects on public or community land owe an annual social contribution of "at least forty percent (40%) of the project's aggregate earnings in the previous year", and non-land-based projects on such land at least 25%, according to a summary by Oraro & Company Advocates.
Individual deals are setting their own terms. In November 2025, Mongabay reported that more than 220 communities in Sierra Leone's Sittia chiefdom signed a mangrove carbon agreement under which they are set to receive "40-50% of gross revenue" from credit sales. The agreement obliges the developer "to disclose sales and other related information". Mongabay also reports a Carbon Market Watch researcher saying that the lack of price transparency is a major barrier for communities trying to judge whether their share is fair.
The integrity bodies have noticed the gap. The ICVCM's October 2025 report on sustainable development benefits and safeguards says "The ICVCM should require transparent reporting on benefit-sharing arrangements" and should "promote participatory monitoring mechanisms".
A percentage in a contract is a promise. Transparency is the evidence trail behind it.
What a benefit-sharing record has to show
Before thinking about software, it helps to be clear about what a credible record of benefit sharing would contain. Each element answers a different question, and each has a different person who can check it.
Question | What the record would hold | Who can check it |
|---|---|---|
What was promised? | The share and its basis (gross revenue, earnings, per credit) from the benefit-sharing plan | Community members, buyers, verifiers |
What came in? | Revenue for the period, as disclosed by the developer | Buyers, verifiers, regulators |
What went out? | Each payment or benefit, with date, amount, recipient group and method | Members, verifiers |
Did it arrive? | Confirmation of receipt from the people or groups paid | Members themselves |
What if it did not? | A complaint route that cannot be quietly deleted | Members, verifiers |
Most projects can produce the first row from a signed agreement. The second sits with the developer and the buyers, and the Sierra Leone example shows how hard price disclosure can be. The last three rows are field evidence. They are the part a community monitoring tool is placed to help with, because the people who should receive the money are the same people already submitting data from their phones.
What the CitizenClimate app records today
Some of the building blocks already exist in the app. This section covers only what the app does now.
Community members earn "points, badges and, where your project offers them, local currency rewards", according to the App Guide. On the field data collection page, "projects can add a currency reward, set per project and per survey". The project decides whether to offer a currency reward and how much it is.

When a member submits a survey, the app confirms what they earned. The Data Integrity and Methodology Protocol describes a daily check of new submissions; where it rejects one, "The points and payment earned for it are reversed". Submissions are never deleted. Faulty ones are archived with a reason from a fixed list.

The app also has a grievance mechanism. Members can file a grievance that moves from Pending to Under Review to Resolved. The App Guide states that "Grievances can't be deleted, and your name isn't shown to the project developer or to other members", and the Protocol gives VVBs read access to all grievances.

Two more facts matter here. Verification bodies "can be granted direct read access to your project data", according to the pricing page FAQ. Exports in CSV and JSON carry the raw records rather than summaries.
There are also clear limits. Rewards are set by the project, and the App Guide describes crediting and reversing them. It does not describe a money-transfer service. The app records rewards credited for survey work. It does not record carbon revenue, and it holds no view of whether a project has met its benefit-sharing share.
Concept: a community benefit-sharing ledger
Concept, not a product feature. This describes an idea CitizenClimate is exploring. It is not available in the app today, and there is no release date or price.
Today the app credits project-set rewards per survey and reverses them if the daily check rejects a record. The idea we are exploring is a project-level ledger that would set those rewards, and any other payments, against the share the project promised.

Here is how it could work, step by step.
Record the promise. The project developer would enter the share from the benefit-sharing plan once, with its basis: a share of gross revenue, of earnings, or a fixed amount per credit.
Count rewards already credited. Survey rewards recorded in the app would be added up automatically by period and by community. These are the only figures the app holds today.
Log other payments with evidence. Most benefit sharing is not survey rewards. Community fund transfers, school fees or a cash distribution would be logged by the developer, each with a date, amount, recipient group and a photo or document as evidence. Like survey records, the entries could be archived with a reason but never deleted.
Ask members to confirm. Members could see payments addressed to them or their community and tap "received" or "not received". A "not received" answer could open a grievance, which would then follow the anonymous, undeletable route the app already uses.
The result would be a single view: promised share, payments logged, the portion confirmed by members, and open grievances about payments. A verifier with read access could follow each figure back to its entries. A buyer could see more than a percentage in a project document.
What the ledger would not prove
Some limits would remain, and they matter for anyone judging a concept like this.
Revenue is still the developer's number. The ledger could show what was paid out against what was disclosed. It could not show that disclosed revenue was complete. Price transparency would still depend on contracts and disclosure rules.
Definitions stay contested. "Aggregate earnings" and "gross revenue" are defined in agreements and regulations, not in an app. The ledger would only record the basis the project entered.
Non-cash benefits are harder to log. A new water point or training programme has value that is hard to express as a share. These could be logged with photo evidence, but their valuation would remain a judgement.
Confirmation needs consent and trust. Members would need to understand what they are confirming, in their own language, and feel safe saying "not received". The app's anonymous grievances help, but they would not replace good process on the ground.
How this fits with standards and verification
Nothing in this concept changes who certifies a project or issues credits. CitizenClimate's data is structured to align with the monitoring requirements of Verra VCS, Gold Standard, Plan Vivo, Puro.earth and Carbon Standards International. CitizenClimate is not certified, accredited or endorsed by any standard body, and it does not issue credits. CitizenClimate has no affiliation with the Plan Vivo Foundation, and the Foundation does not endorse it.
We do not suggest that Plan Vivo, Kenya's Designated National Authority or the ICVCM requires or recognises a tool like this. The point is narrower. Where a standard, a regulation or an agreement sets a share, the evidence that it reached people is field evidence, and field evidence is what community-led dMRV is built to collect. Weighted household surveys, such as those described on our SDG impact page, already ask communities how a project affects them. A payment confirmation would be a more direct question.
Frequently asked questions
What is carbon revenue sharing transparency?
It means a community, and anyone verifying its project, can see evidence that the share of carbon revenue promised to a community actually reached it. That usually means three things on record: the share agreed in the benefit-sharing plan, the payments and benefits delivered against it, and some confirmation from the people who were meant to receive them, with a way to complain if they did not.
How much carbon revenue must go to communities?
It depends on where the project is and which standard it uses. Plan Vivo states that at least 60% of the revenue from each certificate sale goes to the local community. Kenya's 2024 Carbon Markets Regulations set at least 40% of the previous year's aggregate earnings for land-based projects on public or community land. Individual agreements, such as the Sierra Leone mangrove deal reported by Mongabay, set their own shares.
Who sets the rewards community monitors earn in the app?
The project does. A project can choose to offer a currency reward for each survey, alongside points and badges. The app credits it when a member submits a survey and reverses it if the daily check described in the Protocol rejects the record. The project decides whether to offer rewards and how much they are worth, and the App Guide does not describe a money-transfer service.
Can a verifier see reward and grievance records in CitizenClimate?
Verification bodies can be granted direct read access to project data in a read-only VVB role, and the Protocol states that VVBs can read all grievances. Project data can be exported as CSV or JSON with raw records rather than summaries. The app does not hold a project's carbon revenue or benefit-sharing accounts.
Try the parts that exist today
The benefit-sharing ledger is a concept. The building blocks behind it are in the app now: project-set rewards per survey, a daily check that can reverse them, anonymous grievances that cannot be deleted, and read access for verifiers. If you run a community carbon or nature project, download the free app and try them with your monitors, or read the App Guide first.



Comments