EPA RMP Is Current. Which Facility Record Proves What?
Separate applicability, hazard assessment, prevention, emergency response, accident history and the submitted RMP before scoping a facility review.
Signals to watch
- A facility says its RMP is current while a regulated process, substance quantity or ownership record has changed
- An emergency-response document is offered as proof that hazard assessment and prevention-program duties are complete
- A five-year resubmission date is quoted without the latest submission version or the change that set the update clock
An EPA Risk Management Plan (RMP) is not one document that proves every process-safety claim. For a facility covered by 40 CFR Part 68, a useful review separates six records: applicability, hazard assessment, prevention programme, emergency response, five-year accident history and the version of the RMP submitted to the US Environmental Protection Agency. The first job is to find which record no longer matches the facility.
That is the answer an industrial process-safety consultancy practice lead needs when an authorised chemical-manufacturing, storage-terminal or environmental-compliance Telegram group says, “the RMP is current,” while also mentioning a new vessel, a different substance quantity or a response-plan revision. A day can matter when a site walk-through or proposal meeting is being scheduled. It does not turn the message into a confirmed compliance defect or a buyer. It makes the mismatch worth checking before the conversation moves on.
The EPA Risk Management Program page places the rule under Clean Air Act section 112(r). The current regulatory text is in 40 CFR Part 68. Those sources define the legal objects; a consultant still needs facility-controlled evidence and qualified legal and engineering review for an actual determination.
“Current RMP” is a conclusion, not a source record
Applicability begins with a process, a regulated substance and the quantity in that process. Under section 68.10, the programme applies when a stationary source has more than a threshold quantity of a regulated substance in a process, subject to the rule’s definitions and exclusions. The substance list and thresholds appear in section 68.130.
This is why a general chemical inventory is not enough. The evidence must connect a named substance and quantity to a defined process at the stationary source. If a group message mentions “more ammonia capacity next month,” it leaves open the chemical form, process boundary, maximum intended inventory, threshold and effective date. The facility may be covered already, may move between programme levels or may remain outside the cited route. Current public information is not sufficient to choose among those explanations.
The EPA RMP Rule overview is useful for orientation, but it is not the facility’s applicability calculation. Keep the official rule beside the controlled inventory and process record.
The facility record has six layers
Use six separate evidence slots. A blank slot is an unanswered question, not proof of non-compliance.
- Applicability record. Identify the stationary source, covered process, regulated substance, maximum quantity, threshold and programme level. Preserve the calculation version and its owner.
- Hazard-assessment record. Keep the worst-case and applicable alternative-release scenario inputs, consequence assumptions and five-year accident-history basis. Do not substitute an emergency map for the analysis.
- Prevention-programme record. Link the process to the applicable Program 2 or Program 3 prevention elements, such as process-safety information, hazard review or process hazard analysis, operating procedures, training, maintenance, management of change and incident investigation where the rule requires them.
- Emergency-response record. Determine whether the facility follows the applicable response-program route or coordinates with local responders under the rule. Retain the current plan or coordination evidence, exercise or notification records and responsible contacts.
- Accident-history record. The five-year accident history has its own event criteria and reporting fields. It is neither the full incident log nor a substitute for investigation files.
- Submitted-RMP record. Preserve the EPA submission version, submission or resubmission date, facility and process identifiers, certifications and any later correction or update. This is the reporting surface, not the entire operating programme.
The distinction matters commercially. A company asking for “an RMP update” may need a narrow submission correction, an applicability reassessment after a process change, new consequence modelling, a prevention-programme review or emergency-coordination work. Quoting one package before identifying the broken layer creates the wrong scope.
An illustrative change shows where the evidence separates
Suppose an authorised terminal-operations group contains three incomplete fragments:
Illustrative composite: “Tank B starts taking a higher concentration next month. The county response sheet was updated. Our RMP was filed three years ago.”
This is not a real company statement, customer record or compliance result. It gives a practice lead three facts to test and many facts that remain unknown.
“Higher concentration” belongs first in the applicability and hazard-assessment slots. The county sheet belongs in the emergency-response slot. “Filed three years ago” belongs in the submitted-RMP slot. None proves that the process quantity changed, that an earlier update event occurred, that the release scenarios remain valid or that the prevention programme reflects the change.
The first useful request is therefore not “send the RMP.” Ask for the current process/substance inventory and change record, the last applicability decision, the affected release-scenario inputs, the prevention records touched by the change, the emergency-response or coordination revision, and the latest EPA submission receipt. The records can then show whether the work is a calculation, engineering, procedure, coordination or submission task.
The update clock must be tied to an event
Section 68.190 contains the RMP update rules. The five-year cycle is important, but earlier events can require revision or resubmission. A reviewer should record the last submission date and then test the actual change against the current rule rather than promise that “three years means no update.”
The event log should name the change, effective date, affected process, regulatory assessment, document versions and approval owner. If the facility concludes that no resubmission is triggered, retain the rule-based decision and supporting facts. If the change affects the underlying programme without changing the submitted RMP immediately, retain that distinction too.
For a separate rapid workplace-event clock, use the OSHA severe-injury reporting source check. When a forwarded interpretation conflicts with the current regulatory text, the official-source ladder helps recover the controlling source. The SEC incident-response evidence map shows why an operational record and a regulator-facing record should remain separate in another domain.
Telegram fragments belong in a review queue, not a compliance verdict
TOP Prospect can organise matching fragments from Telegram groups the user has deliberately connected and is authorised to access, preserving original text, source, time and a reason for human review. The current matching-target interface saves configuration but does not automatically create new candidates. The product cannot inspect chemical inventories, calculate offsite consequences, enter EPA systems, contact responders or determine compliance.
That boundary is useful: a score may move the “new tank / old RMP” discussion above a generic chemical mention, but the practice lead still decides whether the fragments concern the same facility and whether to request evidence. The Telegram Signal workflow explains the authorised-source and human-review model.
Key facts
- RMP applicability is tied to a covered process containing more than a listed substance’s threshold quantity, subject to current rule definitions and exclusions.
- Hazard assessment, prevention, emergency response, accident history and the submitted RMP are related but non-interchangeable records.
- Program 1, Program 2 and Program 3 routes depend on rule criteria; a message or public record does not establish the programme level by itself.
- The RMP has a five-year resubmission cycle and earlier update events under section 68.190.
- The submitted plan reports selected information; it does not replace the facility’s underlying analyses and operating records.
- A defensible service scope starts with the first facility record that cannot be reconciled to the current process.
FAQ
Is an EPA Risk Management Plan the same as an emergency response plan?
No. Emergency response is one layer of the Risk Management Program record. Applicability, hazard assessment, prevention, accident history and the submitted RMP remain separate.
Does every facility handling a listed substance have to submit an RMP?
No. The process must meet the rule’s applicability conditions, including more than the applicable threshold quantity, after applying definitions and exclusions.
How often is an RMP resubmitted?
The rule includes a five-year cycle and specified earlier update events. Review the current section 68.190 facts instead of using the calendar alone.
Can a public RMP record prove that the safety programme is effective?
No. It can establish selected submitted facts and dates. Effectiveness and current implementation require the underlying facility evidence and qualified review.
Editorial review completed 22 August 2026 against the current EPA RMP pages and 40 CFR Part 68. Qualified process-safety, engineering, emergency-response and legal reviewers must determine actual applicability and required action.
Frequently asked questions
Is an EPA Risk Management Plan the same as an emergency response plan?
No. Emergency response is one part of the Risk Management Program record. Applicability, hazard assessment, prevention, accident history and the submitted RMP are separate evidence objects.
Does every facility handling a listed substance have to submit an RMP?
No. Applicability depends on whether a covered process contains more than the threshold quantity of a substance listed under 40 CFR 68.130, together with the rule definitions and exclusions.
How often is an RMP resubmitted?
The rule includes a five-year resubmission cycle and earlier update events. The facility must identify which event applies instead of relying only on the previous submission date.
Can a public RMP record prove that the underlying safety programme is effective?
No. A public or submitted record can establish selected reported facts and dates; it does not by itself verify every underlying analysis, procedure, implementation step or current condition.
Sources and further reading
How a Signal worth attention is found
See how Top Prospect finds and organizes Signals worth checking, keeps the original Telegram context, removes duplicates, and helps you decide what to review first. You decide whether to follow up and what to do next.
