Apr 23 2025

We’ve added retirement user and project type data to OffsetsDB

by
Grayson Badgley +Anderson Banihirwe +Kata Martin 
Grayson Badgley
Anderson Banihirwe
Kata Martin

We’ve expanded the functionality of OffsetsDB, our database that organizes offset data from five of the largest offset registries. Starting today, you can access two new types of data: standardized information about the organizations and companies using offsets, and improved information about project types.

Adding the retirement user data is a big change. Hardly a week goes by without someone emailing us asking how to figure out who benefits from retiring the offset credits sold by a particular project. It’s such a common question because it’s such an important question. A transparent offset market requires that we’re able to trace offset credits to companies and the specific claims (e.g., net zero) those companies make.

Unfortunately, the global carbon market doesn’t always make that easy.

Part of the problem is that there’s no requirement to disclose who’s using which offsets. Anyone who uses a voluntary offset to make an environmental claim has the option to publicly disclose that credit retirement. But most don’t. Of 1.34 billion credit retirements tracked in OffsetsDB, only 0.67 billion include information about who benefits from that retirement. In other words, we know next to nothing about who used roughly half the offset credits within the voluntary carbon market.

And the half we do have data for is a bit of a mess. Rather than existing in a single place, every registry has its own version of user data, with no consistency between how different registries keep their records. In fact, even individual registries don’t organize their own retirement user data in a consistent way.

Say you want to know how many credits Delta, the commercial airline, has retired. First, you have to gather retirement data from all the registries — there’s no guarantee Delta will have only purchased from one. Then you have to run multiple searches of those registries’ data, using a variety of different possible ways of writing the airline’s name. A retirement could be linked to “Delta,” or “Delta Airlines,” or “Delta Air Lines.” In fact, Delta often retires credits under “DL,” which is its airline code used for its flight numbers. Lack of standard schema makes it painstaking to answer even simple questions about trends in offset usage. It also doesn’t help that we’re constantly getting new retirement data with no guarantees about what format that data will use.

Suffice it to say, none of this is good for market transparency.

Retirements
transactions
View in OffsetsDB

Our updates to OffsetsDB bring both increased standardization and searchability to user data. For this initial release, we used a mostly manual process to pull information from offset registries and fit it to a common format. While we’ve automated parts of the process, we foresee some amount of manual intervention going forward. In fact, this first release only standardizes a little over two-thirds of the 0.67 billion classifiable credits in the database.

It’s a big lift, but we think it’s worth the ongoing effort. Claims backed by offsets can’t be taken seriously if there’s no way to tie them to specific credits that come from specific projects. With that in mind, we’re excited to see standards bodies within the carbon market, such as ICVCM and SBTi, start to advocate for full, complete, and standardized disclosures of retirement user data. Hopefully, over the long term, this will make user data less messy — and make our job easier.

Our other change to OffsetsDB is smaller in scope, but still important. Previously, you could search OffsetsDB by project categories — broad groupings of projects, like Forests or Renewable Energy. We’ve now added project types that further refine those categories, allowing more precise searches. So rather than looking at everything categorized as Forest, you can now distinguish reforestation projects from improved forest management projects.

Project types
78
Categories
12
Berkeley-typed projects
9,903
Newly-typed projects
113
Total projects
10,361

While the distinction between categories and types might seem minor, it takes a fair amount of work to assign projects to their appropriate type. OffsetsDB originally sorted projects into categories based on their protocol. But a protocol such as ACM0002 — Grid-connected Electricity Generation from Renewable Sources — could include electricity generated by wind, solar, or hydroelectric facilities. To sort these projects by type, we have to turn to project specific paperwork. And there is a lot of paperwork to go through — OffsetsDB tracks more than 10,000 projects.

Thankfully, we didn’t have to start from scratch. That’s because the folks over at the Berkeley Carbon Trading Project maintain a similar offsets database that already contains detailed information about project types. And, what’s more, they publish their project-type information using a permissive license, which means we can freely incorporate their work into OffsetsDB. That’s wonderful because project-type data is the sort of thing you only need to create once. This underscores the value we see in open science — once someone classifies a project and shares the data, no one else should ever have to do that work again.

As with previous installments of OffsetsDB, you’re free to access the data both through our the browser-based database tool or by downloading the data and playing around with it yourself. Keep track of our progress on GitHub or reach out at hello@carbonplan.org if you have any questions.


Questions? Interested in collaborating on these problems?
email us
EMAIL
hello@carbonplan.org
NEWSLETTER
Subscribe
CarbonPlan is a registered nonprofit public benefit corporation in California with 501(c)(3) status.
(c) 2025
CARBONPLAN
TERMS OF USE
/
PRIVACY POLICY
SCROLL: 0.00
661b819