The written safety programs ISNetworld asks for

The practical answer

RAVS — Review and Verification Services — is the part of ISNetworld onboarding that consumes weeks rather than hours. Reviewers read your written safety programs against a defined checklist and return them for what is missing. Contractors who plan for the statistics and not the programs consistently miss their client's start date.

Which programs get requested

The set follows the hazards of your scope, so a roofing contractor and an instrumentation contractor are asked for different documents. The commonly requested core:

• An overarching written safety and health program naming a responsible person.
• Hazard communication, with a current chemical inventory and SDS access procedure.
• Lockout/tagout, distinguishing authorized from affected employees.
• Fall protection, where work occurs at height.
• Confined space entry, with entrant, attendant and entry-supervisor roles assigned.
• Respiratory protection, tied to medical evaluation and fit testing.
• PPE hazard assessment, documented per task rather than asserted generally.
• Emergency action and incident reporting procedures.

Why submissions come back

Rejections are usually structural rather than substantive — the content is fine, the scaffolding is missing. Four causes account for most of them:

• No named responsible person with a title and, ideally, a signature.
• No review or revision date, so the reviewer cannot tell whether the program is current.
• No training and acknowledgement procedure describing who is trained, on what, how often, and how it is recorded.
• Unedited template language — a program that never names your company, your equipment or your actual work reads as purchased rather than implemented.

How to sequence it

Submit RAVS first, statistics second. Statistics file in hours once your 300A logs and EMR letter are in hand; program review runs in cycles and each rejection re-enters the queue. Contractors who onboard smoothly are the ones who had current programs before a client mandated the network — not the ones drafting under a deadline.

If you are buying help, buy it once and maintain in-house afterwards. The recurring consultant fee is the largest line after the subscription for many contractors, and it buys the same document every year.

What a reviewer-ready program contains

Before submitting anything, check each document against this list — it is close to what the checklist is actually testing:

• Your company name in the body, not just the cover page.
• A named responsible person with a title.
• An issue date and a revision date.
• Scope — which employees and which operations the program covers.
• Roles and responsibilities, assigned to positions rather than to individuals who may leave.
• Training requirements, including frequency and refresher triggers.
• A recordkeeping procedure describing where records live and for how long.
• A review cadence stating when the program is re-examined.

The programs outlive the network

Whatever you build for RAVS is the same material every other network, and most direct-submission clients, will ask for. Write it so it is yours: named, dated, specific to your scope, and actually trained against. That converts a compliance expense into something reusable — and makes the second and third network submission a copy operation.

If you are the one collecting these

Requiring a network puts the cost on your subcontractors. For a sub list in the dozens, you can request the same programs and documents directly: CoverWarden collects the prequalification packet — written programs, 300A with TRIR and DART computed, EMR letter checked against your cap, licenses, W-9 and the COI with its endorsement pages — through a free no-login link that costs the sub nothing.