Managing risk in projects - Application guidelines (IEC 62198:2025)

IEC 62198:2025 provides principles and generic guidelines on managing risk in projects. In particular it describes a systematic approach to managing risk in projects based on ISO 31000. Guidance is provided on the principles for managing risk in projects, the framework and organizational requirements for implementing risk management, and the process for conducting effective risk management. This third edition cancels and replaces the second edition, published in 2013, and constitutes a technical revision.
This edition includes the following technical changes with respect to the previous edition:
a) now aligned with ISO 31000, Risk management - Guidelines and ISO 21502, Project, programme and portfolio management - Guidance on project management.
b) the principles and generic guidelines on managing risk in projects have been updated to take into account developments in risk management and leadership, with particular reference to implementing risk management within the broad scope of project management envisaged by ISO 21502, including project-related oversight and direction by the sponsoring organization.

Risikomanagement für Projekte - Anwendungsleitfaden (IEC 62198:2025)

Gestion des risques liés à un projet - Lignes directrices pour l'application (IEC 62198:2025)

L'IEC 62198:2025 fournit des principes et des lignes directrices génériques sur la gestion des risques dans les projets. Elle décrit en particulier une approche systématique de la gestion des risques dans les projets, basée sur l'ISO 31000. Elle fournit des lignes directrices sur les principes de gestion des risques dans les projets, le cadre et les exigences organisationnelles pour la mise en œuvre de la gestion des risques, et le processus pour mener une gestion efficace des risques. Cette troisième édition annule et remplace la deuxième édition, publiée en 2013, et constitue une révision technique.
Cette édition inclut les modifications techniques suivantes par rapport à l'édition précédente :
a) alignement avec l'ISO 31000, Management du risque - Lignes directrices et l'ISO 21502, Management de projets, programmes et portefeuilles - Recommandations sur le management de projets.
b) mise à jour des principes et lignes directrices génériques concernant le management du risque dans les projets, afin de tenir compte des développements en matière de management du risque et de leadership, avec une référence particulière à la mise en œuvre du management du risque dans le domaine d’application étendu du management de projet envisagé par l’ISO 21502, comprenant la supervision et la direction liées au projet proposées par l’organisme commanditaire.

Obvladovanje tveganja v projektih - Smernice za uporabo (IEC 62198:2025)

Ta dokument podaja načela in splošne smernice za obvladovanje tveganja v projektih. Zlasti opisuje sistematičen pristop k obvladovanju tveganja v projektih, ki temelji na standardu ISO 31000.
Smernice navajajo načela za obvladovanje tveganja v projektih, okvir in organizacijske zahteve za izvajanje obvladovanja tveganja ter postopek za učinkovito obvladovanje tveganja.

General Information

Status
Published
Public Enquiry End Date
22-Feb-2024
Publication Date
10-Sep-2025
Technical Committee
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
03-Sep-2025
Due Date
08-Nov-2025
Completion Date
11-Sep-2025

Relations

Standard
SIST EN IEC 62198:2025 - BARVE
English language
48 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)


SLOVENSKI STANDARD
01-oktober-2025
Nadomešča:
SIST EN 62198:2014
Obvladovanje tveganja v projektih - Smernice za uporabo (IEC 62198:2025)
Managing risk in projects - Application guidelines (IEC 62198:2025)
Risikomanagement für Projekte - Anwendungsleitfaden (IEC 62198:2025)
Gestion des risques liés à un projet - Lignes directrices pour l'application (IEC
62198:2025)
Ta slovenski standard je istoveten z: EN IEC 62198:2025
ICS:
03.100.01 Organizacija in vodenje Company organization and
podjetja na splošno management in general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD EN IEC 62198

NORME EUROPÉENNE
EUROPÄISCHE NORM August 2025
ICS 03.100.01 Supersedes EN 62198:2014
English Version
Managing risk in projects - Application guidelines
(IEC 62198:2025)
Gestion des risques liés à un projet - Lignes directrices pour Risikomanagement für Projekte - Anwendungsleitfaden
l'application (IEC 62198:2025)
(IEC 62198:2025)
This European Standard was approved by CENELEC on 2025-07-30. CENELEC members are bound to comply with the CEN/CENELEC
Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC
Management Centre or to any CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the
same status as the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the
Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Türkiye and the United Kingdom.

European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2025 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN IEC 62198:2025 E
European foreword
The text of document 56/2058/FDIS, future edition 3 of IEC 62198, prepared by TC 56
"Dependability" was submitted to the IEC-CENELEC parallel vote and approved by
CENELEC as EN IEC 62198:2025.
The following dates are fixed:
• latest date by which the document has to be implemented at (dop) 2026-08-31
national level by publication of an identical national
standard or by endorsement
• latest date by which the national standards conflicting with the (dow) 2028-08-31
document have to be withdrawn
This document supersedes EN 62198:2014 and all of its amendments and corrigenda (if
any).
Attention is drawn to the possibility that some of the elements of this document may be the
subject of patent rights. CENELEC shall not be held responsible for identifying any or all
such patent rights.
Any feedback and questions on this document should be directed to the users’ national
committee. A complete listing of these bodies can be found on the CENELEC website.
Endorsement notice
The text of the International Standard IEC 62198:2025 was approved by CENELEC as a
European Standard without any modification.
In the official version, for Bibliography, the following notes have to be added for the standard
indicated:
IEC 31010 NOTE Approved as EN IEC 31010
IEC 60812 NOTE Approved as EN IEC 60812
IEC 61882 NOTE Approved as EN 61882
Annex A
(normative)
Normative references to international publications
with their corresponding European publications
The following documents are referred to in the text in such a way that some or all of their
content constitutes requirements of this document. For dated references, only the edition
cited applies. For undated references, the latest edition of the referenced document
(including any amendments) applies.
NOTE 1  Where an International Publication has been modified by common modifications, indicated
by (mod), the relevant EN/HD applies.
NOTE 2  Up-to-date information on the latest versions of the European Standards listed in this annex
is available here: www.cencenelec.eu.
Publication Year Title EN/HD Year
ISO 31000 - Risk management - Guidelines - -

IEC 62198 ®
Edition 3.0 2025-06
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Managing risk in projects – Application guidelines

Gestion des risques liés à un projet – Lignes directrices pour l'application

ICS 03.100.01  ISBN 978-2-8327-0501-8

IEC 62198:2025-06(en-fr)
IEC 62198:2025 © IEC 2025
CONTENTS
FOREWORD . 3
INTRODUCTION . 5
1 Scope . 6
2 Normative references . 6
3 Terms and definitions . 6
4 Managing risks in projects . 9
5 Principles . 11
6 Project risk management framework . 12
6.1 General . 12
6.2 Leadership and commitment . 13
6.3 Design of the framework for managing project risk . 14
6.3.1 Understanding the project and its context . 14
6.3.2 Establishing the project risk management policy . 14
6.3.3 Accountability . 15
6.3.4 Integration into project management processes . 16
6.3.5 Resources . 16
6.3.6 Establishing internal project communication and reporting mechanisms . 16
6.3.7 Establishing external project communication and reporting mechanisms . 17
6.4 Implementing project risk management . 17
6.4.1 Implementing the framework for managing project risk. 17
6.4.2 Implementing the project risk management process . 17
6.5 Monitoring and review of the project risk management framework . 18
6.6 Continual improvement of the project risk management framework . 18
7 Project risk management process . 18
7.1 General . 18
7.2 The project risk management plan . 19
7.3 Communication and consultation. 20
7.4 Scope, context and criteria . 21
7.4.1 General . 21
7.4.2 Defining the scope . 21
7.4.3 Establishing the external context . 21
7.4.4 Establishing the internal context . 22
7.4.5 Establishing the context of the project risk management process . 22
7.4.6 Defining risk criteria . 23
7.4.7 Key elements . 23
7.5 Risk assessment . 24
7.5.1 General . 24
7.5.2 Risk identification . 24
7.5.3 Risk analysis . 25
7.5.4 Risk evaluation . 26
7.6 Risk treatment . 26
7.6.1 General . 26
7.6.2 Selection of risk treatment options . 27
7.6.3 Risk treatment plans . 28
7.7 Monitoring and review . 28
7.7.1 General . 28
IEC 62198:2025 © IEC 2025
7.7.2 Management meetings . 29
7.8 Recording and reporting the project risk management process . 29
7.8.1 Reporting . 29
7.8.2 Records and data storage . 30
7.8.3 The project risk register . 30
Annex A (informative) Examples . 32
A.1 General . 32
A.2 Project risk management process . 32
A.2.1 Stakeholder analysis (see 7.3) . 32
A.2.2 External and internal context (see 7.4.3 and 7.4.4) . 33
A.2.3 Risk management context (see 7.4.5) . 35
A.2.4 Risk criteria (see 7.4.6) . 36
A.2.5 Key elements (see 7.4.7) . 37
A.2.6 Risk analysis (see 7.5.3) . 38
A.2.7 Risk evaluation (see 7.5.4) . 41
A.2.8 Risk treatment (see 7.6) . 42
A.2.9 Risk register (see 7.5.2 and 7.8.3) . 42
Bibliography . 44

Figure 1 – Relationship between the components of the framework for managing risk,
adapted from ISO 31000 . 13
Figure 2 – Project risk management process, adapted from ISO 31000 . 19
Figure A.1 – Risk management scope for an open pit mine project . 36
Figure A.2 – Distribution of cost estimate using simulation (example only) . 41

Table 1 – Typical phases in a project . 10
Table A.1 – Stakeholders for a government project . 32
Table A.2 – Stakeholders and objectives for a ship upgrade . 33
Table A.3 – Stakeholders and communication needs for a civil engineering project . 33
Table A.4 – External context for an energy project . 34
Table A.5 – Internal context for a private sector infrastructure project . 35
Table A.6 – Example risk management context for a power enhancement project . 35
Table A.7 – Criteria for a high-technology project . 36
Table A.8 – Key elements for a communications system project . 37
Table A.9 – Key elements for establishing a new health service organization . 38
Table A.10 – Example consequence scale . 39
Table A.11 – Example likelihood scale . 39
Table A.12 – Example of a matrix for determining the level of risk . 40
Table A.13 – Example of priorities for attention . 42
Table A.14 – Example of a treatment options worksheet . 42
Table A.15 – Simple risk register structure . 43
Table A.16 – Example scale for control effectiveness (CE) . 43

IEC 62198:2025 © IEC 2025
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
Managing risk in projects -
Application guidelines
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international
co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and
in addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports,
Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC Publication(s)”). Their
preparation is entrusted to technical committees; any IEC National Committee interested in the subject dealt with
may participate in this preparatory work. International, governmental and non-governmental organizations liaising
with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for
Standardization (ISO) in accordance with conditions determined by agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence between
any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) IEC draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). IEC takes no position concerning the evidence, validity or applicability of any claimed patent rights in
respect thereof. As of the date of publication of this document, IEC had not received notice of (a) patent(s), which
may be required to implement this document. However, implementers are cautioned that this may not represent
the latest information, which may be obtained from the patent database available at https://patents.iec.ch. IEC
shall not be held responsible for identifying any or all such patent rights.
IEC 62198 has been prepared by IEC technical committee 56: Dependability. It is an
International Standard.
This third edition cancels and replaces the second edition, published in 2013, and constitutes
a technical revision.
IEC 62198:2025 © IEC 2025
This edition includes the following technical changes with respect to the previous edition:
a) now aligned with ISO 31000, Risk management – Guidelines and ISO 21502, Project,
programme and portfolio management – Guidance on project management [1] .
b) the principles and generic guidelines on managing risk in projects have been updated to
take into account developments in risk management and leadership, with particular
reference to implementing risk management within the broad scope of project management
envisaged by ISO 21502, including project-related oversight and direction by the sponsoring
organization.
The text of this International Standard is based on the following documents:
Draft Report on voting
56/2058/FDIS 56/2081/RVD
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this International Standard is English.
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/publications.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under webstore.iec.ch in the data related to the
specific document. At this date, the document will be
• reconfirmed,
• withdrawn, or
• revised.
___________
Numbers in square brackets refer to the Bibliography.
IEC 62198:2025 © IEC 2025
INTRODUCTION
Every project involves risk. Project risks can be related to the objectives of the project itself or
to the objectives of the assets, products or services the project creates. This document provides
guidelines for managing risks in a project in a systematic, effective, efficient and consistent
way.
Risk management includes the coordinated activities to direct and control an organization with
regard to risk. ISO 31000, Risk management – Guidelines, describes:
a) the principles for effective risk management,
b) the framework that provides the foundations and organizational arrangements for designing,
implementing, monitoring, reviewing and continually improving risk management throughout
an organization, and
c) a process for managing risk that can be applied to all types of risk in any organization.
This document shows how those general principles and guidelines apply to managing
uncertainty, threats and opportunities in projects. It applies to all kinds of projects and project
management processes. When applying this document in conjunction with flexible or agile
project management processes, the project’s objectives, requirements and specifications are
expected to evolve as the project progresses. The application of this document can be adjusted
in these circumstances.
This document is relevant to individuals and organizations concerned with any or all phases in
the life cycle of projects. It can also be applied to sub-projects and to sets of inter-related
projects and programmes.
The application of this document can be tailored to each specific project by taking into
consideration factors such as context, objectives and requirements. Therefore, it is not in the
scope of this document to impose a certification system for risk management practitioners.
The guidance provided in this document is not intended to override existing industry-specific
standards, although the guidance can be helpful in such instances.

IEC 62198:2025 © IEC 2025
1 Scope
This document provides principles and generic guidelines on managing risk in projects. In
particular it describes a systematic approach to managing risk in projects based on ISO 31000.
Guidance is provided on the principles for managing risk in projects, the framework and
organizational requirements for implementing risk management, and the process for conducting
effective risk management.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies.
For undated references, the latest edition of the referenced document (including any
amendments) applies.
ISO 31000, Risk management – Guidelines
3 Terms and definitions
For the purposes of this document, the following terms or definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following
addresses:
• IEC Electropedia: available at https://www.electropedia.org/
• ISO Online browsing platform: available at https://www.iso.org/obp
3.1
event
occurrence or change of a particular set of circumstances
Note 1 to entry: An event can have one or more occurrences, and can have several causes and several
consequences.
Note 2 to entry: An event can also be something that is expected which does not happen, or something that is not
expected which does happen.
Note 3 to entry: An event can be a risk source.
[SOURCE: ISO 31000:2018, 3.5]
3.2
opportunity
combination of circumstances expected to be favourable to objectives
Note 1 to entry: An opportunity is a positive situation in which gain is likely and over which one has a fair level of
control.
Note 2 to entry: An opportunity to one party may pose a threat to another.
Note 3 to entry: Taking or not taking an opportunity are both sources of risk.
[SOURCE: IEC 31010:2019, 3.2 [2]]
IEC 62198:2025 © IEC 2025
3.3
project
temporary endeavour to achieve one or more defined objectives
Note 1 to entry: A project generally consists of a set of coordinated and controlled activities (3.1) with start and
finish dates, conforming to specific requirements, including the constraints of time, cost and resources.
Note 2 to entry: An individual project can form part of a larger project structure and generally has a defined start
and finish date.
Note 3 to entry: In some projects the objectives and scope are updated and the product or service characteristics
defined progressively as the project proceeds.
Note 4 to entry: The output of a project can be one or several units of product or service.
Note 5 to entry: The project’s organization is normally temporary and established for the lifetime of the project.
Note 6 to entry: The complexity of the interactions among project activities is not necessarily related to the project
size.
[SOURCE: ISO 21502:2020, 3.20, modified – The Notes have been taken from
ISO 10006:2017, 3.3. [3]]
3.4
project management
coordinated activities to direct and control the accomplishment of agreed objectives
[SOURCE: ISO 21502:2020, 3.24]
3.5
project plan
documented description of the technical and management baselines to be followed for a project
[SOURCE: ISO 21506:2024, 3.68 [4]]
3.6
risk
effect of uncertainty on objectives
Note 1 to entry: An effect is a deviation from the expected. It can be positive, negative or both, and can address,
create or result in opportunities and threats.
Note 2 to entry: Objectives can have different aspects and categories, and can be applied at different levels.
Note 3 to entry: Risk is usually expressed in terms of risk sources, potential events, their consequences and their
likelihood.
[SOURCE: ISO 31000:2018, 3.1]
3.7
risk management
coordinated activities to direct and control an organization with regard to risk
[SOURCE: ISO 31000:2018, 3.2]
IEC 62198:2025 © IEC 2025
3.8
risk management framework
set of components that provide the foundations and organizational arrangements for designing,
implementing, monitoring, reviewing and continually improving risk management throughout the
organization
Note 1 to entry: The foundations include the policy, objectives, mandate and commitment to manage risk (3.6).
Note 2 to entry: The organizational arrangements include plans, relationships, accountabilities, resources,
processes and activities.
Note 3 to entry: The risk management framework is embedded within the organization's overall strategic and
operational policies and practices.
[SOURCE: ISO Guide 73:2009, 2.1.1 [5]]
3.9
risk management policy
statement of the overall intentions and direction of an organization related to risk management
[SOURCE: ISO 31073:2022, 3.2.2 [6]]
3.10
risk management plan
scheme within the risk management framework specifying the approach, the management
components and resources to be applied to the management of risk
Note 1 to entry: Management components typically include procedures, practices, assignment of responsibilities,
sequence and timing of activities.
Note 2 to entry: The risk management plan can be applied to a particular product, process and project (3.3), and
part or whole of the organization.
[SOURCE: ISO 31073:2022, 3.2.3]
3.11
risk management process
systematic application of management policies, procedures and practices to the activities of
communicating, consulting, establishing the context, and identifying, analysing, evaluating,
treating, monitoring and reviewing risk
[SOURCE: ISO 31073:2022, 3.3.1]
IEC 62198:2025 © IEC 2025
3.12
risk treatment
process to modify risk
Note 1 to entry: Risk treatment can involve:
– avoiding the risk by deciding not to start or continue with the activity that gives rise to the risk,
– taking or increasing risk in order to pursue an opportunity,
– removing the risk source,
– changing the likelihood,
– changing the consequences,
– sharing the risk with another party or parties (including contracts and risk financing), and
– retaining the risk by informed decision.
Note 2 to entry: Risk treatments that deal with negative consequences are sometimes referred to as “risk
mitigation”, “risk elimination”, “risk prevention” and “risk reduction”.
Note 3 to entry: Risk treatment can create new risks or modify existing risks.
[SOURCE: ISO 31073:2022, 3.3.32]
3.13
threat
potential source of danger, harm, or other undesirable outcome
Note 1 to entry: A threat is a negative situation in which loss is likely and over which one has relatively little control.
Note 2 to entry: A threat to one party may pose an opportunity to another.
[SOURCE: IEC 31010:2019, 3.5]
3.14
uncertainty
state, even partial, of deficiency of information related to understanding or knowledge
Note 1 to entry: In some cases, uncertainty can be related to the organization’s context as well as to its objectives.
Note 2 to entry: Uncertainty is the root source of risk, namely any kind of “deficiency of information” that matters in
relation to objectives (and objectives, in turn, relate to all relevant interested parties’ needs and expectations).
[SOURCE: ISO 31073:2022, 3.1.3]
3.15
work breakdown structure
decomposition of the defined scope of a project or programme into progressively lower levels
consisting of elements of work
[SOURCE: ISO 21502:2020, 3.29]
4 Managing risks in projects
Every project involves uncertainties that can lead to risks. These uncertainties can relate to the
objectives of the project itself (for example to complete the project within a specified time frame
and budget) or to the requirements of the assets, products or services that the project creates
(for example for a product to be safe, dependable and environmentally sustainable).
IEC 62198:2025 © IEC 2025
The consequences that could arise from uncertainty in a project can be beneficial as well as
detrimental, so project risk management is directed not only to avoiding or reacting to problems
but also to identifying and capturing opportunities. Taking account of project risks contributes
to better decisions, better project outcomes and increased value for stakeholders.
This document is relevant to individuals and organizations concerned with any or all phases in
the life cycle of projects. To obtain maximum benefit, risk management activities should be
initiated at the outset when considering a project, and continued through subsequent phases
(see Table 1). However, project risk management can be initiated successfully at any point in
the life cycle. It is scalable, so it can be used with both small and large projects and with
individual phases of projects. It can also be applied to sub-projects and to sets of inter-related
projects and programmes.
Risk management should be integrated with project management activities and processes. It
should not be separate or an afterthought.
A typical set of project phases and their characteristics is shown in Table 1. In practice, there
can be iteration between the phases.
Table 1 – Typical phases in a project
Phase 1 Phase 2 Phase 3 Phase 4 Additional activities
Phase label Identify Pre- Feasibility Deliver Operate and Abandon
feasibility maintain
Concept Design and Implement Dispose
Select develop
Install and
commission
Purpose Appraising Selecting Defining the Delivering Realising the Closure:
opportunities: options: project: the project: benefits: ensure safe
determine identify and finalize the produce an evaluate the and
whether the appraise scope and operating project acceptable
project could project detail of the asset, outcome to closure or
be development preferred product or ensure disposal
worthwhile options and option service, performance
and its select the consistent
alignment preferred one with the
with business agreed scope
strategy
Focus of risk Strategic Risk-based Design and Project Operation Disposal and
management threats and options delivery delivery, test and rehabilitation
activities opportunities selection strategy and handover maintenance
NOTE The additional activities in the two right-hand columns correspond to phases in the life cycle of an asset,
product or service that is created by a project. They are not project phases, but they are included here because
they are often considered by project managers as they proceed through phases 1 to 4.

It is common for each phase to culminate in a decision point (sometimes called a gate) at which
executive approval is provided for progression and entry to the next phase. Information on risks
and risk management is an important part of the information provided to executives to support
their decisions. Information on risks and controls in each phase should also be shared with
other teams managing the next phase of the project.
All executives and people in the organizations associated with a project have a role in managing
the risks associated with their decisions and activities. This document is intended for use by:
a) project directors and project managers who are part of an organization that owns or
commissions the project or that will own or manage the assets, products or services the
project will create,
b) members of project teams who are responsible for significant sub-projects, groups of
activities or packages of work, and the associated risks,
IEC 62198:2025 © IEC 2025
c) risk managers and members of risk management groups, internal or external to the
organization, who are responsible for overseeing, supporting or administering risk
management activities in the project,
d) project owners or sponsors who are responsible for ensuring that the sponsoring
organization’s business interests in the project are maintained and that the expected
outcomes and benefits are realized,
e) executives who have to approve the progression of the project at each decision point and
the expenditure, resource allocation and objectives associated with the subsequent phase,
f) peer reviewers who provide assurance to the executives who make approval decisions that
the supporting information is comprehensive, accurate, valid and reliable,
g) project directors and project managers who are part of a contracting organization, or a sub-
contractor or supplier, that bids for or delivers some or all of the project and its associated
assets, products or services,
h) financiers and insurers who provide financial and related support for the project,
i) regulators of project-related activities or the assets, products or services that can be created
by the project, and
j) other stakeholders, including sub-contractors, suppliers, users or beneficiaries of the
assets, products or services that can be created by the project, and other parties who could
have an interest in the project and its outcomes (including the wider public).
5 Principles
For project risk management to be effective, efficient and consistent, an organization should at
all levels comply with the principles shown below.
a) Risk management creates and protects value.
Risk management contributes to demonstrable progress towards organizational objectives
and improvement of performance and quality in projects and the assets, products and
services they create. The objectives shall be understood clearly by all parties.
c) Risk management is part of decision-making.
Risk management helps decision makers make informed choices about the project, within
each stage of its life, prioritize actions and distinguish among alternative courses of action.
This implies that all decisions should consider risk.
d) Risk management is an integral part of all organizational processes associated with a
project.
Risk management is not a stand-alone activity that is separate from the main activities and
processes of the project or the organization. Risk management is part of the responsibilities
of project managers and of staff at all levels. It is an integral part of all the organizational
processes associated with a project, including strategic project and investment planning,
project management and management of project change.
e) Risk management explicitly addresses uncertainty.
All people in the organization should explicitly take account of uncertainty, the nature of that
uncertainty, and how it can be addressed, particularly in critical processes.
f) Risk management is systematic, structured and timely.
A systematic, timely and structured approach to risk management contributes to consistent,
comparable and reliable project decisions and their successful application, to the efficiency
and effectiveness of project management processes and to the benefits the project aims to
deliver. A sound framework for risk management should be applied from the beginning of a
project.
IEC 62198:2025 © IEC 2025
g) Risk management is based on the best available information.
The inputs to the process of managing risk in a project are based on information sources
such as technical and engineering analyses, physical site and equipment inspections, test
results and progress reports, supplemented with historical data, experience, stakeholder
feedback, forecasts and expert judgement. However, those involved with managing risks in
a project should inform themselves of, and should take into account, any limitations of the
data or modelling used, uncertainty in the information available or the possibility of
divergence among experts.
h) Risk management is tailored.
Risk management activities are adapted to the kind of project, the project’s external and
internal context and those of the organizations involved, and the level of uncertainty and
complexity associated with the project. The level of risk management effort is proportionate
to the situation.
i) Risk management takes human and cultural factors into account.
The capabilities, perceptions and intentions of people and organizations that can facilitate
or hinder achievement of the project’s objectives are taken into account when managing
risk, as are social and organizational changes brought about by the project.
j) Risk management is transparent and inclusive.
Appropriate and timely involvement of stakeholders and, in particular, decision makers at
all levels of the organization, ensures that risk management remains relevant and up to
date. Involvement also allows stakeholders to be properly represented and to have their
views taken into account in determining risk criteria.
k) Risk management is dynamic, iterative and responsive to change.
As a project progresses and as related external and internal events occur, context and
knowledge change, monitoring and review take place, new risks emerge, some risks change,
and other risks disappear. Therefore, risk management activities in a project help project
decision-makers to continually identify, understand and respond to change.
l) Risk management facilitates continual improvement of the organization.
Organizations should develop and implement strategies to improve the maturity of their
project risk management alongside all other aspects of their organizational processes.
6 Project risk management framework
6.1 General
Project risk management processes should be integrated with project management processes.
The project management framework – the way in which the project management process will
be organized, structured and controlled – should provide the foundations and arrangements
that will embed project risk management throughout the project through all phases, at all levels
and across all the organizations involved. The success of project risk management will depend
in part on the effectiveness of the integration.
The project risk management framework assists in managing project risks. It does this through
consistent and effective project risk management processes (see Clause 7), applied at varying
levels and within the specific context of the project. The framework and processes ensure that
information about project risk is adequately reported and used as a basis for governance,
decision making and accountability at all relevant organizational and project levels.
Organizations often adopt a common risk management framework, aligned with their corporate
risk management framework, and they customize it in a similar way in many projects.
This Clause 6 describes the necessary components of the framework for managing project risk
and the way in which they interrelate in an iterative manner. Figure 1 shows the risk
management framework and process in ISO 31000 applied to managing risk in projects.
IEC 62198:2025 © IEC 2025
This framework is not intended to prescribe a management system, but rather to assist the
organizations involved in a project to integrate project risk management into the overall project
management framework. Therefore, organizations should adapt the components of the
framework to their specific needs and the specific project requirements.
If an organization's existing project management practices and processes include components
of risk management, or if the organization has already adopted a formal project risk
management process for particular types of projects, risks or situations, then these should be
critically reviewed and assessed against this document to determine their adequacy and
effectiveness.
Figure 1 – Relationship between the components of the framework
for managing risk, adapted from ISO 31000
6.2 Leadership and commitment
The introduction of risk management and ensuring its on-going effectiveness require sustained
commitment by management of all the organizations involved in the project, including owners
and key contractors. Strategic and rigorous planning is also necessary to achieve commitment
at all levels. Management of owner, contractor and major sub-contractor or supplier
organizations should:
a) define and endorse a common risk management policy for the project,
b) ensure that the cultures of the participating organizations and the project risk management
policy are aligned as far as possible,
c) align project risk management objectives and criteria with the objectives and strategies of
the organizations involved, and particularly those of the owner organization,
d) determine project risk management performance indicators that align with performance
indicators for the project itself and the organizations involved,
e) inform employees about any legal, regul
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

Loading comments...