ISNetworld Compliance. Why It Exists and How to Be Real About It

Subcontractor workers are over-represented in serious workplace incidents at major industrial sites. The pattern shows up in oil and gas, refining, petrochemical, and heavy construction: the worker hurt on a major operator's site is often a subcontractor's employee, working under a different safety culture than the operator's own crew. Operators built ISNetworld and the other prequalification platforms because the consequences of that gap are paid in lives.

That's why the platforms exist. They're imperfect. But the question they try to answer does this contractor's safety system actually protect their workers on my site?. Is the right question. It's also the gate to the work: for most major Alberta operators, an active ISN qualification is the difference between being on the bid list and never seeing it. A contractor who treats ISN as a real description of their system gets both outcomes that matter. Workers who are genuinely protected, and the operator access that keeps the company working.

What ISN reviews and why

ISNetworld's RAVS (Review and Verification Services) examines a contractor's written safety programs against operator-specific requirements. The review covers:

  • Drug and alcohol program. Because impaired workers around heavy haul, energized equipment, and confined spaces are a foreseeable hazard
  • Lockout/tagout. Because uncontrolled energy release is a leading cause of industrial fatalities
  • Working at heights. Because falls remain a top trauma fatality in Alberta and industrial fall heights are unforgiving
  • Confined space. Because the OHS Code requires permit-to-work and atmospheric testing for a reason; rescuers often die alongside entrants
  • Hazard assessment and control. Because if hazards aren't being identified, controls aren't being designed
  • Training and competency. Because the worker doing the task needs to know the hazard and the control
  • Incident investigation. Because operators want to know contractors actually learn from incidents instead of repeating them
  • Short-service worker management. Because workers in their first 6 months on a site or in a role have demonstrably higher incident rates

Each of these maps to a specific way workers get hurt at industrial sites. The platform isn't an arbitrary gate. But it is a gate, and a clean RAVS file is what gets a qualified crew through it and onto the job.

Where contractors actually fall short

From operator and RAVS feedback, the gaps that recur. Each one both a worker-safety failure and a reason work gets blocked or paused:

Generic drug and alcohol policies. A boilerplate policy doesn't meet CAOEC energy-industry standards. Operators want pre-access testing, post-incident testing, random for safety-sensitive positions, reasonable suspicion, and documented chain of custody. The policy exists to keep impaired workers off site. Which is to keep workers (including the impaired one) alive. A policy that doesn't meet the standard is also one of the most common reasons a RAVS submission gets kicked back, delaying mobilization.

Lockout programs that don't address group lockout or multi-energy isolation. A single-person padlock procedure doesn't cover the reality of a turnaround with electricians, mechanical, and instrumentation all working on the same piece of equipment. Group lockout and multi-energy isolation are required by OHS Code Part 15 and by physics. Fail either and someone gets electrocuted, crushed, or burned.

Fall protection programs without site-specific tie-off plans. A generic "use 100% tie-off" policy doesn't tell a worker where to anchor on a vessel, on structural steel, or on scaffold edges. Site-specific anchor identification is the difference between a controlled exposure and a fatal fall.

Short-service worker (SSW) management as a sticker, not a system. A hi-vis distinction is the visible part. The real system is mentorship pairing, progressive task authorization (no SSW worker leading critical lifts), and weekly competency check-ins. The 6-month window exists because workers new to a role or site are statistically more likely to be hurt.

Trade-specific content missing. Generic "fall protection program" pages don't pass at the oilsands standard because the operators have lost too many contractors to generic systems. Welding programs need hot-work permitting. Scaffolding needs erection/inspection competencies. NDT needs radiation control.

Treating the platform as compliance theatre vs. as a check

The pattern that fails workers: a contractor builds documents to pass RAVS, then operates differently on site. The pattern that protects them: a contractor builds an HSMS that runs the way the documents say, then files those documents in RAVS. The platform doesn't see the difference. But the operator's safety advisor, the worker's supervisor, and the worker's family do.

There's a commercial dimension to the same choice. A paper system eventually gets tested by an incident, and an incident on an operator's site is exactly what gets a contractor removed from it, and off every other bid list that operator influences. The contractor whose RAVS file describes how the work is actually done protects their workers and their standing. The two are the same investment. A current COR-certified HSMS typically supplies most of what RAVS asks for.

Practical sequence

  1. Build the HSMS for the work. The hazards your crews actually face on the operators' sites
  2. Operate it for at least 90 days. Supervisors using FLHAs, daily pre-job tailboard meetings, near-miss reporting flowing
  3. Submit to RAVS. The documentation is a description of an operating system
  4. Complete operator-specific orientations. Suncor Life Saving Rules, CNRL handbook, Imperial-specific
  5. Track worker tickets continuously. Fall protection, confined space, ground disturbance, H2S Alive, WHMIS, First Aid

Plan 4-8 weeks from clean start to fully mobilization-ready when operator approval is included. The platform turnaround is not the bottleneck. The underlying system is. A contractor who keeps the system current keeps the qualification current, which keeps them continuously eligible for work instead of scrambling at each bid.

Platforms beyond ISN

Operators use different platforms depending on sector:

  • Avetta. Growing in petrochemical and refining
  • ComplyWorks (Calgary-based). Strong in commercial and industrial construction
  • Veriforce. Common in pipeline and midstream
  • ContractorCheck. Construction GC focused

Documents are largely portable. A strong HSMS feeds all of them. Most contractors end up on 2-3 to cover their operators, and the portability is part of the payoff: one well-built system qualifies you across multiple platforms and therefore across multiple operators' bid lists. Our overview of contractor prequalification in Alberta walks through how the platforms fit together.

What active qualification opens

Active ISN qualification is a prerequisite for most major Alberta operator work, including Suncor, CNRL, Imperial, Cenovus, Pembina, Inter Pipeline, ATCO, Enbridge, and TC Energy. Without it, a contractor doesn't see the bid list. So the revenue stakes are direct and significant. But the reason the platform exists is that the workers operators are responsible for keep getting hurt, and the platforms are part of how they try to change that. The contractor who builds for the worker passes the gate as a consequence; the contractor who builds only for the gate eventually fails the worker, and the incident takes the qualification with it.

Sources