Win a new utility contract and forget to update your certificate of insurance? Your ISNetworld grade already dropped before the first crew hit the field.
Your T&D crew just got awarded a transmission line rebuild for a new utility client. The operations manager is fired up. The foreman is scheduling linemen. Nobody has told the safety coordinator — or the insurance broker — that this client has a $5 million umbrella requirement and specific additional insured language that your current certificate of insurance doesn't include. The ISNetworld submission went in six months ago. It was accurate then. It's not accurate now.
Here's what happens next, and most in-house safety managers don't see it coming because the standard doesn't describe it this way.
ISNetworld doesn't just collect your certificate. Their RAVS® (Review and Verification Services) team reviews it against the requirements your hiring client has set — and those requirements are client-specific. A gas distribution operator working with Client A has different minimum limits than when they add Client B to their portfolio. The system doesn't automatically know you won new work. It only knows what you uploaded.
When your certificate doesn't meet Client B's requirements, that client's dashboard flags your company as non-compliant. Your ISNetworld grade drops. Sometimes it drops quietly — no alert, no email to the safety coordinator, just a red flag on a procurement screen that a supply chain manager glances at before approving a work order. By the time the field superintendent asks why the crew got held at the yard, the grade has been red for two weeks.
This is not a hypothetical. It's what happens on gas distribution contract startups in the Gulf Coast region every time a mid-size contractor adds a new municipal utility client with tighter insurance requirements than their oilfield clients.
Most safety coordinators at contractor companies treat ISNetworld insurance submissions as a once-a-year renewal task — upload the new COI in January, done. That's what the standard renewal workflow looks like. The problem is that ISNetworld grades are evaluated continuously by each hiring client, not on an annual cycle. A new contract relationship triggers a new compliance check against a new set of requirements.
Most safety coordinators assume the grade drop happens when the COI expires. The real problem is the grade drops the moment the new client's requirements don't match the current certificate on file — and that can happen on Day 1 of a new contract, not Day 365.
A safety manager who learned prequalification from reading the ISNetworld documentation understands renewal timelines. One who has actually managed multiple client relationships in ISNetworld simultaneously understands that every new client relationship is a new compliance evaluation — and the clock starts immediately.
A dropped ISNetworld grade doesn't issue a fine. It does something more damaging for an electrical T&D contractor: it stops work orders from being approved. Hiring clients — IOUs, municipal utilities, co-ops — often have procurement workflows that auto-flag non-compliant contractors before a human even reviews the project. Your crew stands by at $85–$120 per lineman per hour while your safety coordinator scrambles to figure out why they can't get on-site.
Depending on the contract structure, a delayed mobilization can trigger liquidated damages clauses. On a $2M transmission rebuild, a one-week delay can cost $15,000–$40,000 in standby labor and equipment alone — before any LD clause language comes into play. And that's before the relationship damage with a new client who is now questioning whether they picked the right contractor.
For context on what ISNetworld compliance means to hiring clients, see ISNetworld's Hiring Client resources — the compliance infrastructure utilities have built around this platform is substantial, and contractors who treat it as a paperwork exercise find that out the hard way.
A gas distribution contractor adds a new municipal client. The new client requires: $2M commercial general liability, $5M umbrella, and additional insured status for the client entity by specific legal name. The contractor's current COI lists $1M CGL, $3M umbrella, and names the previous hiring client as additional insured. The broker hasn't been called. ISNetworld has the old certificate. The safety coordinator doesn't know a new submission is required because nobody told them the contract was signed.
The field crew — gas service technicians and distribution operators — shows up for the pre-job meeting. The client's safety rep pulls up the ISNetworld portal on a tablet. Non-compliant. Meeting stops. Crew goes home.
That's not a training failure. That's a process failure at the intersection of operations, insurance, and compliance — and the safety coordinator takes the call.
The fix isn't complicated, but it requires a process that most contractor safety departments don't have:
The overall ISNetworld grade is an aggregate. A specific hiring client's compliance view is separate. Safety managers who don't know that distinction have usually learned it the first time a crew gets turned away.
Not automatically in the sense that ISNetworld sends you a notification. What happens is the new hiring client's requirements become active in the system, and your existing documentation is evaluated against those requirements immediately. If your COI doesn't match, the non-compliance flag is live from the moment the client relationship is active in the portal.
Each hiring client evaluates compliance independently. A grade drop triggered by one client's insurance requirements doesn't automatically affect your standing with other clients whose requirements you do meet. But your overall company grade — the one prospects see — can be affected, which can complicate new bid activity.
RAVS review typically takes 3–10 business days depending on volume. For electrical T&D and gas distribution contractors who can't afford a week of crew standby, that turnaround is the reason the submission has to be right the first time — before the crew mobilizes, not after they're turned away.
In practice it lands on the safety coordinator or the safety manager. The problem is they're often the last person to know when a new contract is signed. The process works when operations, safety, and the insurance broker are looped in simultaneously at contract execution — not sequentially.
If managing ISNetworld across multiple client relationships, tracking COI requirements by client, and making sure the submission is right before the crew leaves the yard is eating your safety coordinator's week — that's the exact administrative load we handle. Talk to EHS, Inc. and find out what it looks like when someone else owns this.
Aaron West
Founder, EHS, Inc. — 18+ years in EHS compliance and contractor safety
Aaron West has spent over 18 years helping contractors and businesses navigate OSHA compliance, ISNetworld® certification, and workplace safety management. He founded EHS, Inc. to make enterprise-level EHS accessible to companies of all sizes — serving contractors and businesses nationwide — without long-term contracts or enterprise overhead.
Our team handles the complexity so you can focus on running your business. No long-term contracts, no learning curve.
Talk to EHSWhen a maintenance tech gets hurt during a refinery turnaround, OSHA doesn't read your safety manual — they pull your training records. Here's what they find.
An OSHA citation hits differently when half your workforce turned over last quarter. Here's exactly what to do in the first 72 hours.
One willful OSHA violation cost a mid-size manufacturer $145K — and turnover is why no one caught it first.
Framework to achieve zero incidents
Stop hitting paywalls
54 topics in English & Spanish