What Is ISNetworld? A Contractor's Guide to ISN, RAVS, and Grades

ISNetworld is a contractor-management and prequalification platform operated by ISN Software Corporation. Large organizations — owners, operators, general contractors, utilities, refiners, manufacturers — use it to collect and verify safety, insurance, and regulatory documentation from the companies they hire, in one place instead of one email chain per vendor.

The important thing to understand up front: ISNetworld is not a regulator and not a certification body. It does not issue safety credentials and it has no enforcement authority over you. It is a document clearinghouse that your customer has chosen to use. Your obligation comes from your contract with that customer, not from ISN.

That distinction matters practically. When a section gets rejected, the question is never "did we break a rule?" — it is "does this document contain the specific elements the reviewer is checking for, in a form the reviewer can find?"

There are two sides of the platform, and they have different roles:

• Hiring Clients subscribe in order to screen contractors. They set their own requirements: which written programs they demand, what insurance limits they accept, what incident-rate thresholds they will tolerate, and what grade counts as passing.
• Contractors (you) pay a separate subscription to maintain a profile and connect to those clients. Contractor pricing scales with things like employee count and the number of hiring clients you're linked to.

So there are three separate parties making decisions about your profile: ISN reviewers judge whether a document meets a checklist, your hiring client decides what the passing bar is, and you supply the underlying records. Anyone who tells you they can guarantee an approval is claiming authority over two parties they don't control.

RAVS stands for Review and Verification Services. It is the process where you upload your written safety programs and an ISN reviewer evaluates each one against a defined set of required elements — then grades that program as accepted or returns it with the specific gaps called out.

Why generic programs fail

The single most common reason a RAVS submission comes back rejected is that the program is a downloaded template. Reviewers are looking for content specific to your operation: named responsibilities, your actual equipment and tasks, your training frequency, your inspection process, your disciplinary structure. A template that says "the Company shall designate a competent person" without designating anyone fails on exactly that line.

Typical programs requested

The exact list depends on your scope of work and your client's requirements, but commonly requested programs include hazard communication, personal protective equipment, lockout/tagout, fall protection, confined space entry, hot work, respiratory protection, electrical safety, fleet and driver safety, and an overarching safety and health management program.

RAVS Plus

Some hiring clients go further and require verification that your written programs are actually being implemented — including employee interviews and evidence requests. This is where a paper-only compliance approach breaks down: the program has to match what your crews actually do.

RAVS is only one of four things being scored. The others:

• Management System Questionnaire (MSQ). A long questionnaire about how your safety, environmental, and quality systems are structured. Answers can be audited against your documentation, so answering aspirationally rather than accurately creates a problem later.
• Incident statistics. Typically TRIR, DART, and your Experience Modification Rate (EMR), supported by OSHA 300/300A logs and a letter from your insurer or carrier. These are compared against hiring-client thresholds and, sometimes, industry averages.
• Insurance certificates. Coverage types, limits, additional-insured and waiver-of-subrogation language, and expiration dates. Certificates lapse quietly and are a leading cause of a profile flipping red without warning.
• Regulatory and citation history, plus any client-specific questionnaires layered on top.

Because the statistical component is arithmetic on your real incident history, it cannot be written around. It can, however, be reported incorrectly — miscalculated hours, wrong recordable classification, or a mismatch between your 300A and what you entered in the platform are all fixable errors that drag a score down unnecessarily.

Contractors regularly discover their profile shows acceptable for one customer and unacceptable for another on the same day. This is by design, not a bug. Each hiring client configures its own requirement set and its own thresholds.

The practical implication is that "passing ISNetworld" is not a state you reach — it is a per-client evaluation you maintain. Adding a new customer can surface a program you've never been asked for, an insurance limit you don't carry, or a statistical cutoff you don't currently meet.

A sequence that avoids wasted effort:

1. Pull the requirement list per client. Before writing anything, identify exactly which programs and thresholds each connected client demands. Most wasted work comes from writing programs nobody asked for.
2. Fix the arithmetic first. Verify your 300/300A logs, hours worked, recordable classifications, and EMR letter. Errors here are cheap to correct and immediately affect scoring.
3. Close insurance gaps. Confirm limits and endorsement language with your broker before submitting, not after a rejection.
4. Write programs to your actual operation. Name roles, reference your real equipment and tasks, state real frequencies. Then make sure your crews are trained to what the document says.
5. Work the reviewer comments deliberately. Rejections list specific missing elements. Address each one explicitly rather than resubmitting a lightly edited document — repeated resubmissions are the main cause of multi-month delays.
6. Put maintenance on a calendar. 300A postings, insurance renewals, EMR updates, and RAVS re-reviews are recurring. Treat them as scheduled work.

Everything above is doable in-house if you have someone with the time and the documentation background. Most small and mid-sized contractors don't — the work lands on an operations manager between bids.

PrecisionEHS is an independent, CSP-led consultancy. We are not affiliated with, endorsed by, or partnered with ISN. What we do is write and revise RAVS programs to your actual scope, verify and correct your OSHA statistics, track insurance and renewal deadlines, and respond to reviewer comments until sections clear — either as a one-time cleanup or as ongoing monthly management.

We don't guarantee approval, because reviewers and hiring clients decide that independently. We do remove the avoidable delays: template rejections, arithmetic errors, lapsed certificates, and unanswered reviewer comments.

If you want a read on your current exposure before talking to anyone, the 60-second compliance scorecard flags the likeliest problems in your profile. For platform-specific detail, see our ISNetworld support page.