EED vs EPBD energy-efficiency and building-performance duties

EED covers economy-wide energy use, savings, public-sector duties, and data-centre reporting. Use it when the question is about consumption, efficiency, procurement, or reporting obligations outside pure building performance.

EPBD covers building energy performance, certificates, and renovation context. Use it when the question is about the building itself or a building unit.

Pick the legal regime by the duty object first. If the object is enterprise energy use, public-sector consumption, or a data-centre report, start with EED. If the object is building performance, keep the EPBD file separate.

Article 11 of the EED uses enterprise energy consumption thresholds: more than 85 TJ average annual energy consumption over the previous three years for a certified energy management system, and more than 10 TJ for an energy audit where no energy management system is implemented.

EPBD building certificates do not replace this enterprise-level EED threshold analysis. A building certificate may help describe a building, but the EED audit can cover buildings, operations, installations, transport, and broader energy-use behaviour.

Do not close an EED Article 11 assessment just because an energy performance certificate exists. Keep enterprise consumption data, audit scope, action plan, and recommendation implementation evidence in the EED file.

Article 12 of the EED requires Member States to require owners and operators of data centres with installed IT power demand of at least 500 kW to make Annex VII information publicly available each year, subject to trade-secret and confidentiality protections.

EPBD building-performance work may still matter for a data-centre building, but the EED data-centre obligation is about data-centre energy performance, the European database, and KPIs such as energy consumption, power utilisation, temperature set points, waste heat, water use, and renewable energy.

Treat data-centre reporting as an EED workstream. A facilities or building team can support it, but the evidence pack needs owner/operator identity, IT power demand, data-centre floor area, traffic/storage information, and the Annex VII KPI set.

EED Articles 5, 6, and 7 cover energy consumption in the public sector, public-building renovation, and public procurement. Article 6 includes a public-building renovation route and an inventory of heated and cooled buildings owned or occupied by public bodies with useful floor area above 250 m2.

EPBD evidence can be relevant because the EED public-building inventory includes energy performance certificate information issued under the buildings framework, but the EED public-sector obligations remain separate duties.

For public estates, keep two linked records: an EED public-sector/public-building file for consumption, renovation rate, inventory, and procurement duties, and an EPBD building-performance file for certificate and building-performance evidence.

EED evidence should include consumption baselines, final-energy and primary-energy calculations where relevant, Article 11 threshold calculations, audit reports, action plans, recommendation implementation rates, public-sector inventories, procurement records, data-centre Annex VII data, and database submissions.

EPBD evidence should be limited here to building-performance records supported by the source set, especially energy performance certificates and building renovation/performance documentation.

One building can generate evidence for both regimes, but a single certificate, audit, or facilities spreadsheet should not be described as satisfying both unless the specific EED and EPBD evidence elements are mapped.

EED timing includes the 11 October 2025 transposition date for many provisions, the 11 October 2026 first-audit date for Article 11 enterprises above 10 TJ without an energy management system, the 11 October 2027 energy-management-system date for enterprises above 85 TJ, and annual data-centre publication from 15 May 2024.

Do not infer EPBD recast deadlines from this page. This comparison uses EPBD only for building-performance and certificate context.

Use EED dates only for EED duties. If a project also depends on current EPBD recast implementation, verify that from EPBD-specific sources before adding dates to a roadmap.

Use EED when the work turns on final or primary energy consumption, enterprise energy-management thresholds, energy audits, action plans, public-sector efficiency, energy-efficient procurement, data-centre performance reporting, or end-use savings.

Use EPBD when the work turns on building energy performance, energy performance certificates, or building renovation strategy and performance evidence.

When both are relevant, write a crosswalk with three columns: EED duty and source, EPBD building-performance record, and the exact evidence item that can be reused. Leave penalties, thresholds, and dates out unless the relevant source is in the evidence file.

EED overlap appears when a building is part of an enterprise audit, public-building inventory, or data-centre report. The EED question is whether the record supports an energy-efficiency duty.

EPBD overlap appears when the same building also needs performance certificates or renovation evidence. The EPBD question is whether the record supports building-performance compliance.

Do not treat the same record as interchangeable by default. Reuse it only after mapping each field to the specific EED duty or EPBD building-performance requirement.

If the question is about enterprise consumption, public-sector duty, procurement, or data-centre reporting, start with EED and gather the consumption or KPI evidence first.

If the question is about a building certificate, renovation record, or building-performance score, start with EPBD and keep the building file separate.

Use the regime that matches the first compliance question. Then check whether the other regime adds a supporting record, rather than assuming one record answers both.