The master meter method is a way to prove a flow meter without hauling in a pipe prover or compact prover. A separately proven reference meter is plumbed in series with the meter being checked, both meters see the same flow, and their readings are compared to work out a meter factor. This guide walks through the actual proving procedure, when operators reach for it, its accuracy limits, and how a SCADA system logs the paired pulse counts.
Master Meter Proving Method in one line: The master meter proving method derives a meter factor by running a known, previously proven reference meter in series with the meter under test so both pass the same volume. The reference meter's corrected volume becomes the standard the working meter is compared against, transferring the reference meter's traceability without a dedicated prover.
In a master meter proving, the master (reference) meter and the meter under test are piped in series so the exact same fluid passes through both during a run. Because the master meter was itself proven against a traceable standard such as a pipe prover, and its own meter factor is known and current, its corrected volume for the run is treated as the true reference volume. The proving system counts pulses from both meters over the same window, applies the master's meter factor and temperature and pressure corrections, and calculates the meter factor for the device under test as the ratio of the reference volume to the raw indicated volume of the working meter.
A run typically starts and stops on a batch of accumulated pulses rather than a fixed physical displacement, since there is no swept prover volume to define the batch. The operator repeats runs until a set of consecutive results falls within the accepted repeatability spread, exactly as with a conventional prover, and the average becomes the new meter factor. Keeping both meters at matched flow rate, temperature, and pressure during the comparison is essential, because any difference in conditions between the two meters translates directly into error in the transferred factor.
The master meter method is attractive where a dedicated prover is impractical: remote wellsite and gathering locations, small skids, temporary or seasonal facilities, and situations where a compact or pipe prover cannot be mobilized cost-effectively. A portable master meter can be carried to several sites in a service truck, letting one traceable reference prove many field meters in a season. It is also common for gas and for high-flow lines where a physical displacement prover would be enormous.
The trade-off is accuracy and traceability chain length. The method stacks the uncertainty of the master meter on top of the working meter's own repeatability, so the result is generally less accurate than proving directly against a pipe or compact prover. The master meter itself must be proven on a regular, documented schedule against a primary standard, and it should be operated near the flow rate and conditions at which it was proven. For those reasons many custody-transfer contracts and standards, including the relevant API MPMS chapter on master meter proving, treat it as an acceptable but secondary method, best used when a displacement prover is genuinely unavailable.
During a master meter proving, both meters are pulse-generating devices feeding a flow computer or proving controller, which is what actually gates the pulse counts, applies the corrections, and computes the factor. A cloud SCADA platform sits above that controller: it records each run's paired raw counts, the master meter factor in force, the live temperature and pressure at both meters, the calculated meter factor, and the pass or fail against the repeatability criterion. Capturing both count streams side by side is what makes the calculation auditable after the fact.
Because Merobix reads these values as tags from the flow computer over a protocol like Modbus or OPC UA rather than wiring to the meters directly, it can time-stamp and retain the full run set, flag runs that fall outside the acceptance band, and roll the accepted average into the working meter's active meter factor. An operator or auditor can then pull up the complete master meter proving from a browser, see which reference meter was used and when that reference was last proven, and confirm the traceability chain without hunting through paper run sheets.
A pipe or compact prover establishes reference volume from a physically calibrated swept volume between detectors, so it is a direct primary comparison. Master meter proving instead uses another meter as the reference, transferring that meter's traceability to the meter under test. It avoids a bulky prover but adds the master meter's own uncertainty to the result.
It is generally less accurate than proving against a displacement prover because the master meter's uncertainty is stacked on top of the working meter's. Accuracy depends heavily on how recently and how well the master meter was proven and on keeping both meters at matched flow, temperature, and pressure. Done carefully it is accepted for many applications but is usually treated as a secondary method.
The master meter must be proven against a traceable primary standard, such as a pipe prover, on a regular documented schedule, because its accuracy is the ceiling for every meter it proves. If the master drifts, every factor it has transferred since its last good proving is suspect. Its proving interval and records are part of the audit trail for any meter it certifies.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.