There's no single fixed list, and that's the first thing that trips contractors up. When you connect with a hiring client in ISNetworld, the platform generates a required-program list built from your declared scope of work, your industry classification, and that specific client's requirements. Two contractors in the same trade can end up with different lists depending on who they're trying to work for.
That said, a core set of written programs shows up on nearly every contractor's list, because they map to the hazards almost all field work involves — Hazard Communication, PPE, Lockout/Tagout, Fall Protection, and the emergency and recordkeeping programs among them. Beyond that core, your trade adds its own: excavation and trenching if you dig, silica exposure control if you cut or grind concrete, confined space if you enter tanks or vaults, and so on. Our guide to OSHA-required written programs walks the full program set.
The list is driven by your scope — which is why generic packs fail
Because ISNetworld builds your list from your declared work types, a generic "contractor safety pack" is the wrong tool twice over: it includes programs you don't need and misses ones you do. The programs that satisfy a review have to match your actual scope and carry the required regulatory elements — which is exactly what a reviewer checks.
The honest way to know your list is to check it inside ISNetworld against your scope. The honest way to know whether your programs are ready for it is to score them against the same lens the reviewer uses — which is what the Compliance Readiness Check does.