EU data-centre labels create an assurance job before they create a ranking

Reuters reported on 21 September that the European Union’s data-centre rating rules would require larger facilities to disclose energy and water efficiency, local water-stress context and potential contributions such as waste-heat reuse. The report says the scheme covers data centres with at least 500 kW of installed IT power demand and does not itself impose consumption caps. The European Commission’s policy page places the rating scheme alongside existing reporting under the Energy Efficiency Directive.

The policy signal is transparency, not proof of sustainability. An efficiency ratio can improve while total electricity or water use rises. Two operators can also report different results because they define the facility, IT load, cooling system, reused heat, renewable supply or reporting period differently. A public label becomes decision-useful only when those choices are consistent and reviewable.

Define the measurement boundary first

Every reported indicator needs a boundary statement. It should identify the buildings and equipment included, meter hierarchy, tenant allocation, treatment of backup generation, purchased cooling, on-site generation and shared infrastructure. The denominator should match the decision: power usage effectiveness measures facility overhead relative to IT energy, while water usage effectiveness depends on how water use and IT energy are defined. Neither ratio alone states total resource demand or local scarcity.

Operators should preserve source readings, transformations, exclusions and corrections in a versioned evidence trail. Colocation facilities need rules for allocating shared consumption without exposing customer-confidential data. Estimates should be marked separately from meters, and late corrections should remain visible. Assurance teams need access to the calculation logic and a sample of underlying evidence, not only the final number.

Connect the label to operating roles

This creates a capability requirement across facilities, sustainability, finance, procurement and data governance. Engineers understand the physical system; data owners maintain definitions and lineage; assurance reviewers test completeness and consistency; procurement teams interpret labels without turning them into unsupported rankings. Local authorities and communities also need totals and water-stress context when a ratio obscures absolute demand.

A 2026 research paper by Daria Onitiu, Sandra Wachter and Brent Mittelstadt argues that power and water efficiency indicators can create an “efficiency paradox” if improving ratios supports larger facilities while absolute environmental pressures grow. The paper is a normative legal and policy analysis, not an empirical estimate of every data centre. It is useful counterevidence because it shows why disclosure design must retain total use, trade-offs and local context.

The strongest argument for simple labels is usability. Buyers and citizens cannot audit every facility. Simplicity, however, should sit at the presentation layer, not erase the evidence layer. A concise rating can link to a machine-readable record of scope, methods, totals, ratios, assurance status and material qualifications.

Procurement should test how the label changes a decision. Specify whether it is an eligibility screen, a weighted criterion or information for contract management. Set no threshold until several representative facilities have been calculated under the same rules and the effect of geography, climate, workload and colocation has been reviewed. Contract clauses can then require timely data, correction notices and access for assurance without implying that one ratio captures the whole environmental effect. This prevents a readable symbol from becoming a false precision instrument and preserves room for material local qualifications.

Before treating a rating as a procurement gate, run a dry calculation across two different facilities and ask an independent reviewer to reproduce it. Log every ambiguity that changes the outcome and resolve it in the data contract. The immediate workforce implication is concrete: designate an indicator owner, a facility-data owner and an assurance reviewer. Without those roles, the label risks being a polished endpoint for inconsistent measurements.