
Loading...
Law Update
Quick note
Below is the official summary and the reference document preview. Use “Open PDF” for full screen view.
The Petroleum and Natural Gas Regulatory Board (PNGRB) has amended the framework governing Emergency Response and Disaster Management Plans, commonly called ERDMPs. The Petroleum and Natural Gas Regulatory Board (Codes of Practices for Emergency Response and Disaster Management Plan) Amendment Regulations, 2026 were notified on 7 August 2026 and published in the Gazette of India Extraordinary, Part III, Section 4, in the issue dated 17 August 2026.
The amendment does more than correct wording in the existing regulations. Its most important changes apply after a major incident. A covered entity must now follow a structured process for explaining lapses, forming an internal committee, fixing responsibility, acting against responsible personnel or contractors, dealing with compensation, and placing the outcome before its board of directors. The nominated director also receives a clear role in ensuring that action-taken information and board-level outcomes reach PNGRB within the prescribed periods.
These changes matter to refineries, pipelines, storage terminals, gas-bottling installations, city gas distribution facilities, fuel-dispensing locations and other operations covered by the ERDMP Regulations, 2010. Entities should review their ERDMP documents, incident-investigation procedures and governance calendars immediately because the amendment states that it comes into force on publication in the Official Gazette.
| Particular | Verified details |
| Issuing authority | Petroleum and Natural Gas Regulatory Board (PNGRB) |
| Document type | Final amendment regulations |
| Title | Petroleum and Natural Gas Regulatory Board (Codes of Practice for Emergency Response and Disaster Management Plan (ERDMP)) Amendment Regulations, 2026 |
| File number | PNGRB/Tech/1-T4SCGD/(4)/2023 |
| Gazette identification | CG-DL-E-18082026-275554; Gazette No. 504 |
| Notification date | 7 August 2026 |
| Gazette issue date | 17 August 2026 |
| Electronic signature date shown in the PDF | 18 August 2026 |
| Effective date | Date of publication in the Official Gazette; the Gazette issue is dated 17 August 2026 |
| Governing law | Section 61 of the Petroleum and Natural Gas Regulatory Board Act, 2006 |
| Principal regulations | PNGRB ERDMP Regulations, 2010 |
| Main subject | PNGRB ERDMP Regulations, 2010 |
| General transition period | Not expressly specified |
The notification date, Gazette issue date and electronic signature date are not the same. For compliance records, entities should preserve the Gazette copy and record the commencement basis used by their legal team. The text expressly links commencement to publication in the Official Gazette rather than to the date on which the notification was signed.
PNGRB issued the amendment under Section 61 of the Petroleum and Natural Gas Regulatory Board Act, 2006. That section allows the Board to make regulations, through notification, that are consistent with the Act and the rules made under it.
The principal ERDMP Regulations were notified in 2010 through G.S.R. 39(E). They establish the basic framework for identifying emergencies, preparing site-specific response plans, arranging emergency resources, defining incident-command responsibilities, conducting drills, documenting medical and evacuation arrangements, reporting incidents and supporting recovery. The framework has subsequently been amended, including in 2014, 2020 and 2025.
This 2026 notification is another amendment. However, it neither supersedes the whole ERDMP scheme nor deletes the obligations under the 2010 regulations. Entities covered by this scheme should consider both the new rules and the main rules and previous amendments as well.
The 2026 amendment operates within the scope of the principal ERDMP Regulations. Regulation 3 of the official consolidated regulations applies the framework to the following broad categories:
The amendment does not introduce a separate registration, licence or certification process. Its practical relevance depends on whether the ERDMP Regulations already cover an entity or installation. Businesses should therefore begin with an applicability review instead of assuming that every company connected with the petroleum sector has identical obligations.
The changes fall into two groups. The first group corrects terminology, numbering and drafting errors. The second group creates or strengthens operational duties involving medical readiness and the handling of major incidents.
| Compliance area | Change made in 2026 | Nature of change | Practical meaning |
| Emergency levels | “Level 1”, “Level 2” and “Level 3” become “Level I”, “Level II” and “Level III” | Editorial standardisation | Documents and labels should use consistent Roman numerals |
| Incident-controller wording | References to “Site” and “Chief” Incident Controller are corrected in Regulation 14.2.2 | Role clarification | Responsibility statements should match the correct incident-control role |
| Flow of information | “Form” is corrected to “from” | Typographical correction | No new operational duty is created |
| Siren code | The wording is revised to a wailing siren of two minutes, a one-minute gap and the same sequence repeated for three siren periods | Operational clarification | Emergency procedures, training material and drills should reflect the clarified pattern |
| Siren-code numbering | Existing clauses are renumbered | Editorial and cross-reference correction | Controlled copies must use updated clause references |
| Medical facilities | ERDMPs must include details of burn-treatment wards and the number of beds | Substantive disclosure requirement | Hospital and medical-resource information needs greater detail |
| Major-incident accountability | New Regulation 24(6) requires explanations, an internal committee, responsibility fixing, action and compensation | Substantive new process | Incident closure now requires a documented accountability trail |
| Recommendation tracking | New Regulation 24(7)(a) requires recommendations to be implemented across all locations in a time-bound manner | Substantive enterprise-wide requirement | Lessons cannot remain limited to the affected site |
| Board oversight and PNGRB reporting | The nominated director must support board deliberation and submission of meeting outcomes to PNGRB | Substantive governance requirement | Major incidents become a board-level compliance matter |
Changes that mainly correct the text
Use of Roman numerals instead of Arabic numerals for emergency levels, the fixing of “form” to “from”, and renumbering of siren code are improvements that will bring about consistency only. They should not, therefore, be viewed as completely new safety requirements.
Nonetheless, controlled documents are essential in emergency management. Use of out-of-date numbering or inaccurate titles can result in confusion during training or even a real emergency. Organizations need to correct cross-reference numbers in ERDMP manuals, SOPs, training presentations, control room instructions, and audits.
Changes that affect operations and governance
The refined siren sequence, further details on burn treatment, the procedure for accountability following the incident, compensation monitoring, and board reporting have compliance implications that require modifications of procedures, responsibility matrices, evidence files, and internal calendars beyond mere proofreading.
Revised Siren Code Requirement
Regulation 14.2.5.9 now describes the relevant warning sequence as:
The amendment also renumbers the following clauses. Sites should verify that siren charts, public-address instructions, control-room cards, induction material and mock-drill scripts all use the corrected wording and clause references. Where siren systems are automated, the configured sequence should be checked against the revised text and tested through the entity's established safety process.
Regulation 19 already requires ERDMPs to contain details of medical facilities. The amendment adds a specific requirement to include details of burn-treatment wards and the number of beds.
This change is important because a general list of nearby hospitals may no longer be enough. A useful and properly maintained ERDMP should identify which medical facilities can handle burn injuries and record their available bed capacity. The notification does not prescribe a fixed number of burn beds that every entity must arrange, nor does it create a new hospital-licensing process. It requires the relevant details to form part of the ERDMP.
As a practical control, entities should verify the information with the medical facility, record the verification date and assign responsibility for periodic updates. Bed capacity can change, so an old list may create a false sense of preparedness even if the ERDMP once contained accurate information.
The 2026 amendment does not reproduce the test for a major incident. That test comes from Regulation 23 of the principal regulations. Under the official consolidated text, an incident is treated as major if any one of the following occurs:
This classification is the gateway to the new Regulation 24(6) process. An entity should therefore document its classification decision promptly. If a major-incident trigger is met, the organisation should activate the investigation, accountability, governance and compensation workflow without waiting for an informal description of the incident to change.
Explanation for lapses or violations
For each major incident, the entity must submit an explanation for the lapses or violations that resulted in or caused the incident. This explanation is due within three months from submission of the final incident investigation report.
The requirement calls for more than a summary of what happened. The explanation should connect the investigation findings with the identified lapse or violation, corrective action and responsible level. The Gazette does not separately specify the format or recipient of this explanation in the inserted clause, so entities should align their filing approach with PNGRB's reporting practice and obtain clarification where necessary.
Internal committee to fix responsibility
The entity must form an internal committee within one month from submission of the final incident investigation report. The committee must determine responsibility for the incident and accountability for lapses or violations at appropriate levels, including senior officials of the entity.
The amendment does not prescribe the committee's exact composition, minimum number of members, independence criteria, quorum or meeting procedure. Each entity should establish these points through a defensible internal order while preserving fairness, relevant technical expertise and documentary integrity.
Internal committee report
The committee must submit its report to the concerned director of the entity within five months from the date on which the committee is constituted. This deadline runs from committee constitution, not from the incident date or the date of the final investigation report.
Disciplinary or administrative action
Where personnel, a contractor or an agency is found responsible, appropriate disciplinary or administrative action must be taken within three months from submission of the internal committee's report.
The regulation requires an accountability process; it does not permit the outcome to be predetermined. Entities should preserve the investigation record, contractual rights, service rules and principles of procedural fairness while meeting the compliance timeline.
Where death or permanent disability results from such an incident, the entity will be required to pay compensation as per the requirements of the statutes and the company's compensation policy. This amendment does not specify a standard amount for such compensation since the payment amount is dependent on several factors.
The footnote to the notification adds an immediate payment requirement: 25% of the total compensation amount must be released within one month from the date of the fatality or permanent disability.
The timeline table also gives nine months from submission of the final incident investigation report for action concerning Regulation 24(6)(d). The notification does not separately explain whether this nine-month entry refers to full disbursement, reporting of the action, submission of supporting evidence, or all of these. A prudent entity should not delay compensation while waiting for that question to arise. It should calculate the applicable amount promptly, release the required 25% within one month, plan the balance in accordance with law and policy, and document the action for board and PNGRB review.
New Regulation 24(7)(a) requires the entity to comply with all recommendations of the Incident Investigation Committee at all its locations within a time-bound manner and to take the measures needed to prevent recurrence.
The words “at all its locations” are significant. If an investigation reveals a control weakness that also exists elsewhere, the entity should not close the matter after correcting only the affected site. The recommendation should be screened across comparable facilities, equipment, processes and contractor arrangements. Each location should record whether the finding applies, what action was taken and how closure was verified.
This enterprise-wide approach may require coordination among operations, health and safety, engineering, legal, human resources, procurement, contractor management and senior leadership. It may also require changes to standard operating procedures, training, preventive maintenance, emergency equipment or supplier controls.
The nominated director must ensure that an Action Taken Report covers compliance with investigation recommendations, measures adopted to prevent recurrence and action taken under the new Regulation 24(6). The material is to accompany the final incident investigation report for deliberation by the entity's board of directors.
The minutes or outcome of that board meeting must then be submitted to PNGRB according to the prescribed timelines. This creates a governance trail connecting the incident, investigation findings, corrective action, accountability decisions, compensation and board oversight.
The board paper should be written for decision-making rather than mere information. It should show unresolved actions, overdue items, reasons for delay, responsible executives, compensation status and evidence that similar risks were checked at other locations.
| Compliance action | Starting point | Time allowed |
| Release 25% of total compensation for fatality or permanent disability | Date of fatality or permanent disability | One month |
| Constitute internal committee | Submission of final incident investigation report | One month |
| Constitute internal committee | Submission of final incident investigation report | Three months |
| Action on investigation recommendations across locations | Submission of final incident investigation report | Three months for the prescribed board/PNGRB reporting track |
| Internal committee submits report to concerned director | Submission of final incident investigation report | Five months |
| Take appropriate disciplinary or administrative action | Submission of internal committee report | Three months |
| Action relating to committee and disciplinary requirements | Submission of final incident investigation report | Ten months for the prescribed board/PNGRB reporting track |
| Action relating to compensation | Submission of final incident investigation report | Nine months for the prescribed board/PNGRB reporting track, subject to the separate 25% one-month requirement |
The table combines deadlines with different trigger events. It should not be converted into one simple countdown from the incident date. In particular, the one-month compensation payment runs from fatality or permanent disability, while several governance deadlines run from submission of the final incident investigation report.
| Responsible party | Main responsibility under the amended framework |
| Regulated entity | Maintain an updated ERDMP, follow the major-incident process, implement recommendations and address compensation |
| Regulated entity | Investigate the incident and produce recommendations under the existing framework |
| Newly constituted internal committee | Fix responsibility and accountability for lapses or violations |
| Concerned director | Receive the internal committee report |
| Nominated director | Ensure action-taken reporting, board deliberation and submission of meeting outcomes to PNGRB |
| Board of directors | Deliberate on the final investigation report and related action |
| Operations and HSE teams | Implement and verify corrective action across applicable locations |
| HR, legal and contractor-management teams | Support fair disciplinary, administrative, contractual and compensation action |
Internal departments are included here as practical owners, not as a replacement for the legal responsibility placed on the entity and its nominated director.
Stronger incident-closure discipline
An investigation report alone will no longer complete the accountability process for a major incident. Closure must be supported by explanations, committee findings, action against responsible parties where appropriate, compensation records, enterprise-wide corrective action and board-level review.
Greater demand for reliable evidence
Entities will need dated records showing when the final report was submitted, when the committee was constituted, when its report was delivered, what management action followed, when compensation was paid, which locations were reviewed and what the board discussed.
Wider organisational involvement
Major-incident compliance can no longer remain only with the site safety team. The amendment involves senior officials, directors, the board, HR, legal teams, finance, contractor-management functions and operations across multiple locations.
Cost and operational effects
Likely costs may arise from wider corrective-action programmes, ERDMP revisions, medical-resource verification, board reporting, contractor reviews, training and evidence management. The notification does not prescribe fixed implementation fees or a uniform compliance budget.
Maintain proof of compensation calculation and payment, including the 25% release where applicable.
Several points deserve careful internal treatment:
These points do not remove the obligations. They indicate where a regulated entity may need a documented legal interpretation or clarification from PNGRB while following the most conservative workable compliance approach.
The immediate priority is to separate document corrections from the new post-incident governance process. Editorial updates can be handled through document control, but accountability and compensation deadlines require executive ownership.
Management should first issue a controlled amendment to the ERDMP and connected procedures. It should then test whether the organisation can identify a major incident, capture the correct trigger date, constitute a committee, place the matter before the board, complete enterprise-wide action and produce evidence for PNGRB without relying on informal follow-up.
Entities should also run a tabletop exercise of the revised workflow. The exercise should test deadline ownership, record movement, board scheduling, compensation coordination and cross-location corrective action without changing the legal interpretation of the notification.
Corpseed can support businesses that need to translate the PNGRB ERDMP Amendment Regulations 2026 into a workable internal compliance system. Relevant regulatory compliance consulting services may include:
Professional support does not replace the entity's legal duties or guarantee a regulatory outcome. It can, however, help management identify gaps early, assign responsibility clearly and maintain a more reliable record of compliance.
Document Preview
Embedded reference document
Related
Explore more updates from the same department.