Facilities that handle enough of certain regulated substances fall under the EPA Risk Management Program. Many of those same facilities also fall under OSHA process safety management, and the two programs cover much of the same ground with different agencies, different lists and different deadlines.
The result is predictable. Companies build one program well and let the other drift, and the drift is almost always on the EPA side — because PSM has inspectors who show up, and RMP has a filing that quietly goes stale.
What makes RMP different
The offsite consequence analysis. This is the element with no PSM equivalent. RMP requires modeling what happens beyond your fence line — worst-case and alternative release scenarios, distances to endpoints, and the population potentially affected. It reframes the whole program: this is not only about your employees, it is about the neighborhood.
It is a filing, not just a program. You submit a risk management plan to EPA, and it requires updating on a defined cycle and whenever certain changes occur. A program that is being run well but whose submission has gone stale is still a violation, and it is one of the easiest to establish.
It is public-facing. Portions of RMP information are accessible to the public and to local responders. Community and media interest is a real consequence of this program in a way it is not for most OSHA standards.
Coordination with local responders. Emergency response coordination with local agencies is explicit, and it is the element I most often find undone — a plan referencing a fire department that has never visited the site and has no idea what is stored there.
The three program levels
RMP sorts covered processes into program levels based on factors including offsite consequence potential, accident history and whether the process is subject to PSM. The requirements scale accordingly, with the highest level closely mirroring the PSM elements — hazard analysis, operating procedures, training, mechanical integrity, management of change, pre-startup review, compliance audits and incident investigation.
Determining your level correctly matters, because building to the wrong level means either a compliance gap or spending on obligations you do not have.
Where facilities actually fall short
The five-year update forgotten. The plan requires resubmission on a defined cycle and after certain changes. Facilities change ownership, personnel turn over, and the submission responsibility evaporates.
Consequence analysis based on a process that no longer exists. Modeling done at initial submission, with the process modified three times since, never re-run.
Accident history requirements misunderstood. Reportable accident history must be reported, and the criteria are specific. Under-reporting here is common and is exactly the kind of finding that expands an inspection.
PSM and RMP maintained as separate systems. Two sets of procedures, two audit cycles, two sets of training records covering the same process. This doubles the labor and guarantees the two will contradict each other eventually.
No coordination with the local emergency planning committee. Related EPCRA obligations sit adjacent to RMP, and facilities frequently treat them as unrelated filings handled by different people.
Running them as one system
The practical approach is a single process safety management system with the RMP-specific elements layered on: the offsite consequence analysis, the filing and update schedule, the accident history tracking and the responder coordination.
That means one hazard analysis serving both, one management of change process, one mechanical integrity program, one set of operating procedures and one compliance audit cycle — with the submission calendar owned and tracked like any other regulatory deadline.
Start with applicability. Documented, for both programs, based on actual inventory and how the process is defined. A surprising number of facilities have never made either determination formally, which means they do not know what they are supposed to be doing.
Key takeaways
- RMP is the environmental twin of PSM. Overlapping elements, different agency, different substance list, separate filing.
- The offsite consequence analysis has no PSM equivalent. It models release impact beyond the fence line and reframes the program around the community.
- A stale submission is a violation. The plan requires updating on a defined cycle and after certain changes, and this is the most commonly missed obligation.
- Responder coordination is usually undone. Plans routinely reference a fire department that has never been on site.
- Run one system, not two. A single hazard analysis, MOC and audit cycle with RMP-specific elements layered on.
Related reading: Process Safety Management Support · EHS for Chemical Manufacturing · Environmental Compliance Audits
