The 20-Subcontractor SDS Problem: Building a Multi-Employer Worksite SDS Control Program That Actually Holds Up

A mid-size commercial project has 20 subcontractors cycling through over the build. The drywall sub shows up with joint compounds and sealants. The mechanical sub brings cutting oils, pipe dope, and a thread sealant nobody on the site has ever heard of. The painter rolls in with a primer the spec didn’t call for. The roofer’s adhesive arrives in a 55-gallon drum on a Wednesday with no advance notice. By the time the project hits 40% complete, the master HazCom binder in the trailer is three months out of date and the safety manager honestly cannot tell you, off the top of his head, what chemicals are on site today. That is the multi-employer worksite SDS control program construction problem in one paragraph — and it is the precise scenario that produces controlling-employer citations under OSHA’s multi-employer doctrine.

The standard everyone forgets is 29 CFR 1910.1200(e)(2), incorporated into construction through 29 CFR 1926.59. When two or more employers share a worksite, each employer who uses or stores hazardous chemicals must add three specific elements to its written HazCom program: methods to provide other employers SDS access, methods to inform other employers of precautionary measures, and methods to inform other employers of the labeling system in use. This activates the moment the second employer arrives — which describes essentially every commercial construction job in the country.

The GC is the controlling employer under CPL 02-00-124, and that is the entity OSHA expects to make the multi-employer system work. This post walks through the pre-mobilization SDS control program iSi recommends for GCs operating in Kansas, Missouri, Oklahoma, Nebraska, Texas, Arkansas, and Kentucky — the SOP that takes the SDS inventory problem out of the binder-on-Wednesday model and turns it into a controlled, documented program that survives an unannounced inspection.

Why a Multi-Employer Worksite SDS Control Program Construction GCs Build Themselves Almost Always Fails

The default model on most projects looks like this: the GC has a corporate HazCom program. The subs are contractually required to “comply with applicable OSHA standards.” When the inspector arrives, the GC produces the corporate program and asks each sub to produce its own. The subs hand over inconsistent binders, the inspector finds three chemicals on site without an SDS, and the citation lands on the GC under the controlling-employer doctrine — not because the GC did nothing, but because the GC’s reasonable-care procedures were not specific to this site, not documented, and not enforced.

OSHA’s multi-employer policy CPL 02-00-124 is a two-step analysis. Step 1 classifies every employer as creating, exposing, correcting, or controlling. Step 2 asks whether the controlling employer took reasonable care to prevent or detect the hazard. The GC who relies on a corporate program and subcontract boilerplate fails Step 2 every time. The GC who can produce subcontract submittal language, pre-mobilization SDS records, access logs for the central repository, orientation sign-in sheets, and weekly reconciliation records defeats the citation.

The fix is structural. It moves SDS collection from the middle of the project to before mobilization, and it puts a documented operational cycle around the central repository for the duration of construction. The components below are the SOP iSi works through with GC safety directors when we set up a site-specific HazCom control program.

How Does a Pre-Mobilization SDS Submittal Work in a Subcontract?

The single highest-leverage change in any construction-site HazCom program is moving the SDS submittal requirement into the subcontract and tying it to mobilization. The clause has to do four things: name the deliverable, name the deadline, name the consequence, and name the continuing obligation.

The deliverable is specific: a complete chemical inventory in a defined format (CSV with product name, manufacturer, quantity, planned use location, anticipated arrival date) plus PDF copies of every corresponding SDS, or login credentials to a shared SDS platform where the sub’s chemicals are accessible to the GC. “Submit your SDSs” is not specific enough — subs interpret that as a one-time email of whatever they happen to have on the truck.

The deadline is concrete: no later than five business days before scheduled mobilization. This gives the GC’s safety team time to review the inventory against the project’s hazard profile, flag any chemicals that conflict with adjacent trades or building occupancy, and update the central repository before the sub arrives.

The consequence is the leverage: subs who have not completed the pre-mobilization submittal do not get site access. The badge does not activate, the gate does not open, the work cannot start. This is the only enforcement mechanism that actually works. Subs treat the submittal as a paperwork formality until it costs them a day of labor.

The continuing obligation extends past mobilization: every new chemical the sub brings to site requires a 24-hour advance notice and SDS submission before the chemical crosses the gate. This is the provision that closes the most common gap — the sub who arrives with the chemicals listed in the inventory and then, three weeks later, swaps in a different product without notifying anyone.

A subcontract clause that contains those four elements moves the GC’s reasonable-care posture from “we relied on the subs” to “we enforced a documented submittal process.” That is the difference OSHA looks for in a Step 2 analysis.

The Central Location Trap Under 1910.1200(g)(8)

When the GC’s written program designates a central SDS repository — a binder in the trailer, a tablet kiosk, a cloud platform — the GC has just taken on the access obligation under 29 CFR 1910.1200(g)(8). The OSHA standard interpretation on MSDS availability on construction sites is clear: the party that agrees to maintain the central location must provide access to it at all times during each work shift.

The failure mode is predictable. The binder lives in the locked trailer. The day shift can access it. The night shift cannot. The Saturday crew is on site doing a concrete pour, the trailer is locked, and the binder is inside. An inspector who walks the site at 8 p.m. on Saturday and asks the foreman for the SDS for a curing compound is documenting a (g)(8) citation against the GC — not the sub.

Cloud platforms are not a free pass. When the Wi-Fi on the upper floors is unreliable, when a tablet battery dies, when the platform vendor has an outage, the GC who designated the platform as the access path is still on the hook. The OSHA standard interpretation on electronic SDS access requires the employer to have a documented backup access procedure when the primary electronic path is unavailable.

The SOP fix has four components:

Primary access path: specified in the written program — typically a tablet kiosk in the main trailer plus a mobile platform accessible from any device on the project.
Secondary access path: documented and physically available — a printed master binder in a location that is unlocked during every shift, including off-shifts and weekends. The binder lives in a designated cabinet on the project, not in a locked office.
Tertiary access path: the GC’s 24/7 phone line that any worker can call to request an SDS read aloud or texted/emailed within 15 minutes. This is the OSHA-compliant fallback when both primary and secondary paths fail.
Access log: a documented record of how each access path is verified. The night-shift foreman initials a daily access check. The IT team logs platform uptime. The phone line logs any inbound SDS requests.

A GC who can produce all four during an inspection has converted the (g)(8) liability into a defensive posture. The inspector sees that access was designed, redundant, and verified — which is the textbook definition of reasonable care.

The CPL 02-00-124 Reasonable-Care Checklist Inspectors Actually Use

When the OSHA compliance officer arrives on a multi-employer site and identifies a HazCom hazard, the Step 2 reasonable-care analysis runs through a predictable list. The controlling employer who has anticipated the list and built the documentation in advance walks out of the inspection with the citation attached to the creating sub, not the GC. The controlling employer who has not built the documentation walks out with the citation under their own name.

The checklist:

Did the controlling employer require subs to submit SDSs and chemical inventories before mobilization? Evidence: the subcontract clause + the submittal records for each sub on site that day. If the records exist for 17 of 20 subs and three submittals are missing, the gap is the citation.

Did the controlling employer maintain a central SDS repository with documented continuous access? Evidence: the written program designation + the access logs + the documented backup procedures. The inspector tests access in real time. A tablet with a dead battery, a binder in a locked office, a Wi-Fi dead zone on the 12th floor — each is an immediate finding.

Did the controlling employer conduct site orientation that covered HazCom for every sub and every worker on site? Evidence: orientation sign-in sheets with worker name, employer, date, and topics covered. This is the single most-missed documentation artifact in OSHA construction inspections. The fix is to make orientation a hard gate — no badge without a sign-in.

Did the controlling employer have a procedure to discover new chemicals brought on site by subs after mobilization? Evidence: the weekly reconciliation walk + the records of inventory updates + the 24-hour-advance-notice records for new chemicals. Subs bring chemicals onto sites that are not in the inventory. Without a reconciliation cycle, the gap grows weekly.

Did the controlling employer enforce the SDS submittal requirement when subs were late or non-compliant? Evidence: the enforcement log showing when subs were held at the gate, when work was paused for missing SDSs, when corrective action notices were issued. A program with consequences on paper but no enforcement record is not reasonable care — it is wishful thinking.

The Eleventh Circuit’s affirmance in Secretary of Labor v. Fama Construction (OSHRC No. 19-1467) confirmed that controlling-employer liability survives appellate review, and OSHA has continued to apply the doctrine routinely since CPL 02-00-124 was issued in December 1999. The doctrine is not going away. The reasonable-care checklist is the only defense.

The Weekly Reconciliation Cycle That Catches the Drift

A pre-mobilization SDS submittal is necessary but not sufficient. The inventory drifts the moment construction starts. Subs swap products mid-project. Foremen send a runner to the hardware store for a sealant that wasn’t in the bid. A vendor delivers a substitute when the spec’d product is on backorder. By week six, the master inventory and the actual chemicals on site have diverged — and the gap is where the citations live.

The reconciliation cycle is the operational mechanism that closes the drift. The cadence is weekly during active construction, more frequent on fast-moving projects. The procedure has three steps:

Step 1 — Floor walk and inventory. A designated safety team member walks each active work area and records every chemical container observed. The output is a list of products by location.

Step 2 — Reconciliation against the master. The walk list is compared to the master inventory. Discrepancies are flagged: chemicals on site that are not in the master (new arrivals that bypassed the submittal process), chemicals in the master that are no longer on site (demobilized but not removed from the inventory), and SDS gaps (chemicals on site with no corresponding SDS in the central repository).

Step 3 — Closure. Each discrepancy gets a written closure: the new chemical’s SDS is collected and added to the repository, the demobilized product is removed from the inventory, the responsible sub is notified that a submittal gap occurred and the corrective action is documented. The reconciliation log gets dated, signed, and filed.

A GC who can produce 14 weekly reconciliation logs for a 14-week project has the strongest evidence of reasonable care a controlling employer can build. It demonstrates an active program, not a passive one — and that distinction is what carries Step 2 of the multi-employer analysis.

How the HCS-2024 Transition Window Complicates the Picture

The Hazard Communication update is in active compliance phase right now. Chemical manufacturers, importers, and distributors must ship HCS-2024-compliant SDSs and labels for substances by May 19, 2026. Employer compliance for substances follows on November 20, 2026. Mixtures follow a year later on the manufacturer side and 2028 on the employer side.

What this means on a construction site: subs are receiving mixed-version SDSs from their upstream suppliers right now. Some products on site carry HCS-2012 labels and SDSs. Some carry HCS-2024 versions. Some carry both because the sub stocked up before the transition. The central repository needs to accept and organize both versions through November 2026, and the workplace labeling program needs to recognize that secondary containers labeled under the older format remain compliant until the employer compliance date.

The HCS-2024 transition is not a reason to delay building the SDS control program — it is a reason to build it now, because the version drift will widen the gap between the master inventory and reality unless the reconciliation cycle is running. GCs who put the SOP in place before the November 20, 2026 employer deadline avoid the worst-case scenario: a 2027 inspection where a year of mixed-version SDSs has produced an inventory that nobody can reconcile.

Citation Stacking Is the Budget Killer

A single multi-employer HazCom inspection can produce simultaneous citations under multiple subsections of 1910.1200. The exposure stacks fast:

1910.1200(e)(1) — written program inadequate or missing site-specific elements
1910.1200(e)(2)(i) — no method for providing SDS access to other employers
1910.1200(e)(2)(ii) — no method for informing other employers of precautionary measures
1910.1200(e)(2)(iii) — no method for informing other employers of the labeling system
1910.1200(g)(8) — SDS access failures at the central repository
1910.1200(h) — training documentation gaps for affected workers

Each serious-classification citation caps at $16,550 per violation under the 2025 inflation adjustment. Repeat or willful classifications carry up to $165,514 per violation. Five stacked citations at the serious cap is $82,750 from one inspection. A willful classification on any one element multiplies the exposure by ten on that line.

For comparison: an iSi industrial hygiene assessment that identifies the same gaps before the inspector does runs $4,050. The OSHA willful penalty alone is a 41:1 return on the assessment. The math is not close.

What “Reasonable Care” Looks Like in Practice — A Construction Safety Program iSi Builds for GCs

For GCs operating across the Midwest and into Texas, the multi-employer SDS control program is not a one-time project — it is a standing operational system that travels from project to project. iSi works with GC safety directors to build the program once, then deploys it across every active project with site-specific adaptations.

The deliverable for a GC engagement includes the subcontract submittal clause (legally reviewable, ready to add to the subcontract template), the site-specific written HazCom program template, the central repository SOP with primary, secondary, and tertiary access paths, the orientation curriculum and sign-in template, and the weekly reconciliation procedure with audit-defensible logs. The same engagement covers training for the GC’s safety team on the CPL 02-00-124 reasonable-care framework, so the field staff understand why each piece of documentation matters.

Replacing this scope with a dedicated full-time construction safety hire runs $130,000–$195,000 annually in salary and burden alone, and produces a program tied to one person rather than a documented system that survives turnover. iSi’s construction safety program design engagements deliver the full SOP at a fraction of that cost, with a national team across 40 states to support deployment on projects wherever they break ground.

If you are a GC safety director and you have not run a reasonable-care audit against your active projects this quarter, that is the gap to close before the next OSHA visit. iSi runs the audit, identifies the documentation gaps in days rather than weeks, and produces a remediation plan you can put in front of an inspector with confidence.