Tinkerer

Code and Climate Change. Blog about software development in ClimateTech RSS Icon


Carbon Accounting for Software Developers

I’ve previously written about that I think having domain knowledge as a software developer is tremendously important, and really helps you be effective in your role.
As I currently work with carbon emissions and carbon accounting at Climatiq, I figured I’d put together a little reading list of what to read in this space if you’re a software developer / software engineer looking to get a little more domain knowledge.

Carbon Accounting

For corporate carbon accounting, the standard to read is the Greenhouse Gas Protocol Corporate Standard. This standard explains the different reasons behind doing corporate carbon accounting, and sets out guidelines and requirements for doing so. I would recommend reading (or at least skimming) the entire thing in full. This is the text to read when understanding the carbon accounting space.

Greenhouse Gas Protocol (GHGP) also publishes other standards & guidance documents, like guidance for calculating Scope 2 and 3. I have not read all of these myself, but I’d consider them relevant to skim if you’re doing work that deals with one of those areas in particular. In particular I think the Corporate Value Chain (Scope 3) standard is worth skimming.

Here’s also a few notes of things I thought were particularly interesting or important regarding corporate carbon accounting.

General



Scopes

Allocations

Electricity

Product Carbon Footprints

Corporate Carbon Accounting is one thing, that works at a corporate level. Another area is Product Carbon Footprints (PCF) which tries to calculate the carbon emissions of a single product.

Product Carbon Footprint is governed by multiple different standards that agree on most things but not all things, which is a royal pain in the ass.

As before, here are a few of my personal notes:

  1. Quote from the Greenhouse gas protocol: Use of this standard is intended to enable comparisons of a company’s GHG emissions over time. It is not designed to support comparisons between companies based on their scope 3 emissions. Differences in reported emissions may be a result of differences in inventory methodology or differences in company size or structure. Additional measures are necessary to enable valid comparisons across companies. Such measures include consistency in methodology and data used to calculate the inventory, and reporting of additional information such as intensity ratios or performance metrics. Additional consistency can be provided through GHG reporting programs or sector- specific guidance 

  2. Remember when I said that carbon accounting was like modeling the world? Turns out that’s a lot harder if you have to do it through sending PDFs in emails. 

Did you enjoy this post? Please share it!