No bill gives the environmental footprint of a company’s digital technology: neither that of workstations and phones, nor that of servers, nor that of the online services it publishes. A sustainable IT approach in business therefore begins by building this measurement. It then acts in the order we propose: extend the lifespan of equipment, design sober services, host and size at the right level, buy differently, then report. Each step delivers a document that the next one uses.
Two public sources serve as support: Law no. 2021-1485 of 15 November 2021 aimed at reducing the environmental footprint of digital technology in France, known as the REEN law, read on 13 November 2026 in DILA’s LEGI database; the general framework for the eco-design of digital services (RGESN), 2024 version, published on 17 May 2024 by Arcep and Arcom in conjunction with ADEME, read on 12 November 2026 on arcep.fr, which describes itself as “a non-binding document”. The translations of quotations are ours.
Measuring the footprint, the first step of sustainable IT in business
The measurement starts from an inventory: end-user devices, screens, network equipment, servers, hosting and subscribed online software, with for each its quantity, its age and its owner. Added to this are the known consumption figures and the footprint data of the hosting providers.
The RGESN points out, citing the ADEME and Arcep study, that end-user devices, and in particular their manufacture, account for the major part of the environmental footprint of digital technology. It calls for a multi-criteria assessment that considers, as far as possible, greenhouse gas emissions, energy consumption, water consumption and the consumption of metals and minerals. In our reading, a measurement limited to server electricity would omit the main item.
This step has much in common with FinOps. Our FinOps page also starts from resources attributed to owners, recommends tracking footprint indicators alongside cost indicators, and notes that the hosting providers’ calculation methods differ: it is better to compare over time with the same provider than between providers.
The step concludes with the inventory, a first assessment with its written method, and the list of the items that weigh most.
Keeping equipment longer
The RGESN regards extending the lifespan of end-user devices as “an essential lever”. This extension translates into fleet management rules: renew on observed wear rather than on a fixed schedule, repair, reassign, direct towards reuse. Article 16 of the REEN law imposes this last direction on State services and local authorities, according to terms set by decree; in our reading, it does not cover companies.
Software can shorten this lifespan. The RGESN requires that a service remain usable on older device models (criterion 2.2) and older versions of operating systems and browsers (2.4), and that corrective updates be available throughout the planned lifespan of the equipment linked to the service (3.4).
This step produces a written renewal policy, the repair and reuse channels chosen, and the list of older devices that each internal application must continue to serve.
Designing sober services with the RGESN
Article 25 of the REEN law created Article L. 38-5 of the French Post and Electronic Communications Code, in force since 1 January 2024, which provides for a framework aimed at “defining criteria for the sustainable design of digital services in order to reduce their environmental footprint”. The 2024 RGESN has 78 criteria formulated as questions, divided into nine themes, with three levels of priority: “Priority”, “Recommended” and “Moderate”.
The first criteria concern the decision to build: has the service been assessed favourably in terms of usefulness in relation to its impacts (1.1), are its targets and their needs defined (1.2)? Others concern everyday design: a design review and a code review that include reducing the impacts of each feature (2.6), the absence of infinite scrolling (4.2), the archiving and deletion of outdated content (5.8), data retention periods (7.2).
These criteria fit into the code review and the production release criteria described on our software quality page.
The step provides, for each service, the applicable criteria, those the team is aiming for, and their place in the reviews.
Hosting and sizing at the right level
For hosting, the RGESN examines the hosting provider’s reduction approach (8.1), its sustainable management of equipment (8.2), its PUE and WUE (8.3 and 8.4), the documented origin of its electricity (8.5), its location (8.6) and the separation of “hot” and “cold” data (8.8). In architecture, it requires adapting the quantity of resources to the service’s consumption (3.2) and optimising the use of development and test environments (3.7).
Sizing joins the usage levers listed on our FinOps page: rightsizing, switching off unused environments, deleting orphaned resources, storage lifecycle. Our article on reducing the cloud bill explains how the amount of unused resources is calculated. The same page notes the divergences: a pricing commitment reduces the price without changing usage, and the cheapest region is not necessarily powered by the lowest-carbon electricity.
These choices fall within our cloud and platforms domain. The step sets a sizing target per service, the environments to switch off when not in use and the hosting provider’s answers on criteria 8.1 to 8.6.
Buying with environmental requirements
The RGESN requires suppliers to be held to an approach for reducing their impacts (2.8) and the impacts of third-party services to be taken into account when selecting them (2.10). Procurement translates this into requirements: duration of availability of parts and updates, refurbished equipment when usage allows, footprint information requested from hosting providers and software vendors with their calculation method.
For physical products, the digital product passport of Regulation (EU) 2024/1781 will be able to provide data specific to each product, once the delegated act covering its group has been adopted. Public buyers, for their part, integrate sustainable development objectives into the definition of their needs (Article L. 2111-1 of the French Public Procurement Code), as our reading of IT public procurement points out.
The step results in standard clauses, which lawyers and buyers adapt, and in a bid evaluation grid.
Reporting on the approach, and its limits
The RGESN makes the publication of an eco-design statement “a prerequisite for claiming application” of the framework. It advises dating it, updating it, ideally at each significant change, and indicating in it the criteria validated and not validated, the progress plan and a progress score weighted by the priority of the criteria. The framework specifies that this score does not measure environmental impact, and that a communication based on it respects the framework for environmental claims, “in particular in terms of reliability, transparency and verifiability”.
For some companies, this report joins a broader obligation. Directive (EU) 2022/2464, read on 12 November 2026 in the Publications Office’s Cellar repository, replaces Article 19a of Directive 2013/34/EU: the management report of the companies concerned contains the information needed to understand the company’s impacts on sustainability matters, according to standards covering in particular climate change mitigation (Article 29b).
The step delivers the statement itself. The first published version then serves as a point of comparison: each update says what has changed since, according to the same method.