This is a development preview. Visit greensoftware.foundation for the official site.
Green Software Foundation

Building Standards Through AI-Facilitated Consensus

GSF develops open standards for green software — using a novel AI-assisted process that compresses years of consensus-building into weeks.

Standards illustration

SPECIFICATION LIFECYCLE

From idea to published standard

Every GSF specification follows a rigorous seven-stage lifecycle, ensuring quality, consensus, and real-world applicability.

1

Proposal

Requirements gathering from diverse stakeholders, defining scope and objectives, validating requirements.

2

Pre-Draft

Research and analysis, composing a preliminary technical specification draft.

3

Draft

Full specification with structured sections: introduction, scope, objectives, requirements, design, metrics, and compliance.

4

Consistency Review

Peer reviews, stakeholder feedback, and iterative refinement of the document.

5

Working Group Approval

Working group review, broader feedback incorporation, and formal sign-off.

6

Steering Committee Ratification

The Steering Committee officially approves the specification for public release.

7

Published

Public release, ongoing feedback, and maintenance. The standard is available for adoption.

Current Standards & Projects

Specifications at every stage of the lifecycle — from early proposals to internationally recognised standards.

Published

Software Carbon Intensity (SCI)

A specification that describes how to calculate a carbon intensity for software applications.

Learn more →
Ratified

Software Carbon Intensity for Artificial intelligence (SCI for AI)

Extending the Software Carbon Intensity (SCI) to Artificial intelligence (AI). Addressing the challenges of measuring Artificial intelligence carbon emissions

Learn more →
Draft

Software Carbon Intensity for Web (SCI for Web)

Extending the Software Carbon Intensity (SCI) to the Web. Addressing the challenges of measuring website carbon emissions

Learn more →
Ratified

Sustainable Organisational Framework for Technology (SOFT)

A framework for decision-making during the development, implementation, and operation of technology applications by incorporating all available methodologies and instruments.

Learn more →
Published

Real Time Energy and Carbon Standard for Cloud Providers (RTC)

Establish a benchmark for measuring carbon emissions.

Learn more →
Draft

Workload Dynamic Power and Cooling (WDPC)

Standardized data coordination between computational workloads and energy infrastructure

Learn more →
Pre-draft

Software Energy Efficiency (SEE)

Methodology for calculating the energy consumption rate of a software system

Learn more →
Pre-proposal

Software Water Efficiency (SWE)

Methodology for calculating the water consumption rate of a software system

AI-facilitated consensus illustration
OUR APPROACH

AI-Facilitated Consensus: from blank page to agreement in ten weeks

Traditional standards take 3+ years. GSF's AI-facilitated assembly process brought 14 experts from 15 organisations to full consensus on SCI for Web in just 10 weeks. Structured questions feed into LLM synthesis, with human-in-the-loop review, iterative refinement, and explicit decision gates at every stage.

ASSEMBLIES

Most GSF standards begin with an Assembly

Assemblies are dedicated workshops — public or member-only — where experts collaborate on a specific challenge. Whether the goal is exploration, knowledge sharing, developing a new standard, or gathering feedback, assemblies bring the right people together to move from problem to solution.

Assemblies illustration

What makes a good specification

Every GSF standard is evaluated against eight quality characteristics drawn from our standards playbook.

Clarity

Unambiguous language that leaves no room for misinterpretation.

Completeness

Covers all necessary aspects without leaving critical gaps.

Consistency

No internal contradictions; aligned with other GSF specifications.

Testability

Requirements can be verified through objective testing or measurement.

Traceability

Every requirement links back to a stakeholder need or objective.

Maintainability

Structured for easy updates as technology and understanding evolve.

Feasibility

Technically achievable with current or near-term capabilities.

Prioritisation

Critical requirements are clearly distinguished from nice-to-haves.

SCI Certification Programme

GSF members can certify their software product's SCI calculation — demonstrating that it was completed and disclosed following GSF guidelines.

Want to propose a new standard or join an existing project?

Every standard starts with a conversation. Whether you want to contribute to an existing specification or propose something new, we'd love to hear from you.