Two obligations, both described as “every five years,” on the same covered process, arising from the same event. One of them restarts when the process changes. The other, so far as its own text says, does not. That single asymmetry is why process-safety deadlines are worth holding as separate tracked dates rather than as one entry on a calendar labelled process safety — 5 yr.
A facility that handles a highly hazardous chemical at or above a threshold quantity falls under OSHA's Process Safety Management standard, and very often under EPA's companion Risk Management Program rule as well. Between them the two rules impose three recurring acts: the process hazard analysis has to be updated and revalidated at least every five years, compliance with the standard has to be certified as evaluated at least every three years, and an RMP-covered facility has to update and resubmit its Risk Management Plan at least every five years.
Here is the part that is easy to read past. EPA's rule counts its five years from the initial submission or from the most recent update the rule required you to make — and one of those required updates is triggered within six months of any change that requires a revised process hazard analysis. So a management-of-change event that forces a PHA revision pushes your RMP resubmission date out by five years from that update. OSHA's standard contains no comparable provision: its five-year revalidation clock is written against the completion of the process hazard analysis, and the revalidation it asks for is a specific act performed by a team meeting the standard's composition requirement — not the same thing as a change-driven revision.
The practical consequence is counter-intuitive. The more actively a facility manages change — which is to say, the better its process-safety program is working — the further apart those two five-year dates drift. A plant that has not touched its process in a decade keeps them roughly aligned. A plant that revamps a unit every eighteen months does not. Here is how each clock is anchored, what moves it, and how to keep all three current as dates rather than as documents.
General information, not process-safety, engineering or legal advice. States operating OSHA-approved State Plans may impose additional or different requirements, and EPA's RMP rule has been amended and is the subject of a further proposed rule — confirm what currently applies to your facility at the official sources in section 11.
1. What are PSM and RMP?
OSHA's Process Safety Management standard sits at 29 CFR 1910.119. It is a fourteen-element program aimed at preventing catastrophic releases of highly hazardous chemicals, and its constituency is the people inside the fence: operators, maintenance crews, contractors on the unit. EPA's Risk Management Program rule, at 40 CFR Part 68, is its companion and looks outward — at the community and the environment beyond the property line. The two overlap substantially in what they ask a facility to do, which is why most covered sites run a single integrated program and produce one set of documents that satisfies both. What they do not share is a calendar. Remindax helps you hold the dates that program owes and reminds the people responsible; it doesn't conduct or facilitate process hazard analyses, perform compliance audits, manage a PSM program, prepare or submit Risk Management Plans, or hold process safety information.
Coverage under either rule is a threshold question rather than an application you file. There is no process-safety licence to renew and no regulator who writes to tell you that you are now in scope — a facility becomes covered because of what it has on site and how much of it, and the obligations attach from there. Because a covered site invariably carries a stack of other recurring obligations alongside these, the process-safety dates belong in the same register as the permits, inspections and training records the site already owes, which is what compliance tracking software is for: tracking and reminders, not a GRC suite.
1.1 The three dated acts, and what each one is anchored to
Of the fourteen PSM elements, three carry a recurring deadline — and each is anchored to a different act, which is the whole reason they need separate tracking:
- →The PHA revalidation is anchored to the analysis. Paragraph (e)(6) requires that at least every five years after the completion of the initial process hazard analysis, the PHA is updated and revalidated by a team meeting the standard's composition requirement, to assure that it stays consistent with the current process. The dated act is the revalidation itself.
- →The compliance audit is anchored to a certification. Paragraph (o)(1) does not say “audit every three years.” It says employers shall certify that they have evaluated compliance with the standard at least every three years, to verify that the procedures and practices developed under it are adequate and are being followed. The audit is the work; the certification is the date.
- →The RMP resubmission is anchored to whichever submission came last. Section 68.190 requires a covered facility to update and resubmit its Risk Management Plan at least once every five years from the date of its initial submission — or from the most recent update the rule required. That second limb is what makes this clock behave differently from the other two.
- →Mechanical integrity has no interval written into the rule at all. Paragraph (j)(4) sets the frequency of inspections and tests of process equipment by reference to manufacturers' recommendations and good engineering practice, and more frequently if prior operating experience shows it necessary. There is no number to look up: you determine the interval, and you are then held to the one you determined.
Suppose a management-of-change project revises a covered process enough to require a revised PHA. Under EPA's rule, that starts a six-month deadline to update the RMP — and because §68.190 counts the five years from the most recent required update, meeting that six-month deadline resets your resubmission date five years out from the day you filed it. Under OSHA's standard, the same project produces a PHA revision under the management-of-change element, but the standard does not say that a change-driven revision satisfies or restarts the five-year revalidation required by (e)(6), which is a distinct act by a team meeting a specified composition. The safe reading, and the one worth building your tracking around, is that the RMP date moved and the revalidation date did not. Confirm the point for your own program against OSHA's standard and interpretations before relying on it either way.
2. How often are PSM and RMP deadlines?
At least every five years after the completion of the initial process hazard analysis, by a team meeting the standard's composition requirement.
At least every three years, certifying that compliance with the standard has been evaluated. The audit is conducted by at least one person knowledgeable in the process, a report of findings is developed, and a response to each finding is promptly determined and documented.
At least every five years from the initial submission or the most recent required update — so a mid-cycle update moves the date. Required updates include six months after a change requiring a revised PHA or a revised offsite consequence analysis, six months after a change altering the Program level of a covered process, three years after a newly regulated substance is listed, and on the date a regulated substance is first present above a threshold quantity in a new or already covered process.
PHAs and their updates and revalidations are retained for the life of the process. Compliance audits are retained as the two most recent reports only.
Written out like that, the pattern is easier to see than it is on a calendar. Two of these dates never move except by being met. One of them moves whenever the process does. And the fourth line is the one people are most often surprised by, because it means the two records behave nothing alike: the PHA file is a continuous chain running back to the day the process started up, while the audit file is a rolling window that drops its third-oldest entry every time a new one lands.
3. Why tracking process-safety dates matters
Every one of these obligations is knowable years in advance, which is precisely what makes them easy to lose. Four properties explain why:
One clock is rewritten by your own project work
The RMP resubmission date is recalculated from the last required update. A capital project that closes in March changes a compliance date in a portal nobody on that project ever opens.
The audit clock counts a certification, not an audit
Work can be complete and the obligation still open. An audit performed, reported, and never certified or responded to leaves the dated act undone.
The records are kept to different depths
A gap in the PHA chain never ages out, because that chain is kept for the life of the process. A gap two audits back has already left the file you are required to hold.
The interval you must meet is sometimes one you set
Mechanical integrity has no fixed frequency in the rule. Your own determination becomes the standard you are measured against — and it lives in an engineering document, not a compliance calendar.
This is the property most likely to catch a well-run plant rather than a neglected one. Every change significant enough to require a revised process hazard analysis pushes the RMP resubmission out by five years from the update you file within six months of it. Nothing about that event pushes out the PSM revalidation. A facility that manages change diligently therefore accumulates distance between two dates it originally set on the same day — and the distance grows in proportion to how much real engineering work the site is doing. The failure mode is not neglect. It is a competent team checking the RMP portal, seeing a resubmission date comfortably in the future, and reading that as evidence that process safety is current.
Underneath all of this sits the reason the intervals are long in the first place. These are not administrative filings; the programs exist because the failure they guard against is a fire, an explosion or a toxic release, and the deadlines are spaced to match how slowly the underlying analysis needs revisiting. That spacing is also what makes them hard to hold. A three-year gap outlasts most reorganisations. A five-year gap outlasts most people in the role. The person who owes the next revalidation is frequently not the person who signed the last one, and there is no renewal notice anywhere in either rule that will tell them.
4. Who needs to track process-safety dates
Refineries know they are covered. The more interesting list is the sites that hold a threshold quantity of something without thinking of themselves as chemical plants at all, and the people whose job the deadlines quietly became:
Refineries & chemical plants
Many covered processes, each with its own PHA history, and a turnaround schedule that revises several of them in a single outage — moving some RMP dates and none of the revalidation dates.
Learn More
Food processing & cold storage
An anhydrous ammonia refrigeration charge above threshold makes a distribution warehouse a covered facility. The process safety obligations arrive attached to the plant room, not to anything the business thinks of as chemistry.
Water & wastewater treatment
Chlorine and sulphur dioxide systems bring both rules to a public utility whose compliance calendar was built around permits and monitoring reports, on entirely different rhythms.
Learn More
Manufacturers that crossed a threshold
A formulation change, a larger day tank or a new storage arrangement takes a process above a threshold quantity. Nothing is issued and nobody writes — the obligations simply begin, and so does a five-year count nobody diarised.
Multi-process, multi-site operators
The audit certification is generally a facility-level act; the PHA history belongs to each covered process. So one site produces one audit date and several revalidation dates, and a group produces a matrix.
EHS & process-safety managers
Inheriting a program mid-cycle, with three anchor dates recorded in three systems — a PHA file, an audit binder, and a federal portal — and no single view that says which one is nearest.
Learn MoreThe last card describes the situation these dates most often arrive in, and it is worth being precise about what makes it hard. The three anchors are not merely in different systems; they are owned by different functions. The PHA history sits with process engineering. The audit certification sits with the EHS or compliance function. The RMP submission sits in a federal reporting system that somebody touches once every few years. A manager taking over a program can reasonably ask each of those three groups whether things are current, receive three sincere yeses, and still be six weeks from a lapsed revalidation — because nobody was asked the question the other way round: which of our dates is nearest? For everything a covered site carries alongside these, health and safety tracking holds it in the same register: tracking and reminders, not an EHS management system.
5. What happens when a process-safety clock is missed
Process-safety lapses come in a small number of recognisable shapes, and only one of them looks like a missed deadline while it is happening.
A revalidation that quietly went past due. The five-year interval is long enough that the people who ran the last one have often moved on, and the obligation is anchored to a document rather than to anything that arrives in an inbox. There is no notice, no portal turning red, and no counterparty asking. The lapse is typically discovered either during a compliance audit — which is the point of having one — or by an inspector, and by then it is not a date that was missed but an interval that has been open for a while.
An audit done but never certified or closed out. The standard asks for four connected things: an evaluation of compliance, a report of the findings, a promptly determined and documented response to each finding with deficiencies documented as corrected, and the certification that ties it to a date. Facilities routinely complete the first two and stall on the third, so a genuine audit sits in a binder with a dozen open findings and no dated certification against it. On the record that exists, the three-year obligation has not been met — and because only the two most recent audit reports are retained, an incomplete cycle can drop out of the file entirely before anyone reconciles it.
A required RMP update that was never filed. This is the failure specific to EPA's side, and it has a double consequence. The six-month update owed after a change requiring a revised PHA is an obligation in its own right; missing it also means the five-year clock never restarted, so the facility is now working from a resubmission date it believes has moved and which has not. Where the change altered the Program level applying to a covered process, the update carries more weight still, because the requirements themselves have changed.
Mechanical integrity intervals that drifted from what the program says. Because the frequency is set by manufacturers' recommendations and good engineering practice rather than by a number in the rule, a facility can fall behind its own written intervals without ever passing a regulatory date. The gap usually surfaces as an audit finding, which is the mechanism working as designed — provided the audit is happening on time.
Enforcement follows the ordinary routes: OSHA cites PSM deficiencies under the Occupational Safety and Health Act, and EPA enforces the RMP rule under the Clean Air Act, with facilities in State Plan states answering to their state agency. But the consequence that matters is not the citation. An out-of-date process hazard analysis is a document describing a process that has changed, being relied on by people making decisions about a process that exists. That is a different kind of exposure from a late filing, and it is the reason these particular intervals are worth holding as tracked dates with real lead time rather than as items on a to-do list.
6. How Remindax keeps every clock current
Remindax holds the dates and reminds the people who have to act on them. It does not conduct or facilitate process hazard analyses, perform compliance audits, manage a PSM program, prepare or submit Risk Management Plans, or hold process safety information.
Three anchors, held separately
The PHA revalidation date, the compliance-audit certification date and the RMP resubmission date as three distinct entries per covered process — so being current on one is never displayed as being current.
The date that moves, moved deliberately
Record a required RMP update when it is filed and reset the five-year resubmission date from it — as an act someone performs, not an assumption. The revalidation date sits alongside, visibly unchanged.
Reminders with months of runway
Staged alerts by Email, SMS and WhatsApp, set far enough ahead that a revalidation team can be assembled and an audit scheduled — not so late that the only option is to book whoever is available.
Per process, per site
Each covered process carries its own history, and each facility its own audit certification. Pairs with Locations and Equipment asset profiles, so a process's dates live where the process physically is.
A record that outlasts the interval
When each revalidation was completed, when each audit was certified, and when each RMP submission or update was filed — a dated chain that survives the turnover a five-year interval guarantees.
Dates and status only
GDPR-ready, hosted on AWS secure cloud with encrypted storage. Remindax holds when things are due and whether they were done — not your PHA, your audit findings, your process safety information or your RMP contents.
The mechanically important one is the second. Almost every tracking system can hold a fixed recurring date; very few make the moving one explicit. Treating the RMP reset as a recorded act — this update was filed on this day, so the next resubmission is five years from here — is what stops the two five-year dates from being silently assumed to be the same date. It also creates the artifact that the six-month update obligation was actually met, which is the thing that is hardest to reconstruct years later.
7. Why spreadsheets fail for process-safety tracking
A spreadsheet handles fixed recurring dates well enough. The specific thing it cannot do is hold a date whose value is rewritten by an event recorded somewhere else.
A cell containing an RMP resubmission date five years out is correct until a management-of-change project requires a revised PHA, and from that point it is wrong — not because anyone made an error, but because the underlying rule recalculated it and nothing propagated the change into the file. The formula that produced it counted forward from the wrong anchor. And the six-month update deadline that same event created cannot be entered in advance either, because until the change happens there is nothing to enter.
It also flattens distinctions the rules keep separate. A row labelled “audit — 3 yr” records neither whether the certification was made nor whether each finding was responded to and documented as corrected, which is what the standard actually asks for. A single “PHA” column cannot distinguish a change-driven revision from a five-year revalidation by a team meeting the composition requirement, so the more diligently a site manages change, the more confidently its own tracker will misreport its position. And a spreadsheet is a natural place to start pasting in the detail behind the dates — findings, chemical quantities, process descriptions — which is process safety information that has no business in a tracking file.
Then there is the interval itself. A five-year date outlasts the file, its author and usually the software it was written in. What gets lost first is not the date but the reasoning: which day the process was first analysed, which update reset the RMP clock and when, and why the next revalidation falls where it does. A system that holds each anchor as its own tracked date, records the act that moved one of them, reminds a named owner with months of runway, and keeps a dated history per covered process turns process safety from something a facility remembers into something it can show.
8. Key takeaways
- ✓OSHA's PSM standard (29 CFR 1910.119) and EPA's RMP rule (40 CFR Part 68) cover facilities holding highly hazardous chemicals at or above a threshold quantity — coverage begins by operation of the rules, with nothing issued and nobody notified.
- ✓Three acts carry recurring deadlines: the PHA is updated and revalidated at least every five years, compliance is certified as evaluated at least every three years, and the RMP is updated and resubmitted at least every five years.
- ✓Each is anchored to a different act — the analysis, the certification, and the last submission — so they cannot be tracked as one recurring entry.
- ✓The RMP clock is recalculated from the most recent required update, so a change requiring a revised PHA pushes it out five years from that update. OSHA's standard contains no equivalent reset for the five-year revalidation.
- ✓The two five-year dates therefore drift apart in proportion to how actively the site manages change — a well-run program separates them faster than a neglected one.
- ✓The records are kept to different depths: PHAs and their revalidations for the life of the process, compliance audits as the two most recent reports only.
- ✓Mechanical integrity has no interval in the rule — frequency follows manufacturers' recommendations and good engineering practice, so the standard you are held to is the one you set.
- ✓Tracking all three anchors per covered process — as dates and status, never as analyses — is what keeps the program current and the record defensible.
Never let one clock come due unnoticed
Track PHA revalidation, compliance-audit certification and RMP resubmission — automatically, for every covered process. Remindax holds each anchor separately, records the update that moved one of them, and reminds the right person while there is still time to assemble a team.
GDPR-ready · AWS secure cloud · Encrypted storage · Setup in under 5 minutes
9. Frequently Asked Questions
Three recurring dates. Under OSHA's PSM standard the process hazard analysis is updated and revalidated at least every five years after the completion of the initial PHA, and the employer certifies that compliance with the standard has been evaluated at least every three years. Under EPA's RMP rule the Risk Management Plan is updated and resubmitted at least every five years. Each is anchored to a different act, so being current on one says nothing about the others.
It resets one of them. Section 68.190 counts the five years from the initial RMP submission or from the most recent update the rule required - and an update is required within six months of a change that requires a revised process hazard analysis. So filing that update pushes the resubmission date five years out from the day it was filed. OSHA's standard contains no equivalent provision: paragraph (e)(6) runs from the completion of the process hazard analysis and asks for a revalidation by a team meeting the standard's composition requirement, which a change-driven revision under management of change is not. Track the two dates separately and confirm the point for your own program against OSHA's standard and interpretations.
Updating and revalidating the process hazard analysis at least every five years, by a team meeting the standard's composition requirement, to assure that the analysis is still consistent with the current process. It is a distinct act from the PHA updates that management of change produces during the interval, and the standard sets no fixed procedure for it beyond the five-year interval and the team requirement.
They are companion rules with different constituencies. OSHA's Process Safety Management standard at 29 CFR 1910.119 protects workers inside the facility; EPA's Risk Management Program rule at 40 CFR Part 68 protects the surrounding community and environment. Many facilities are covered by both and run one integrated program, but the two rules keep separate deadlines - which is exactly where facilities get caught out.
At least every three years - though the standard's wording is worth noting. Paragraph (o)(1) requires the employer to certify that compliance with the standard has been evaluated at least every three years, so the dated act is the certification rather than the audit itself. The audit is conducted by at least one person knowledgeable in the process, a report of the findings is developed, and the employer promptly determines and documents a response to each finding and documents that deficiencies have been corrected.
To very different depths, which surprises people. Process hazard analyses, their updates and revalidations, and the documented resolution of PHA recommendations are retained for the life of the process. Compliance audits are retained as the two most recent reports only. So a gap in the PHA chain never ages out of the file you are required to hold, while a gap three audits back has already left it.
The standard sets no interval. Paragraph (j)(4) requires the frequency of inspections and tests of process equipment to be consistent with applicable manufacturers' recommendations and good engineering practices, and more frequently if determined necessary by prior operating experience. In practice that means the interval is one you determine and are then measured against, which is why it belongs in a tracked register rather than only in an engineering document.
No. Remindax tracks the dates - the PHA revalidation, the compliance-audit certification, the RMP resubmission and any required update - and reminds the people responsible. Conducting or facilitating process hazard analyses, performing compliance audits, managing the program, and preparing and submitting Risk Management Plans are done by your process-safety team and its advisers. Remindax is not a PSM, EHS, PHA-facilitation or SDS-management platform, holds no process safety information, and is not a source of process-safety, engineering or legal advice.
Yes. Each covered process carries its own PHA revalidation history and each facility its own audit certification and RMP submission record, with their own reminders and their own recipients. That separation is the point: one process being current says nothing about the next one, and a facility whose RMP date has been reset by an update can still be approaching a revalidation that never moved.
Yes - a forever-free plan, no credit card required.
PSM requirements are set by OSHA at 29 CFR 1910.119 and RMP requirements by EPA at 40 CFR Part 68; states operating OSHA-approved State Plans may impose additional or different requirements, and EPA's RMP rule has been amended and is the subject of a further proposed rule. Remindax tracks the dates and reminds you; it doesn't conduct or facilitate process hazard analyses, perform compliance audits, manage a PSM program, prepare or submit Risk Management Plans, or hold process safety information. Confirm what applies to your facility at the official sources below; this is general information, not process-safety, engineering or legal advice.
11. Sources & references
This page summarizes public requirements and isn't process-safety, engineering or legal advice. States operating OSHA-approved State Plans may impose additional or different requirements, and EPA's RMP rule was amended in 2024 and is the subject of a further proposed rule — confirm what currently applies to your facility at the official sources below and with your state agency.
- •OSHA — 29 CFR 1910.119, Process safety management of highly hazardous chemicals — the standard itself, including the fourteen elements and the appendices listing highly hazardous chemicals and their threshold quantities.
- •29 CFR § 1910.119 (Cornell LII) — paragraph (e)(6) on the five-year PHA update and revalidation, (e)(7) on retaining PHAs for the life of the process, (j)(4) on mechanical-integrity frequency, (l) on management of change, and (o) on the three-year compliance-audit certification and the two-report retention rule.
- •40 CFR § 68.190 — Updates — the provision this page turns on: the five years run from the initial submission or the most recent required update, and the list of events that require an update, including six months after a change requiring a revised PHA.
- •EPA — Risk Management Plan (RMP) Rule Overview — who is covered, what an RMP must contain, and how the program relates to the Clean Air Act.
- •EPA — Risk Management Program Safer Communities by Chemical Accident Prevention Final Rule — the 2024 amendments to Part 68 and their compliance dates.
- •EPA — Common Sense Approach to Chemical Accident Prevention Proposed Rule — proposed in February 2026 with comments closing 11 May 2026, this would modify or rescind parts of the 2024 rule. Check its current status before relying on any provision the 2024 amendments introduced.