ISNetworld rejected my certificate of insurance. What do I fix?

ISNetworld is a contractor management platform. Operators and other "hiring clients" use it to collect and check information from contractors before letting them on site. ISN says documents submitted in ISNetworld "are reviewed by ISN's Review and Verification Services (RAVS) Team" against "regulatory and Hiring Client requirements" (ISN). Insurance certificates are on the list of documents it reviews.

The important part for you: the requirements come from the hiring client, not from ISN. ISN's own materials describe hiring clients setting insurance requirements that "reflect a company's risk tolerance and exposure based on the type of work performed," and configuring them by contractor using tools like an Insurance Pre-Questionnaire, Insurance Classification and an Insurance Variance Tool (ISN).

So when you fail insurance in ISNetworld, the question is never "what does ISN want." It is "what did this hiring client require for my type of work, and where does my paper fall short."

ISN also lets you grant your agent or broker access to submit and monitor insurance documentation. Use that. Your agent can see the requirement, upload the right endorsements, and respond to deficiencies without you as the middleman.

Hiring client insurance requirements in ISNetworld usually mirror the insurance exhibit in your MSA. Expect them to specify:

• Lines of coverage: GL, auto, workers comp and employer's liability, umbrella or excess, and sometimes pollution or professional.
• Minimum limits for each line.
• Additional insured status for the hiring client (often "and its parent, subsidiaries and affiliates").
• Waiver of subrogation on GL, auto and workers comp.
• Primary and non-contributory wording.
• Insurer financial rating minimums.
• Supporting documents: endorsement copies, sometimes policy declarations.

Two contractors working for the same operator can see different requirements. A hiring client can set different requirements by type of work, location or risk level, and ISN describes requirements that "can be configured by location, level of risk, or specific designations" (ISN).

If you work for several operators through ISNetworld, you are meeting several sets of requirements with one insurance program. Build the program to the strictest one you need to clear.

These are the deficiencies we see most often when a contractor sends us an ISNetworld rejection. None of them is about price. All of them are about paper matching paper.

Contractors sometimes ask their agent to "just check the boxes" on the certificate. In Texas that does not work, and it can create bigger problems than a failed review.

Texas Insurance Code Chapter 1811 governs certificates of insurance for Texas risks. The key lines:

• A certificate "is not a policy of insurance and does not amend, extend, or alter the coverage" (§1811.152).
• A certificate "shall not confer to a certificate holder new or additional rights beyond what the referenced policy or any executed endorsement of insurance provides" (§1811.153).
• A certificate "may not contain a reference to a legal or insurance requirement contained in a contract other than the underlying contract of insurance" (§1811.154).
• A person may not require a certificate "that contains any false or misleading information concerning the policy" (§1811.054).

That is why reviewers ask for endorsement copies. The endorsement is the evidence. The certificate is a summary. If the AI box is checked and the policy has no AI endorsement, the hiring client has nothing, and your agent has a problem.

It is also why phrases like "per MSA" or "as required by contract dated..." on a Texas certificate draw pushback from agents. The fix is on the policy, not in the description box. See why was my certificate of insurance rejected.

Contractors usually talk about this as their ISNetworld "grade" dropping. How a hiring client's grade or status is calculated is set by that hiring client, and insurance is only one input alongside safety programs, statistics and training. But an insurance deficiency is one of the fastest ways to lose an acceptable status, because it happens on a date: the day your policy expires or the day a hiring client changes its requirement.

Three things trigger most insurance-driven drops:

1. Renewal not uploaded. Your policies renewed, but the renewal certificate and endorsements did not make it into ISNetworld before the old ones expired.
2. The hiring client changed its requirement. ISN says contractors receive "important updates from connected Hiring Clients about new or changing requirements." A higher umbrella limit or a new pollution requirement can put you out of compliance overnight.
3. A mid-term change. A carrier change, a nonrenewal, or a new entity name.

What happens next depends on the hiring client. Some will hold work until it is fixed. Some allow a short cure period. For more, see what happens if my ISNetworld insurance grade drops.

When a contractor brings us an ISNetworld deficiency, this is the order we work in.

1. Pull the exact requirement. Export or screenshot the hiring client's insurance requirement and the deficiency comments. Do not work from memory or from what another operator wanted.
2. Pull the policies. Not the certificate, the policies and every endorsement. Read the AI, waiver, PNC and contractual liability language.
3. List every gap at once. Name match, AI, waiver on each line, PNC, limits, umbrella follow-form, dates. Fixing one deficiency at a time can mean weeks of resubmissions.
4. Get endorsements issued. Most AI, waiver and PNC endorsements can be added mid-term. Some are blanket and some must be scheduled. Some carry an additional premium.
5. Upload the complete package. Updated certificate, every endorsement, and the umbrella wording, with form numbers legible.
6. Ask about a variance only for real mismatches. If a hiring client wants professional liability from a roustabout crew, ask. ISN describes a variance tool on the hiring client side. Do not use variances to cover a gap you could close with an endorsement.

If the same deficiencies keep coming back across operators, the problem is the program, not the paperwork. That is the point where an MSA and insurance review pays for itself.

For a typical oilfield service contractor working for an operator through ISNetworld, a complete insurance upload usually includes:

• Certificate of insurance (ACORD 25 is the standard form most agents use; ACORD forms are deemed approved in Texas under Ins. Code §1811.103).
• GL additional insured endorsement(s), ongoing and completed operations, scheduled or blanket.
• GL primary and non-contributory endorsement.
• GL waiver of subrogation endorsement.
• Auto designated insured or additional insured endorsement and auto waiver.
• Texas workers comp waiver of subrogation (WC 42 03 04), scheduled or blanket.
• Umbrella or excess schedule of underlying insurance and follow-form or AI wording.
• Pollution policy declarations or endorsement, if required.

Name the files clearly ("GL AI blanket CG form.pdf" beats "scan0045.pdf"). Reviewers are matching documents to requirements. Make it easy.

Many operators in the Permian, Eagle Ford and Haynesville use ISNetworld. Others use Avetta. Some contractors maintain both.

The insurance logic is the same on both platforms: the hiring client sets the requirement, a reviewer compares your documents to it, and endorsements carry the weight. The interfaces and terminology differ. If your program clears a strict MSA cleanly, it will usually clear either platform with the right uploads.

The places contractors get stuck are the trade-specific exposures: auto pollution for water haulers, professional liability for inspection firms, and completed operations AI for well servicing work.