Automate RFI Requests for Subcontractor SDSs: Close the Compliance Gap

Manual RFIs to collect subcontractor Safety Data Sheets cost time and carry a compliance risk at the same time. Every day a subcontractor's chemical is in use on site before its SDS arrives conflicts with 29 CFR 1910.1200(g)(8), which requires SDSs to be readily accessible during each work shift, and a timestamped, automated request loop is the documented reasonable diligence a controlling employer needs under OSHA's Multi-Employer Citation Policy (CPL 02-00-124). Automating the request-validate-store loop cuts the per-document handling time and closes that gap.

This is the construction-specific playbook: the legal duty, the real numbers, a worked ROI, the automation architecture, and the mistakes that get GCs cited.

The Legal Duty Behind the SDS Chase

Two separate OSHA obligations make subcontractor SDS collection non-optional — and people routinely confuse them.

1. The on-site coordination duty (your own written program). Under 29 CFR 1910.1200(e)(2) — applied to construction verbatim by 29 CFR 1926.59 — your written HazCom program must describe how, on a multi-employer worksite, you will provide other employers access to SDSs for chemicals their workers may be exposed to, the labeling system in use, and the protective measures needed. This is your duty, regardless of who brought the chemical.

2. The controlling-employer duty (someone else's hazard). Under the Multi-Employer Citation Policy (CPL 02-00-124), a GC with general supervisory authority over the site (the "controlling employer") can be cited for a subcontractor's hazard — including a sub's missing SDS or unlabeled container. But the standard is reasonable care / reasonable diligence, not the same degree of care as the employer who created or is exposed to the hazard, and not strict liability for everything a sub does. The Fifth Circuit confirmed the policy in Acosta v. Hensel Phelps (909 F.3d 723, 5th Cir. 2018).

The practical lesson: you are not automatically liable for a sub's paperwork — you are liable for failing to exercise diligence. An automated, timestamped SDS-request system is the cleanest evidence of that diligence you can produce in an opening conference.

Not legal advice. Multi-employer enforcement turns on the facts of each site, and 22 OSHA-approved State Plans may apply their own (sometimes stricter) rules. Confirm your obligations with your jurisdiction.

What the Standards Actually Require — Cite Table

The "Compliance Gap": Why Manual RFIs Fail

The traditional workflow is dangerously slow:

1. A sub mobilizes with a new sealant or coating.
2. The safety officer notices the missing SDS.
3. The project engineer drafts and issues a formal RFI.
4. The sub's admin hunts for the file and emails it back.
5. A GC admin renames it and drops it in the binder.

Across those days, the chemical is already being applied. If an inspector arrives or an exposure incident occurs, the site is non-compliant under 29 CFR 1910.1200(g)(8).

The gap is not a paperwork annoyance. It is the exact window in which a missing-SDS citation, a willful-violation argument (you knew and didn't act), and a multi-employer theory all become available to OSHA simultaneously.

Worked Example: The ROI of Automating One Project

Consider a mid-size commercial project with 25 subcontractors, each averaging 4 new chemical products, for 100 SDS requests over the job. The figures below are assumptions to replace with your own:

Your rates and times will differ; run the same three multiplications with your numbers. The larger difference is not on the invoice: the manual loop leaves gap days in which a chemical is in use without its SDS, and those are the days that create the citation exposure under 29 CFR 1910.1200(g)(8).

The Automation Architecture (4 Layers)

1. Trigger the request from the workflow, not from a person noticing

Link the SDS requirement to an event that already happens: the submittal, the material delivery, or the subcontractor onboarding step. When a sub submits a product for approval, the system blocks closure until a conforming SDS is attached. The document is required before the chemical lands — this single change closes most of the gap.

2. Validate automatically

A document-classification step rejects the wrong file type instantly. If a sub uploads a marketing product data sheet instead of a 16-section SDS, the system bounces it and re-issues the request — no human review for the obvious failures. (For how to tell the two apart, see the 16 sections of an SDS.)

Validation has to check currency, not just format. A sub can upload a genuine 16-section SDS that is simply old — a pre-reformulation or pre-HCS-2024 version — which sails through a file-type check but still fails 29 CFR 1910.1200(g)(5) (the sheet must be current within three months of new hazard information). So the validate step should also compare the document's revision date/version against the manufacturer's current sheet where possible, and flag a valid-but-stale document for refresh. "It's a real SDS" is not the same as "it's the right SDS."

3. Bypass the sub for known products

For common, named products ("ProMar 200," a specific adhesive), pull the current manufacturer SDS from a master database/API rather than asking the sub at all. This guarantees the current sheet required by 29 CFR 1910.1200(g)(5) and removes a human round-trip entirely.

4. Store, version, and re-request on expiry

Keep every SDS access-controlled, versioned, and timestamped, and auto-notify subs 30 days ahead of known revisions. The timestamped request log is your reasonable-diligence record if a multi-employer citation is ever argued.

A Citation-Backed Request Beats a Polite Email

The reason manual RFIs stall is that they read like a favor. A request that names the product, cites the obligation, sets a deadline, and specifies the format gets returned faster — and documents your diligence. A strong SDS RFI includes:

• The exact products (manufacturer + product name), not "your chemicals."
• The legal hook — the sub's duty to transmit a current SDS and your access duty under 1910.1200.
• A deadline tied to mobilization, not an open-ended "when you can."
• Format and channel — a current GHS-aligned 16-section SDS, uploaded to your portal (reject email attachments).
• Secondary-container labeling expectations for anything decanted on-site.

Generate that language with citations pre-filled using the Subcontractor RFI Writer, and find the holes in your existing library with the gap-analysis method.

Common Mistakes That Get GCs Cited

• Treating multi-employer liability as strict — it isn't; the standard is reasonable diligence. Over-promising blanket responsibility in contracts can backfire.
• Accepting product data sheets as SDSs — a marketing brochure is not a 16-section SDS and won't satisfy an inspector.
• Letting chemicals on-site before the SDS — once it's in use, 1910.1200(g)(8) applies immediately; there is no documentation grace period.
• Filing an archived SDS — ask the sub for the sheet their supplier is shipping today. The preparer has 3 months to add new hazard information (1910.1200(g)(5)), so an archived PDF can be a revision behind.
• Relying on email threads — no audit trail, no expiry tracking, no proof of diligence. Use a portal with timestamps.
• Omitting the coordination method from your written program — 1910.1200(e)(2) requires it in writing, not just in practice.

What to Do Next

1. Map your chemical inputs. Identify every place chemical data enters the project — submittals, RFIs, deliveries, daily logs — and pick the earliest one as your trigger point.
2. Mandate digital submission in the subcontract. Require SDS upload to your portal as a condition of mobilization; reject email attachments by policy.
3. Gate the workflow. Block submittal/closure until a conforming SDS is attached, so the document always precedes the chemical.
4. Automate validation and expiry reminders. Bounce wrong file types automatically; re-request 30 days before known revisions.
5. Keep the log. Preserve timestamped requests and confirmations as your reasonable-diligence record.

Done well, the SDS RFI stops being a cost center and becomes a continuously-maintained, audit-ready asset — and your safety team spends its hours on field hazards instead of chasing paperwork.

Sources & Verification

• 29 CFR 1910.1200(e)(2), (g)(5), (g)(8) — Hazard Communication (SDS access & multi-employer coordination)
• 29 CFR 1926.59 — Construction adoption of HazCom
• OSHA Directive CPL 02-00-124 — Multi-Employer Citation Policy; Acosta v. Hensel Phelps, 909 F.3d 723 (5th Cir. 2018)
• 29 CFR 1903.15(d) — civil penalty amounts (serious max $16,550; willful/repeat max $165,514; 2026 unchanged from 2025)

OSHA penalty and citation figures verified against HazComFast's regulatory source modules and the eCFR, last verified October 5, 2026. Not legal advice; State-Plan rules may differ.

Related: SDS Management hub · Subcontractor HazCom Survival Guide · Multi-Employer Worksite Doctrine · Construction HazCom (1926.59) · HazCom Standard 1926.59 · Subcontractor RFI Writer · SDS Gap Analyzer · For Subcontractors