Scopes, Boundaries, and What Counts

Carbon accounting is the discipline of counting, honestly and in a standardized way, the greenhouse-gas emissions a project causes. Its reputation for tedium is undeserved, because underneath the frameworks lies a simple and consequential question: when you say a campus is clean, exactly which emissions are you counting, and which are you conveniently leaving out? The frameworks exist to stop people from answering that question differently every time it is asked.

The organizing idea is the division of emissions into three scopes, a convention widely used in corporate carbon reporting. Scope one covers emissions from sources the operator directly controls and burns on-site. For a data center, the largest scope-one source is usually backup generation — the diesel or gas generators that run during grid outages and testing. Scope two covers emissions from purchased electricity: the power drawn from the grid to run the servers and cooling. For most data centers, scope two is the giant, because these are electricity-hungry buildings. Scope three covers everything else in the value chain that the operator does not directly control: the emissions embedded in constructing the building, in manufacturing the servers, in the supply chain, and more. Scope three is the hardest to measure and, for a data center, often larger than people expect once construction and hardware are included.

The reason the scopes matter for our purposes is that they define the boundary of the claim, and boundaries are where honesty is won or lost. A campus that reports only scope two — and reports it using annual average grid data — can tell a flattering story while ignoring the diesel it burns in outages and the mountain of embedded carbon in its concrete. A campus that accounts across all three scopes tells a fuller and less flattering but more durable story. As disclosure requirements tighten and customers demand supply-chain accountability, the narrow boundary becomes a liability. The trend is unmistakably toward wider boundaries, and a site-selection or development team that plans only for the narrow one is planning to be caught short.

Scope two deserves a closer look because it connects directly to the procurement discussion of the previous module. Recall the gap between clean generation purchased and electricity actually consumed. Carbon accounting is where that gap becomes visible or stays hidden, depending on the method. Under a method called market-based accounting, a campus counts the clean attributes it has purchased — its certificates and PPAs — against its consumption, which can make a campus with lots of annual certificates look nearly carbon-free. Under location-based accounting, a campus counts the actual average emissions of the grid it draws from, regardless of what it purchased. The two methods can produce wildly different numbers for the same building. The honest practice is to report both, because the divergence between them is itself the information: a large gap signals that the clean claim rests heavily on purchased attributes rather than on genuinely clean local power. A discerning customer reads that gap the way a lender reads the difference between reported and audited earnings.

Embedded carbon in construction — sitting in scope three — is the part most often ignored and increasingly the part that matters at the siting stage, because some of it is decided by where and how you build. Concrete and steel are carbon-intensive to produce, and a hyperscale campus consumes staggering quantities of both. This embedded carbon is emitted up front, before a single server switches on, and it cannot be offset away by clean operations later; it is already in the atmosphere. Two implications follow. First, the choice of construction materials and methods becomes a carbon decision, not merely a cost decision. Second, extending the life of an existing structure, or building where lower-carbon materials are available, can matter as much as the operational power mix. A team that obsesses over clean electricity while ignoring the carbon poured into the foundations is optimizing the visible half of the problem.

What should a foundational practitioner take from all this? Chiefly, a habit of asking about boundaries. Whenever you encounter a carbon claim, ask which scopes it includes, whether scope two is market-based or location-based or both, and whether embedded construction carbon is counted at all. These questions separate a claim that will survive scrutiny from one that will crumble under it. And they connect to siting because the wider and more honest your carbon boundary, the more the specific characteristics of a place — the cleanliness of its grid in real time, the availability of low-carbon materials, the option to reuse existing structures — come to bear on the decision. A narrow boundary makes every site look similar; an honest boundary reveals the real differences between them. Carbon accounting, done properly, is not a report you write at the end. It is a lens that sharpens the map.