The GHG Protocol and Why Scopes Exist

Before there was a common way to count corporate emissions, every company that bothered to measure did so differently, which made the numbers useless for comparison. The Greenhouse Gas Protocol, developed by a partnership of the World Resources Institute and the World Business Council for Sustainable Development beginning in the late 1990s, solved that coordination problem. It is not a law. It is a standard, a shared set of accounting rules, and its authority comes from near-universal adoption. Almost every corporate climate disclosure, every regulatory reporting regime, and every carbon target you will encounter is built on its definitions. Learning it is like learning double-entry bookkeeping: unglamorous, foundational, and non-optional.

The Protocol's central move is to divide emissions into three scopes based on how directly the reporting company controls the source. This matters because a naive count would either miss most of a company's real climate impact or double-count emissions across the economy. The scope structure is designed to let each company take responsibility for a defined slice while making clear where the boundaries lie.

Scope 1 is direct emissions from sources the company owns or controls. For a data center, Scope 1 is comparatively small: the diesel burned by backup generators during outages and testing, the natural gas for any on-site heating, refrigerant leaks from cooling systems, which matter more than people expect because many refrigerants are potent greenhouse gases, and fuel for company vehicles. A pure data center with a clean grid connection has modest Scope 1 emissions. But note the exception that is growing in importance: facilities that install on-site gas generation to escape grid interconnection queues are pulling large combustion emissions directly into their Scope 1, and that is becoming visible and contested.

Scope 2 is indirect emissions from the generation of energy the company purchases and consumes, overwhelmingly electricity for a data center. This is where the action is. A large facility's electricity draw, run through the carbon intensity of its regional grid, produces by far its largest operational emissions. And here the Protocol makes a subtle but crucial distinction between two accounting methods. The location-based method multiplies your consumption by the average emissions intensity of the local grid, an honest picture of the physical electrons you are pulling. The market-based method lets you reflect contractual instruments, renewable energy certificates and power purchase agreements, that assign specific low-carbon generation to your consumption. A company can report a near-zero market-based Scope 2 while its location-based Scope 2 remains substantial, because the physical grid it draws from is still largely fossil-fueled. Both numbers are legitimate and the Protocol requires disclosing both, but they answer different questions, and the gap between them is where much of the honest debate about corporate climate claims now lives.

Scope 3 is everything else: all the indirect emissions across the value chain that the company does not own. For a data center operator this is frequently the largest scope of all, and the hardest to measure. It includes the embodied carbon in the servers, network gear, concrete, and steel that build and fill the facility, the emissions of the supply chain that manufactures them, the upstream extraction and processing of the fuels burned to make the electricity, employee commuting and business travel, and, for cloud providers, sometimes the emissions associated with customers' use of the service. Because Scope 3 spans the whole economy, one company's Scope 3 is another company's Scope 1 or 2, which is why cross-company totals cannot simply be added up without double-counting. The Protocol organizes Scope 3 into fifteen defined categories to bring order to this sprawl.

Why does an infrastructure practitioner need this taxonomy? Because the scope in which an emission falls determines who is accountable for it, how it must be reported, and increasingly whether it can be regulated. A rule that targets Scope 1 and 2 hits your operations directly. A rule that reaches Scope 3, and disclosure rules are moving in that direction, reaches your entire supply chain and construction footprint. Faraday's read: the scopes are not accounting trivia. They are the map of your climate liability, and the boundaries between them are exactly where the disclosure fights and the greenwashing accusations play out. Know which bucket every major emission falls into, and know the difference between your location-based and market-based numbers cold, because someone who matters will eventually ask.