GHG Protocol status + 2024-2025 update pipeline. STATUS: GHG Protocol Suite established 1998 + active maintenance by WRI + WBCSD + Independent Standards Board + Technical Working Groups; freely available + downloadable from ghgprotocol.org. CURRENT EDITIONS: Corporate Standard (2004 revised); Scope 2 Guidance (2015); Corporate Value Chain Standard (2011); Product Life Cycle Standard (2011); Project Protocol (2005); Mitigation Goal Standard (2014); Policy and Action Standard (2014); Land Sector + Removals Guidance (2025). 2024-2025 UPDATE PIPELINE: comprehensive consultation underway (2022-2025) for major Corporate Standard + Scope 2 Guidance + Scope 3 Standard updates; new editions anticipated 2026-2027; KEY UPDATE AREAS: (a) AI + machine learning emissions - data centre + training + inference + cooling + embodied emissions of hardware; (b) CLOUD COMPUTING - shared infrastructure + virtualisation + multi-tenant + Scope 2/3 allocation; (c) IMPROVED SCOPE 2 + MARKET-BASED method - hourly matching + 24/7 carbon-free energy + temporal granularity; (d) IMPROVED SCOPE 3 + supplier engagement + supplier-specific data + Sustainability Hub data sharing; (e) LAND SECTOR + REMOVALS GUIDANCE 2025 - new guidance on land use + land use change + forestry (LULUCF) + carbon removals + biomass + bioenergy + biogenic CO2 + biochar + nature-based solutions; (f) CARBON MARKET INTEGRITY - carbon offset use rules + voluntary carbon market integrity + supplemental mitigation; (g) DOUBLE COUNTING + INVENTORY VS CONTRIBUTIONS clarifications; (h) FINANCIAL SECTOR PCAF alignment + financed emissions methodology integration; (i) sectoral guidance for hard-to-abate sectors (shipping + aviation + cement + steel + chemicals + agriculture); (j) climate transition plans + reduction roadmaps + interim milestones. ENGAGEMENT: organizations should track GHG Protocol consultation + draft updates + plan transition + maintain current-edition compliance + prepare for 2026-2027 new editions.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.