What this is
What is an energy consumption log?
What is an energy consumption log?
An energy consumption log is the periodic record of energy use by source and area, taken from meters and invoices. It exists to turn utility bills into structured data, consumption by meter, by energy type and by area, against which base load, intensity and variance can be tracked over time.
What is the difference between a consumption log and an energy review?
The log captures the raw readings; the review analyses them. A log entry with no review behind it is just an archived number, and a review with no log behind it has nothing to analyse. The two are sequential, not interchangeable.
What is base load, and why does the log ask for it?
Base load is what a site draws when nothing is being made: standing losses from compressors, refrigeration and lighting left running. It is usually the easiest saving available, and a log that never separates it from production consumption cannot show whether it is falling.
Scope
When is an energy consumption log required?
The log is the input, not the analysis. Its most common misuse is being read as though it already contains the conclusion the energy review is supposed to produce.
Use this template when
- A metered energy source needs its reading captured for the period: electricity, gas, fuel oil, steam or compressed air
- A new meter or sub-meter has come into service and needs to be added to the record
- Production volume is available for the period, so consumption can be normalised into an intensity figure
- A reading looks implausible or a meter looks suspect, and that needs to be flagged before it feeds anything downstream
- The Energy and Decarbonisation programme needs current consumption data to run its next review or report
Do not use it for
- Energy Review, which analyses the logged data to identify where energy is used most and where savings are available
- Energy Saving Initiative, which records a specific reduction project, its baseline, cost and result
- Greenhouse Gas Inventory, which converts consumption into emissions rather than tracking it as energy
- Environmental Performance Report, which compiles this data for external reporting rather than capturing it
- Meter calibration or asset maintenance records, which belong with the meter as an asset, not with the reading it produced
Compliance mapping
Which ISO 50001 cl.9.1 requirements does this satisfy?
ISO 50001 treats energy data as an input to a management system rather than an end in itself, so the clauses that govern a consumption log describe how the data is planned for and used, not the format of the log.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 50001 cl.6.6 | Planning for the collection of energy data: meters, relevant variables, frequency and responsibility defined and applied | Header |
| ISO 50001 cl.9.1 | Monitoring and measurement of key characteristics of operations that determine energy performance, using equipment that provides valid data | Readings |
| ISO 50001 cl.9.1.1 | Determination of what needs to be monitored and measured and the criteria against which energy performance is evaluated | Site totals |
| ISO 50001 cl.6.4 | Energy performance indicators appropriate to monitoring and measuring energy performance, reviewed and compared against the baseline | Site totals |
| ISO 50001 cl.8.1 | Operational planning and control of significant energy uses, including base load and non-production consumption | Base load |
| ISO 50001 cl.7.5.3 | Control of documented information: retained, protected and available where it is needed | Related records |
What it does not cover
- Energy Review, which analyses this log's data over a period to identify where energy is used most and where savings are available.
- Energy Saving Initiative, which records a specific reduction project's baseline, cost and result once one has been identified.
- Greenhouse Gas Inventory, which converts logged consumption into an emissions figure using separate conversion factors.
- Environmental Performance Report, which compiles this data for external reporting rather than capturing it in the first place.
- Meter calibration or asset maintenance record, which is where a suspect or faulty meter is actually diagnosed and fixed.
Global
Energy Consumption Log requirements by country
Few regimes mandate a consumption log as a distinct instrument. What they mandate is the disclosure or certification outcome the log's data feeds, which is why its regulatory reach is indirect.
SEC climate-related disclosure rule; state and municipal energy benchmarking ordinances
No federal duty to log consumption, but disclosed and benchmarked figures are drawn from exactly this data.
The log itself satisfies no US instrument directly, but a site without reliable readings cannot support whatever disclosure obligation sits above it.
Streamlined Energy and Carbon Reporting (SECR)
Large companies must disclose UK energy use and intensity annually in the directors' report.
The totals and intensity figures this log produces are the primary source data for that disclosure, so an unreliable log becomes an unreliable disclosure.
ISO 50001 cl.6.6 and cl.9.1
Certified organisations must plan energy data collection and monitor performance against defined criteria.
Certification audits examine this log directly. Gaps in metering coverage or unexplained variance are a documented nonconformity, not just a data quality issue.
How to complete it
How to complete an energy consumption log, step by step
The log's fields are arithmetic. What decides whether the data underneath is worth anything is judgement the form does not prompt for.
A consumption jump has three explanations: a real change in production or weather, a meter or reading error, or a genuine saving or loss nobody has noticed yet. Recording the percentage without pursuing which of the three applies converts a signal into decoration.
Non-production consumption does not fall just because output rose; it has to be measured on its own account, typically from off-hours or weekend readings, or it disappears inside a total that improves purely through dilution. A site cannot know whether its standing losses are falling if they are never isolated.
A raw total answers nothing on its own. Energy per tonne of product, adjusted for the things that genuinely vary period to period, is what determines whether a low month is an improvement or just a quiet one. Comparing raw totals across periods with different output flatters or damns the site for reasons unrelated to energy performance.
A meter marked suspect or faulty should have its reading held out of the intensity and variance calculations until it is fixed or replaced, with the gap noted rather than estimated silently. A trend built partly on noise looks like data and isn't.
What auditors find
Most common energy consumption log findings
The findings against a consumption log are less about missing entries and more about entries that were never interrogated.
| Finding | Clause | What fixes it |
|---|---|---|
| Readings recorded without a plausibility or meter-working check. | ISO 50001 cl.9.1 | Require Reading Plausible and Meter Working to be answered before the entry is accepted, and route anything but Yes to review. |
| Base load and non-production consumption never separated from the total. | ISO 50001 cl.8.1 | Capture an off-hours or weekend reading each period and record it against Non Production Consumption, not just the monthly total. |
| Variance against the previous period left unexplained. | ISO 50001 cl.9.1.1 | Require a stated reason wherever variance exceeds a defined threshold, tied to a production, weather or fault explanation. |
| Energy per tonne of product calculated without a matching production figure for the same period. | ISO 50001 cl.6.4 | Enter Production Volume for the identical period as the consumption reading before deriving intensity. |
| A meter recorded as suspect or faulty with its reading still feeding the site total. | ISO 50001 cl.9.1 | Exclude or flag suspect and faulty meter readings in the total, and open an action to fix the meter. |
| Unexplained consumption logged as 'some' or 'significant' with no linked action. | ISO 50001 cl.8.1 | Raise the action record and populate Action Required, CAPA ID and owner whenever unexplained consumption is anything but none. |
Case in point
Case in point: the total that hid a failing compressor
A site logged total electricity every month for two years, with variance sitting comfortably under ten percent each period. Production had grown steadily over that time, so a rising total read as expected and nobody split it against output. When an energy review was finally run, energy per tonne of product had climbed for six consecutive quarters, a trend the raw total had completely absorbed.
The cause was a compressed air leak that had grown slowly enough that no single month's variance ever crossed the threshold anyone was watching. Non-production consumption, never separately logged, would have shown the base load rising independent of output from the first quarter it started. The fix was not a bigger variance check; it was logging base load every period instead of only when someone remembered to ask for it.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- ENV-031
- Archetype
- Log
- Record ID
- ECL-2026-000
- Scoring
- Consumption per unit
- Direction
- High is bad
- Singleton
- No
- Basis
- ISO 50001 cl.9.1
- Links
- Links Site, Asset
- Tags
- Environment, Energy
- Sections
- 5
- Fields
- 40
- Follow up fields
- 3
- Repeating sections
- 1
- Links out
- 3
Header
6 fieldsLog ID*
Auto sequence. Format ECL-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Readings
Repeats9 fieldsMeter Reference*
Energy Type*
Electricity, natural gas, fuel oil, steam or compressed air.
Area Or Plant Served*
Reading*
Consumption This Period*
Previous Period
Variance Percent
Reading Plausible*
- Yes3 pts
- Questionable1 pt
- Impossible0 pts
Meter Working*
- Yes3 pts
- Suspect1 pt
- Faulty0 pts
Site totals
9 fieldsTotal Electricity*
Total Gas
Total Energy*
Production Volume
Energy Per Tonne Of Product*
Intensity Trend*
- Improving3 pts
- Stable2 pts
- Worsening0 pts
Peak Demand
Peak Demand Charges Incurred
- No3 pts
- Yes0 pts
Power Factor
Related records
1 fieldPerformance Report ID
The report this consumption data feeds.
Links to ENV-053 Report ID
Base load
15 fieldsLook At Non Production Hours
What the site draws when nothing is being made is pure waste and usually the easiest saving on the plant. Compressors, lighting and refrigeration dominate it.
Non Production Consumption
Base Load Percent Of Total
Base Load Trend
- Falling3 pts
- Stable2 pts
- Rising0 pts
Refrigeration Share
Typically the largest single load on a meat or dairy site.
Compressed Air Share
Unexplained Consumption*
- No3 pts
- Some1 pt
- Significant0 pts
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Energy Lead*
Signature*
Engineering*
Second Signature*
ENV-031 · record IDs look like ECL-2026-000 · Links Site, Asset
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The log itself is simple arithmetic. What fails around it is the meter nobody flagged, the base load nobody separated out, and the variance that sat unexplained until the review found it.
Holds the consumption log against the meter and site register, flags gaps and suspect readings, and carries the totals forward into the review and inventory that depend on them.
Takes a meter flagged suspect or faulty out of the log's data and into a calibration or repair work order, so a bad meter gets fixed rather than just noted.
Watches variance and base load trends across periods, and raises the review early when a pattern looks like a real change rather than waiting for the scheduled interval.
This template lives in KnowEnviro — environment and energy. Aspects, permits, waste, emissions, spills and sustainability reporting.
Meet KnowEnviro→Glossary
Energy Consumption Log definitions and key terms
- Base load
- The energy a site consumes when nothing is being made: standing losses from compressors, lighting, refrigeration and controls left running.
- Energy intensity
- Consumption normalised against a production or activity measure, such as energy per tonne of product, used to compare periods with different output fairly.
- Significant energy use
- An area, process or piece of equipment accounting for substantial energy consumption or offering substantial potential for improvement.
- Variance
- The period-on-period change in a reading or total, used to flag whether an unexplained shift needs investigating before it is reported further.
- Energy performance indicator (EnPI)
- A quantified value or measure of energy performance, such as intensity or base load share, defined so it can be tracked consistently over time.
FAQ
Frequently asked questions about energy consumption log
How often should meters be read for the log?+
Monthly, aligned to invoice periods, is the norm and is what most billing and reporting cycles expect. Sub-metered significant energy uses that vary quickly, such as a compressor with an intermittent fault, benefit from more frequent reading, but the monthly cadence is what feeds the review and any external disclosure.
Should the log record consumption with or without normalising for production?+
Both. The raw reading is the fact; the normalised intensity is the interpretation. Recording only the normalised figure loses the ability to check the arithmetic later, and recording only the raw figure loses the comparison the whole exercise exists to support.
What counts as an implausible reading?+
A reading inconsistent with the meter's history, the site's known load, or physical possibility, for instance a jump that would require doubling the site's connected electrical capacity. Flag it rather than average it, because averaging a bad reading into the trend just moves the error somewhere less visible.
Who should complete the log?+
Facilities, because they hold the meter and invoice relationship, but a suspect reading should route to whoever maintains the meter as an asset. The log records the number; fixing the source of a bad number is someone else's job and should not stall in the log.
Does a rising total always mean falling performance?+
No. A rising total with rising production and flat or falling intensity can be a genuinely good period. It is the intensity and the base load share that indicate performance, and reporting the total alone without them tells the reader nothing about whether the site is improving.
What happens to a period where a meter was faulty?+
The gap should be noted, not filled with an estimate presented as a reading. An estimated figure is legitimate provided it is marked as one; a faulty meter's number carried forward as though it were measured data corrupts every trend calculation drawn from it afterwards.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Energy and Decarbonisation
Greenhouse Gas Inventory
Records emissions across scope 1, 2 and where available scope 3
Energy Review
Identifies where energy is used most and where the largest savings are available
Energy Saving Initiative
Records an energy reduction project, its baseline, its cost and its result
Sustainability Objectives
Sets environmental and sustainability targets with measures, owners and dates
Packaging Sustainability Review
Reviews packaging materials for recyclability, weight and recycled content
Supplier Environmental Assessment
Assesses a supplier's environmental performance and certifications
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 50001:2018 clauses 6.4, 6.6 and 9.1
- UK Streamlined Energy and Carbon Reporting (SECR) requirements
- SEC climate-related disclosure rule, energy and GHG data provisions
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.