Skip to content

Who Gets the Money? Benefit-Sharing in Blue-Carbon Projects

Follow a blue-carbon dollar from buyer to village: revenue waterfalls, disbursement channels and the design choices that decide who actually gets paid.

Priya RamanBlue Carbon Analyst8 min read
On this page

When a company buys a hundred tonnes of blue carbon from a coastal restoration project, the money travels. It passes through registries, brokers, project entities, governments and community funds before — if the project is well built — it reaches the fishers, rangers and villages whose coast stores the carbon. Every step in that journey is a place where value can leak, stall or be captured. This article follows the money: how blue-carbon revenue is actually divided, which contract terms decide whether communities see a fair share, and the questions to ask when a glossy benefit-sharing brochure meets a bank statement. For the broader menu of sharing models, see our companion piece on designing benefit-sharing in blue carbon projects; here we focus on the plumbing and the arithmetic.

The revenue waterfall: where each dollar goes

Project developers rarely publish a full waterfall, but every project has one. A typical sequence looks like this:

  1. Gross sale proceeds — the buyer's payment for credits, minus any broker or marketplace fees (often 2–10 percent).
  2. Registry and issuance costs — account fees, issuance levies charged per credit.
  3. Project operating costs — monitoring, reporting and verification (MRV), staff, vessel time, nursery operations.
  4. Developer margin or investor return — the share that compensates whoever financed years of pre-revenue work.
  5. Government share — where national law claims a percentage of carbon revenue, or where the state is the legal carbon-rights holder and redistributes.
  6. Community share — whatever the contract says remains for the people of the coast.

The order matters enormously. Structures that carve out the community share last, from whatever is left after costs and margins, routinely deliver small and volatile payments. Structures that carve it out first — a defined percentage of gross revenue, or a fixed floor payment per credit retired — deliver money communities can plan a school year around. This single contract variable is the strongest predictor of whether benefit-sharing is real.

Gross, net and the floor payment: the arithmetic of fairness

Three phrases sound similar and are very different:

  • A share of net revenue. "Thirty percent of net project revenue will flow to the community fund." Net of what? If the developer deducts MRV, salaries, marketing, a management fee payable to itself and a return of capital, thirty percent of the residue can approach zero. Land-based carbon projects have been criticised for exactly this.
  • A share of gross revenue. Cleaner, harder to game, and easy to audit against registry retirement records. A community entitled to 20 percent of gross can check the registry, count credits retired at known prices, and compute its entitlement with a spreadsheet.
  • A floor payment per credit. "At least $1.50 per credit issued, escalating with inflation, regardless of project costs." This is the most protective structure: it converts a percentage promise into a price promise, and it survives bad years when costs eat the margin.

Sophisticated buyers now ask to see the waterfall in the offtake agreement itself, not in a separate community benefits document that can be amended quietly.

The channels: how money actually reaches people

Even a well-protected community share has to travel the last kilometre. Four channels dominate, and robust projects usually combine them:

Direct household or individual payments. Familiar from terrestrial projects in the Amazon basin and from community forestry carbon in Mesoamerica. Transparent and popular, but administratively heavy in cash economies, and they can strain communities over eligibility boundaries. Direct payments work best where the group being compensated is well defined — a village, a clan estate, a registered fishers' association.

Community development funds. Revenue pools into a locally governed fund that finances public goods: boat engines, school fees, seawalls, health posts. Funds create visible, shared assets rather than divisible cash, and they can outlast a single project. Their weakness is governance — capture by local elites is the classic failure mode, mitigated by rotating committees, published accounts and independent signatories.

Wages and procurement. Employment in monitoring, nursery operations, patrol and dive teams is benefit-sharing that arrives as a payslip. Because restoration projects need labour exactly where the carbon sits, this channel can be large — in some mangrove programmes, wages exceed fund transfers in early years before credit sales ramp up. Procurement commitments (local vessel charters, locally built infrastructure) widen the circle to businesses.

Equity and co-ownership. The deepest channel: the community holds shares in the project entity, so its revenue isn't a transfer at all but a return on ownership. Equity survives leadership changes and aligns long-run incentives, though it demands legal capacity and patience. Where carbon tenure itself rests with customary owners — a genuine question of who owns blue carbon — co-ownership is often the only honest structure, because the community was never a beneficiary of someone else's project; it is the project's rightful owner purchasing services from a developer.

Timing: matching the money to the cash-flow reality of carbon

Blue-carbon projects have a brutal cash-flow shape: years of spending, then issuance, then sales, then — finally — transfers. Communities asked to change how they use a coast in year one may not see credit revenue until year four or five. Projects that survive this gap do so by paying pre-carbon benefits: wages, equipment and fund seeding financed by grants or blended capital before the first credit is sold. Blended finance structures exist precisely to bridge this valley of death.

Volatility is the second timing problem. Credit prices move; a community fund pegged only to revenue will boom and bust. Good structures smooth payments (holding reserves in strong years), diversify benefits (wages and ecosystem services don't crash with credit prices) and report honestly about the variability rather than projecting a flat line into village meetings.

Transparency plumbing: how a community checks its share

A benefit-sharing commitment is only as good as its audit trail. The functional minimum:

  • Registry transparency. Credits are issued and retired on a public registry, so volumes and, indirectly, prices can be verified by anyone. Our guide to carbon registries explains what to look up.
  • Published accounts for the community entity, in the local language, presented annually in open meetings — not just filed somewhere.
  • An independent audit right, funded in the budget, letting the community appoint its own reviewer of the developer's cost deductions and transfer calculations.
  • A grievance mechanism that is cheap to trigger and has teeth — the ability to pause distributions or escalate to the standard body, not a suggestion box.

Buyers can hard-wire much of this: making payment of milestones conditional on evidence of community distributions is now a common clause in sophisticated offtake agreements.

A worked example (illustrative)

At Tidewright we publish an illustrative waterfall with every project. For one of our fictional kelp-restoration programmes: of each $100 in gross credit revenue, registry and transaction costs take roughly $6; verification and MRV around $14; project operations $35; the financing stack $25; and $20 flows to the Sea Country fund — protected as a gross-revenue percentage — with an additional floor guarantee per credit held in escrow. The fund's council publishes its accounts annually, and ranger employment sits outside the $20, as operating cost, so community jobs never compete with community distributions. These are our numbers, presented as illustrative — the point isn't the percentages, it's that a waterfall this explicit can be interrogated line by line. That interrogability is the standard worth demanding from everyone.

Key takeaways

  • The decisive contract term is where the community share sits in the waterfall: a percentage of gross revenue or a floor per credit beats a residual share of net revenue every time.
  • "Benefits" travel through four channels — direct payments, community funds, wages/procurement and equity — and durable projects combine several.
  • Carbon cash flow is back-loaded; pre-carbon benefits and smoothed payments are what carry a project across the years before issuance.
  • Registry records, published accounts, funded audit rights and working grievance mechanisms are the minimum transparency plumbing.
  • Equity is a different category entirely where customary owners hold carbon tenure: ownership, not benefaction.

FAQ

What percentage of blue-carbon revenue should communities receive?

There is no universal benchmark, and the honest answer depends on tenure and law. Practice across credible land- and ocean-based projects clusters in the 20–50 percent range of gross revenue flowing to communities in aggregate (counting funds, wages and payments together), with higher shares where communities are the carbon-rights holders. Treat any fixed "industry standard" figure with suspicion; ask instead of which base the percentage is calculated.

How do communities actually receive the money?

Through the channels described above: direct payments to registered members, publicly governed development funds, employment, local procurement and, increasingly, equity dividends. The mechanism should be chosen with the community, not for it — some groups prioritise divisible cash, others prioritise collective infrastructure.

Don't the ecosystem benefits — fish, coastal protection — count as the community's share?

They are real and often large, but they flow whether or not a carbon project shares revenue. Counting restored fisheries as "benefit-sharing" is double counting in moral form: contractual sharing must be additional to what restoration delivers anyway.

What is the single biggest red flag for a buyer?

A community benefits document that is separate from, and subordinate to, the commercial contracts — amendable without community consent, and silent on the revenue base. That, and the absence of free, prior and informed consent, which we cover in our FPIC explainer.

How does this apply to kelp projects specifically?

Rocky-reef kelp projects add a twist: the carbon case is younger and often smaller than mangrove projects, so community value frequently arrives first through fisheries recovery, rangers' employment and co-management authority rather than credit revenue. Platforms like Canopy Ledger make the monitoring side of that value visible — but the contract still decides who gets paid. Communities evaluating a project can work through the governance questions in our community solutions overview with the same rigour a buyer would.