Photo: BalticServers.com, via Wikimedia Commons (CC BY-SA 3.0)
In February 2026, ISO and IEC quietly published ISO/IEC TS 20125-1:2026, “Information technology, Digital services ecodesign, Part 1: Ecopractices for life cycle stages.” Most software organisations have never heard of it. That’s about to change, and the teams who engage with it early will have a real advantage over the ones who wait for it to show up in a customer’s procurement checklist.
This post explains what TS 20125 actually says, why it’s a bigger deal than it sounds, and what your organisation can start doing about it this quarter.
What ISO/IEC TS 20125 actually is
TS 20125 is developed by ISO/IEC JTC 1/SC 39/WG 4, the working group dedicated to eco-design of digital services. It sets out requirements and recommendations for reducing the environmental impact of a digital service across six life-cycle stages:
- Requirements gathering, prioritization, and contextualization
- Design phase
- Implementation
- Use and run / operations
- Maintenance
- End of life
For each stage, the standard defines a handful of “ecopractices” (around two dozen in total), covering things like setting an environmental budget before you build, designing frugal user paths, monitoring resource usage in production, raising users’ awareness of their own impact, and properly decommissioning hardware and data at end of life. Each ecopractice comes with concrete requirements (what you shall do), recommendations (what you should do), and quantitative indicators to track progress.
It’s worth being precise about what this document is. It’s a Technical Specification (TS), not yet a full International Standard. ISO publishes a TS when a topic is mature enough to need formal guidance but not yet ready for full IS-level consensus. It explicitly stays out of performance, reliability, and availability concerns (those are covered by standards like ISO/IEC 25010 and 27001) and out of broader CSR topics like diversity or labour practices. Its scope is narrow and clear: the environmental footprint of digital services, full stop.
Why this matters now
Until TS 20125, most ecodesign frameworks for digital services were either national (RGESN, the French government’s référentiel), product-specific (Germany’s Blauer Engel), or organisational (our own GSP™ certification). TS 20125 is the first attempt at an international, ISO/IEC-level reference for ecodesigning a digital service itself, applicable regardless of jurisdiction, sector, or whether the service has a user interface at all.
That matters for three reasons:
- It’s a common language. When a client, auditor, or procurement team asks “have you considered the environmental impact of this service across its life cycle?”, there’s now a single international reference to point to instead of a patchwork of regional rules.
- It anticipates regulation. Frameworks like the EU’s CSRD and the broader Green Deal agenda are steadily pushing companies to account for the environmental footprint of what they build, not just their offices and supply chains. ISO/IEC standards have a long track record of becoming the de facto basis for that kind of regulation once it lands on digital services specifically.
- Early engagement shapes the conversation. Organisations that adopt TS 20125 early get to define what “good” looks like in their sector before it becomes a mandatory checkbox. That’s a genuinely different position than scrambling to comply once a client RFP starts asking for it.
Conformance is self-declared, which is both good and bad news
TS 20125 does not come with an accredited third-party certification body. Instead, the standard defines a self-declared conformance model with two tiers:
- Partial conformance: cover all life-cycle stages you have direct or indirect control over, implement the applicable ecopractices for those stages, and publicly disclose a dated plan to reach full conformance within two years, reporting progress at least every 12 months.
- Full conformance: cover every applicable life-cycle stage and ecopractice, demonstrably reduce at least one environmental impact category, and publicly disclose your methodology, the impacts you acted on, and the indicators you used.
The good news: there’s no gatekeeper, no expensive audit, and no waiting list. You can start today. The bad news: because conformance is self-declared, the only thing standing between a genuine claim and greenwashing is the quality of your disclosure. Saying “we’re TS 20125 conformant” with a vague paragraph won’t hold up to scrutiny. Saying it with a clear methodology, real indicators, and an honest roadmap will.
What organisations need to do to adopt it
In practice, getting started looks like this:
- Inventory your digital services. TS 20125 applies per service, and which ecopractices apply depends on the service type (with or without a user interface, new or existing); the standard provides a cross-reference table to help you map this out.
- Run a gap assessment. For each service, check your current practices against the applicable ecopractices at each life-cycle stage you control.
- Pick an impact assessment approach. This can range from a full Life Cycle Assessment (ISO 14040/44) to lighter open tools the standard references, like Boavizta or the GHG Protocol, depending on your maturity and resources.
- Set environmental budgets and indicators. This is where the standard stops being paperwork and starts being engineering practice: budgets per stage, tracked over time, feeding back into design and operations decisions.
- Decide your conformance path and publish it. Partial conformance with a credible, dated roadmap is a legitimate and honest place to start. Full conformance is the target, not a prerequisite for engaging.
- Train your teams continuously. The standard itself requires ongoing training and monitoring of ecodesign practices as part of maintenance, not a one-off workshop before launch.
None of this requires a moonshot. It requires a deliberate first pass and a habit of revisiting it, which is exactly the kind of work most engineering organisations are not yet set up to do alone.
Where GreenSeal comes in
This is squarely the kind of gap we exist to close. We help organisations run the gap assessment, choose a workable impact assessment methodology, set up the measurement and indicators the standard expects, train engineering teams on what’s required, and put together a conformance disclosure that will actually hold up under scrutiny. See our ISO/IEC TS 20125 readiness service for the details.
It’s also worth being clear about how this relates to our own GSP™ certification. TS 20125 operates at the level of a specific digital service: does this service follow recognised ecodesign practices? GSP™ operates one level up, at the organisation: does the team building it have the measurement infrastructure and improvement culture to keep meeting standards like this one over time, not just once. The two reinforce each other; we wrote about that dynamic in more depth in RGESN and GSP™: Two Different Answers to the Same Question, and the same logic applies here.
TS 20125 is brand new, which means almost nobody has implemented it yet. That’s precisely the moment when getting ahead of a standard is cheapest and most valuable: before it’s a compliance obligation, while it’s still a genuine differentiator.
