ISNetworld RAVS 360: What Alberta contractors need to know.

ISNetworld is a contractor management platform used by large operating companies to pre-qualify and monitor the contractors they hire. RAVS 360 — Review and Verification of Safety 360 — is the scoring system within ISNetworld that evaluates each contractor's health and safety program.

When a contractor creates an ISNetworld account and begins uploading their safety documentation, ISNetworld reviews the content against a set of requirements set by the client operator. The RAVS 360 module produces a score from 0 to 100 that summarises how complete and current the safety program is.

Prime contractors use the RAVS 360 score as a quick screen before awarding work. A score below their threshold flags the contractor as non-compliant, which can mean delayed approvals, removal from bid lists, or being held off a project until gaps are corrected.

ISNetworld is most heavily used in Alberta's oil and gas and industrial construction sectors, where large operators such as Suncor, Imperial Oil, TC Energy, and Pembina Pipeline require all contractors to maintain an active account. The platform is also common in BC, Saskatchewan, and Ontario in similar industrial sectors.

The RAVS 360 score is not a simple document checklist. ISNetworld reviews the content of uploaded documents against the requirements defined by each client operator. Different operators can set different requirements, which is why a contractor might have a high score with one prime contractor and a lower score with another using the same account.

The score is calculated across several broad categories:

• Safety program documentation: Safety manual content, written programs, hazard assessments, and company policies. ISNetworld reviewers (called MCAs) read uploaded documents and score them against content requirements, not just presence.
• Insurance and WCB: Current certificate of insurance naming the operator as additional insured, WCB clearance letters, and proof of appropriate coverage limits.
• Injury and illness statistics: Total Recordable Incident Rate (TRIR), Lost Time Incident Rate (LTIR), and hours worked for the past three years. Statistics are self-reported and subject to verification.
• Training and qualifications: Employee and supervisor training records for courses required by the client operator — orientation, H2S Alive, WHMIS, first aid, and others depending on the scope of work.
• Regulatory compliance: Evidence of compliance with applicable provincial OHS legislation, including JHSC minutes, inspection logs, and corrective action records.

Each category is weighted, and the weights can vary by client operator. ISNetworld does not publish the exact weighting formula, but safety program documentation and statistics typically carry the most weight.

There is no universal minimum RAVS 360 score. Each operator sets their own threshold. In practice, the thresholds cluster around consistent ranges:

The safest target is 70 or above. This satisfies most Alberta prime contractor requirements, including operators in oil and gas, pipeline, and industrial construction. If you are working with a specific prime contractor, ask them directly what score they require before investing time in improvements that may not move the needle for that particular relationship.

The document requirements inside an ISNetworld account vary by client operator. However, the following are required by the majority of Alberta operators using the platform:

• Company safety manual or health and safety management system documentation
• Certificate of insurance (general liability and excess liability) naming the operator as additional insured
• WCB clearance letter current within 90 days
• Annual injury and illness statistics — TRIR, LTIR, total hours worked for the past three calendar years
• Written hazard identification and assessment procedures
• Emergency response plan
• Incident investigation procedure
• WHMIS program and training records
• Worker and supervisor competency and training records
• Vehicle and equipment inspection procedures (if applicable to the scope of work)
• JHSC or safety representative records (for companies with the required worker count under provincial OHS legislation)
• Drug and alcohol policy (required by most oil and gas operators)

ISNetworld assigns each document to a review queue. A trained MCA (Management and Compliance Analyst) employed by ISNetworld reviews the content against the requirements for each client operator. Documents that are complete and meet content requirements are approved; documents with gaps generate corrective action notices that must be addressed to maintain or improve the score.

A RAVS 360 score that was acceptable when a project started can fall below a prime contractor's threshold before the project ends. The most common causes:

• Insurance certificates expire: ISNetworld tracks expiry dates and automatically flags accounts when certificates are not renewed. A lapsed insurance certificate can cause an immediate score drop.
• WCB clearance letters are not updated: WCB clearance letters are typically valid for 90 days. Many contractors upload one and forget it. After 90 days the letter expires and the score drops.
• Injury statistics go stale: ISNetworld requires annual updates to TRIR, LTIR, and total hours worked. If the previous year's statistics are not entered by the required date, the account goes into arrears and the score falls.
• Safety program changes are not uploaded: If the company's safety manual or written programs change — new province, new scope of work, regulatory update — the changes need to be uploaded and re-reviewed. Old documents may fail review against updated operator requirements.
• Training records are not maintained: Worker certifications expire. If an operator requires current H2S Alive records, for example, and a worker's certificate lapses, the account falls out of compliance for that operator's requirements.

The pattern is consistent: contractors set up their ISNetworld account when they need it to get approved by a prime contractor, then let it drift. A year later, the score has dropped from 72 to 54 because three documents expired and statistics were not updated. By that point the prime contractor has already flagged the account as non-compliant.

Improving a RAVS 360 score is straightforward in principle but time-consuming to execute correctly. ISNetworld's review queue means that uploaded documents are not scored immediately — there is a processing delay that can range from days to several weeks depending on volume. Plan for this before a project start date.

The typical improvement sequence:

1. 1

   Pull the account's corrective action log

   ISNetworld generates a list of outstanding corrective actions — documents that have been reviewed and found deficient. This list shows exactly what is holding the score down and is the fastest way to prioritise improvements.

2. 2

   Renew expired documents first

   Insurance certificates, WCB clearance letters, and expired training records are typically quick wins. These are administrative renewals that do not require changes to the underlying safety program.

3. 3

   Update annual statistics

   Enter current TRIR, LTIR, and hours worked for each required year. Accurate statistics matter — ISNetworld can verify reported numbers against WCB data, and inflated statistics can create compliance issues with the operator.

4. 4

   Address safety program content gaps

   Documents that failed review because of missing content require revision and re-upload. This is where a safety manual that meets ISNetworld's content requirements makes a significant difference. A generic document may clear the checklist but still generate corrective actions on content review.

5. 5

   Upload revised documents and monitor

   After uploading corrected documents, monitor the account for the review outcome. If a document is rejected again, ISNetworld provides a reason. Address the specific gap noted and re-upload.

Many contractors treat ISNetworld as a one-time setup task. They hire someone to build the account, achieve a passing score, and get approved by the prime contractor they needed. Six months later, the score has dropped and they are scrambling again before a new project starts.

The contractors who avoid this pattern treat ISNetworld as an ongoing compliance function, not a project. That means:

• Tracking document expiry dates and renewing before they lapse
• Entering annual statistics by the required deadline each year
• Monitoring the account for new corrective actions after each review cycle
• Uploading updated safety documents when the underlying program changes
• Checking which client operators have been added to the account and ensuring their specific requirements are met

For many small and medium contractors, this is not a full-time function but it is a consistent one. The work happens in batches — a few hours at expiry time, a few hours when new operators are added, a few hours when statistics are due. The alternative is a reactive scramble every time a prime contractor flags a non-compliant account.

Some contractors handle this in-house; others outsource it to a contractor management specialist who monitors the account, handles renewals, and keeps the score above threshold without requiring the company owner to track the deadlines themselves.

On-Track Safety handles ISNetworld account setup and ongoing maintenance for contractors across Western Canada. This includes initial account build, document uploads, corrective action resolution, annual statistics, and monitoring for expiries and score changes. Learn more about contractor management services.