If your crews share a jobsite with other trades — and on almost every demolition, GC, or heavy civil project in NJ, NY, or PA they do — hazard communication program requirements for NJ contractors aren't optional paperwork. They're one of the most commonly cited items on multi-employer worksites, and ISNetworld reviewers flag missing or outdated HazCom programs constantly. Under 29 CFR 1926.59, which incorporates the general industry standard at 1910.1200, every employer using or storing hazardous chemicals on a jobsite needs a written program, current safety data sheets, labeled containers, and trained employees — and on a shared site, you also need a plan for communicating hazards to the other contractors working next to your crew.
What 29 CFR 1926.59 Actually Requires
The standard breaks down into four pieces that OSHA compliance officers check in order: a written hazard communication program, a chemical inventory, safety data sheets (SDS) for every hazardous product on site, and employee training before anyone works around those chemicals. The written program has to name who's responsible for maintaining it, how the chemical list gets updated, where SDS sheets are kept and how workers access them, and how labels are maintained on secondary containers. A generic downloaded template with your company name pasted in doesn't hold up during an audit — inspectors expect the program to reflect the actual chemicals on that specific site, not a boilerplate list.
Multi-Employer Worksite Hazard Communication
This is where most contractors get cited, not on the paperwork itself. On a demolition or heavy civil site with five or six subs working simultaneously, each employer has to make sure other employers' workers know about the hazardous chemicals their crew brought onto the site — solvents, coatings, fuels, adhesives, dust suppressants, epoxies. That means SDS sheets need to be accessible to every contractor on site, not locked in a super's trailer that only your own foreman can get into. If you're the GC or CM, your site-specific safety plan needs to spell out how subcontractors exchange chemical hazard information before work starts, and that expectation should be written into your subcontractor agreements, not assumed.
Building a Written HazCom Program That Holds Up
A written HazCom program that survives both an OSHA inspection and an ISNetworld review has a few things in common: it's specific to the chemicals actually used on your projects, it's updated when new products come on site, and it ties directly to your training records. Training has to happen before an employee's first exposure to a hazardous chemical, and it needs to cover how to read a label, how to read an SDS, and what physical and health hazards apply to what they're using that day — not a once-a-year classroom session disconnected from the actual products on site.
Contractors preparing for an audit, a new GC prequalification, or just cleaning up a program that's fallen behind should have the following in place:
- A written hazard communication program specific to your company and updated within the last 12 months
- A current chemical inventory list matching what's actually stored and used on active job sites
- SDS sheets for every hazardous product, accessible to all employees and, on multi-employer sites, to other contractors
- Labeled containers for all secondary containers, not just original manufacturer packaging
- Documented HazCom training completed before first exposure, with records retained
- A designated program administrator named in the written program
- A written process for how hazard information gets exchanged with subcontractors or other employers on shared sites
Hazard communication gets treated as a back-office task until it shows up as a citation line item or a stalled prequalification. Blueprint Safety builds written HazCom programs that match the chemicals your crews actually use in the field, sets up training that holds up under review, and helps GCs put multi-employer hazard exchange language directly into their site safety plans — so the program works on the ground, not just in a binder.