Scope GuideEU

EU Energy Efficiency Directive (EED) Scope and Who Must Comply

Identify which obligations apply to your organization and why.

Focus: enterprise thresholds (85 TJ / 10 TJ), public bodies scope, and data centre reporting triggers.

Back to main artifact Review sources

Author

Sorena AI

Published

Feb 21, 2026

Updated

Feb 21, 2026

Sections

Structured answer sets in this page tree.

Primary sources

Cited legal and guidance references.

Publication metadata

Sorena AI

Published Feb 21, 2026

Updated Feb 21, 2026

Overview

The EED is a package of obligations that apply to different actors. The most common scoping mistakes are mixing up Article 11 thresholds with older large-enterprise concepts, using inconsistent organizational boundaries for energy consumption, and ignoring the separate data centre reporting trigger. This page gives you a defensible scoping approach, grounded in Directive (EU) 2023/1791 and the 2024 Commission guidance, plus a checklist of evidence to retain.

Section 1

Directly obligated parties (the usual "must comply" buckets)

Some EED obligations are placed on Member States, who then implement measures nationally. Others directly drive enterprise duties or sector reporting triggers.

Start by classifying where you fit, then map the obligations to owners and evidence.

Enterprises above thresholds, if your 3 year average annual energy consumption across all carriers exceeds the Article 11 thresholds, you must implement a certified EMS above 85 TJ or carry out energy audits above 10 TJ if no EMS is in place.
Public bodies, via Member State implementation, obligations include the Article 5 final energy consumption reduction track, public building duties, and public procurement requirements.
Data centre operators, if installed IT power demand is >= 500 kW, the operator must publish or report the required Annex VII information each year, subject to confidentiality rules.

Section 2

Enterprise threshold scoping (how to avoid the common boundary trap)

The thresholds are based on energy consumption, not headcount or turnover. That makes boundary definition the key control.

Your scoping should withstand scrutiny: auditors should be able to reproduce your result from stored inputs.

Define the organizational boundary, which legal entities, sites, and operations are included, and keep the rationale in writing.
Define the energy boundary, which carriers and uses are included, and treat purchased electricity, fuels, purchased heat or cooling, and fleet fuels consistently.
Compute the 3 year average annual consumption in TJ and store the calculation inputs, conversion factors, and review sign off.
Set retest triggers, acquisition, divestiture, new site, and major load change, and review the route at least annually.
If annual consumption crosses the relevant threshold in a given year, be ready to make that information available to the competent national authority.

Recommended next step

Use EU Energy Efficiency Directive (EED) Scope and Who Must Comply as a cited research workflow

Research Copilot can take EU Energy Efficiency Directive (EED) Scope and Who Must Comply from clarifying scope and applicability with cited answers to a reusable workflow inside Sorena. Teams working on EU Energy Efficiency Directive (EED) can keep owners, evidence, and next steps aligned without copying this guide into separate documents.

Research workflow

Open Research Copilot for EU Energy Efficiency Directive (EED) Scope and Who Must Comply

Start from EU Energy Efficiency Directive (EED) Scope and Who Must Comply and answer scope, timing, and interpretation questions with cited outputs.

Explore next step

Talk to Sorena

Talk through EU Energy Efficiency Directive (EED)

Review your current process, evidence gaps, and next steps for EU Energy Efficiency Directive (EED) Scope and Who Must Comply.

Explore next step

Section 3

Data centres: don't confuse installed IT demand with facility power

The data centre trigger is tied to installed information technology (IT) power demand, not the broader facility power envelope.

Treat measurement method and boundary as part of your compliance evidence, so year-over-year reporting stays consistent.

Confirm whether installed IT power demand is >= 500 kW, the reporting trigger, and whether you reach the >= 1 MW band where best-practice expectations intensify.
Define the reporting perimeter, data centre sites, colocation boundaries, and tenant responsibilities, and document who publishes and who submits to the European database.
Keep publication history, database submissions, and supporting calculation sheets under version control.

Section 4

Public bodies: treat national implementation as the control source

Public-sector obligations are implemented through Member State measures and may have scope nuances (which entities count as public bodies, what consumption is included, and what exclusions apply).

Your compliance workflow should explicitly link to the Member State implementation and assign owners for reporting and building inventory duties.

Determine whether your organization qualifies as a public body under the applicable national definition and how consumption is aggregated.
Identify the relevant obligations, reduction planning and reporting, public building inventories, renovation planning, and procurement energy-efficiency requirements.
Store the scope memo, baseline definition, reporting method, governance approvals, and links to the national implementation text and guidance.

Primary sources