Skip to main content
  • Solutions
      • Compliance Management
      • Audits and Inspections
      • Compliance Obligations
      • Document Management
      • Incident Management
      • Management of Change
      • Risk Register
      • Pipeline Safety
      • Task Tracking
      • Training
      • Environmental
      • Air Quality
      • ISO 14001
      • EPA RMP
      • LDAR
      • SPCC
      • Stormwater
      • TSCA PCB Management
      • Waste Management
      • Water Quality
      • Health and Safety
      • ISO 45001
      • Asbestos
      • Chemical Management
      • Emergency Planning
      • Industrial Hygiene
      • Hazard Analysis
      • Process Safety Management
      • Other
      • ISO 9001
      • Contractor Management
      • Customer Management
      • Data Management
      • Land Management
      • Oil and Gas
      • Preventive Maintenance
      • EHS Dashboard
      • Mobile EHS App
  • Industries
      • Mining
      • Oil and Gas
      • Manufacturing
      • Food and Beverage
      • Higher Education
      • Healthcare
      • Construction
      • Municipalities
      • Utilities/Power
      • Transportation
      • Petrochemicals
      • Chemicals
  • About
      • Accessibility
      • Security
      • AI Features
      • System Status
      • Release Notes
      • Support
      • Why Ecesis
      • About EDS
      • Frequently Asked Questions
      • Join Our Team
      • Pricing
      • EHS Resources/Tools
      • EHS Compliance Calendars
      • EHS Calculators
      • EHS Inspections
      • EHS Program Audits
      • EHS Blog
Ecesis EHS Software
  • Ecesis EHS Software on LinkedIn
  • Ecesis EHS Software on Facebook

RMP Program
Levels

The EPA's Risk Management Program (40 CFR Part 68) classifies every covered process into one of three program levels with progressively more rigorous prevention program requirements. Program level determines what you must do, what you must document, and what you must submit. Misclassifying a process is one of the most consequential mistakes in RMP implementation — classify too low and you may be cited for missing required elements; classify too high and you spend resources building program elements that do not apply. This guide walks through the classification logic, the requirements for each level, and what to do when a classification changes.

The Three Program Levels at a Glance

Program 1

Lowest burden. Available only when offsite risk is minimal.

  • Worst-case scenario only
  • 5-year accident history
  • Emergency response coordination
  • Risk Management Plan submission

Program 2

Mid-tier. Streamlined prevention program.

  • All Program 1 requirements
  • Worst-case + alternative scenarios
  • Safety information
  • Hazard review
  • Operating procedures
  • Training
  • Maintenance
  • Compliance audits
  • Incident investigation

Program 3

Highest burden. PSM-equivalent prevention program.

  • All Program 2 requirements
  • Process hazard analysis
  • Process safety information
  • Pre-startup safety review
  • Mechanical integrity
  • Hot work permits
  • Management of change
  • Contractors
  • Employee participation
  • Trade secrets

How to Determine Program Level

Program level is determined process by process, not facility-wide. A single facility can have processes in different levels. Run this evaluation for each covered process at your site.

Step 1: Check Program 1 eligibility

A process qualifies for Program 1 only if all four of the following are true:

  • The worst-case release scenario does not have any public receptors within the distance to the toxic or flammable endpoint
  • No accidents from the process in the last five years caused offsite deaths, injuries, evacuation, sheltering in place, property damage, or environmental damage
  • Emergency response procedures have been coordinated with local emergency response organizations
  • The process is not subject to OSHA PSM and not in a Program 3 NAICS code (these conditions automatically push it to Program 3)

If all four are true, the process is Program 1. If any are false, continue to Step 2.

Step 2: Check Program 3 conditions

A process is Program 3 if either of the following is true:

  • It is subject to OSHA Process Safety Management (29 CFR 1910.119)
  • It is classified in one of the ten NAICS codes listed at 40 CFR 68.10(d) (see table below)

If either is true, the process is Program 3. If neither is true, the process is Program 2 by default.

Step 3: Default to Program 2

If a process does not qualify for Program 1 (because it has public receptors, recent offsite-consequence accidents, or untreated emergency coordination) and is not Program 3 (because OSHA PSM does not apply and the process is not in a Program 3 NAICS code), it is Program 2.

Public receptor means any offsite location where members of the public could be exposed — residences, schools, hospitals, prisons, public recreation areas, commercial or industrial facilities. The endpoint distance is the distance at which a toxic substance reaches the toxic endpoint concentration or a flammable substance produces 1 psi overpressure or sufficient radiant heat for second-degree burns. The endpoint distance is determined by air dispersion modeling, typically using EPA's free RMP*Comp tool or commercial models like ALOHA or PHAST.

The Program 3 NAICS Codes

40 CFR 68.10(d) lists ten North American Industry Classification System (NAICS) codes that automatically place a process in Program 3, even if OSHA PSM does not apply. The list captures industries that EPA determined warrant the most rigorous prevention program based on accident history.

NAICS Code Industry
32211Pulp Mills
32411Petroleum Refineries
32511Petrochemical Manufacturing
325181Alkalies and Chlorine Manufacturing
325188All Other Basic Inorganic Chemical Manufacturing
325192Cyclic Crude, Intermediate, and Gum and Wood Chemical Manufacturing
325199All Other Basic Organic Chemical Manufacturing
325211Plastics Material and Resin Manufacturing
325311Nitrogenous Fertilizer Manufacturing
32532Pesticide and Other Agricultural Chemical Manufacturing

Program 1 in Detail

Who qualifies

Program 1 was designed for low-risk processes whose worst-case release would not reach the public. In practice, qualifying processes tend to be small, isolated facilities with no nearby populations — certain remote utility operations, small ag retailers in rural settings, and some research operations. Most chemical, refining, and water/wastewater facilities do not qualify.

What is required

  • Hazard assessment: Worst-case release scenario only (no alternative scenarios required)
  • 5-year accident history: Document any accidental releases from the process in the last five years
  • Emergency response coordination: Verify that local emergency responders know about the regulated substance, are willing and able to respond, and that response procedures are coordinated
  • RMP submission: Submit the abbreviated Program 1 portions of the Risk Management Plan
  • Recordkeeping: Maintain records substantiating Program 1 eligibility for the duration of coverage

What is not required

Program 1 processes do not need a written prevention program, PHA, training records, MOC, mechanical integrity, or compliance audits. The compliance burden is fundamentally lower — but the eligibility test is strict, and any change that creates public receptors or causes an offsite-consequence accident triggers reclassification.

Program 2 in Detail

Who qualifies

Program 2 is the default for any process that doesn't qualify for Program 1 and isn't pulled into Program 3 by PSM coverage or NAICS code. Common Program 2 processes include water and wastewater treatment with chlorine, ammonia refrigeration in food and cold storage, propane distribution, and certain ag retailers with anhydrous ammonia.

Hazard assessment

Worst-case release scenario plus at least one alternative release scenario for each regulated toxic substance and one collective alternative scenario for flammables. Alternative scenarios should reflect more likely release events that could reach an offsite endpoint — transfer hose failures, vessel ruptures with mitigation, process upsets.

Streamlined prevention program (40 CFR 68.48–68.60)

  • Safety information: Documentation of regulated substance hazards, equipment design, and operating limits
  • Hazard review: Identification of process hazards, opportunities for equipment malfunction or human error, and safeguards (similar to but less rigorous than full PHA)
  • Operating procedures: Written procedures for normal and emergency operations
  • Training: Initial and refresher training (every three years) for operators
  • Maintenance: Written procedures for ongoing maintenance, inspection, testing, and quality assurance
  • Compliance audits: Every three years, two most recent reports retained
  • Incident investigation: Investigation of incidents that resulted in or could reasonably have resulted in a release

Emergency response

Same as Program 3 — either a written emergency response plan if employees respond, or coordination with local responders if they do not.

Program 3 in Detail

Who qualifies

Any process subject to OSHA PSM (29 CFR 1910.119), or any process classified in one of the ten Program 3 NAICS codes listed above. This captures most refining, chemical manufacturing, and large industrial chemical handling operations.

Hazard assessment

Same as Program 2 — worst-case plus alternative release scenarios for each regulated toxic substance and one collective alternative for flammables.

Full prevention program (40 CFR 68.65–68.87)

The Program 3 prevention program is essentially identical to OSHA PSM:

  • Process safety information — chemical hazards, technology, equipment
  • Process hazard analysis — HAZOP, What-If, FMEA, Fault Tree, etc., revalidated every 5 years
  • Operating procedures — startup, normal ops, shutdown, emergencies
  • Training — initial and refresher every 3 years
  • Contractors — selection, evaluation, oversight
  • Pre-startup safety review
  • Mechanical integrity
  • Hot work permits
  • Management of change
  • Incident investigation
  • Employee participation
  • Compliance audits
  • Trade secrets
If you operate Program 3 processes, you are almost certainly already running an OSHA PSM program. The smart approach is to integrate the two: one set of PHAs, one set of operating procedures, one MOC system, one set of training records, one audit cycle. Ecesis PSM software and RMP software share the same platform so the integration happens by default.

Mixed-Level Facilities

It is common for a single facility to have processes in different program levels. For example, a chemical manufacturing facility might have:

Example mixed-level facility

  • Process A: A reactor producing organic intermediates — subject to OSHA PSM, NAICS 325199 — Program 3
  • Process B: A chlorine dioxide system for water treatment — not PSM-covered, not in a Program 3 NAICS code, but with public receptors within worst-case distance — Program 2
  • Process C: A small anhydrous ammonia tank for fertilizer feedstock — remote location with no public receptors and no offsite-consequence accidents — Program 1

The facility submits one Risk Management Plan covering all three processes, but each process has its own program level designation, prevention program, and corresponding hazard assessment.

What Happens When Program Level Changes

Several events can change a process's program level. Each requires action.

Common reasons for level changes

  • Adding a new regulated substance that brings the process under PSM
  • Removing a regulated substance such that PSM no longer applies
  • Changes to nearby populations that create or eliminate public receptors
  • An offsite-consequence accident that disqualifies the process from Program 1
  • Expanded coverage from a new EPA rulemaking
  • Reclassification of the facility's NAICS code

What you must do

  • Document the date and reason for the program level change
  • Build out (or stand down) the prevention program elements that apply at the new level
  • Conduct or refresh hazard assessment as required at the new level
  • Submit a revised Risk Management Plan to EPA within six months
  • Update emergency response coordination if the change affects offsite consequences
  • Train operators on any new procedures or protocols introduced by the new level
Don't drift downward without justification. A facility cannot reclassify a process to a lower program level simply because conditions feel safer. Reclassification requires that the eligibility criteria for the lower level are actually met — verified worst-case modeling, documented absence of public receptors, clean accident history, and where applicable, exit from PSM or the Program 3 NAICS code list. EPA inspectors look closely at downward reclassifications and require strong supporting documentation.

Documentation Tips

Maintain a program level log

For each covered process, keep a written record showing the program level designation, the date assigned, the basis for the designation (PSM coverage, NAICS code, worst-case distance, public receptors, accident history, emergency coordination), and any subsequent changes. This is one of the first documents EPA inspectors request.

Tie classification to MOC

Any change to a covered process should include a step in the MOC review asking: "Does this change affect program level?" Catching a level change at the MOC stage is far better than discovering it during an audit.

Track public receptor changes

New residential development, new schools, or new commercial buildings near the facility can create public receptors that did not exist before. Periodically verify the surrounding area against the worst-case endpoint distance — aerial imagery and county GIS records make this straightforward.

Bottom line: Program level classification is a process-by-process determination that drives the entire scope of your prevention program. Get it right at the start, document the basis clearly, and revisit it whenever changes occur. Ecesis EPA RMP software tracks program level designations, links each process to its prevention program elements, and flags MOCs that may trigger reclassification — so the level you submit always matches the level you operate.

Ecesis Software for RMP Compliance

EPA RMP Software

Track program levels and prevention program elements per process

PSM Software

Integrated Program 3 prevention program with PSM

Hazard Analysis

PHAs for Program 3 and hazard reviews for Program 2

Management of Change

Catch program-level-affecting changes at the MOC stage

Compliance Audits

Triennial RMP audits with corrective action tracking

Emergency Planning

Local responder coordination for Program 1, 2, and 3

Related Resources
EPA RMP Software Implementation Guide RMP vs PSM Program Levels Regulated Substances RMP*eSubmit Guide Offsite Consequence Analysis Safer Communities Rule Common Violations 5-Year Accident History Anhydrous Ammonia

What Is Ecesis?

Ecesis is a leading EHS Software Solution that has been helping companies around the world reach their EHS goals since 1993.

About Us

Why Ecesis Join Our Team Pricing Resources EHS Blog

Get in Touch

1499 West 120th Avenue
Suite 110
Westminster, CO 80234
(720) 547-5102 (866) 733-6912 Click To Email Us

Connect With Us

EHS Software on LinkedIn EHS Software on Facebook EHS Blog

Copyright © 2026 EnviroData Solutions, Inc.

Terms of Use    Privacy Statement    Cookies

×

Please complete the form below or call us at (720) 547-5102 to learn more about Ecesis.

Enter Your Name


Enter Your Phone Number


Let Us Know How We Can Help You


Enter Your E-mail


Please check the reCAPTCHA box.