What this is
What is a meter reading record?
What is a meter reading record?
It is the individual data point behind meter-based maintenance: running hours, cycle counts, distance or throughput for one asset, taken at a set interval. Each entry carries the previous reading, the calculated usage since last time, and a plausibility check, so the number is trusted before it feeds anything downstream.
What makes a reading 'implausible'?
A reading is implausible when it is lower than the last one without a documented reset, or when the jump since the last reading is outside what the asset could plausibly do in the elapsed time. Both point to the same two causes: a meter fault, or a transcription error, and the record forces a call on which before the figure is used for anything.
How does this differ from the Meter Based PM Record?
This record captures the raw reading and whether it looks trustworthy. The Meter Based PM Record (MNT-027) is the maintenance event that fires once a reading crosses a threshold. This template can trigger that one, but it exists independently of whether any PM work is due — readings are taken on schedule regardless.
Scope
When is a meter reading record required?
This is a single reading, not a maintenance event and not a schedule. Recording the wrong thing here means the utilisation trend it feeds is wrong from the first entry.
Use this template when
- A scheduled meter round is due for an asset with running hours, cycles or distance tracked
- An operator or technician is capturing a running total at the point of observation, not reconstructing it later
- The reading needs to be checked for plausibility against the previous value before it counts
- A meter has been replaced or reset and the offset needs to be recorded against the new baseline
- The reading is being used to decide whether a meter-based PM interval has been reached
Do not use it for
- Meter Based PM Record, which is the maintenance event that fires once a threshold is crossed, not the reading itself.
- Preventive Maintenance Plan, which sets the interval and logic this reading is checked against, rather than capturing any single data point.
- Daily PM Checklist, which covers routine condition and lubrication checks on a fixed calendar, not usage-based readings.
- Downtime Record, which captures when an asset was stopped and why, not how much it has run.
- Anything outside KnowMaintain, which belongs in the workspace that owns that process.
Compliance mapping
Which ISO 55001 cl.9.1 requirements does this satisfy?
ISO 55001 cl.9.1 covers monitoring, measurement, analysis and evaluation of asset performance. This record is where that clause becomes a specific, timestamped number rather than a general commitment to 'monitor condition'.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 55001 cl.9.1 | Determine what needs to be monitored and measured, including asset condition and usage | Readings |
| ISO 55001 cl.9.1 | Retain documented information as evidence of the monitoring results | Header |
| ISO 55001 cl.9.1 | Evaluate asset performance against what the maintenance plan assumed | Utilisation |
| ISO 55001 cl.9.1 | Ensure measurement methods produce valid, comparable results over time | Readings |
| ISO 55001 cl.9.1 | Analyse monitoring data to inform maintenance decisions | Utilisation |
| ISO 55001 cl.9.1 | Identify who carried out the measurement and when | Header |
| ISO 55001 cl.9.1 | Account for changes to monitoring equipment that affect measurement continuity | Readings |
What it does not cover
- A reading logged without checking it against the previous value, which lets a meter fault or a mistyped figure flow straight into the utilisation trend.
- A meter marked 'Suspect' or 'Faulty' with no follow-up captured, which leaves the asset running on a broken sensor until someone happens to notice.
- A reading recorded against the wrong asset ID, which corrupts that asset's usage history and understates the correct asset's at the same time.
- An offset applied after a meter reset without the reason on file, which makes the lifetime running total impossible to reconcile later.
- Utilisation flagged 'Higher than assumed' with no interval review triggered, which leaves the PM plan running on a rate the asset has already outgrown.
Global
Meter Reading Record requirements by country
ISO 55001 is a voluntary international standard with no statutory force on its own, so what actually drives adoption of disciplined meter reading varies by where the asset sits and who is asking for the evidence.
ISO 55001:2014
Certification body
A certified asset management system needs evidence that condition and usage monitoring actually happens at the frequency the plan specifies, not just that a plan exists on paper.
PAS 55 heritage practice
Industry expectation, pre-dating ISO 55001
UK asset-intensive sectors that built asset management practice on PAS 55 still expect meter data as the baseline evidence for utilisation-based interval decisions, independent of formal certification.
No federal meter reading mandate
Contractual and insurance driver
Adoption is usually driven by warranty terms tied to hours or cycles, and by insurers who expect utilisation records as evidence that maintenance intervals were actually followed, not assumed.
How to complete it
How to complete a meter reading record, step by step
Filling in the fields is mechanical. The judgement calls that decide whether the record is defensible sit in how those fields are interpreted at the point of entry.
The template gives three options and no numeric threshold. A site needs its own working definition of what jump in hours or cycles is impossible for a given asset, or 'plausible' becomes whatever the person entering the reading feels like on the day.
Anyone can tick 'Meter Replaced Or Reset' and enter an offset. Whether that offset is checked against the actual replacement work order, rather than just typed in to make the running total look continuous, is the difference between a real correction and a fabricated one.
The field exists to flag drift, but flagging is not the same as acting. A site has to decide whether 'Higher than assumed' automatically opens a PM interval review, or whether it's left to whoever reads the report next — which in practice means it often isn't.
If the meter feeding a threshold-based PM is marked faulty, the interval calculation is running on unreliable input. Deciding whether that suspends the automatic trigger, or whether the schedule proceeds on the last trusted reading, changes what 'due' means for that asset.
What auditors find
Most common meter reading record findings
The failures that turn up in reviews of meter-based maintenance data cluster around the same handful of gaps, almost always caught after a schedule has already run on bad numbers.
| Finding | Clause | What fixes it |
|---|---|---|
| Usage-since-last-reading calculated and used despite the reading being marked 'Questionable' | ISO 55001 cl.9.1 | Hold questionable and impossible readings out of the utilisation calculation until the meter is verified, rather than letting the figure pass through by default. |
| No previous reading captured, so the plausibility check has nothing to compare against | ISO 55001 cl.9.1 | Pull the last accepted reading for the asset automatically rather than relying on the operator to remember or look it up. |
| Meter reset offsets applied with no reference to the work that caused the reset | ISO 55001 cl.9.1 | Require a linked work order or replacement reference whenever an offset is entered, so the lifetime total can be audited. |
| 'PM Interval Review Needed' left as 'No' on records where utilisation was flagged as drifting | ISO 55001 cl.9.1 | Treat a drift flag and a 'No' review answer on the same record as a contradiction worth querying, not two independent fields. |
| Faulty meter recorded with no corrective action raised against the asset | ISO 55001 cl.9.1 | Route any 'Faulty' or repeated 'Suspect' result straight into a work request rather than leaving it as a comment on the reading. |
| Readings taken well outside the set interval, with the gap itself unrecorded | ISO 55001 cl.9.1 | Compare the reading date against the expected interval and surface the gap, since a late reading understates true usage between rounds. |
Case in point
Case in point: the compressor that ran hot for six weeks on a stuck meter
An hours meter on a plant air compressor seized at a fixed value after a wiring fault. Every weekly round for six weeks logged the same figure, each one accepted because it wasn't lower than the last reading and the jump — zero — never tripped the impossible-jump check built for excessive usage, only for excessive shortfall.
The compressor kept running well past its hours-based service interval because the PM trigger never fired. It was caught on a routine vibration check, by which point a bearing had already started to go. The gap the record missed was a reading that stayed suspiciously flat, not one that jumped — a plausibility check tuned for one failure mode and blind to its mirror image.
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.
3 sections
- Reference
- MNT-028
- Archetype
- Record
- Record ID
- MTR-2026-000
- Scoring
- Not scored
- Direction
- n/a
- Singleton
- No
- Basis
- ISO 55001 cl.9.1
- Links
- Links Asset
- Tags
- Maintenance, Data
- Sections
- 3
- Fields
- 25
- Follow up fields
- 2
- Repeating sections
- 1
- Links out
- 3
Header
10 fieldsRecord ID*
Auto sequence. Format MTR-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*
Raised By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area
The area within the site.
Exact Location
Drop a pin for anything hard to find.
Asset*
Asset ID*
Format AST-0000.
Links to FDN-002 Asset ID
Readings
Repeats9 fieldsMeter Type*
Reading*
Reading Date*
Previous Reading
Usage Since Last Reading
Plausible*
A reading lower than the last one, or an impossible jump, means a meter fault or a typing error.
- Yes3 pts
- Questionable1 pt
- Impossible0 pts
Meter Working Correctly*
- Yes3 pts
- Suspect1 pt
- Faulty0 pts
Meter Replaced Or Reset
Offset Applied
Utilisation
6 fieldsUtilisation Versus Assumed*
Assets used far more or far less than the PM plan assumed need their intervals revisited.
- As assumed3 pts
- Higher than assumed1 pt
- Lower than assumed1 pt
PM Interval Review Needed*
- No3 pts
- Yes1 pt
PM Triggered By This Reading
PM Record ID
Links to MNT-027 PM ID
Recorded By*
Signature*
MNT-028 · record IDs look like MTR-2026-000 · Links Asset
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form captures one number. Catching the meter that's stuck, chasing the reading that's overdue, and turning a drift flag into an actual interval review is the work that slips.
Holds the meter reading history against the asset register, flags readings that fail the plausibility check, and keeps utilisation drift visible instead of buried in a report nobody opens.
Picks up any corrective action raised from a faulty or suspect meter and tracks it through to closeout, so 'someone should look at that' doesn't stay a comment on a reading.
Keeps the assumed usage rate the PM plan was built on next to the actual reading trend, so a drift flag has something concrete to be checked against.
Chases overdue meter rounds, surfaces assets sitting on a stuck or flat reading, and holds every write to the record for your approval before it touches the register.
This template lives in KnowMaintain — asset maintenance. Work orders, planned maintenance, calibration, reliability and shutdowns.
Meet KnowMaintain→Glossary
Meter Reading Record definitions and key terms
- Meter-based maintenance
- A PM strategy that triggers work from actual usage — hours, cycles, distance — rather than from a fixed calendar interval.
- Running hours
- Cumulative operating time recorded from an asset's hour meter, the most common basis for meter-based PM on rotating and combustion equipment.
- Plausibility check
- The comparison of a new reading against the previous one and the elapsed time, used to catch meter faults and entry errors before they reach the trend.
- Utilisation drift
- The gap between an asset's actual measured usage rate and the rate its PM plan was designed around, whether running harder or standing idle more than assumed.
- Meter offset
- A correction value applied after a meter is replaced or reset, needed to keep the asset's lifetime running total continuous across the change.
FAQ
Frequently asked questions about meter reading record
What is the meter reading record template based on?+
It is built against ISO 55001 cl.9.1, the asset management systems clause covering monitoring, measurement, analysis and evaluation. It underpins every meter-based PM decision made from this data.
What sections does the meter reading record contain?+
Three sections: Header, Readings and Utilisation. Readings repeats where more than one meter is captured for the same round.
How often is a meter reading record raised?+
At the moment the reading is taken, on the fixed interval the asset's meter schedule specifies — not reconstructed afterwards from memory or a paper tally sheet.
What happens when a reading is marked impossible?+
It should not be allowed to update the usage-since-last-reading figure or the utilisation comparison until the meter is checked. Treating it as a normal data point defeats the purpose of the plausibility field.
Does this record trigger maintenance work directly?+
It can flag that a threshold has been reached, but the actual PM event is captured on the Meter Based PM Record (MNT-027). This template is the evidence trail behind that trigger, not the work itself.
Can the meter reading record template be changed?+
Yes. The plausibility thresholds, meter types and utilisation logic are all editable, and the link to the asset register comes with it. Most sites install it as it is, run it for a cycle, then tighten the thresholds.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Planned Maintenance
Asset Register
Holds every piece of equipment, machine, vehicle and tool you track
Tool and Equipment Register
Holds portable tools, gauges, lifting accessories and small equipment that sit below asset level but still need control
Maintenance Request
Asks maintenance to look at a problem or carry out a job
Work Order
The main record for a planned maintenance job, covering what, where, who and when
Corrective Work Order
Covers a repair to fix something that has already failed or degraded
Emergency Work Order
Covers urgent work where equipment has stopped or become unsafe
More in PM Schedules
Preventive Maintenance Plan
Sets out what preventive work each asset needs, how often and why
Daily PM Checklist
Covers daily checks such as lubrication points, fluid levels and visual condition
Weekly PM Checklist
Covers weekly preventive tasks including cleaning, belt and chain checks and minor adjustments
Monthly PM Checklist
Covers monthly preventive tasks including deeper inspection, filter changes and fastener checks
Quarterly PM Checklist
Covers quarterly preventive tasks that usually need the asset stopped
Annual PM Checklist
Covers the yearly overhaul tasks, including full strip down where required
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 55001:2014 cl.9.1 — Monitoring, measurement, analysis and evaluation
- ISO — International Organization for Standardization, standard governance
- PAS 55 — Optimal management of physical assets (heritage UK practice)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.