Skip to content

Who Benefits? Designing Benefit-Sharing in Blue Carbon Projects

How blue carbon projects can share revenue, jobs and decision power fairly with coastal communities — models, safeguards and the questions to ask first.

Priya RamanBlue Carbon Analyst10 min read
On this page

A blue carbon project that restores mangroves, marshes or kelp on someone's coast generates value for decades — and every model of that value depends on the people who live there. Fisherfolk shift their grounds, rangers do the monitoring, communities absorb the rules about what can be used and where. Whether those people share in the upside is not an ethical garnish on the project; it is the difference between a credit that endures and one that unravels in a decade, undermined by the very exclusion that designed it. This piece is a practical map of how benefit-sharing can be structured, the models in use, and the safeguards that separate a genuine share from a brochure.

Why benefit-sharing is the make-or-break design question

Carbon projects are long contracts. A thirty-year credit programme on a coastline is a thirty-year set of decisions about access, labour, money and risk — made in the first two years, lived out by people who often weren't in the room.

The record of land-based carbon projects offers the cautionary tale. Where projects treated host communities as scenery — fencing off forests, pricing them out of their own resources, paying them in vague promises — the carbon was fragile: encroachment, resentment, legal challenge and reversal. Where communities had real stakes, permanence improved because stewardship paid. Ocean projects are younger, but there is no reason to expect a kinder dynamics curve. In blue carbon, the community is often the ecosystem's longest-standing manager and its first responder — fishers who know the nursery bays, Indigenous rangers who hold tenure deeper than any registry title.

Benefit-sharing is also increasingly the precondition for legitimacy: buyers conducting diligence now ask about it by name, and frameworks for high-integrity credits treat community benefit as a core quality criterion rather than a co-benefit ribbon.

What can actually be shared

"Benefits" is a wide word. In practice it spans five distinct currencies, and a well-designed project shares across most of them:

  1. Revenue — a defined percentage of gross or net carbon-credit income, protected in writing.
  2. Employment and enterprise — paid roles in monitoring, nursery work, reef maintenance and eco-tourism; local procurement for vessels, gear and lab services; spin-off businesses like dive operations or seaweed food ventures.
  3. Assets and co-ownership — equity in the project entity, community-held title to credits, or ownership of durable project infrastructure.
  4. Governance — seats with real votes on the project board, control over monitoring data, and joint authority over rule changes.
  5. Ecosystem services themselves — the fisheries recovery, coastal protection and water quality that restoration delivers, which everyone on the coast receives whether or not they hold a certificate.

A project that shares only the fifth item and calls it benefit-sharing is doing PR. The services are valuable, but they flow regardless of the contract; sharing means something additional that the contract creates.

The main models, with their strengths and snags

Fixed revenue share

The community receives a contractual percentage of credit revenue — commonly in the range of 10 to 30 percent depending on the legal context, sometimes higher. Simple, auditable, and understood by buyers. The snag: percentages of net revenue can shrink to nothing if the developer deducts costs liberally. Shares of gross revenue, or a floor payment per credit sold, are far more robust.

Community investment fund

Project revenue flows into a locally governed fund that finances community-defined priorities — boats, clinics, scholarships, coastal defences. This turns abstract percentages into visible public goods, and it can outlast any single project. The snag is governance: without credible local structures and rotating leadership, funds can be captured by whoever is best connected.

Co-ownership of the project entity

Communities hold equity — shares in the SPV or trust that owns the credits. This aligns incentives the deepest and survives leadership turnover, because the community profits as an owner rather than a paid party. The snag is complexity: equity demands legal sophistication, patient capital and years of participation in decisions the community may not have asked to make.

In-kind and livelihood agreements

No cash share, but durable goods: new moorings, patrol boats, hatchery support, training credentials, guaranteed access to traditional harvest zones within the project's rules. These can carry more real value than cash in remote economies — but they are the easiest model to hollow out, because in-kind promises are hard to audit and easy to quietly redefine. Any in-kind commitment must be quantified, scheduled and tied to a breach mechanism.

Hybrid structures

Most credible projects blend the models: a floor revenue share plus a community fund plus governance seats plus local employment minimums. Hybrids survive the failure of any one component and let the community trade cash visibility against control.

The safeguards that make sharing real

Whatever the model, these are the guardrails that distinguish durable benefit-sharing:

  • Consent before design. Sharing designed without the community is not sharing. Free, Prior and Informed Consent (FPIC) is the floor — our FPIC and community rights explainer lays out what it demands in practice.
  • Tenure first. You cannot share what you do not resolve. Whose coast is it? The article on carbon rights and sea tenure covers the legal groundwork that must precede any contract.
  • Indigenous sea-country partnership by right, not invitation. On Indigenous estates, benefit-sharing moves a step further — from a stakeholder arrangement to a rights-holder arrangement, often with co-design or community leadership. The Indigenous benefit-sharing case explores this in depth.
  • Transparent arithmetic. Publish the share formula, the gross/net definition, the cost deductions allowed, and a worked example. If a project can't tell you what 100 credits sold at $30 delivers to the village, it doesn't know yet — or doesn't want to say.
  • Independent grievance and audit. A community appeal channel that doesn't run through the developer, and periodic third-party audits of the distributions themselves.
  • Permanence of the share, not just the carbon. The sharing commitment must survive refinancings, sales of the project, and management turnover. Put it in the project documents and the registry, not in the slide deck.

What buyers should ask

Buyers are the demand-side lever on all of this. Before retirement, ask four questions:

  1. Who negotiated on behalf of the community, and were they chosen by the community?
  2. What percentage of gross revenue reaches local hands, and is that in the legal documents?
  3. Which of the five benefit currencies flow — and which conspicuously don't?
  4. Who audits the distributions, and can we see the last one?

A project that answers cheerfully and specifically is usually telling the truth. A project that answers with adjectives is not. Our broader buyer's due-diligence guide pairs well here.

A note on Tidewright's own practice

Tidewright's projects are fictional and illustrative, but designed on these principles: every reef program includes a published community revenue floor, locally governed funds at sites like those described across our projects portfolio, and governance seats for coastal councils and Indigenous ranger partners through the Reef Partners program. Fictional or not, the structure is what any real project should be able to show on paper.

Key takeaways

  • Benefit-sharing spans five currencies — revenue, employment, assets, governance and ecosystem services — and strong projects share across several.
  • The robust models are gross-revenue floors, community funds, co-ownership and hybrid structures; pure in-kind promises are the most fragile.
  • The guardrails are FPIC, tenure resolution, Indigenous partnership of right, transparent formulas and independent audit of distributions.
  • Buyers are the fastest enforcement mechanism: ask for the formula, the percentage and the audit, and prefer the project with receipts.
  • Community benefit is not a co-benefit; it is the integrity infrastructure that makes the carbon itself last.

FAQ

Is there a standard percentage that should go to communities?

No single standard exists yet, and expectations differ by country and legal context. As a working benchmark, share structures below roughly 10 percent of gross revenue are increasingly viewed as thin; serious projects commonly commit 20 percent or more, or bind equivalent value into community funds and co-ownership.

Is benefit-sharing the same as "co-benefits"?

No. Co-benefits are the ecosystem services and jobs that a project incidentally delivers. Benefit-sharing is the contractual distribution of the project's value and power. A project can claim rich co-benefits while sharing nothing of its revenue.

Who should negotiate benefit terms on the community's side?

Representatives chosen by the community itself — ideally several, spanning fishers, women, youth and, on Indigenous estates, traditional owners with separate negotiating authority — supported by independent legal advice funded by the project but accountable to the community.

Can benefit-sharing fail even with good contracts?

Yes — through delayed payments, creative cost deductions, or governance capture. That's why audit rights, gross-revenue definitions and independent grievance channels matter as much as the percentage.

Does benefit-sharing apply to smaller restoration projects without credits?

It should. Any project that rules over a community's coast — even a publicly funded restoration — needs its own version of consent, local employment, and shared decision rights. The credit distinguishes how much cash there is to share, not whether sharing is owed.