A well test procedure is the operational routine a field crew follows to measure how much oil, gas, and water a single well is producing. It involves diverting that one well away from the shared production path, routing it to a test separator, waiting for flow to stabilize, and then recording each phase's rate over a defined test duration. Done consistently, the result becomes the well's contribution to allocation and the baseline for spotting production problems. This guide explains the procedure the operator actually runs and how automated test scheduling in SCADA replaces the manual rotation of wells through a test separator.
Well Test Procedure in one line: A well test procedure is the workflow for measuring an individual well's production: it is routed to a test separator, given time to stabilize, and its oil, gas, and water rates are recorded over a set duration. That measured rate is used to allocate the well's share of the battery's total production and to track its performance over time.
A well test starts with routing. On a typical battery, many wells flow together into common equipment, so to measure just one the operator opens that well's path to the test separator and closes it off from the group header, or aligns a multi-well test manifold so only the chosen well reaches the test vessel. From that moment the test separator sees flow from a single source, which is the entire premise of the measurement: whatever oil, gas, and water come through belong to that one well.
Routing a well to a fresh flow path disturbs it, so the procedure requires a stabilization period before any numbers are trusted. When flow is diverted, pressures shift, slugs of liquid move through the lines, and the separator's levels swing until they settle. Recording rates during that transient would misrepresent the well, so the operator waits, often watching separator level and pressure steady out, before starting the timed portion of the test. How long stabilization takes depends on the well and the facility, but skipping it is one of the most common ways a test comes out wrong.
Once stable, the operator records the oil, gas, and water rates over the test duration. Oil and water accumulation or metered flow off the separator liquid outlet, gas rate off the gas outlet meter, and the elapsed time together give the per-day rates for each phase. A longer test averages out the surging that many wells produce naturally and gives a more representative result than a brief snapshot. The recorded rates, tied to the date and duration, become the well's official test for the period.
The reason a battery bothers to isolate and test each well is allocation. The sales meter at the outlet measures the whole battery's production, but that total has to be divided back among the individual wells for accounting, reserves, royalty, and partner shares. The well test is where each well's proportion comes from: its measured oil, gas, and water rates set the ratios used to back-allocate the battery total. A test that is run carelessly does not just misjudge one well, it distorts the share assigned to every well in the group.
Because tests carry that weight, the procedure emphasizes consistency and documentation. The same routing, the same stabilization discipline, and a comparable duration each time make results across wells and across months comparable. The operator records not only the rates but the conditions of the test, so a later reviewer can judge whether a surprising result reflects a real production change or a test that was cut short. A well that suddenly tests very differently prompts a retest before its number is trusted in allocation.
Frequency is part of the procedure too. Wells change: they load up with water, decline, or respond to interventions, so a test from months ago may no longer represent current production. Operators set a target test frequency and rotate wells through the test separator to keep each well's number reasonably current. The manual version of this rotation, walking or driving a route to realign the test manifold well by well, is exactly the labor that automated testing is designed to reduce.
When a test separator and its routing valves are automated, the manual rotation of wells becomes a scheduling problem the control system can solve. Rather than an operator driving out to realign a manifold, motorized valves route each well to the test separator in turn on a defined cycle. SCADA holds the schedule, opens and closes the right paths, and waits out the stabilization period before it begins recording, applying the same timing to every well without the variation a busy crew introduces.
A cloud SCADA platform such as Merobix makes both the schedule and the results visible from a browser. The system can log which well was on test, when it stabilized, and the oil, gas, and water rates it produced, then store those as the well's test record for allocation. Because separator level, pressure, and meter data are trended continuously, an engineer can confirm a test truly stabilized before accepting its numbers, catching the short or disturbed tests that quietly corrupt allocation when they slip through by hand.
The larger benefit is that every well gets tested more often with less effort. Automated rotation keeps each well's number current instead of relying on whichever wells the route happened to reach that month, and the results feed the allocation math with a documented, time-stamped provenance. The well test procedure still defines what a valid test is, stabilization, duration, complete three-phase rates, but SCADA runs it on schedule and preserves the evidence that it was run correctly.
Long enough to pass the stabilization period and then average out the well's natural surging, which varies with the well and the facility. Many operators use a fixed minimum duration after stabilization so results are comparable well to well and month to month. A test that is too short can capture a slug or a lull and misrepresent the well's true rate.
Routing a well to a fresh flow path disturbs its pressures and pushes liquid slugs through the lines, so the separator's levels and rates swing before settling. Recording during that transient would give numbers that do not reflect steady production. The stabilization period lets the flow settle so the measured oil, gas, and water rates are representative of the well.
The well test procedure is the physical routine of routing a well to the test separator, letting it stabilize, and recording its rates. The allocation factor is the math that uses those measured rates to divide the battery's metered total among the wells. The procedure produces the input; the allocation factor is what that input is used to calculate.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.