ISO 50002 Energy Audits: Process, Scope and Reporting Explained

Most organisations that "had an energy audit" actually received a list of suggestions. ISO 50002 exists to make the exercise repeatable and defensible: it specifies the process an energy audit must follow, the evidence it must rest on, and what the report must contain. The result is a set of opportunities with quantified savings, costs and confidence levels — something a finance director can act on.

What ISO 50002 is — and is not

ISO 50002, Energy audits — Requirements with guidance for use, is a process standard. It applies to all forms of energy and all types of organisation, and it deliberately does not tell you which measures to install or set sector-specific thresholds. It defines how the audit is planned, conducted, analysed and reported, and what competence and independence the auditor needs.

It also is not a management system. That is ISO 50001 — and the two are complementary: the audit is the diagnostic that finds opportunities, while ISO 50001 is the framework that keeps delivering them. In Europe, the closely aligned EN 16247 series covers the same ground (with parts for buildings, processes, transport and auditor competence) and is the reference commonly cited for mandatory audit obligations under energy-efficiency legislation.

The audit process, step by step

• 1. Planning and agreeing the scope. Objectives, boundary, level of detail, timeframe, the data required and who provides it. Ambiguity here is the single biggest cause of a disappointing audit;
• 2. Opening meeting. Brief the site team, confirm access and safety, agree the measurement plan and set expectations for what the audit will and will not cover;
• 3. Data collection. Utility bills and interval data, meter and sub-meter records, equipment inventories and ratings, operating schedules, production or occupancy data, and previous studies;
• 4. Measurement. Where existing data is insufficient, targeted measurement — temporary logging, power quality, temperatures, flows, run hours — to close the gaps that matter;
• 5. Site visit. Verifying what is actually installed and how it is genuinely operated, which is routinely different from the drawings and the schedules;
• 6. Analysis. Building the energy balance, normalising for weather and activity, establishing performance indicators and baselines, and quantifying each opportunity's saving, cost and interaction with the others;
• 7. Reporting. The deliverable, covered below;
• 8. Closing meeting. Presenting findings, testing assumptions with the people who run the plant, and agreeing priorities.

Scaling the depth: not every audit is the same

A useful feature of the standard is that audit rigour is scaled to purpose and agreed up front. In practice this spans a spectrum:

• Screening / walk-through — bills, a site tour and benchmarking to size the prize and find obvious wins;
• Detailed — sub-metering, an energy balance by end-use, and costed measures with reasonable confidence;
• Investment-grade — measurement-backed, often supported by calibrated simulation, with savings robust enough to underwrite finance or a performance contract.

Paying for investment-grade rigour on a small site wastes money; commissioning a walk-through to justify a seven-figure retrofit wastes the whole project. Matching the level to the decision being made is the client's most important choice.

What the report must deliver

ISO 50002 sets expectations for the output, and a compliant report is notably more than a measures list. It should present the scope and methodology (so results can be reproduced), the energy-consumption baseline and its breakdown by end-use, the performance indicators used, and then — for each opportunity — the estimated energy and cost saving, implementation cost, payback or return, the assumptions behind the numbers, and the confidence level. Interactions between measures must be handled honestly: better controls and a more efficient chiller do not deliver the sum of their individual savings.

Where savings will later be claimed or guaranteed, the audit should also state how they will be verified — which is where ASHRAE Guideline 14 and IPMVP measurement & verification pick up the thread.

Where audits fall down

• No agreed boundary — arguments later about whether tenant loads, transport or a leased unit were ever in scope;
• Bills without interval data — monthly totals hide the overnight and weekend baseload where the easiest savings usually sit;
• No normalisation — a mild winter is reported as a saving, which destroys credibility at the first cold year;
• Measures listed without costs — unfundable, so nothing happens;
• No owner — a report with no named person accountable for each action becomes shelfware.

The takeaway

ISO 50002 turns "we should look at our energy" into a structured, evidence-based exercise with an auditable trail. Agree the boundary and the depth before anyone visits site, insist on interval data and weather normalisation, and demand that every opportunity carries a cost, a saving and a stated confidence. Then hand the good ones to a named owner — the standard finds the savings, but only your organisation can bank them.

This article is general guidance and reflects information available at the time of writing. ISO 50002 and EN 16247 requirements are defined by the published standards and are periodically revised — always confirm the current edition and any national or regulatory obligations that apply to your organisation.