Most HSE managers in the oilfield didn’t choose their drug and alcohol testing for oil and gas companies‘ programs based on a legal deep dive. They chose it because an operator’s contractor management platform flagged a gap, or because a near-miss on location made clear that testing wasn’t optional anymore. That’s the honest starting point for this topic. Testing programs in oil and gas exist because the work is genuinely dangerous and because the companies that hire contractors have decided they won’t accept the risk of an impaired worker on a rig, in a confined space, or behind the wheel of a vacuum truck.
This piece walks through where testing obligations actually come from, how operator and contractor responsibilities differ, what state law adds to the picture, and what a program needs to include to survive an audit.
Why the oilfield treats this differently than other industries
Upstream and midstream work combines several hazards that rarely show up together anywhere else: heavy rotating equipment, high-pressure lines, confined spaces, H2S exposure, long-haul driving on rural roads, and crews working extended hours far from home. A worker who’s impaired doesn’t just put themselves at risk. In most locations, a single bad decision can affect an entire crew.
The data backs up why regulators and operators keep the pressure on. Marijuana remains the substance most often flagged in federal drug testing programs. According to data reported through the FMCSA’s Drug and Alcohol Clearinghouse, marijuana accounts for roughly 60 percent of positive results among DOT-regulated drivers, a group that includes a meaningful share of the trucking and hauling workforce that services oilfield sites. State-level legalization hasn’t changed the federal calculus. A positive THC result under a DOT-covered program still triggers removal from safety-sensitive duty regardless of where an employee lives or what their state allows recreationally.
The regulatory layer: what’s actually mandated
Here’s where a lot of confusion starts. OSHA does not require drug and alcohol testing. There’s no OSHA standard that mandates a testing program for oilfield workers, and OSHA’s post-accident reporting rule specifically prohibits employers from using testing to retaliate against an employee who reports an injury, though it does not prohibit testing conducted under DOT or state drug-free workplace rules.
The federal mandate that does apply comes from the Department of Transportation, and it only reaches specific job functions.
Pipeline operators and covered contractors. If your operation involves gas, hazardous liquid, or carbon dioxide pipelines, LNG plants, or underground gas storage, PHMSA’s Part 199 regulations apply to your covered employees, meaning anyone performing operations, maintenance, or emergency response functions on regulated pipeline facilities. For calendar year 2026, PHMSA has set the minimum random drug testing rate at 50 percent of covered employees, the same rate that’s applied since 2020, because industry-wide positive rates reported through the Drug and Alcohol Management Information System have stayed above the 1 percent threshold that would allow a reduction to 25 percent.
Drivers. Trucking is inseparable from oilfield logistics, whether it’s hauling produced water, moving rigs, or delivering sand and chemicals to a frac site. Any driver who holds a CDL and operates under FMCSA authority falls under Part 382, which sets the same testing floor: a 50 percent random drug testing rate and a 10 percent random alcohol testing rate for calendar year 2026. Both DOT programs run on the same underlying procedures, specified in 49 CFR Part 40, covering specimen collection, laboratory testing, and Medical Review Officer review.
What DOT rules don’t cover is the bulk of the field workforce: roughnecks, roustabouts, derrickhands, wireline crews, and most general oilfield labor. Unless that work also involves a covered pipeline function or a CDL, there’s no federal statute forcing a test. That gap is exactly where operator-driven requirements take over.
Contractor site access: where the real enforcement happens
For most contractors, the testing requirement that actually determines whether they can show up to a location doesn’t come from a federal agency. It comes from the operator, enforced through a contractor prequalification platform.
Major operators including ExxonMobil, Marathon, Continental Resources, and XTO Energy require contractors to maintain an active, compliant profile on systems like ISNetworld, Veriforce, Avetta, or NCMS before issuing a work order. These platforms score contractors against categories that typically include a written safety program, OSHA 300 log history, Experience Modification Rate, training records, and drug and alcohol testing policy documentation. Fall short in any category and a contractor can lose the “green check” needed for site access, which in practice means losing the contract.
Veriforce dominates pipeline-adjacent work and ties its qualification records to specific operator requirements under 49 CFR Parts 192 and 195. ISNetworld is more broadly used across general oil and gas and petrochemical operations, with a standardized grading system contractors need to maintain at an A or B level. A contractor working across multiple operators in the Permian Basin or other shale plays will often need active profiles on two or three of these platforms simultaneously, each with its own document upload cadence and renewal deadlines.
The training layer adds another wrinkle worth knowing. Veriforce PEC Safety Training, still widely called PEC Safeland by people in the field, and Basic Orientation Plus are among the most commonly required site orientations. These aren’t the same thing as drug testing compliance, but they usually get reviewed together during a prequalification audit, and missing or expired training records can stall a contractor’s approval just as fast as a missing testing policy.
Operator obligations versus contractor obligations
This is the distinction that trips people up most often. Operators generally don’t run the testing program directly. They set the standard, and they use prequalification platforms and master service agreements to require contractors to meet it. The operator’s obligation is to define the requirement clearly, verify contractor compliance before granting site access, and maintain records showing that verification took place, since the operator inherits liability if an unqualified or untested contractor is injured or causes an incident on location.
The contractor’s obligation is heavier and more operational. A contracting company has to do the following:
- Establish a written policy
- Enroll employees in a random testing pool if DOT-covered functions are involved
- Administer pre-employment and post-accident testing
- Maintain chain of custody and Medical Review Officer review for every test
- Keep documentation current inside whatever prequalification platform the operator uses
That list gets longer when a contractor works for multiple operators. A testing policy that satisfies one operator’s Veriforce profile may need additional documentation to satisfy a different client’s ISNetworld requirements.
The practical takeaway for HSE managers is that “compliant” isn’t a single fixed target. It means meeting the DOT floor for any covered functions, meeting each operator’s contractual requirements, and being able to prove both with documentation an auditor can verify without a follow-up call.
State law: the layer most field teams forget
Federal DOT rules and operator contracts sit on top of a patchwork of state law that varies more than most HSE teams expect. States generally fall into three categories.
- Open states, including Texas, have no statute specifically governing private employer drug testing. Employers can generally set their own policy without a state framework dictating procedure, though DOT rules still apply where federal jurisdiction attaches.
- Mandatory states, including Oklahoma, Louisiana, and Iowa, have statutes that spell out exactly how workplace testing has to be conducted: which labs can process specimens, what notice employees must receive, how confirmation testing has to work, and who’s authorized to review results as a Medical Review Officer. Getting these procedural details wrong can undermine an employer’s legal defense even when the underlying test result is accurate.
- Voluntary states offer a workers’ compensation premium discount to employers who certify a drug-free workplace program that meets state standards. Oklahoma’s program allows a discount of up to 15 percent, and other states in this category, including Georgia, Ohio, and South Carolina, offer discounts generally in the 5 to 7.5 percent range, with Ohio’s phased program reaching as high as 20 percent over time. Certification usually requires a written policy, employee notice periods, defined testing categories, and annual recertification, but the savings can offset a meaningful share of a testing program’s cost for a mid-sized contractor with a large field crew.
None of this changes the DOT floor for covered functions. A pipeline company operating in an open state still has to hit PHMSA’s 50 percent random rate. But it does mean a testing policy written for one state’s field operation may not automatically satisfy the notice and procedure requirements in another, which matters for contractors working multi-state basins.
What a compliant program actually looks like
Strip away the platform-specific paperwork, and a defensible oilfield testing program has a consistent shape.
It starts with a written policy that names every category of testing the company performs: pre-employment, random, reasonable suspicion, post-accident, return-to-duty, and follow-up testing for anyone who’s completed a substance abuse evaluation. The policy has to be distributed to employees before testing begins, with documented acknowledgment, and it has to specify consequences clearly enough that there’s no ambiguity when a result comes back positive.
Random selection has to be genuinely random and has to be spread across the calendar year. One of the most common findings during a DOT or platform audit is a company that ran its entire annual random testing quota in January and then stopped, which technically hits the numeric target but fails the requirement that selection be unpredictable throughout the year. Most C/TPAs handle this through quarterly draws.
Every test needs a documented chain of custody from collection through laboratory result, and every non-negative result needs review by a certified Medical Review Officer before it’s reported to the employer. For DOT-covered testing, this isn’t optional. For non-DOT testing conducted only to satisfy an operator’s contractual requirement, it’s still the standard that keeps a positive result defensible if it’s ever challenged.
Recordkeeping closes the loop. DOT rules generally require records to be kept for at least five years, and separate from that, whatever operator platform a contractor works under will expect current copies of the testing policy, proof of enrollment in an active random pool, and MRO contact information uploaded and kept current in the contractor’s profile.
Where a third-party administrator earns its place
Most contractors don’t have the internal bandwidth to run random pool selection, manage MRO relationships across multiple states, track DAMIS or Clearinghouse reporting deadlines, and keep documentation synchronized across two or three prequalification platforms at once, all while running field operations. That’s the gap a full-service third-party administrator is built to close.
TEAM Qualify manages background screening and drug and alcohol testing programs for employers across oil and gas, staffing, construction, and transportation, handling collection site coordination, random pool administration, MRO review, and the documentation trail operators and prequalification platforms expect to see. For an HSE manager trying to keep a program compliant across multiple operators and multiple states without adding headcount, that kind of support is usually the difference between chasing paperwork every quarter and having a program that simply runs.
