Custody transfer turns a stream of oil or gas into money, and the numbers that do the converting have to be trustworthy enough to settle against. A measurement audit is the periodic, structured check that confirms they are. It steps back from any single reading and examines the whole apparatus of a custody point, the meters, the calculations, the calibrations, and the records, to judge whether the quantities being reported are supported by evidence and conform to what the contract and the regulator require. This guide defines what a measurement audit covers, how its scope is framed, and how the findings feed back into measurement discipline, keeping the topic on the measurement-discipline review rather than the SCADA or alarm audits covered elsewhere.
Measurement Audit in one line: A measurement audit is a formal, periodic review of a custody transfer point conducted by an internal measurement group or a third party to verify that its meters, calculations, calibrations, and records conform to contract and regulatory requirements. It is a discipline-level assessment rather than a single calibration or proving run, examining whether the reported quantities are properly supported by documentation and traceable evidence. The output is a set of findings, ranked by significance, that drive corrections and improvements to the measurement.
A measurement audit looks at a custody point as a complete measurement system rather than at any one instrument. On the primary side it examines the meter itself and its installation, the condition and traceability of the primary element, and whether the physical arrangement matches what the calculations assume. On the secondary side it reviews the transmitters and their calibration histories, checking that instruments were verified on schedule, that the as-found and as-left values were recorded, and that any adjustments were documented. The point is to confirm that the hardware producing the raw inputs is sound and its condition is evidenced.
The audit then follows those inputs into the calculations. It verifies that the flow computer or measurement calculation is using the correct method, that the constants and configuration such as plate and pipe dimensions, gas composition, and reference conditions are right and match the physical installation, and that the results can be reproduced from the recorded inputs. This is where a measurement audit connects the physical meter to the reported quantity, checking that the arithmetic between them is both correct and consistent with the applicable standards the contract references.
Finally the audit weighs the records themselves, because in measurement a quantity is only as defensible as the paper trail behind it. The auditor looks at calibration and proving reports, configuration records, event and change logs, and the quantity records, judging whether they are complete, internally consistent, retained for the required period, and free of undocumented edits. A well-supported custody point can show, for any period, exactly what was measured, under what configuration, with what instruments in what state, and who changed what and when. Gaps in that evidence are findings even when the numbers themselves look plausible.
The scope of a measurement audit is framed against two references: the commercial contract governing the custody point and the applicable regulatory and industry requirements. The contract sets out what the parties agreed about how gas or liquid is measured, the standards to be followed, and the tolerances that apply, while regulation sets the baseline obligations for how measurement is performed and documented. The audit measures the site against both, so a finding is not the auditor's personal preference but a gap between the observed practice and a stated requirement.
A measurement audit is periodic by nature, run on a cadence rather than in reaction to a single event, though a dispute, a significant mismeasurement, or a change of operator can prompt one outside the normal schedule. It can be conducted by an operator's own measurement group as an internal audit, by the counterparty exercising an audit right the contract grants them, or by an independent third party engaged to give a neutral assessment. The higher the value and the more contentious the point, the more likely it is that an independent or counterparty-witnessed audit is involved, because both sides want assurance the numbers they settle on are sound.
It is worth distinguishing this measurement audit from the several other audits an operation runs. A SCADA or alarm audit looks at the control system and its alarm rationalisation; a tag audit checks the integrity of the data historian's tag database; a relative accuracy test audit is a specific emissions-related check on an analyser. The measurement audit is narrower and deeper on one thing: whether a custody transfer point's quantities are correct, supported, and compliant. Confusing it with those other reviews leads people to expect the wrong scope, so it is best treated as the measurement-discipline audit specifically.
The deliverable of a measurement audit is a report of findings, usually ranked by significance, that separates issues which could have affected reported quantities from those that are documentation or housekeeping matters. A finding that a transmitter ran past its calibration due date, or that a configuration constant did not match the installed hardware, carries direct quantity implications and gets priority; a finding that a report was filed late but the numbers are sound is still a gap to close but a lower one. Ranking the findings lets the operator direct effort where the measurement, and therefore the money, is most exposed.
The value of the audit is realised in the follow-up, not the report. Each finding should map to a corrective action with an owner and a due date, and the more useful audits also look for systemic causes, such as a calibration programme that keeps slipping or a change process that lets undocumented edits through, so the fix prevents recurrence rather than patching one instance. Over successive audits the trend in findings becomes a measure of the measurement programme's health in its own right.
A cloud SCADA such as Merobix makes both the audit and the follow-up materially easier by keeping the evidence continuously available and centralised. When quantity records, event and configuration logs, alarms, and calibration status for many custody points live in one accessible system, an auditor can pull the trail for any period without a site visit or a scramble to assemble records, and the operator can monitor between audits for the very conditions audits catch, such as an instrument drifting toward its due date or a configuration change without a logged reason. That continuous visibility does not replace the formal periodic audit, but it shrinks the surprises the audit uncovers and shortens the path from a finding to a verified fix.
A proving or calibration checks one instrument's performance at one time, whereas a measurement audit steps back and reviews the whole custody point, including whether those provings and calibrations were done on schedule, recorded properly, and applied correctly. The audit uses calibration and proving records as evidence rather than performing them. In short, proving verifies a meter, and the measurement audit verifies that the entire measurement system and its records conform to contract and regulation.
It can be conducted by the operator's own measurement group as an internal audit, by the counterparty exercising an audit right granted in the contract, or by an independent third party engaged to provide a neutral assessment. Higher-value or more contentious custody points are more likely to involve an independent or counterparty-witnessed audit, since both parties want assurance the settled numbers are sound. The choice depends on the contract terms and the reason the audit is being run.
Common findings include instruments run past their calibration due dates, configuration constants that do not match the installed hardware, quantities that cannot be reproduced from recorded inputs, undocumented changes to a flow computer, and incomplete or improperly retained records. Findings are usually ranked so that issues capable of affecting reported quantities are prioritised over pure documentation or housekeeping gaps. Each should map to a corrective action with an owner and a due date.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.