GHG Protocol for IT & Telecommunications

What is GHG Protocol?

The Greenhouse Gas (GHG) Protocol is the world's most widely used accounting and reporting standard for greenhouse gas emissions, developed jointly by the World Resources Institute (WRI) and the World Business Council for Sustainable Development (WBCSD). It provides a comprehensive framework for measuring, managing, and reporting emissions across three distinct scopes — direct emissions, indirect energy-related emissions, and all other indirect emissions in a company's value chain. Since its introduction in 2001, the GHG Protocol has become the de facto global benchmark for corporate climate accountability, underpinning regulatory requirements such as the EU Corporate Sustainability Reporting Directive (CSRD) and science-based target frameworks.

GHG Protocol and the IT and Telecommunications Industry

The information technology and telecommunications sector is one of the largest and fastest-growing contributors to global energy consumption, currently accounting for an estimated 2 to 4 percent of worldwide greenhouse gas emissions — a share that continues to rise as digital infrastructure expands. For companies operating data centers, mobile networks, cloud platforms, and device manufacturing supply chains, the GHG Protocol is not an abstract compliance exercise but a practical tool for understanding where emissions originate and how to reduce them.

Telecommunications operators, for example, run vast networks of base stations, routers, and switching centers that consume electricity around the clock. A major mobile network operator in Europe may operate tens of thousands of cell towers, each drawing continuous power. Data center operators face similarly intensive energy demands: a hyperscale facility can consume as much electricity as a small city. For software companies relying on third-party cloud infrastructure, the challenge lies in measuring emissions generated by providers such as AWS, Google Cloud, or Microsoft Azure — emissions that fall under Scope 3 of the GHG Protocol.

Device manufacturers add another layer of complexity. The production of smartphones, servers, routers, and laptops involves extensive global supply chains with significant embedded carbon. Under Scope 3 accounting rules, a company like a semiconductor manufacturer is responsible for tracking emissions from raw material extraction through component fabrication, assembly, logistics, product use, and end-of-life disposal. This breadth of accountability is what makes GHG Protocol particularly demanding — and particularly valuable — for the IT and telecommunications sector.

Key Requirements

• Scope 1 emissions reporting: Companies must measure and disclose all direct greenhouse gas emissions from sources they own or control, including on-site diesel generators used for data center backup power, fuel combustion in company-owned vehicles, and refrigerant leaks from cooling systems in server facilities.
• Scope 2 emissions reporting: All indirect emissions from purchased electricity, heat, steam, or cooling must be reported. IT companies must choose between location-based methods (using regional grid averages) and market-based methods (using energy attribute certificates or power purchase agreements), with the GHG Protocol requiring disclosure of both where applicable.
• Scope 3 emissions reporting: This is the most extensive and often the most significant category for IT and telecoms firms. It covers 15 categories including purchased goods and services, capital goods, fuel and energy-related activities, upstream transportation, waste generated in operations, business travel, employee commuting, upstream and downstream leased assets, processing of sold products, use of sold products, end-of-life treatment of sold products, franchises, and investments.
• Organizational boundary setting: Companies must define whether they are reporting using an equity share approach or a control approach (financial or operational), which determines which subsidiaries, joint ventures, and leased assets fall within the reporting boundary.
• Base year establishment: A historical base year must be selected and recalculated when significant structural changes occur, ensuring comparability of emissions data over time.
• Third-party verification: For companies subject to regulatory frameworks building on the GHG Protocol — such as CSRD — limited or reasonable assurance from an independent auditor is increasingly mandatory.
• Emission factor sourcing: Companies must use credible, regionally appropriate emission factors from sources such as the International Energy Agency, national government databases, or supplier-specific data where available.
• Data quality documentation: The protocol requires companies to document data sources, methodologies, assumptions, and uncertainty ranges to support transparent reporting and year-on-year comparability.

Implementation Steps for IT and Telecommunications Companies

1. Conduct an emissions inventory scoping exercise. Before collecting any data, identify which entities, facilities, and operations fall within your organizational boundary. For a telecommunications group with subsidiaries across multiple countries, this step determines whether regional operating companies, joint ventures with infrastructure sharing arrangements, and leased tower assets are included in your inventory. Document the rationale for each inclusion or exclusion decision.
2. Map all emission sources by scope. Walk through each category of the GHG Protocol systematically. For Scope 1, list all combustion sources: standby generators, company fleet vehicles, and HVAC refrigerants. For Scope 2, obtain electricity consumption data from utility meters and billing records for every facility. For Scope 3, prioritize the categories most material to your business model — for a cloud infrastructure company, purchased goods and use of sold products will typically dominate.
3. Collect activity data from internal systems and suppliers. Pull electricity consumption records from building management systems and energy management platforms. Request emissions data or spend data from key hardware suppliers. For employee business travel, extract flight and rail records from corporate travel booking systems. Where primary data is unavailable, apply spend-based estimation using EXIOBASE or comparable environmentally extended input-output databases.
4. Apply appropriate emission factors and calculate totals. Match each activity data point to a corresponding emission factor. For grid electricity, use market-based factors if you have renewable energy certificates or power purchase agreements in place; otherwise use location-based factors from the national grid operator. Convert all gases to carbon dioxide equivalents using IPCC global warming potential values, covering CO2, CH4, N2O, and fluorinated gases where relevant.
5. Set a base year and establish internal controls. Choose a base year that is representative of typical operations and document it formally. Establish data governance processes — assigning data owners for each emission category, creating audit trails for how figures were derived, and implementing approval workflows before figures are published externally.
6. Engage your supply chain on Scope 3 data quality. Send supplier questionnaires requesting primary emissions data, particularly to your top 20 hardware vendors by spend. For telecoms network equipment suppliers such as antenna and router manufacturers, request product carbon footprints aligned with ISO 14067. Better supplier data reduces reliance on estimation and improves the credibility of your reported figures.
7. Identify reduction opportunities and set science-based targets. Use the inventory results to prioritise decarbonisation initiatives: switching data centers to 100 percent renewable electricity, deploying energy-efficient network equipment, electrifying the vehicle fleet, and extending the lifecycle of hardware to reduce embodied carbon in Scope 3 categories. Submit targets to the Science Based Targets initiative (SBTi) for validation to ensure alignment with 1.5 degree pathways.
8. Arrange third-party assurance and publish your report. Engage an accredited verification body to provide limited assurance over your Scope 1, 2, and material Scope 3 figures. Publish your GHG inventory as part of your annual sustainability report, aligned with GRI Standards, TCFD recommendations, or the European Sustainability Reporting Standards (ESRS E1) as required by your regulatory obligations.

Frequently Asked Questions

Does the GHG Protocol apply to small and mid-sized IT companies, or only large enterprises?

The GHG Protocol itself is a voluntary standard and does not impose legal obligations based on company size. However, regulatory frameworks that reference the GHG Protocol — notably the EU CSRD — apply to large companies first and will progressively cover smaller listed companies from 2026 onward. Beyond regulation, many enterprise procurement teams now require suppliers of all sizes to disclose GHG emissions as a condition of vendor qualification, making GHG accounting a commercial necessity for IT companies throughout the supply chain, regardless of their own regulatory status.

What is the difference between Scope 2 market-based and location-based accounting, and which should IT companies use?

Location-based accounting reflects the average emissions intensity of the electricity grid in the region where a facility operates. Market-based accounting reflects the emissions associated with the specific electricity products a company has contractually procured, such as renewable energy certificates (RECs in North America) or Guarantees of Origin (GOs in Europe). The GHG Protocol requires companies to report both figures. For IT companies operating large data centers with active renewable energy procurement programs, the market-based figure will typically be significantly lower — but both must be disclosed to prevent greenwashing concerns and to allow stakeholders to compare companies operating in different grid regions.

How should a software-as-a-service company account for emissions from cloud hosting providers?

Cloud-hosted workloads fall under Scope 3, Category 1 (purchased services) for the company procuring the cloud services. The most accurate approach is to use emissions data directly from cloud provider dashboards — AWS Customer Carbon Footprint Tool, Google Cloud Carbon Footprint, and Microsoft Azure Emissions Impact Dashboard all provide facility-level or workload-level estimates. Where provider data is unavailable, companies can estimate emissions using spend-based factors or by modelling compute hours multiplied by server power usage effectiveness (PUE) and regional grid intensity. As cloud emissions can represent the single largest Scope 3 category for pure software companies, investing in data quality here yields significant reporting and reduction value.

How does the GHG Protocol interact with the EU Corporate Sustainability Reporting Directive?

The CSRD mandates disclosure under the European Sustainability Reporting Standards, specifically ESRS E1 for climate. ESRS E1 is explicitly designed to be consistent with the GHG Protocol's Corporate Standard and the GHG Protocol Scope 3 Standard. Companies reporting under ESRS E1 must disclose Scope 1, 2, and 3 emissions using GHG Protocol methodology, report a base year, describe recalculation policies, and provide a breakdown of Scope 3 by all relevant categories. Crucially, ESRS E1 also requires reporting against the EU Taxonomy for Sustainable Activities and physical climate risk disclosures, extending beyond pure GHG accounting. For IT and telecoms companies in scope for CSRD, aligning with the GHG Protocol now is the most efficient preparation for mandatory ESRS E1 disclosure.

Summary

The GHG Protocol provides IT and telecommunications companies with the structured, credible foundation they need to understand and reduce their climate impact across the full value chain — from the electricity powering their data centers to the embedded carbon in the devices their customers use. With regulatory pressure intensifying through CSRD and customer scrutiny of supplier emissions growing across every market segment, the question for IT and telecoms leaders is no longer whether to implement GHG accounting but how quickly they can build the internal capability to do it well. Starting with a robust inventory, engaging your supply chain early, and aligning with science-based targets will position your organisation ahead of compliance deadlines and create a defensible, credible narrative for investors, customers, and regulators alike.