Reading a carbon project document without taking it on trust

21 September 2026

The only way to know whether a tokenised carbon credit actually represents a tonne of avoided or removed emissions is to read the project document that sits behind it. A project document is the public file a developer submits to a registry such as Verra or Gold Standard. It describes what the project does, where it is, how it calculates its emissions reductions, and how it proves those reductions are real and permanent. You can read these documents yourself without being a climate scientist. This page explains what to look for in a project document, what questions to ask, and which red flags suggest the credit is more marketing than substance.

Where to find the document

Every carbon credit token issued on a registry has a unique serial number or project ID. If a tokenised credit does not link to a registry ID, treat it as unverified. For Verra projects, go to the Verra Registry and search by the project ID number. For Gold Standard, use the Gold Standard Impact Registry. The project document is usually a PDF. It will be long, often 50 to 200 pages, but you do not need to read every word. Focus on the sections that describe methodology, baseline, additionality, and permanence.

Step 1: Check the methodology

The methodology is the recipe the project uses to calculate how many tonnes of CO₂ it has avoided or removed. Every credit must reference an approved methodology from the registry. Look for the methodology name and version number. Common categories are:

• Renewable energy: replaces fossil-fuel electricity. Often uses a grid emissions factor.
• Forestry or land use: measures carbon stored in trees or soil. Often uses growth models.
• Methane capture: captures methane from landfills or livestock. Uses a conversion factor from methane to CO₂ equivalent.

If the methodology is missing, vague, or not from the registry’s approved list, the credit may not be valid. If the methodology is a generic one that does not fit the project type, that is also a red flag.

Step 2: Understand the baseline

The baseline is the hypothetical scenario of what would have happened without the project. The credit represents the difference between that baseline and the project’s actual emissions. A credible baseline must be conservative - meaning it should not overstate what would have happened.

For example, a forestry project might assume the land would have been cleared for farming. If the land was already protected by law, the baseline is unrealistic. Look for a section called “baseline scenario” or “without-project scenario.” Ask yourself: Is the baseline plausible? Is it supported by local data or government policy? If it relies on assumptions that seem convenient, the credits may be inflated.

Step 3: Verify additionality

Additionality means the emission reductions would not have happened without the carbon credit revenue. A project that would have been built anyway - because it is profitable, legally required, or already funded - does not produce real credits.

The project document should include an additionality assessment. Common tests include:

• Investment analysis: shows the project is not profitable without carbon revenue.
• Barrier analysis: identifies regulatory, technological, or financial barriers that the revenue overcomes.
• Common practice analysis: shows the project type is not already standard in the region.

If the additionality section is missing or uses generic language, the project may not be additional. If the project is a solar farm in a country that already subsidises solar, it likely fails additionality.

Step 4: Assess permanence and leakage

Permanence matters most for forestry and land-use projects. Carbon stored in trees can be released by fire, disease, or logging. The project document should explain how it manages these risks. Look for:

• Buffer pools: a percentage of credits set aside to cover reversals.
• Monitoring plans: how often the project checks for loss of carbon.
• Insurance or replacement obligations: what happens if carbon is released.

Leakage means the project shifts emissions elsewhere. For example, protecting a forest may cause logging to move to a neighbouring area. The document should account for leakage and deduct it from the credit calculation.

Step 5: Look for third-party verification

A project document is the developer’s own description. It must be verified by an accredited third-party auditor. The registry will list the verifier’s name and the verification date. Check that the verifier is independent - not owned by the developer or a related company. A recent verification is better than one from several years ago, because conditions on the ground change.

Red flags that suggest marketing over substance

• No registry ID or a link that leads to a generic page.
• Vague project location: “Southeast Asia” is not specific enough.
• Claims of “net-zero” or “carbon negative” without a clear calculation.
• Credits from avoided deforestation that were issued before the project started.
• Methodology older than five years that has not been updated.
• No mention of buffer pools for forestry projects.
• Project developer is also the verifier or shares a parent company.

What a real claim looks like

A real claim from a tokenised carbon credit will include a direct link to the registry page for that specific credit. The project document will be publicly available, and the methodology will match the registry’s approved list. The baseline will be conservative, additionality will be tested, and permanence risks will be addressed. You will be able to read the verification report and see the verifier’s name. None of this guarantees the project is perfect, but it means the credit is backed by a process that other parties can check.

Reading a project document is not a quick job. It takes time and a willingness to look past the marketing. But it is the only way to know whether the tokenised credit you are looking at represents real emissions reductions or just a piece of paper that says it does.

Back to carbon credits