Every Site Has an SDS Binder. Nobody at Corporate Has the Same One.

A safety director rolling up the year's compliance picture asks each plant manager to confirm their safety data sheet library is current. Every site says yes. What "yes" means turns out to be different at every site — one plant maintains a shared drive updated by the EHS coordinator, another still keeps a binder at the receiving dock that hasn't been reconciled against actual chemical inventory in over a year, a third relies on whatever the supplier attaches to the shipment and assumes that's sufficient. Each answer satisfies the person who gave it. None of them can be verified from corporate, and no one at corporate would know which version is closest to accurate without visiting in person.

Hazard communication is one of the standards multi-site operators most reliably assume is handled, because it looks administrative rather than technical — a binder, not a machine guard. That assumption is exactly backward. 29 CFR 1910.1200 imposes a set of obligations that apply at each individual workplace, not to the company as a whole, and it depends on operational discipline — someone updating a library every time a new chemical arrives — that is far easier to let slip at a facility corporate rarely visits than at one it built the program for directly.

What the Standard Actually Requires, Site by Site

1910.1200 requires that employers maintain a safety data sheet for each hazardous chemical present at the workplace, that those sheets be readily accessible to employees during each work shift, and that containers of hazardous chemicals be labeled with the information required under the standard's labeling provisions — product identifier, signal word, hazard statements, and pictograms consistent with the manufacturer's classification. None of that is satisfied by a policy document at headquarters. It is satisfied, or not, at the individual location where the chemical is actually stored and used, by whoever is responsible for keeping that location's library current as chemicals rotate in and out.

That per-site obligation is the whole difficulty. A written hazard communication program can be identical at every facility a company operates, and frequently is — corporate EHS drafts one policy, trains every site on it, and considers the requirement satisfied. But the policy is not the compliance obligation. The obligation is that the SDS on file at each site actually matches the chemicals actually on that site's shelves, today, and that any employee on any shift can locate the sheet for anything they're handling without waiting on someone else to produce it. A uniform policy paired with forty different execution realities is not uniform compliance; it is one compliance picture at headquarters and forty separate, unverified ones on the floor.

Where Consistency Breaks Down Across a Portfolio

The break rarely happens because a site ignores the requirement. It happens because purchasing is decentralized in ways EHS policy doesn't reach. A plant manager in one region buys a solvent from a regional distributor who ships an SDS in a format nobody has seen before; a site in another region buys the same chemical family from a different supplier with a different manufacturer classification for the same hazard. Multiply that by however many procurement relationships a large operator maintains across its footprint, and the SDS library at each site becomes a function of that site's purchasing history rather than a controlled document anyone at corporate designed.

Secondary container labeling compounds it. 1910.1200 requires that containers into which a hazardous chemical is transferred from its original container be labeled unless they meet a narrow immediate-use exception, and enforcement of that labeling requirement does not care whether the site's practice matches the plant three states away. One facility might use commercial GHS labels ordered through the same corporate program; another might use a hand-written label convention a supervisor set up a decade ago and never revisited. An inspector who finds a mislabeled secondary container at one site has no reason to assume it is an isolated lapse rather than a sign of how labeling actually works across the company — and a subsequent inspection at another site that turns up the same gap looks less like coincidence and more like a program that was never actually standardized past the policy document.

When People Move Between Sites, the Labels Don't Travel With Them

Large operators move people across facilities more than the org chart admits — a technician covering a shortage, a maintenance crew brought in for a shutdown, a supervisor rotating through as part of a development track. Each of those employees was trained on hazard communication at their home site, against that site's labeling conventions and that site's chemical inventory. Arriving at a different facility, they are working around chemicals that may be functionally identical to what they know at home but labeled, stored, and classified differently, because that site built its own version of the program independently.

The standard doesn't require a single national labeling convention, and most operators wouldn't be able to force one onto every supplier relationship even if they wanted to. But it does require that any employee at a given workplace have ready access to the information for chemicals they are actually handling there, and an employee who has learned to read one site's labels fluently is not automatically equipped to read another's. A visiting worker who assumes a pictogram means the same thing it meant at their home plant, because it usually does, is the exact scenario in which "usually" stops being good enough. This is a training gap that a written hazcom policy doesn't catch, because the policy was satisfied at both sites independently — it's a gap in what actually transfers with the person, and it only shows up when someone is standing in front of an unfamiliar container without the context to know what changed.

Why a Central Library Doesn't Solve It Alone

The intuitive fix — a single corporate SDS management system that every site pulls from — solves the retrieval problem without solving the currency problem. A centralized platform makes it easier for an employee to find a sheet quickly, but it does not automatically know that a site substituted a different degreaser last quarter, and it does not label the container on the shelf. The system is only as accurate as the site-level discipline that feeds it: someone at each facility has to notice a new chemical arriving, request or upload its current SDS, and confirm the container in use is labeled to match. Centralizing the library changes where the information lives. It does not change who is responsible for keeping it true, and that responsibility still sits at the site, one purchase order at a time.

What does help is treating hazard communication consistency the way electronic recordkeeping or contractor prequalification increasingly get treated at scale: as a compliance function with an owner who checks execution against the written program on a schedule, rather than a policy that's assumed self-enforcing once it's been distributed. That means a periodic reconciliation between what's actually stocked at each site and what's in that site's SDS library, and a labeling spot-check that doesn't wait for an OSHA inspector to be the first one to notice the gap.

None of this requires new authority over how sites buy chemicals. It requires knowing, on a recurring basis, whether what each site says about its hazard communication program is actually what's happening on the floor — because right now, for most multi-site operators, that question only gets answered site by site, after the fact, usually during an inspection rather than before one.