Ops GuideEU

EU Energy Efficiency Directive (EED) Reporting and Metrics

What to track, what to publish, and how to keep it defensible.

Focus: Article 11 Action Plans + implementation rate, plus data centre annual publication.

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

EED reporting gets hard when teams mix internal evidence with external publication. The directive expects concrete outputs, Action Plans, annual report publication of the recommendation implementation rate for enterprises on the audit route, annual data centre publication, and in some cases authority-facing data submissions, while also protecting trade and business secrets. This page shows how to design reporting that is publishable, traceable, and repeatable across years.

Section 1

Reporting model: separate internal evidence from publishable outputs

Build two layers: a full internal evidence pack (traceable inputs, calculations, site details) and an external disclosure layer (publishable summaries).

This prevents the most common failure modes: (1) leaking sensitive data, or (2) publishing untraceable numbers.

Internal layer: threshold calculation sheet, audit reports, EMS evidence, action tracking, savings verification, approvals.
External layer: annual report disclosure fields and summaries; data centre publication outputs; public-body reports (as implemented nationally).
Link both layers through an evidence index and a versioning scheme.

Section 2

Article 11 outputs: Action Plans + implementation rate disclosures

The directive expects enterprises on the audit route to produce a concrete and feasible Action Plan based on audit recommendations.

It also requires the Action Plans and the recommendation implementation rate to be published in the enterprise annual report and made publicly available, subject to confidentiality protections.

Action Plan fields, recommendation, decision, rationale, owner, due date, budget, expected savings, and measurement method.
Implementation rate, define what counts as implemented and keep the definition stable from year to year.
Management submission, keep the record of when the Action Plan was submitted to management and which resources were approved.
Confidentiality handling, publish aggregated rates and themes, and keep site-level sensitive details internal.

Section 3

Data centres: annual publication outputs (>=500 kW installed IT demand)

Treat data centre publication as a recurring compliance output with stable definitions, QA, versioning, and database submission controls.

If you change boundaries or measurement methods, document why and how comparability is maintained.

Publication package, required Annex VII information, calculation notes, and the confidentiality review record.
Database submission, report the KPIs to the European database under Delegated Regulation (EU) 2024/1364, first by 15 September 2024 and then by 15 May each year from 2025.
Versioning, year, perimeter, definitions, publication URL, database confirmation, and internal raw dataset.
Quality gates, validation checks, anomaly handling, sign off workflow, and comparability notes.

Section 4

Suggested KPI set (make it comparable year-over-year)

Choose KPIs you can sustain. If the KPI set changes every year, you lose comparability and trust.

Use a small core set plus optional site-level deep dives.

Energy consumption, total by carrier and any normalized intensity metric that is meaningful for the operation.
Route decision, 3 year average TJ with data sources, conversion factors, and annual refresh date.
Measures, count of measures identified, accepted, implemented, estimated savings, verified savings, and lifecycle cost distribution.
Action Plan execution, on-time completion rate, budget variance, management approval date, and recurring benefits sustained.
Data centres, installed IT power demand band, publication completeness, database submission status, and year-over-year change explanations.

Section 5

Operating cadence (who runs what, when)

Reporting works when it is a calendar process with clear owners and approvals.

Assign one person accountable for the evidence index and publication schedule.

Q1, refresh the threshold calculation and boundary memo, and confirm the route and coverage.
Q2 to Q3, update audits and Action Plans, verify savings, and prepare EMS internal audits and management review.
Q4, prepare the annual report disclosure layer, aggregate the implementation rate, and finalize the data centre publication and database package if applicable.
One accountable owner, keep one person responsible for the evidence index, publication schedule, and version history.

Recommended next step

Operationalize EU Energy Efficiency Directive (EED) Reporting and Metrics across ESG workflows

ESG Compliance can take EU Energy Efficiency Directive (EED) Reporting and Metrics from operationalizing this sustainability obligation across workflows and reporting 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.

ESG workflow

Open ESG Compliance for EU Energy Efficiency Directive (EED) Reporting and Metrics

Start from EU Energy Efficiency Directive (EED) Reporting and Metrics and manage cross team sustainability work, reporting, and evidence from one workflow.

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) Reporting and Metrics.

Explore next step

Primary sources