The problem

Under CSRD, software's electricity already sits in Scope 2 (your servers) and Scope 3 (cloud and SaaS). Most organisations report it from a supplier's statement or a spend-based estimate and can't say which applications drive it.

The fix you can use today

• Measure energy for your biggest applications under a defined workload.
• Report with the Software Carbon Intensity method (ISO/IEC 21031:2024).
• State the boundary, the allocation rule and whether each figure is measured or estimated.

The W3C suggests that companies report the emissions of their digital services openly. GreenCode ties each energy figure to the exact version and test that produced it.

Tools that help

• Software Carbon Intensity (SCI) (Green Software Foundation): the Green Software Foundation's method, SCI = ((E x I) + M) per R, adopted as ISO/IEC 21031:2024
• Cloud Carbon Footprint: estimates the energy and emissions of AWS, Azure and Google Cloud usage from billing and usage data

How GreenCode helps

GreenCode helps tackle this by tying each energy measurement to a specific version, configuration and test run. It states the allocation rule and confidence, so a reported figure can be traced back to what produced it. More on this.

Tags

#esg#standards#reporting

Sources

• Accurate ESG data for CSRD reporting
• W3C, Web Sustainability Guidelines: transparent reporting of digital emissions

All GreenCode Tech Tips