Process Safety Management Doesn't Cover Your Company. It Covers Whichever Processes Cross the Threshold, Site by Site.

A corporate EHS director reviewing a portfolio's chemical inventory asks a simple question: which of our sites are subject to Process Safety Management? The honest answer, more often than the org chart would suggest, is "we're not entirely sure without checking every site's current inventory." That's not a failure of diligence so much as a structural feature of the standard itself. Process Safety Management under 29 CFR 1910.119 was never written to apply to a company, or even to a facility. It applies to a covered process — a specific piece of the operation that either handles a listed highly hazardous chemical above its threshold quantity or holds enough flammable liquid or gas in one process to cross the standard's general threshold. A facility can have five processes running side by side, one of them covered and four of them not, and the same is true across a hundred facilities. Coverage is granular in a way that a company-wide safety calendar isn't built to track.

The Threshold Doesn't Announce Itself

Appendix A to 1910.119 lists more than 130 specific chemicals with their threshold quantities, and separately, the standard covers any process with more than 10,000 pounds of a flammable liquid or gas in one location, with some exclusions for things like fuel used for the workplace's own consumption. Both triggers are quantity-based, and quantity is the one variable a corporate program has the least reliable real-time visibility into. A plant that increases production and adds a second anhydrous ammonia refrigeration loop, or a site that starts storing a solvent in bulk instead of drums to cut delivery costs, can cross a PSM threshold as a side effect of an operational decision that never touched a safety committee. Nobody filed paperwork with corporate because nobody thought of it as a compliance event — it was a procurement or engineering decision, made at the site, for site reasons.

This is the gap that matters more than any single missing binder: a portfolio's PSM obligations can change without corporate knowing it happened, because the trigger lives in operational data — tank capacities, process inventories, storage volumes — that safety teams don't always see in real time. A quarterly or annual chemical inventory review across every site, cross-checked against Appendix A and the flammable-liquid threshold, is the only way to catch a site that crossed the line quietly. Waiting for a site to self-report puts the burden on people who may not know the report is owed.

Coverage Follows the Process, Not the Site's History

Once a process is covered, 1910.119 attaches a specific set of obligations to it — not to the facility as a whole, and not to the company. A process hazard analysis has to be conducted and then revalidated at least every five years under 1910.119(e)(6). A compliance audit of the PSM program has to happen at least every three years under 1910.119(o). Mechanical integrity requirements apply to the equipment within that process. Management of change procedures have to be followed for modifications to that process specifically. None of these clocks are calendar-year clocks that reset company-wide on January 1. Each one starts running from when that particular process was first covered, or from when its last PHA or audit was completed, which means a portfolio with a dozen covered processes across different sites is very likely running a dozen different five-year and three-year clocks, none of them synchronized.

A corporate calendar that tracks "PSM compliance" as a single annual milestone is tracking the wrong unit. The unit that matters is the individual process, and the schedule that matters is that process's own PHA revalidation date and audit date, inherited from whenever it was first identified as covered. A site that was covered eight years ago and a site that crossed the threshold last quarter are on entirely different timelines, even if they make the same product using similar equipment.

What Counts as "One Process" Isn't Always Obvious

The threshold question gets harder once a site has more than one vessel or unit handling the same chemical, because 1910.119 evaluates coverage at the level of the process, and interconnected equipment can count as a single process even when it's spread across a building or a yard. Two storage tanks feeding the same reaction unit through connected piping are typically treated as one process for threshold purposes, even if neither tank alone holds enough of the chemical to trigger coverage on its own. A site engineer optimizing for throughput or redundancy by adding a second tank and tying it into the existing system may be creating a PSM-covered process without ever framing the change that way, because from an operations standpoint it looked like capacity planning, not a regulatory event.

This is a second, quieter version of the visibility gap described above. It isn't only total inventory that needs monitoring — it's how equipment gets connected. A management-of-change review that only asks "are we changing the chemical or the quantity" can miss a change that alters what counts as one process without changing either. The sites best positioned to catch this are the ones where engineering change requests are routed through EHS as a matter of course, not just chemical purchasing requests.

Contractors Inside a Covered Process Inherit the Program, Not Their Own Rules

Once a process is covered, 1910.119(h) places specific obligations on both the host employer and any contractor working on or near that process — informing contractors of the known hazards, obtaining information about the contractor's own safety performance and training, and ensuring contract employees understand the applicable safety procedures. Portfolios that rely heavily on contract labor for turnarounds, mechanical integrity work, or maintenance at covered sites need this to function as a standing process, not a one-time onboarding packet, because contractor rosters turn over and the specific hazards of a given process don't change to accommodate whoever's on-site that week. A contractor management program built for general facility work — badge, orientation video, PPE issued at the gate — is not the same obligation as the one 1910.119(h) creates for a contractor whose crew is welding on a line that's part of a covered process, and treating them identically is where this tends to break down at scale.

A New Site Can Arrive Already Covered, or Not Covered Yet for the Wrong Reason

Acquisitions compound this. A newly acquired site may already have a process that meets PSM's chemical or quantity thresholds, with a PHA and an audit history that reflects the acquired company's program rather than yours — or with gaps that were never caught because the acquired company's own EHS function was thinner than assumed. Absorbing that site means absorbing its existing PSM clocks as they stand, not resetting them to a corporate baseline, and it means auditing the inherited program against 1910.119's actual requirements rather than assuming a plant that's been operating for years must already be compliant. The reverse case is just as real: a site that was never covered because its process never crossed the threshold at the time of acquisition can cross it later through the kind of ordinary volume growth described above, and there is no mechanism that automatically flags that transition to whoever now owns the corporate program.

What a Portfolio-Level View Actually Requires

None of this is solved by a single company-wide PSM policy document, however well written, because the policy document was never the hard part. The hard part is the inventory: knowing, at any given time, which processes across which sites currently meet a threshold, and tracking each covered process's own PHA revalidation date, audit date, and management-of-change history independently. That requires a standing mechanism — not a one-time survey — for sites to report changes in chemical inventory and process volumes up to whoever owns PSM compliance at the corporate level, paired with a periodic independent check rather than reliance on self-reporting alone.

A portfolio that can produce, on request, a current list of every covered process, its trigger chemical or quantity, and its next PHA and audit due dates is demonstrating something an inspector will notice: that coverage is being tracked as a live condition of the operation, not assumed based on which sites have always been assumed to be "the chemical plants." The alternative — finding out a process was covered only after an incident forces the question — is the outcome this structure exists to prevent, and it tends to surface at the single worst possible moment to discover a five-year-old PHA that was never revalidated.