Your IT emissions are probably an estimate.
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 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.
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.
Your IT emissions are probably an estimate. Under the EU's CSRD rules, software's electricity is already in your numbers. Your own servers sit in Scope 2. Cloud and software services sit in Scope 3. But most firms copy a supplier's statement, or estimate from what they spend. So they cannot say which applications use the energy. And an estimate can only be restated, not reduced. Here is the fix you can use today. Measure the energy of your biggest applications, under a defined workload. Report it with the Software Carbon Intensity method, now an ISO standard. State the boundary, and how shared energy is split. And say whether each figure is measured or estimated. The W3C suggests that companies report the emissions of their digital services openly. For cloud use, estimate from billing data using tools like Cloud Carbon Footprint. GreenCode helps tackle this by tying each energy figure to its exact version and test. It states the split rule and its confidence, so every figure can be traced. That was GreenCode Tech Tip number twenty-three. Follow for the next tip, and find more on greencode.ai/tech-tips.
Share this
