Release notes December 2025

Benchmarking

We have introduced a Benchmarking feature which allows companies to compare their carbon footprint to their peers. The Benchmarking feature can be found under Analyse in the sidepane.

Companies can be compared on total emissions, emissions per full-time equivalent (FTE), or emissions per turnover. The data used for creating the benchmarks is based on emissions reported in Carbon+Alt+Delete. This data is of course completely anonymised and we invite all companies to fill in the benchmarking details to further improve this feature.

Read more about the methodology behind Benchmarking here and you can find detailed instructions on how to use the feature here.

Company Templates

Setting up new company accounts just got a lot easier. You can now pre-define all the boundaries of different company setups in Company Templates. Administrators will be able to find this feature in Consultancy Settings.

As you can set all boundaries (including custom fields and business metrics), there are many different applications of this, including but not limited to:

• Making country-specific templates by setting specific preferred datasets and translating activity categories
• Re-structuring activity categories and setting up new elements to track specific activities (e.g. Purchased Water and Waste Water)
• Setting up standards for custom fields and business units

You can read more about Company Templates in this article.

Ademe v23.6

We've updated our emission factor database to ADEME Base Carbone v23.6. This update includes:

• Updated emission factors across all categories, including electricity, energy, industrial emissions, heat and steam and activity-based and spend-based goods
• Tailored biogenic and land-related readout
• Improved geographic coverage for French activities and domains

This ADEME v23.6 is also being released under a new approach, where the previous version remains available in the app in the factor library, for import via reference and in all historical entries. This approach should smoothen out version issues for databases with large discontinuities.

AI Import improvements

We’ve significantly enhanced the AI Import Engine to deliver more accurate and efficient data processing.

The activity category matching logic has been improved, increasing overall matching accuracy. More reliable activity category identification also leads to better Emission Factor (EF) matching, resulting in higher-quality outputs and fewer manual corrections.

These improvements translate into greater efficiency for consultants, reducing time spent on reviews and adjustments while improving overall confidence in imported data.

We will continue to refine the AI Import Engine to further increase accuracy, automation, and performance in upcoming releases.

Minor updates & fixes

• Open CEDA and Ademe import tempaltes and factor references available on support pages
• Fixed an issue where report generation could fail depending on consultancy logo

API Updates

What's new

1. GET /accounts/v1/template-companies  Get Template Companies
2. POST /accounts/v1/template-companies  Post Template Company
3. GET /accounts/v1/template-companies/{template_company_id}  Get Template Company
4. PUT /accounts/v1/template-companies/{template_company_id}  Put Template Company
5. DELETE /accounts/v1/template-companies/{template_company_id} Delete Template Company
6. POST /accounts/v1/template-companies/{template_company_id}/duplicate Post Template Company Duplicate
7. POST /benchmarks/v1/benchmark-results-query  Post Benchmark Results Query
8. POST /value-mappings/v1/value-mappings  Post Value Mapping
9. POST /value-mappings/v1/value-mappings/batch  Post Value Mappings Batch
10. PUT /value-mappings/v1/value-mappings/{value_mapping_id}  Put Value Mapping

What's deleted

1. POST /emission-factors/v1/value-mappings
   • Replaced by: POST /value-mappings/v1/value-mappings
2. POST /emission-factors/v1/value-mappings/init
   • Replaced by: POST /value-mappings/v1/value-mappings/batch
3. PUT /emission-factors/v1/value-mappings/{value_mapping_id}
   • Replaced by: PUT /value-mappings/v1/value-mappings/{value_mapping_id}

What's changed 

1. New property in Company object
   1. companyStatus
   2. createdAt