top of page
Search
Blog cover: grievances that leave a trace, beside the grievance screen of the CitizenClimate app in an empty demo state

Carbon project grievance mechanism: what makes one credible

Writer: Nick
Nick
Nov 10
9 min read

A carbon project grievance mechanism is the formal route by which people affected by a project can raise a concern and get a response they can follow. It is credible when the people it serves know about it and trust it, when each complaint moves through clear stages with a recorded outcome, and when someone independent can check that complaints were handled fairly. Most major carbon standards ask projects to run one.


This guide sets out the test most practitioners use, what the standards ask for, and what a grievance record needs to keep so that a community and a verifier can both see it working. It sits in our series on community-led dMRV, because a complaints channel is part of the evidence a project produces, not an add-on.


What a carbon project grievance mechanism is for

Carbon projects change how land is used and how money flows in places where people live. Restrictions on grazing or firewood, disputed boundaries, late or unclear benefit payments and broken equipment are ordinary sources of complaint. A project-level grievance mechanism gives those complaints somewhere to go before they turn into conflict, and gives the project developer an early warning that something in the design is not working.


It also matters for the credits themselves. A project that cannot show how it handled complaints from first report to close is harder to defend when questions arise later.


The record shows something else too: whether the mechanism is used at all. A channel that exists on paper but has never received a complaint in a large project is itself a finding worth asking about.


The test: the UN Guiding Principles' seven criteria, plus one

The common yardstick is Principle 31 of the UN Guiding Principles on Business and Human Rights, published by OHCHR in 2011. It says non-judicial grievance mechanisms should be legitimate, accessible, predictable, equitable, transparent, rights-compatible and a source of continuous learning. Mechanisms run at operational level, which is what a project developer's channel is, should also be based on engagement and dialogue.

Stat card: 7 + 1 criteria that make a grievance mechanism effective, from UN Guiding Principle 31
Principle 31 of the UN Guiding Principles (OHCHR, 2011): seven criteria for all non-judicial mechanisms, plus engagement and dialogue for operational-level ones

The table turns each criterion into a practical question for a carbon project. The middle column paraphrases the Principle; the right-hand column is our suggestion for evidence a reviewer could ask to see.


Criterion

What it asks, in short

Evidence a project can show

Legitimate

Trusted by the people it serves, and accountable for fair handling

Who handles complaints, and how conflicts of interest are avoided

Accessible

Known to everyone it is meant for, with help for those facing barriers

Channels in local languages, with and without a phone; records of how people were told

Predictable

A clear procedure with an indicative time frame for each stage

Published stages and target times, and dates recorded at each stage

Equitable

Fair access to information, advice and expertise

How complainants can get support or representation

Transparent

Parties kept informed; enough performance information to build confidence

Status visible to the complainant; summary figures shared with the community

Rights-compatible

Outcomes and remedies accord with internationally recognised human rights

Resolution notes that say what was done, not only "closed"

Continuous learning

Lessons used to improve the mechanism and prevent future harm

Recurring themes reviewed, and design changes recorded

Engagement and dialogue

Users consulted on design and performance; dialogue as the main route

Minutes of the consultation where the channels were agreed


Most of the right-hand column comes down to records: dated statuses and resolution notes, kept so that a complaint cannot quietly disappear. That is where field data practice and safeguards practice meet.


What the carbon standards ask for

Each standard words its rules differently, and they change. Treat the summaries below as pointers and check the current version before relying on them.


Gold Standard. Its Stakeholder Consultation and Engagement Requirements, version 2.1 (released 14 June 2022, as listed on Gold Standard's requirements page) require all projects to set up a formal input and feedback, and grievance mechanism, so that stakeholders have a way to submit input. The minimum named in the requirements is the Continuous Input and Grievance Expression Process Book; other routes, such as telephone or email, can sit alongside it.


Plan Vivo. The PV Climate Project Requirements, version 5.7, give the grievance mechanism its own section (3.17). The mechanism must be accessible and culturally appropriate, all issues raised through it must be documented, and it must be described in each Project Agreement. Clause 3.17.3 says that, where possible, grievances "should be reconciled by the affected parties"; where that is not possible, the mechanism "must identify an independent arbitrator" to mediate a resolution. The same document links the mechanism to consent: rights holders must be able to raise consent issues through it throughout the project period. Our Plan Vivo alignment page covers the wider standard.


Verra. Verra runs its own programme-level route for complaints. Its notice of 13 December 2023 says complaints "may be submitted anonymously" and that Verra "will not charge fees for processing complaints"; in October 2026 Verra replaced that policy with its Grievance Redress Process, version 2.0, so check the new text before relying on the 2023 terms. Separately, Verra has moved the effective date of VCS Version 5 to 1 July 2027. Project teams should read the project-level rules on stakeholder engagement and grievance redress in the version that applies to them, rather than rely on summaries.


The Article 6.4 mechanism. Under the Paris Agreement's crediting mechanism, the Supervisory Body adopted an appeal and grievance procedure (version 01.0) that took effect on 2 May 2024, as the UNFCCC announced. A summary by Slaughter and May, written on 28 May 2024, notes that under that text grievances about approved activities carry no filing fee and no time bar, and that the panel's findings are recommendations rather than binding decisions. The summary describes the 2024 text; the Supervisory Body revises its procedures, so check the current version on the UNFCCC rules and regulations page.


How well do the standards' own mechanisms work? A 2023 review commissioned by Carbon Market Watch found that only Gold Standard gave communities affected by projects appropriate recourse. The 2024 update, written by Perspectives Climate Group, recorded improvements but concluded that serious shortcomings persist.


Two levels: the project's channel and the standard's

A credible set-up has at least two routes, and people should know about both.


The first is the project's own mechanism, run by the developer or coordinator. It handles everyday complaints quickly and close to where they arise. Its weakness is obvious: the organisation being complained about is often the one answering.


The second is the standard's mechanism, and for Article 6.4 activities the UN procedure. It sits outside the project and can be used when the project route fails or cannot be trusted. Its weakness is distance: it is harder to reach for someone in a remote village, and usually works in a few languages.


The two levels need each other. The project channel should tell people, in plain terms, how to escalate. And when someone does escalate, the project's own record of what happened is the first thing anyone will ask to see.


What a credible grievance record keeps

Whatever tool a project uses, a paper book, a hotline log, a spreadsheet or an app, the record should answer the same questions. What was raised, and when? Which community did it come from? What stage is it at? Who responded, and with what outcome? Can any of that be changed afterwards? Who outside the project can read it?


Here is how one tool handles those questions. The CitizenClimate app has a grievance screen, described in the App Guide and the Data Integrity and Methodology Protocol (October 2026). A community member taps "File a Grievance" and gives a title and a description. The grievance is tracked with a status, "Pending → Under Review → Resolved", and the project developer can reply with a resolution note that the member sees when they open it. Other members can vote grievances up or down, which helps the developer prioritise.

CitizenClimate demo project grievance screen with a case history, Under Review statuses, resolution notes and votes
Illustration: grievance screen in the CitizenClimate demo project. The project, villages, cases, dates and votes are simulated.

Three properties matter for the criteria above:


  • Permanence, within limits. The Protocol states that "Grievances can never be deleted", and that the title and description cannot be changed after creation, nor can the creation date or the community. The date the developer responded and the date the grievance was resolved are set automatically. The status and the resolution note are updated by the project developer as the case moves on.

  • Anonymity. The App Guide says the member's "name isn't shown to the project developer or to other members". The community of origin is recorded for context, and votes are aggregated so individual voting is not visible.

  • Verifier access. VVBs, the independent auditors, have a read-only role. The Protocol says they "can read all grievances across a project, including the full history of status changes and resolution responses", which "provides an independent view of whether community concerns are being addressed in good faith and within a reasonable timeframe".

Diagram of a grievance record moving from Pending to Under Review to Resolved, then read by the VVB
How a grievance is recorded, from the CitizenClimate Protocol (October 2026), sections 4 and 8

Our Philippines indigenous forest use case shows how grievance tracking can be set up alongside SDG and biodiversity surveys for a REDD+ project. It describes a survey design, not measured results.


What this kind of record does not do matters as much. An in-app channel is run by the project developer, so it does not replace the standard's independent mechanism or an arbitrator. It needs an enrolled member with a phone or computer, so it should sit alongside a book, a meeting or a trusted person for those without one. Whether a project's mechanism satisfies a standard is for that standard and the verifier to judge.


Common failures, and how to avoid them

These are common design weaknesses in project-level mechanisms, and most can be fixed before the first complaint arrives.


  • Nobody knows it exists. Explain the channels in local languages at consultation meetings, and again when monitoring starts. Record that you did.

  • One channel only. An email address or a single phone number excludes many of the people most affected. Pair written and spoken routes with digital ones.

  • No time frames. Publish target times for acknowledging and resolving complaints, and record the dates so anyone can see whether they were met.

  • Complaints that can be deleted or reworded. If the original complaint can be edited or removed, a reviewer has no way of knowing what was taken out. Keep the complaint as it was raised, and record each later step alongside it.

  • Fear of retaliation. Offer an anonymous route, and remember that in a small community a detailed description can identify the person who wrote it. Say so plainly when you explain the channel.

  • "Resolved" with no explanation. A resolution note should say what was done and whether the complainant accepted it.

  • No way up. Tell people how to reach the standard's mechanism if the project route fails.


Frequently asked questions

Is a grievance mechanism required for carbon projects?

Under the standards covered here, yes. Gold Standard requires all projects to set up a formal input and grievance mechanism, and Plan Vivo's PV Climate requirements give it a dedicated section, including an independent arbitrator where the parties cannot settle a grievance themselves. Requirements differ in detail and change between versions, so check the current text of your standard before designing the mechanism.


Can carbon project grievances be anonymous?

They can, and the UN Guiding Principles' focus on legitimacy and accessibility supports it, because fear of retaliation keeps many people silent. Verra's 2023 grievance policy said complaints may be submitted anonymously. In the CitizenClimate app, a member's name is not shown to the project developer or other members, though the community of origin is recorded. Anonymity can make follow-up harder, so explain the trade-off.


What is the difference between a project grievance mechanism and a standard's grievance process?

The project mechanism is run by the developer or coordinator and handles everyday concerns close to where they arise. A standard's process sits above it: stakeholders can complain to the standard directly, and it is the route to use when the project channel fails or cannot be trusted. A credible set-up tells people about both and how to move from one to the other.


What do verifiers look for in a grievance mechanism?

Verifiers generally want to see that the mechanism was agreed with stakeholders, that people know about it, and that complaints were logged and closed with a recorded outcome. Dated stages, resolution notes and complaints that cannot be deleted make that easier to check. Direct read access to the grievance record means a verifier does not have to rely on a summary prepared by the developer.


Start with the record

A grievance mechanism earns trust through what it records and who can see it. If you are designing a carbon project grievance mechanism, or one for a nature project, the CitizenClimate app gives each community member an anonymous grievance channel whose records cannot be deleted and which your verifier can read. Download the free app, or read the App Guide to see how the grievance screen works.

Comments


bottom of page