Research guide · Source evidence and limits
An energy audit is not a pump order
An announcement about an energy audit can justify a research question. It does not establish that a business will replace pumps, change valves or buy a particular control system. Separate the audit, its findings, the organisation's decision and any later implementation evidence.
For Irish industrial suppliers, that distinction helps decide whether to commission broad account research or a narrower investigation into an evidenced development. It also prevents an energy-efficiency narrative becoming an unsupported claim about equipment demand or savings.
This is a commercial research guide, not an energy audit, an equipment recommendation or advice about whether a business has legal audit obligations.
What the primary source establishes
The EU Energy Efficiency Directive defines an energy audit as a systematic procedure to understand an energy-consumption profile, identify and quantify cost-effective saving opportunities and renewable-energy potential, and report findings. That definition covers buildings, industrial or commercial operations and other services.[18]
The distinction between findings and implementation is visible in the text itself. Article 11(2) separately addresses an action plan arising from audit recommendations, with measures to implement recommendations where technically or economically feasible.[18] This guide does not assess which enterprises that provision applies to or interpret its implementation in Irish law.
Annex VI specifies measured, traceable operational data as part of the audit criteria and calls for detailed, validated calculations for proposed measures.[18] A public sustainability headline is not that underlying analysis.
These observations come from the consolidated text dated 5 August 2026, accessed on 1 October 2026.[18] We use them to distinguish types of evidence—not to turn a regulatory provision into a supplier sales deadline.
Classify the statement before interpreting it
| Public statement you might encounter | Record the narrow observation | Keep these questions open |
|---|---|---|
| An audit is planned | The organisation says it plans an assessment | Has it happened, which site or systems are covered, and what was found? |
| An audit is completed | The organisation reports completion | Are relevant findings available and attributable to the target site? |
| A measure is recommended | A stated analysis proposes a specific measure | Has management accepted it, and is an equipment change actually involved? |
| A measure is approved | A decision is reported for a defined scope | How will it be delivered, who selects suppliers, and what remains uncommitted? |
| Work is completed | A defined intervention is reported as implemented | What evidence supports performance, and is any separate future requirement established? |
These are our working research distinctions, not official audit classifications or a mandatory project sequence. Do not populate a later row merely because an earlier one is evidenced.
The object of the statement matters too. A group-wide energy target is not a site-specific project. A building-heating review is not automatically a process-pumping review. “Utilities” is not enough detail to confirm which system, asset or component is involved.
Ask for a relevance bridge, not a savings promise
For a pump or flow-control supplier, a defensible research note needs a bridge from the published observation to the application being investigated:
- Attribute the activity. Identify the company and site. Does the evidence concern its own operations, a customer project or a group-level programme?
- Locate the system. State what is actually described: a production process, cooling circuit, water system or another defined scope. Leave it unknown if the source does.
- Name the change. Distinguish measurement, operating changes, maintenance, design investigation and physical modification. Do not select “equipment change” because that best suits your range.
- Explain the research relevance. Describe why the observed scope may warrant investigation. This remains a hypothesis about relevance, not a technical fit finding.
- Retain the decision gaps. Record approval, specification, delivery route, existing arrangements and package status independently.
Do not multiply a site's energy bill by an assumed savings percentage and present the result as the value of your offer. Do not transfer a savings figure from a published case study to another account. Without the appropriate evidence and technical assessment, energy use is context rather than a product-performance claim.
Worked example — wholly fictional
The supplier, companies, site and all statements below are invented. No actual audit, audit report, grant recipient or customer result is represented.
An invented flow-control supplier's account brief seeks process-production operators in the Republic of Ireland. Its optional project-signal rule requires an evidenced, site-specific proposal affecting a relevant fluid system. An audit announcement alone does not meet that rule.
First record: account fit without a qualifying project signal
Fictional Process Operator C is stipulated to pass the brief's identity, operating-activity, territory, exclusion and source-use checks. An invented statement says C completed an energy audit, but supplies no findings or system scope.
Decision: include C as an industry-matched account. Under the exercise's bounded project review, record no qualifying signal identified in the bounded review. That is not “no project exists”. The audit is an observed contextual event, but it does not satisfy this brief's fluid-system development rule.
Second record: a relevant proposal, not a purchase
A later invented, attributable statement proposes investigating control changes to a recirculating water system at C's fictional production site. It explicitly leaves the choice between operational changes and equipment changes unresolved. The exercise stipulates that the source can be used for the intended output.
Decision: the stated proposal now satisfies the fictional signal rule. Keep the company record stable and add an opportunity-signal classification with the actual scope and stage. Do not create a second company or label it “pump purchase”. The potential relevance is an investigation into a fluid system; compatibility, equipment changes and procurement remain unknown.
Third record: the proposed measure does not require an equipment change
An invented follow-up states that the selected action is an operating-schedule adjustment, with no equipment change in that defined action.
Decision: close the equipment-change hypothesis for this action. Preserve the earlier proposal as history and update the current project note. C may remain a valid industry-matched account if the required checks still hold. A negative equipment result does not erase company fit or prove that C has no other projects.
No savings amount, performance improvement or supply opportunity is established at any point in this example.
Decide which research brief you actually need
Choose account research when the main question is which businesses perform a relevant activity in your territory. A new project is not a prerequisite. Specify the operating role and exclusions rather than requiring every account to have an energy announcement.
Add project-signal research when a defined change is essential to your question. Agree what qualifies: for example, a site-specific proposed change to a fluid system, rather than any sustainability statement. State what evidence is needed and which unknowns remain acceptable at the research stage.
Hold an equipment-change claim when the source identifies only an assessment, broad target or unresolved recommendation. Hold technical and savings conclusions for appropriately qualified assessment. Research-fit is not buying-ready, and a project-signal label is not a probability of sale.
Before handing an efficiency signal to sales
- ☐ Does the observation identify the company, site and relevant system?
- ☐ Are “planned”, “assessed”, “recommended”, “approved” and “implemented” kept distinct?
- ☐ Does the qualifying-signal rule match the evidence, rather than a product keyword?
- ☐ Are company fit and project status separate fields?
- ☐ Are operating changes separated from physical equipment changes?
- ☐ Are savings described only within their evidenced scope, with no transferred or invented result?
- ☐ Are duty conditions, compatibility, supplier selection and present availability left unresolved where unsupported?
- ☐ Does the next check answer a specific missing question, without creating artificial urgency?
Continue from the question to a reviewable output
Use the pump and flow-control prospecting guide to frame the application and customer role. Compare the fictional account examples with the fictional project brief to see why the two research classes need different evidence.
For an activity-led brief, review industrial account research. For a defined development question, review Opportunity Intelligence. Then request a written scope with your range, territory, qualifying change and exclusions. Keep private audit reports, confidential customer information and personal contacts out of the enquiry.
Evidence, attribution and limits
All cited sources were accessed 1 October 2026. No private energy-audit report, manufacturer performance claim or named facility record is used. The research framework and fictional example are original; neither supplies engineering, grant-eligibility or legal advice.
The definitions and audit-criteria summaries are adapted from Directive (EU) 2023/1791, consolidated text of 5 August 2026, © European Union, 1998–2026. EUR-Lex licenses its EU-owned consolidated texts under Creative Commons Attribution 4.0 International.[16] The identified summaries have been shortened and paraphrased and remain available under that licence without additional DemandRange reuse restrictions. No EU endorsement is implied.