Inferensys

Glossary

Scope 3 Emissions

All indirect greenhouse gas emissions occurring in an organization's value chain, including embodied carbon in purchased hardware, capital goods, and downstream usage of AI products.
Wide-angle shot of a modern WeWork open floor plan with creative walls covered in AI system architecture diagrams, product team collaborating in standing desk area with industrial lighting.
INDIRECT VALUE CHAIN EMISSIONS

What is Scope 3 Emissions?

Scope 3 emissions encompass all indirect greenhouse gas (GHG) emissions that occur in an organization's value chain, excluding those from purchased energy (Scope 2). For AI enterprises, this includes the embodied carbon in purchased hardware, capital goods, and the downstream energy consumption of deployed models.

Scope 3 Emissions are defined by the Greenhouse Gas (GHG) Protocol as all indirect emissions—excluding Scope 2—occurring across a reporting company's upstream and downstream value chain. This category captures the full lifecycle carbon impact of business activities, from the extraction of raw materials for purchased GPUs and servers to the end-use energy consumption of AI products by customers.

For enterprise AI governance, Scope 3 is typically the dominant emission category, often dwarfing operational Scope 1 and 2 footprints. Quantifying these emissions requires a Model Lifecycle Assessment (LCA) that accounts for the embodied carbon in data center construction, the manufacturing of specialized accelerators, and the downstream inference costs incurred by users, making it a critical focus for Sustainable AI Reporting.

SCOPE 3 DEEP DIVE

Frequently Asked Questions

Clear, technical answers to the most common questions about value chain emissions in the context of artificial intelligence infrastructure and reporting.

Scope 3 emissions are all indirect greenhouse gas (GHG) emissions that occur in an organization's value chain, both upstream and downstream, excluding those from purchased energy (Scope 2). For an AI enterprise, this is the most significant and hardest-to-quantify category. It encompasses the embodied carbon of purchased GPUs and networking hardware (Category 1: Purchased Goods and Services), the emissions from cloud provider data center construction (Category 2: Capital Goods), and critically, the downstream energy consumed by customers when they run inference on a deployed model (Category 11: Use of Sold Products). Unlike direct operational control, managing Scope 3 requires granular lifecycle assessment data from silicon manufacturers and cloud vendors.

INDIRECT VALUE CHAIN IMPACTS

Key Characteristics of Scope 3 Emissions

Scope 3 encompasses all indirect emissions not included in Scope 2 that occur in the value chain of the reporting company, including both upstream and downstream emissions. For AI enterprises, this is often the largest and most complex category to measure.

01

Upstream vs. Downstream Classification

Scope 3 is divided into upstream emissions (purchased goods and services, capital goods, fuel-and-energy-related activities, upstream transportation, waste, business travel, employee commuting, and upstream leased assets) and downstream emissions (downstream transportation, processing of sold products, use of sold products, end-of-life treatment, downstream leased assets, franchises, and investments).

  • Upstream Example: Embodied carbon in GPUs and server racks purchased from hardware vendors.
  • Downstream Example: Electricity consumed by end-users running inference on a deployed AI model.
02

Category 1: Purchased Goods & Services

This is typically the most significant category for AI companies. It captures the cradle-to-gate emissions of all products and services purchased during the reporting year.

  • Hardware: Emissions from mining rare earth minerals, semiconductor fabrication, and assembly of servers.
  • Cloud Services: Emissions from third-party data center construction and upstream energy infrastructure.
  • Software & Consulting: Emissions from the operations of SaaS providers and professional services firms.

Calculation methods include supplier-specific data, hybrid models combining supplier and secondary data, and spend-based methods using environmentally-extended input-output (EEIO) databases.

03

Category 11: Use of Sold Products

For AI companies offering model-as-a-service or on-device inference, this category captures the energy consumed by customers when using the product. It requires estimating the total lifetime energy consumption of the deployed system.

  • Direct Use-Phase Emissions: Electricity consumed by end-user devices during inference.
  • Indirect Use-Phase: Energy consumed by networking infrastructure transmitting data to and from the model.

Calculation requires defining a functional unit—such as emissions per million inferences—and multiplying by projected usage volumes over the product's lifespan.

04

Category 2: Capital Goods

This category covers the upstream emissions from the production of long-lived assets like data center buildings, custom ASIC fabrication facilities, and server fleets. Unlike purchased goods, capital goods are depreciated over their useful life.

  • Data Center Construction: Emissions from concrete, steel, and cooling infrastructure.
  • Custom Silicon Development: Emissions from the research, design, and fabrication of proprietary AI accelerators.

Emissions are accounted for in the year of acquisition, not amortized, per the GHG Protocol.

05

Category 3: Fuel- and Energy-Related Activities

This category captures emissions from the extraction, production, and transportation of fuels and energy consumed by the reporting company that are not already included in Scope 1 or Scope 2.

  • Transmission & Distribution Losses: The electricity lost as heat when transmitting power from the generation source to the data center.
  • Upstream Fuel Emissions: Emissions from extracting and refining natural gas used for on-site backup generators.

This category ensures that the full lifecycle of energy procurement is captured, not just the combustion or generation phase.

06

Calculation Challenges & Data Quality

Scope 3 accounting is inherently uncertain due to reliance on secondary data and supplier estimates. The GHG Protocol defines a data quality hierarchy:

  • Tier 1: Supplier-specific emissions data (highest quality, rarely available).
  • Tier 2: Hybrid models combining supplier activity data with industry-average emission factors.
  • Tier 3: Spend-based methods using EEIO databases (lowest quality, highest uncertainty).

For AI hardware, embodied carbon estimates can vary by 2-3x depending on the semiconductor foundry's energy mix, making supplier engagement critical for accurate reporting.

GHG PROTOCOL EMISSION CATEGORIES

Scope 3 vs. Scope 2 vs. Scope 1 Emissions

Comparative analysis of the three emission scopes defined by the Greenhouse Gas Protocol, focusing on organizational boundaries, control mechanisms, and relevance to AI infrastructure.

FeatureScope 1Scope 2Scope 3

Definition

Direct emissions from owned or controlled sources

Indirect emissions from purchased energy generation

All other indirect emissions in the value chain

Reporting Requirement

Mandatory

Mandatory

Voluntary (except under CSRD)

Primary AI Relevance

On-premise data center diesel generators

Cloud compute electricity consumption

Embodied carbon in GPUs and downstream model usage

Emission Source Examples

Company vehicles, on-site fuel combustion

Purchased electricity, steam, heating, cooling

Purchased goods, capital equipment, business travel, product use

Control Level

Calculation Complexity

Low

Medium

High

Data Availability

High (direct metering)

High (utility bills, cloud APIs)

Low (supplier estimates, industry averages)

Decarbonization Lever

Fuel switching, electrification

PPAs, 24/7 CFE procurement

Supplier engagement, circular economy, model optimization

Typical Share of AI Company Footprint

< 5%

15-30%

65-85%

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.