Employer Guide

Contractor Onboarding on Wellsites: ISNetworld, Avetta and Veriforce, Explained

Operators do not let contractor crews near a wellsite on a handshake. Before a vendor reaches the gate, the operator checks the company's safety record, its insurance and its training. ISNetworld, Avetta and Veriforce are the platforms that hold those files. Here is how contractor onboarding works on those platforms, and what it takes to stay approved.

Why operators vet contractors

When a service contractor works on an operator's lease, the operator carries part of the risk. An accident on location can become a liability question that lands on both companies. So operators run contractor management programs that decide who is allowed to work, and under what conditions.

The vetting is not a formality. Operators use these programs to see a contractor's safety record before the first job, and to keep that record current for as long as the relationship lasts. The platforms exist to make that check repeatable across every vendor on location.

Gate access depends on it. A contractor that clears the review gets a gate pass or an approval in the operator's system. One that does not stays outside the fence, no matter how good the bid was.

How the platforms work

The platforms sit between the contractor and the operator. ISNetworld, Avetta and Veriforce each run a database where a vendor company uploads its safety data once: insurance certificates, safety program documents, training rosters, incident rates and OSHA logs.

Operators who subscribe to a platform pull the parts they need from a contractor's profile. One operator may want a full safety program review. Another may only check insurance and training. The contractor uploads once, and each operator sees the parts it asks for.

That is the core idea: the contractor maintains one profile instead of mailing paperwork to every operator it works for.

What goes into the profile

Building the profile is the real work, and it takes more than a binder of old certificates. The platforms expect current documents, in the formats they specify.

• Insurance certificates, often with the operator named as additional insured and limits that match the contract.
• Safety program documents: the written policies for hazard communication, PPE, permits and emergency response.
• Training rosters that show who on the crew holds what, with expiry dates. SafeLand and PEC courses are common requirements. See the SafeLand and PEC safety training guide for how they compare.
• Incident rates and OSHA logs that show the company's recordable injury history.
• Drug and alcohol program documents where the operator asks for them. See the drug and alcohol testing guide for how DOT rules fit in.

The profile is only as good as its newest document. An expired insurance certificate reads the same as no certificate in the operator's system.

The questionnaire cycle

Uploading documents is half the process. The rest is the questionnaire cycle.

Operators send questionnaires through the platforms. The questions cover the contractor's safety management, training and procedures, and they differ by operator. One operator's questionnaire can run dozens of questions. Another's is shorter.

Answers get reviewed, and the review can come back with requests for more detail or corrective action. The contractor fixes the gaps and resubmits.

Most of this runs on an annual cycle. The contractor updates its profile once a year, answers the new questionnaires and renews the expiring documents. The annual update is not optional. A company that misses it falls out of compliance, and the operators that follow the profile get notified.

Who owns the work at the vendor

On the vendor side, the work belongs to named people, not to the company as a whole. A safety coordinator usually owns the safety program and the incident data. A compliance admin owns the platform logins, the document uploads and the questionnaire deadlines.

The job changes with every contract. A new operator means a new questionnaire. A new insurance policy means new certificates. A new hire means a new training roster entry, and that feeds into the oilfield new hire onboarding checklist.

The vendors that stay approved are the ones that treat the profile as a live file, checked weekly, not a task done once a year.

What lapses cost

The cost of a lapse is simple: no gate pass, no work, no invoice.

A certificate expires on a Friday. The crew reaches the gate on Monday. The operator's system flags the vendor as non-compliant, and the gate does not open. The crew waits, the job moves, and there is no invoice for work that never happened.

The flag follows the profile. Every operator that pulls the profile sees the lapse, and each one decides whether to let the crew in. A single expired certificate can cost work at more than one location.

Keeping expiries on a calendar

Every document in the profile has a date: the certificate that expires, the questionnaire that is due, the insurance that renews. The discipline is to keep those dates on a calendar that someone checks before dispatch, not after.

One way is a document list with alerts that fire before the expiry. That is where software earns its keep. OpsFlo is software that tracks field tickets, dispatch, approvals, timesheets and documents for oilfield service companies. Keep the certificate expiry dates next to the crew list so nothing lapses on a Friday.

The operator's platform is the referee. Your calendar is the defense. The crew that shows up with valid paperwork is the one that works.

Sources and further reading

• ISN: ISNetworld contractor management
• Avetta: contractor and supplier risk management
• Veriforce: contractor compliance and training