ISNetworld® Compliant Safety Programs vs. OSHA Compliant Safety Programs
I cannot stress this enough... ISNetworld® compliant safety programs are not always OSHA compliant safety programs. They are usually two different animals with very different end goals and purposes. We talk to people all the time that say well Company X says they can give me an OSHA compliant safety program based upon the ISNetworld® compliant safety programs. This may be true for some of the shorter programs, but this is not the case for each and every ISNetworld® written safety program requirement.
ISNetworld® exists merely to review and verify certain documentation such as insurance certificates, OSHA logs, and of course, written safety programs. This service is provided to the major corporations that hire ISNetworld® exactly for this purpose. Written safety programs required by OSHA are usually much more in-depth and extensive, especially in such jurisdictions like California with much more complex regulatory requirements than federal OSHA.
ISNetworld® requires some, and only some, of the OSHA standards to create their safety programs. When you answer the questions prior to submitting your safety program, you will see a list of requirements that need to be satisfied in order to be ISNetworld® compliant. ISNetworld® does not list every mandatory OSHA requirement for all of their written safety programs. For example, OSHA requires sections A-Z to become an OSHA compliant safety program, while ISNetworld® requires A-C, D, and G. Therefore, some of the OSHA requirements are left out.
Every company using the ISNetworld® system must decide how to effectively draft their safety and health program policies and procedures. On the one hand, you will need to meet the ISNetworld® requirements. On the other hand, you have certain regulatory obligations to meet also that may or may not exactly align with the ISNetworld® written program requirements.
For example, the I2P2, or Injury and Illness Prevention Programs (IIPP), required under CalOSHA are often required by ISNetworld® for companies that do not even fall under that jurisdiction. 1926 Construction safety and health requirements imposed on a company that operates in the General Industry 1910 arena might be another example of ISNetworld® versus OSHA where scope and applicability of standards arises as a prevailing concern.
All in all, a company has to be wise on what applies from an OSHA regulatory standpoint and what applies to meet the ISNetworld® written program requirements. These are two very different agencies with opposing goals and interests...both of which create lots of red tape and administrative burden, especially when determining how to draft written safety programs and policies.
This organization is in no way endorsed, sponsored, approved by, or otherwise affiliated with ISNetworld®.