Completion Fluids and Brine: Density, Clarity, and What a Plugged Screen Costs

The fluid that touches the formation decides completion quality. Brine does two jobs at once: it holds the well in balance with its density, and it leaves the pay zone clean enough to produce. Get the first wrong and the well can kick. Get the second wrong and the formation takes damage it never gives back. This guide covers what a completion fluids program has to control, what API RP 13J asks for, and why the completion report has to carry the numbers.

Why completion fluid is a completion risk

Solids are the quiet killer in a completion. A brine that looks clear to the eye can still carry enough particles to plug a wire-wrapped screen or a gravel pack. Once a screen plugs, the well either cleans up slowly or never reaches its expected rate, and the fix is usually a workover that costs more than the original completion.

Density swings are the second risk. Brine is the primary barrier for most of the completion, and the well relies on it until the tree is in place. If density drifts low, the well is underbalanced and can take a kick. If it runs high, fluid is lost into the formation and the salt used to make the brine starts damaging the rock it is meant to protect. Clarity matters for the same reason: the cleaner the fluid that touches the formation, the less damage before the well goes on production. The isolation work that starts at the cement sets the standard here (see the casing and cementing isolation guide), and the brine has to meet it.

What API RP 13J covers

API RP 13J is the recommended practice for heavy brine well control fluids. It covers brine selection, density control, filtration, and the field testing methods used to prove the fluid is right. Operators and service companies write it into their completion programs so both sides run the same tests and judge the same numbers.

The practice sets the clarity targets and the tests to check them, including suspended solids measurement, filtration testing, and the handling of samples. It also covers instrument calibration and how results get recorded. A supplier lab sheet means little if the field tests disagree; RP 13J gives everyone the same test to run so the argument stops at the data.

The loading and testing sequence

Filtering happens at the plant and it happens again on location. The cleanest load starts with filtered brine in a pit that has been washed and inspected, transferred through clean lines into a tank that is checked before it is filled. A dirty pit or a rusty manifold can undo an entire filtration campaign in one load. The same attention to preparation carries into the pumping stage, and it pays to keep the completion and frac crews on the same page about what is in each tank (see the frac support coordination guide).

Density checks happen before the job and during it. The first check is against the ticket at transfer, the next is at the tank before pumping starts, then samples run at set intervals during displacement and again once the string is on depth. Every check goes on a brine test sheet with the time, the tank, and the person who ran it. That sheet is the proof the well stayed in balance from load to handover.

The record that proves it

Brine work is invisible once the well is handed over, which is exactly why it has to be documented. The record is the brine ticket, the test sheets, and the filtration reports. Together they show what went into the well, what it tested at, and when it was checked. A completion file without them is a file with a hole in it, and the next engineer to touch the well will have to guess. Paper tickets that go missing cost real money (see what a lost rig ticket costs), and brine documents are no different.

Attach those documents to the completion record the day the job runs, while the numbers are still on someone's desk. Field software that keeps tickets, timesheets, approvals, and documents on the same job makes it routine: the brine ticket is scanned, the test sheet is attached, and the completion record is complete before the rig moves. Try it in OpsFlo field software on the next completion.

← Back to rigs.work