--- title: U.S. rulemaking (Nov 3, 2026) forces operators to revalidate HAZOP LOPA, SIS evidence and audit MOC records description: HAZOP LOPA guidance covers practical lifecycle controls and safer, traceable engineering decisions for teams to review and record. url: "https://mangansoftware.com/docs/hazop-lopa/" updated: "2026-11-11" category: Functional Safety News --- # U.S. rulemaking (Nov 3, 2026) forces operators to revalidate HAZOP LOPA, SIS evidence and audit MOC records # U.S. rulemaking (Nov 3, 2026) forces operators to revalidate HAZOP LOPA, SIS evidence and audit MOC records HAZOP LOPA is the focus of this MSS technical news article. New Federal Register rulemaking and related agency proposals published the week of Nov 3, 2026 (PHMSA / EPA references in the Nov 3 Federal Register) explicitly link audit frequency, MOC/PHAs and incorporation of consensus standards into pipeline and chemical safety programs — creating immediate editorial and commercial opportunity for how to re-run, document and defend HAZOP/LOPA and [SIS](https://mangansoftware.com/docs/instrumented-systems-configuring-a-safety-instrumented-system/) evidence. The discussion uses the verified source evidence to separate confirmed facts from engineering interpretation. It also explains why the topic matters across the asset lifecycle, where decisions should be recorded and how teams can keep responsibilities, actions and evidence visible. [![HAZOP LOPA shown as a 3d illustration for the BetterDocs news article](https://mangansoftware.com/wp-content/uploads/2026/11/hazop-lopa-3d-illustration.jpg)](#elementor-action%3Aaction%3Dpopup%3Aopen%26settings%3DeyJpZCI6IjE5MzAyIiwidG9nZ2xlIjpmYWxzZX0%3D) ## HAZOP LOPA: Latest Evidence and Technical Context The Federal Register materials published the week of 3 November 2026 set out a technical context that directly affects how operators assemble and present process hazard analysis evidence. PHMSA’s proposal at §193.503(k) would adopt the auditing cadence language found in OSHA’s Process Safety Management regulations, requiring operators that elect subpart F to audit their compliance programmes once every three years. The same package proposes incorporation by reference of mandatory provisions in NFPA 59A‑2026 and introduces explicit linkages between management of change (MOC) and PHAs in §193.503(j). PHMSA’s notice of proposed rulemaking emphasises that audits are intended to backstop operator performance of amended or new PHAs in connection with MOC implementation: the stated objective is to ensure documentation and continual improvement rather than to force wholesale re‑performance of PHAs. At the same time, EPA’s RMP reconsideration materials and public pages set out the agency’s prior changes and its approach to elements such as third‑party audits and safer technology/alternatives analyses. Those materials, together with OSHA enforcement memoranda and historical RAGAGEP guidance, form the enforcement lens regulators are likely to use when assessing MOC, PHA and [SIS](https://mangansoftware.com/docs/sis-lifecycle/) evidence during inspections. For engineering teams this collection of agency positions and reference standards establishes what counts as auditable information: not only the PHA outputs themselves but the surrounding MOC records, evidence of why LOPA credit was given to specific independent protection layers (IPLs), and traceability of safety instrumented system (SIS) specifications back to safety‑instrumented function (SIF) testing and performance records. The original evidence is available from [U.S. Government Publishing Office (Federal Register) — Federal Register / Vol. 91, No. 211 / Tuesday, November 3, 2026 (Proposed Rules)](https://www.govinfo.gov/content/pkg/FR-2026-11-03/pdf/FR-2026-11-03.pdf). ## Why HAZOP LOPA Matters Across the Lifecycle Taken together, the proposals create an immediate compliance imperative. Auditable MOC decisions, current PHAs (including HAZOP records), documented [LOPA](https://mangansoftware.com/docs/what-is-lopa/) reasoning and maintainable SIS evidence are now part of what operators will need to demonstrate on a recurring basis. The practical consequence is that engineers and process‑safety professionals must think of HAZOP→LOPA→SRS information as a lifecycle package rather than a one‑off study: the package must show the technical basis, the decision path, and the verification that controls perform as assumed. From a lifecycle perspective, this matters at multiple handover points: when a proposed change is scoped and reviewed under MOC; when assumptions from a HAZOP are converted into LOPA credit and IPL descriptions; when a safety requirement is translated into a Safety Requirements Specification (SRS); and when SRS items are subject to field testing and ongoing monitoring. The enforcement materials and proposed rule language make clear that auditors will examine the chain of evidence linking those stages. Consequently, teams should plan reviews that explicitly map PHA findings to LOPA conclusions and to the SRS, and record the approvals, assumptions and tests that support each link. Practically, that reduces the risk that an inspector or auditor will find a gap between a written PHA and the operational reality of an IPL or SIS. ## Requirements and Practical Controls Begin every revalidation effort with the Federal Register trigger in mind: the proposed three‑year audit cadence and the incorporation of consensus standards mean records and traceability must be demonstrable. At a minimum, a practical verification sweep should check the following core items: PHA dates and revision history; associated MOC records showing why and how the PHA was amended; LOPA worksheets recording credited IPLs and the rationale for credit; and SRS entries that trace each SIF to tests and operational performance data. A pragmatic one‑page checklist for teams can be rendered in prose and used immediately: – Confirm the controlling PHA document and list all revisions since the baseline HAZOP. Note author and approver for each revision. – Pull the MOC record for each PHA change: confirm scope, impact analysis, required actions and closure evidence. – Verify LOPA worksheets: confirm initiating event selection, assumptions, frequency and consequence values, and the IPLs credited with explicit descriptions of function and proof tests. – Trace each LOPA‑credited IPL to the SRS: check that SIF descriptions, demand mode, safety integrity targets and test intervals are recorded. – Review field test records and functional safety assessments to confirm that SIF performance is consistent with the credited reliability. – Identify owners, due dates and verification tasks for any gaps found; require sign‑off and an auditable completion record. When validating decisions, follow a disciplined sequence: define the decision, confirm the source inputs, involve the right disciplines (process, instrumentation, operations, maintenance, and safety assurance), and record assumptions explicitly. Assign named owners and clear due dates for remediation; then capture verification evidence once actions are complete. Where IEC 61511 principles are relevant, ensure functional safety lifecycle tasks and proof‑test records are available to support SRS claims. Thinking in terms of discrete, accountable steps — similar to an action item tracker — makes audit preparation tractable and repeatable. ## How MSS Supports Better Lifecycle Information Controlled lifecycle information and structured workflows make it much easier to demonstrate the chain of technical decisions regulators will scrutinise. Mangan Software Solutions provides an environment that links engineering information, lifecycle activities and accountable decisions so that source evidence, reviews, approvals and operating records appear together in the same context. That does not replace specialist engineering judgement; rather, it organises the artefacts that support it so auditors and inspectors can rapidly see why a decision was made and how it was implemented. In practice this means recording the PHA outputs alongside the MOC rationale, LOPA worksheets and SRS entries; capturing owners, completion dates and verification checkpoints; and retaining proof‑test and SIF performance records with their associated assessments. Workflows that reflect these steps help teams find the current basis for a decision, demonstrate continuity of evidence during audits, and reduce the administrative effort of assembling compliance packages. For teams adopting systematic approaches to action tracking, an integrated record of responsibilities and verification significantly improves the defensibility of a HAZOP→LOPA→SRS package without obscuring the underlying engineering analysis. [Watch a recorded demo](#elementor-action%3Aaction%3Dpopup%3Aopen%26settings%3DeyJpZCI6IjE5NDk5IiwidG9nZ2xlIjpmYWxzZX0%3D)