EU Energy Efficiency Directive Action Plan Evidence Workflow

The evidence workflow should first show why the organisation is in scope and which sites, carriers, and operations are covered. Article 11 uses average annual energy consumption over the previous three years, taking all energy carriers together, as the trigger for enterprise obligations.

Keep the boundary evidence separate from the action-plan evidence. The boundary record explains whether the enterprise is using a certified energy management system, is subject to an energy audit because it does not use one, or is outside the Article 11 enterprise thresholds but still running voluntary audits or SME support measures.

The action plan should be built from the audit recommendations, not from a generic project list. Article 11 says the plan must identify measures to implement each recommendation where technically or economically feasible, and Annex VI requires audits to identify energy-efficiency measures, renewable-energy potential, validated savings calculations, and data that can be stored for historical analysis and tracking performance.

A useful evidence record therefore pairs each recommendation with a feasibility conclusion, expected savings, implementation owner, target asset or process, and the reason for deferring any recommendation that is not technically or economically feasible.

Article 11 requires Member States to ensure that action plans and recommendation implementation rates are published in the enterprise's annual report and made publicly available, subject to trade-secret, business-secret, and confidentiality protections under Union and national law. The workflow should therefore separate publishable information from protected technical or commercial detail before annual-report drafting starts.

For public-sector workstreams, use a different evidence lane. Articles 5, 6, and 7 concern public bodies' consumption reduction, public-building renovation, and high-energy-efficiency public procurement. Those records should identify the public body, building inventory or procurement record, annual energy-consumption evidence, and reporting route rather than being mixed into enterprise audit action plans.

A data-centre operator should not treat the Article 12 reporting file as the same record as an Article 11 audit action plan. The data-centre evidence lane should track the reporting database submission, key performance indicators, and published information required for energy performance and sustainability transparency.

Annex VII identifies the minimum monitored and published information, including operator identity, location, floor area, installed power, data traffic, stored and processed data, and performance indicators such as energy consumption, power utilisation, temperature set points, waste heat utilisation, water usage, and renewable-energy use.

The workflow should be updated when the legal trigger, operating boundary, or measured performance changes. The strongest triggers come directly from Article 11 and Annex VI: a new three-year consumption calculation, a new or renewed energy audit, a change in the certified energy management system scope, management review of recommendations, or new stored operating data showing whether implemented measures are performing.

Operational triggers should also include national implementation changes, confidentiality decisions before annual-report publication, material changes to sites or energy carriers, and data-centre reporting corrections. Each trigger should create a dated evidence entry rather than overwriting the previous action-plan record.