If a hiring client just told you to "get on ISNetworld," you are probably staring at a portal asking for dozens of documents and a long questionnaire, with a deadline attached. This guide explains exactly what the platform asks for, which written safety programs get reviewed, why accounts get sent back, and what it actually takes to reach an approved status.
What ISNetworld actually is
ISNetworld is a contractor prequalification platform. Large facility owners and general contractors, the companies that hire you, use it to check that their subcontractors carry the right insurance, have an acceptable safety record, and maintain written safety programs before letting them on site. You do not buy ISNetworld because you want to. You join because a customer, usually an owner or a general contractor, made an active account a condition of doing work for them.
Inside ISNetworld, a team called RAVS (Review and Verification Services) reviews the written safety programs you upload and grades them against a consistent set of requirements. RAVS is the part of the process that trips most contractors up, because a safety program that reads fine to you can still be marked deficient for reasons that have nothing to do with how safe your crews actually are.
The three parts of getting qualified
Getting to an approved standing generally breaks into three pieces of work that run in parallel:
1. The management questionnaire
A long self-assessment about how your company runs safety: your policies, your training, your incident history, your procedures. Its length depends on what your hiring client turned on, and it can be substantial. Your answers have to line up with the written programs you upload, which is a common place accounts fall out of sync.
2. Written safety programs (the RAVS review)
The documented programs that describe how you control specific hazards. These are what RAVS grades. The list you need depends on your trade and what your hiring client requires, covered in the next section.
3. Document uploads and data
Supporting records the platform and your hiring client ask for, which commonly include:
- Certificates of insurance (COI) matching the client's coverage requirements
- Your OSHA Form 300A summary, and often the 300 log, for recent years
- Your Experience Modification Rate (EMR) letter from your insurer
- Training records, and sometimes program-specific rosters
Which written safety programs you will likely need
There is no single fixed list, because the requirement is driven by your trade and by what the hiring client turns on. That said, most contractors are asked for a common core of programs, plus a set of trade-specific programs triggered by the work they actually do. Each program below is anchored to the federal OSHA standard it comes from.
The common core (most trades)
| Program | Primary OSHA standard (construction / general industry) |
|---|---|
| Hazard Communication (HazCom) | 29 CFR 1926.59 / 1910.1200 |
| Personal Protective Equipment (PPE) | 29 CFR 1926.95 & 1926.28 / 1910.132 |
| Emergency Action Plan | 29 CFR 1926.35 / 1910.38 |
| Fire Prevention | 29 CFR 1926.150 & Subpart F / 1910.39 |
| Fall Protection | 29 CFR 1926.501 & 1926.502 / 1910.28 & 1910.30 |
| Safety training / accident-prevention program | 29 CFR 1926.21 & 1926.20 (construction) |
| Injury & illness recordkeeping | 29 CFR Part 1904 (Forms 300, 300A, 301) |
Two items often bundled into a safety manual, incident/accident investigation and a drug & alcohol policy, are worth a note. Incident investigation is a widely expected best practice, but it is not a standalone OSHA written-program mandate for private contractors. Likewise, OSHA has no general drug-testing standard; a testing policy is a company policy (with separate federal rules, 49 CFR Part 40, only for DOT-covered safety-sensitive roles like CDL drivers). A good program presents these honestly rather than implying an OSHA mandate that does not exist.
Trade overlays (triggered by your scope of work)
On top of the core, the work you perform triggers additional programs. A few of the common ones:
| If your crews do this | You will likely need | OSHA standard |
|---|---|---|
| Work on or near energized equipment | Lockout/Tagout; Electrical Safety | 1910.147 / 1926.417; 1910.331–.335 / 1926.416 |
| Cutting, sawing, grinding concrete/masonry | Respirable Crystalline Silica | 1926.1153 / 1910.1053 |
| Enter tanks, vaults, manholes, vessels | Confined Space | 1926 Subpart AA / 1910.146 |
| Trenching and excavation | Excavation | 1926 Subpart P |
| Erect or work from scaffolds | Scaffolding | 1926 Subpart L / 1910.27 |
| Crane, rigging, steel erection | Cranes & Rigging | 1926 Subpart CC; 1926.251 |
| Welding, cutting, hot work | Hot Work / Welding & Cutting | 1926 Subpart J / 1910.252 |
| Respirator use (silica, coatings, welding) | Respiratory Protection | 1910.134 / 1926.103 |
What RAVS reviewers check
RAVS grades each written program against a consistent structure. A program that is missing pieces of that structure gets marked deficient even if the underlying practice is sound. Reviewers look for:
- The required sections: purpose and scope, definitions, roles and responsibilities assigned to named positions (not just "management"), step-by-step procedures, hazard identification tied to the hierarchy of controls, training and competency (including when training happens), inspections and audits, a review schedule with revision triggers, specific regulatory citations, records management, and incident reporting.
- Company-specific content: your legal company name on the cover and throughout, every placeholder replaced, and content that reflects your real scope of work and field practices.
- Assertive language: "must," "shall," and "will." Hedging words like "should," "may," and "possibly" get flagged as deficient.
- Specific frequencies: "daily" or "annually," not "regularly."
- Administrative basics: an effective date and revision date, version history, and a management signature or commitment statement. Undated or unsigned programs are a deficiency.
Why contractor accounts get rejected
The most common reasons a submission comes back, drawn from what reviewers repeatedly flag:
- Missing programs, or programs that are incomplete. This is the number one reason contractors stall.
- Generic template content, the wrong company name, or placeholder text left in.
- A program written for the wrong trade.
- Non-assertive language ("should/may" instead of "shall/will/must").
- Undated documents or no revision history.
- No management approval or signature.
- Vague incident reporting (for example, "report accidents to your supervisor" with no detail on what is reportable, who is notified, and how it is documented).
- Missing training frequencies, missing rosters, out-of-scope uploads, or inconsistent file naming.
Notice how many of these are format and completeness problems, not safety problems. That is the frustrating part for a contractor who runs a genuinely safe operation: the rejection is usually about how the program is written and assembled, not about how you work.
How long it takes
Each RAVS review round typically takes around 10 to 15 business days. That matters because the clock resets on a rejection. If your first submission comes back deficient, you fix it and wait for the next round. Two rounds of back-and-forth can put you six weeks out from where you started, which is a serious problem when a hiring client attached a deadline before you can bid or start work. Getting the programs right the first time is the whole game.
Keeping the account current after approval
Reaching an approved status is not a one-time event. Programs are re-verified on a recurring cycle, your OSHA 300A rolls over every year, your EMR letter and insurance certificates renew, and each new hiring client can add its own requirements to your account. An account that was green last year can quietly fall out of compliance and block a bid at the worst possible moment. The ongoing upkeep is the part most contractors underestimate.