EU Seveso III Compliance Guide for Major-Hazard Sites (2026)
By Dimitris Mitsios · Dimitris works at Tekmon, which pays for sponsored placements on this site. Disclosure · AI-assisted (how pages are made)
What Directive 2012/18/EU requires of lower-tier and upper-tier establishments, how competent authorities inspect them, and how to map each duty to the software that holds the evidence.

Quick Facts
- Directive: Directive 2012/18/EU (Seveso III), adopted 4 July 2012. Member States had to apply their national measures from 1 June 2015, when the Seveso II Directive was repealed (Articles 31 and 32).
- Scope: 11,059 establishments in the EU27 in 2022, with 43% on average upper-tier and 57% lower-tier, according to the Commission's implementation report for 2019–2022.
- Accident data: Member States report major accidents meeting the Annex VI criteria to the Commission within one year, through the eMARS database the Commission keeps for sharing lessons learned (Articles 18 and 21; eMARS).
What Seveso III actually requires (without the legalese)
Seveso III is a risk-based directive. It does not prescribe which incidents you must prevent; it requires you to identify, evaluate, prevent, mitigate and report major-accident hazards involving dangerous substances. The duties scale with how much hazardous inventory you hold:
| Duty | Lower-tier | Upper-tier |
|---|---|---|
| Notification to competent authority (Art. 7) | Yes | Yes |
| Major-accident prevention policy (MAPP) (Art. 8) | Yes, reviewed at least every five years | Yes, reviewed at least every five years |
| Safety management system (SMS) (Art. 8(5), Annex III) | Yes, or other proportionate means that take account of the Annex III principles | Yes, in accordance with Annex III |
| Safety report (Art. 10) | No | Yes, reviewed at least every five years |
| Internal emergency plan (Art. 12) | No | Yes |
| External emergency plan (Art. 12) | No | Drawn up by the designated authority; the operator supplies the information |
| Public information (Art. 14, Annex V) | Yes (Annex V, Part 1) | Yes (Parts 1 and 2) |
| Domino-effect cooperation (Art. 9) | Yes, where the competent authority identifies a domino group | Yes, where the competent authority identifies a domino group |
The directive's Annex I is aligned with the CLP Regulation (EC) No 1272/2008 (recital 9), and inspections should, where possible, be coordinated with those under other EU law, including the Industrial Emissions Directive 2010/75/EU (recital 26 and Article 20(9)). If your group reports under the CSRD, the same incident data can also feed ESRS E2 pollution disclosures (see below).
How competent authorities inspect
Article 20 requires Member States to ensure that competent authorities organise a system of inspections, sufficient for a planned and systematic examination of the technical, organisational and managerial systems in use at each establishment. Every establishment must be covered by an inspection plan. The period between two consecutive site visits must not exceed one year for upper-tier and three years for lower-tier establishments, unless the competent authority's inspection programme is based on a systematic appraisal of major-accident hazards. After each inspection, the authority has four months to communicate its conclusions and the actions needed.
Two parts of the directive are worth checking against your own records before an inspection:
- Ageing equipment. Annex III requires the SMS to address the management and control of risks associated with ageing equipment and corrosion, including an inventory of the establishment's equipment and a strategy for monitoring its condition.
- Lessons learned. For upper-tier sites, Annex II asks the safety report to review past accidents and incidents with the same substances and processes and the lessons learned from them. The Commission's eMARS database exists for that exchange of lessons learned (Article 21).
Mapping Seveso duties to software categories
The table below maps Seveso duties to software categories. See also our QHSE software for oil & gas and chemical-management workflows pages.
| Seveso requirement | Primary software category | Why it matters |
|---|---|---|
| MAPP & SMS documentation | QHSE / EHS platform | Single source of truth, versioned, auditable |
| Hazard identification (HAZID, HAZOP, LOPA) | Process safety management software | Structured studies, action tracking, revalidation |
| Management of Change (MoC) | MoC software | Pre-startup review, sign-offs, link to PHA |
| Permit to Work / hot work / confined space | Permit-to-work software | Energy isolation, conflict detection, audit trail |
| Mechanical integrity & inspections | EHS + CMMS integration (see asset integrity management software) | Risk-based inspection, NDT records |
| Incident reporting & investigation | Incident management software | Root cause; after a major accident, the information duties in Article 16 |
| Audits & internal verification | Audit & inspection software | ISO 45001 / ISO 14001 alignment, finding closure |
| Training & competence | LMS / EHS training module | Demonstrable competence per role |
| Contractor control | Contractor management software | Critical for upper-tier turnaround periods |
| Emergency planning | EHS + dedicated drill modules | Drill records, scenario library |
Building a defensible MAPP in 2026
Article 8 requires a written MAPP that is proportionate to the major-accident hazards and sets out the operator's overall aims and principles of action, the role and responsibility of management, and a commitment to continuously improving the control of major-accident hazards. The operator must review it at least every five years. Annex III lists what the SMS that implements it must address, from organisation and personnel to audit and review. To make the MAPP demonstrable, we suggest it includes:
- Stated principles (the actual policy) signed by the operator's accountable person.
- Roles and responsibilities linked to a competence matrix.
- Risk control standards referencing CCPS / EI / ISO 45001 elements (ISO 45001:2018 is the published edition; a draft revision entered a Draft International Standard ballot in June 2026, according to ISO/TC 283).
- KPIs with both lagging (Tier 1 / Tier 2 process safety events as defined in API RP 754) and leading indicators (overdue MoCs, overdue PHA actions, inspection backlog, training compliance). Annex III notes that the monitoring procedures could include safety performance indicators.
- Review cadence with documented management review minutes.
For every platform you evaluate, ask the vendor to build these KPIs into one Seveso dashboard from your own MoC, PHA-action and inspection records during the demo.
Corrected 2026-09-23: an earlier version of this section named Tekmon, a commercial partner of this site, first as an example of QHSE software for Seveso KPI dashboards without disclosure or supporting evidence; that has been removed.
Worked example: tracing one modification through Article 11
This is a constructed example, not an observed case. A site plans to raise the stored quantity of a flammable liquid in an existing tank.
| Step | What should happen | Where the record sits |
|---|---|---|
| Change request | The MoC screen asks whether the inventory or process changes | MoC record |
| Hazard review | The study is updated for the new quantity | PHA or HAZOP file, with new actions |
| Article 11 check | Someone decides whether the change could have significant consequences for major-accident hazards or move the site between tiers | MoC decision, signed |
| Document review | The notification, MAPP, SMS and safety report are reviewed and updated if needed | Document system, with revision history |
| Authority | The competent authority is informed of the details in advance | Correspondence log |
| Start-up | Pre-start-up review and training confirmed | PSSR and training records |
If any row is held only in someone's inbox, that is the gap to fix before an inspection.
What an inspection looks at, and what to keep ready
Article 20(2) describes four things an inspection should be sufficient to check. The right-hand column is our suggestion for evidence to keep ready, not a legal list.
| Article 20(2) aim | Evidence worth having ready |
|---|---|
| The operator can demonstrate measures to prevent major accidents | MAPP, SMS procedures, MoC and PHA records, inspection and maintenance history |
| Means exist to limit consequences on and off site | Internal emergency plan, drill records, information supplied for the external plan |
| The safety report reflects conditions at the establishment | A comparison of the report with current inventory, plant and procedures |
| Information has been supplied to the public (Article 14) | A copy of what was supplied, with its date and next review |
Safety report essentials (upper-tier)
Annex II of Seveso III lists the minimum content of the safety report, and Article 10(5) requires the operator to review it at least every five years, and also after a major accident and whenever new facts or knowledge justify it. In summary, Annex II asks for:
- Information on the management system and organisation of the establishment, covering the Annex III elements. This is where MoC, PtW, training and audit evidence is pulled in.
- A description of the establishment and its environment, its installations and its dangerous substances, including neighbouring establishments and developments that could cause or increase a major accident or domino effects.
- Identification and analysis of major-accident scenarios and their causes: operational, external (such as domino effects) and natural, for example earthquakes or floods.
- An assessment of the extent and severity of the consequences, with maps, images or equivalent descriptions, and a review of past accidents and incidents with the same substances and processes.
- Protection and intervention measures to limit the consequences of a major accident.
A practical tip: if your safety report still references manual paper logs for permits, MoC or incidents, plan to move them into a digital system before the next five-yearly review.
How Seveso connects to CSRD and ESRS E2
If your group reports under the CSRD and pollution is a material topic, ESRS E2 applies. In the simplified standards that apply to financial years beginning on or after 1 January 2027, disclosure requirement E2-4 asks for the amounts of material emissions of pollutants to air, water and soil from your own operations, including those due to environmental accidents (Delegated Regulation (EU) 2026/1563). For Seveso sites, the same incident record can feed both:
- Process safety event in your incident system →
- Information to the competent authority after a major accident, under Seveso III Article 16 (not every process safety event is a major accident) →
- Disclosure in the sustainability statement under ESRS E2, where pollution is material.
Keeping these in one platform means both reports start from the same record. See the CSRD readiness checklist in our ESRS implementation guide for the sustainability-side workflow and our double materiality guide for the assessment methodology.
A practical 90-day plan for upper-tier sites
Days 0–30 — Diagnose
- Pull last 3 years of incidents, MoCs and PHA actions into one view.
- Map every SMS element to a system of record. Identify missing approvals, revisions, access controls and retention evidence in each system, regardless of its product name.
- Run a self-assessment against the 20 elements of the CCPS Guidelines for Risk Based Process Safety.
Days 31–60 — Consolidate
- Pick one platform for MoC + PHA action tracking + incident if you don't already have one. Shortlist using our PSM software guide.
- Move permit-to-work to a digital system if still on paper. Start with hot work and confined space.
- Stand up a Seveso KPI dashboard (Tier 1, Tier 2, MoC backlog, PHA action backlog, audit findings).
Days 61–90 — Evidence
- Re-issue MAPP with KPI links and competence matrix references.
- Run a tabletop exercise that exercises the digital incident-to-regulator notification path.
- Schedule the next safety report revalidation with your competent authority and pre-share the dashboard.
Common pitfalls
- Treating Seveso as a documentation exercise. It is a management system that happens to produce documents.
- Disconnected MoC and PHA. Article 11 requires the operator to review, and where necessary update, the notification, MAPP, SMS and safety report before a modification that could have significant consequences for major-accident hazards. A change that does not trigger that review leaves them out of date.
- Permit-to-work in PDF. Conflicts between isolations are hard to see when each permit sits in a separate file.
- No leading indicators. Lagging indicators show failures only after they happen, while Annex III asks for ongoing assessment of compliance with the objectives of the MAPP and SMS.
- Contractor blind spots. Annex III requires the SMS to cover the involvement of subcontracted personnel who are important to safety, and the hazards of subcontracted activities. Use a contractor management system.
Evaluate a Seveso workflow
Start with process safety management, management of change and permit-to-work scope. Ask each vendor to connect one plant change to its hazard study, procedure revision, training and pre-startup authorization. Retrieve the underlying records after rejecting a proposed closure.
Record which steps are native, configured, integrated or outside the proposal. This site does not rank vendors on Seveso workflows; the QHSE Software Capability Map 2026 shows which capability statements the researched profiles document, and the security, trial and offline evidence study covers attestations and trials. For terms, see the glossary entry on process safety management. A module name does not establish coverage of the full SMS. Use the linked comparison’s published inclusion rule and the same evidence checks for every qualifying product. Sponsored placements are additional and labelled; commercial status does not determine organic eligibility.
Final word
Seveso III asks for more than written policies. Article 8(5) requires the MAPP to be implemented through a safety management system in accordance with Annex III (lower-tier establishments may use other proportionate means), and Annex III requires that system's performance to be monitored. The test is whether your systems can prove, on demand, that those policies are operating. This guide suggests consolidating MoC, PHA actions, PtW and incidents into a small number of integrated platforms, and exposing them through a Seveso KPI dashboard that your inspector can read quickly.
FAQ
Is Seveso the same as COMAH? No. In the UK, the Control of Major Accident Hazards Regulations 2015 are the national rules; they use similar upper-tier and lower-tier terms but are a separate text to check on their own. Our COMAH 2026 guide covers the UK rules.
How often must the safety report be reviewed? At least every five years, and after a major accident (Article 10(5)); the MAPP is reviewed at least every five years too (Article 8(4)).
Sources
- EUR-Lex: Directive 2012/18/EU on the control of major-accident hazards involving dangerous substances (Seveso III)
- European Commission: COM(2025) 508, report on the implementation of Directive 2012/18/EU for 2019–2022
- European Commission, Joint Research Centre: eMARS, the Major Accident Reporting System
- EUR-Lex: Commission Delegated Regulation (EU) 2026/1563 amending the ESRS
- API: RP 754, Process Safety Performance Indicators, fourth edition (August 2026)
- CCPS: Guidelines for Risk Based Process Safety
Corrected 23 September 2026: claims about named vendors that no source we could check supported were removed or reworded to match each product's researched profile.
Corrected 23 September 2026: statistics without a primary source were sourced, labelled as examples or removed, and the regulations cited now link to their official texts.
Reviewed 4 October 2026: articles, statistics and ESRS E2-4 wording rechecked; Article 16 wording narrowed to major accidents; worked example, inspection checklist and FAQ added.
Founder of The QHSE Standard; product marketing at Tekmon
Dimitris Mitsios is the founder of The QHSE Standard and works in product marketing at Tekmon. His professional focus includes software positioning, digital workflows and user adoption.
Dimitris works at Tekmon, which pays for sponsored placements on this site.
Researched and drafted with AI assistance and published under the author's editorial responsibility (how pages are made). Found an error? Send a correction with a source.
Related software
Browse all platforms →Ordered by how closely our sources document this process, not by quality. Sponsored placements are labelled. How lists are ordered
- Process Safety
Haz360
Process Safety
Read the profile - Process Safety
Safeti
Process Safety
Read the profile - Process Safety
BowTieXP
Process Safety
Read the profile

