Consent Before Credits: FPIC and Community Rights in Blue Carbon Projects

A blue carbon project begins before any survey dives or credit methodologies — it begins with a question: who has the right to say yes or no to what happens in this water? Get that question wrong, and a project that might restore meadows and fund coastal livelihoods becomes something else entirely: extraction wearing a green label.

The standard that answers the question is FPIC — free, prior and informed consent — a principle rooted in Indigenous rights and increasingly applied to local communities generally in land- and seascape-scale projects. This guide explains what each of the four words demands in the specific context of a blue carbon project, what happens when projects shortcut them, and how consent stays meaningful across a multi-decade crediting period. It's a companion to our overview of benefit sharing on sea country and the wider integrity requirements for nature-based solutions.

Defining the four words in coastal practice

FPIC is usually treated as a single checkbox. Each word is its own obligation:

Free means consent is given without coercion, manipulation or time pressure. Asking a fishing cooperative to decide before the end of the month because "the grant window closes" fails this test no matter how friendly the meeting is. Funding calendars must adapt to community decision-making timelines, not the other way around.

Prior means consent is sought before project decisions are locked: before the site is chosen, before the funding application names a location, before the registry submission defines a boundary. Consultation about a decision already made is not consultation; it is notification with better catering.

Informed is the most concrete and most often botched. Genuine information for a blue carbon project includes: the activity and its physical footprint; what rights the community keeps and yields (mooring areas, fishing access, harvest rights); the revenue model in plain numbers — gross credit revenue, costs, what flows to the community, when; the risks, including the possibility of failure and the obligations that survive failure; and the monitoring that will watch the site, explained in plain language. If the explanation requires a law degree to follow, the community has not been informed.

Consent means a collective decision through the community's own legitimate decision-making process — which may be a traditional owner group with its own governance structures, an elected council, a cooperative assembly or some combination. Consent is also ongoing: credible frameworks treat it as renewable and revocable through defined checkpoints, not a signature captured once at the start.

Who must be asked: mapping the rights holders

Coastal zones stack rights like sediment layers. A robust project maps:

• Indigenous and traditional owners with recognised or customary rights to sea country. In many jurisdictions — Australia, Canada, New Zealand and elsewhere — these rights carry specific legal weight, and Indigenous-led or co-governed projects are increasingly the norm for credible developers.
• Customary users without formal title: fishers, gleaners, harvesters whose livelihoods depend on the site.
• Statutory stakeholders: councils, fisheries and harbour authorities where access or licencing will change.
• Future rights holders: younger generations, and the question of who signs on their behalf over a 30-year crediting period.

Miss one layer and the project carries a structural fault line. The blue carbon project cycle stage where faults like this emerge is "feasibility" — which is exactly where rights mapping belongs.

What goes wrong when consent is shallow

The failure modes are well documented across nature-based projects generally, and blue carbon inherits them:

• Consent by elite: a project secures signatures from a charismatic individual or a body without genuine community mandate. Later disputes reveal the signature meant little.
• Consent without economics: communities agree to "benefit sharing" without knowing the price per credit or the project costs — then discover the community share of a small net figure is smaller still. Informed consent demands the spreadsheet.
• Consent once, enforced forever: a community that loses confidence mid-project faces a signed agreement and no mechanism to revisit it. Projects without revocation checkpoints systematically overrate their initial consent quality.
• Consent to a different project: the community agreed to seagrass restoration and ranger employment; the delivered project is a monitoring platform and a carbon desk thousands of kilometres away. Scope drift is consent erosion.

Carbon-market integrity frameworks now encode versions of FPIC and community benefit requirements — for a general map, see Core Carbon Principles explained — and major standards require documented stakeholder engagement as a crediting condition. Yet the frameworks set a floor, not a ceiling; good projects treat them as the start of a conversation, not the end.

What good looks like: a working pattern

A well-structured blue carbon consent process for, say, a seagrass restoration project typically looks like:

1. Early presence, no ask. Project team spends time at the site discussing community concerns and ambitions before any proposal exists. Months, not weeks.
2. Co-design. The project boundary, activities and revenue share are built with community bodies, including the option to say no to specific elements (e.g., "credit issuance, yes; restricted-access zones, no").
3. Plain-language documentation. Materials in local language, with independent advice funded for the community — paying for the community's own lawyer and scientist is now regarded as good practice.
4. A formal agreement covering rights, revenue shares, employment and training commitments, monitoring of the agreement itself, and dispute pathways.
5. Renewable checkpoints: consent reviews at defined intervals — some frameworks operate on roughly 3–5 year cycles — with a real possibility of renegotiation or exit by the community.

This takes longer than a pitch-deck schedule likes. Projects that budget the time upfront deliver projects that survive; projects that don't tend to deliver case studies in what not to do.

Why this is a buyer's issue, not just a developer's

Buyers of blue carbon credits carry the consent record in ways they might not expect. Corporate net-zero claims rest on credits; credits rest on project legitimacy; legitimacy rests on whether the people of the place agreed. Reputational exposure travels through the supply chain efficiently — ask any brand that has faced questions about land-based offset projects with contested consent. Our primer on reading corporate ocean claims honestly explains how this shows up in public reporting.

Due-diligence questions a buyer can reasonably ask a blue carbon developer: Who consented, and through what process? What share of net revenue reaches the community, and when? What are the consent checkpoints, and has the community ever exercised one? Can I talk to the rights-holding body directly? A confident developer answers these easily; they are, after all, the answers any honest project keeps close at hand. Tidewright's fictional program work with coastal communities is written to this pattern — shared ownership, renewable consent, and benefits visible on the ground.

Key takeaways

• FPIC is four separate obligations — free, prior, informed, consent — and each can be failed independently of the others.
• Rights in coastal zones stack across Indigenous title, customary use and statutory access; mapping them is feasibility-stage work.
• "Informed" requires the economics in plain language, not just ecology; consent without revenue numbers isn't informed consent.
• Consent is ongoing: credible projects build renewal checkpoints and defined revocation pathways into multi-decade agreements.
• Buyers inherit the consent record; asking consent questions is standard due diligence, not activism.

FAQ

Does FPIC apply to all coastal communities or only Indigenous peoples?

FPIC as a defined right attaches to Indigenous peoples under international instruments, but its principles are widely adopted as good practice for all project-affected communities, and several carbon standards apply stakeholder-consent requirements broadly regardless of title status.

Who pays for the community's independent advice?

Good-practice projects fund it — an independent lawyer and, where needed, scientist, chosen by the community. The cost is minor next to project development budgets, and the conflict-of-interest alternative (project-paid advisers assigned to the community) can poison consent legitimacy.

Can consent be withdrawn once given?

Under strong frameworks, yes, through defined checkpoints and dispute processes — and projects acknowledging that possibility plan accordingly with insurance and staged commitments. Agreements with no exit path should alarm buyers.

What share of carbon revenue should communities expect?

There is no settled rule; it varies with project costs, tenure structure and who delivers the work. The honest benchmark is transparency: a clear waterfall of gross to net to community share, stated before consent is sought, and audited after.

Doesn't FPIC slow down urgently needed restoration?

Consent processes take months to a year or more, and that's the price of legitimacy. Projects built on shallow consent regularly lose more time to disputes, protests and withdrawal than co-design ever would have cost. The ocean deserves restoration; communities deserve restoration done with, not at, them.