Risk Management Cycle or Procedure - ISO 31000 perspective

Risk Management Cycle or Procedure - ISO 31000 perspective

Vijay Reddy

Last updated March 14, 2017


ISO 31000 has introduced some important and more pertinent terms to the risk management standard and hence helps in better orchestration and implementation of the process across the organization to yield benefits whilst at the same time controlling the costs and the overall optimization of resources.

• Risk owner is defined as a “person or entity with the accountability and authority to manage a risk.” This definition will help the risk manager reinforce to management that risk ownership must be with management and not with the risk manager.
Risk appetite is an area that many organizations struggle with and whilst risk appetite, is not defined in ISO 31000 (it is in ISO Guide 73:2009), the Standard defines risk attitude as the organization’s “approach to assess and eventually pursue, retain, take or turn away from risk”.
• Risk management policy is also defined as a “statement of the overall intentions and direction of an organization related to risk management”.
• The risk management plan should specify the “approach, the management components and resources to be applied to the management of risk.” ISO has released ISO Guide 73:2009 Risk management - Vocabulary to provide further guidance with respect to generic terms and definitions relating to risk management to support consistency.

It contains some of the definitions now deleted from ISO 31000. The relationships between the various components of managing risks including the risk management framework is better highlighted and illustrated in ISO 31000 as shown in the figure below. risk cycle                
Mandate and commitment:
Risk management is not a one-off project; it is an ongoing activity requiring ongoing commitment. It must be mandated from the Board (or equivalent), implemented by senior management and supported by all levels of management and risk owners to be sustainable.

Design of framework for managing risk:
Like all good projects, processes and strategies, risk management processes must be well designed to support effective implementation. Defining the context of risk management framework, formulating a risk management policy, embedding processes into practice, assigning resources and determining responsibility are all key elements of designing an effective framework to manage risk. Well designed periodic reporting to stakeholders and effective communication mechanisms will support effective implementation. Implementing risk management: Once the framework has been designed, implementation is about putting the theory into practice and actually bringing the risk management framework to life. Specifically, this is about ensuring the risk management process is understood by risk owners (through good communication and training), and risk management activities actually take place (through risk assessments, risk workshops, internal controls etc) and decisions and business processes actually factor in risk thinking. Monitoring and review: Involves confirmation that the various risk management elements and activities are actually working effectively in line with expectations. Any gaps identified will need to be documented and re-mediated. Continual improvement: This is about continuing to “tweak” and enhance key elements of the risk management framework to either improve current processes and/or progress towards a more mature risk management framework. A highly committed organization will improve both its processes and mature over time.

Integrated Risk Management Principles, Framework and Processes

 integrated risk  

Risk Management Process – Explained

ISO 31000 recognizes the importance of feedback by way of two mechanisms. These are monitoring and review of performance and communication and consultation. Monitoring and review ensures that the organization monitors risk performance and learns from experience. Communication and consultation is presented in ISO 31000 as part of the risk management process, but it may also be considered to be part of the supporting framework. Reporting and disclosure are only very briefly mentioned in ISO 31000 and they are not included in the process shown in the diagram below. Also, the monitoring and review feedback activities set out in ISO 31000 do not explicitly mention the tasks of monitoring risk performance and reviewing the risk management framework. 

After considering numerous options and variants, ISO 31000:2009 largely adopted the same broad process as AS/NZS 4360:2004 for managing risk, as shown in the above diagram. While the process is essentially step like, in practice there is considerably iteration between the steps and between the continuously applied elements of communication and consultation and monitoring and review. Drawing a picture of this is obviously difficult and for this reason, the diagram used in the standard was deliberately not shown as a flow chart. Its purpose is to show the relationship between clauses of the standard that describe the process. The standard gives a set of general options to be considered when risk is treated.

The order of the list reflects preference. Importantly, the options deal with both risks that have downside and/or upside consequences. The options are:

a) Avoiding the risk by deciding not to start or continue with the activity that gives rise to the risk;
b) Taking or increasing the risk in order to pursue an opportunity;
c) Removing the risk source;
d) Changing the likelihood;
e) Changing the consequences;
f) Sharing the risk with another party or parties (including contracts and risk financing);
g) Retaining the risk by informed decision.

Source – ISO 31000 standard.


Preparing for PMP® Certification? Take this test to know where you stand!


PMP is a registered trademark of the Project Management Institute, Inc. 

Find our PMP® Certification Online Classroom training classes in top cities:

Name Date Place
PMP® Certification 6 Jan -21 Jan 2019, Weekdays batch Your City View Details
PMP® Certification 12 Jan -9 Feb 2019, Weekend batch New York City View Details
PMP® Certification 18 Jan -15 Feb 2019, Weekdays batch Boston View Details

About the Author

Vijay Reddy has several years of experience in delivering and managing IT Services, Software Development, Product and Production Support and has expertise in IT strategy consulting, Governance and risk management, IT security, cloud computing and implementation around large customer accounts, managing the delivery of large outsourced IT Service and software development engagements and in depth understanding of deal structures and delivery options and models. His experience has been across diverse industry segments – Banking, consumer products, Retail, Oil & Gas and Hospitality. Vijay is an APM Group International certified and accredited Project Management (Prince2®), Programme Management (MSP®) and IT Governance (COBIT5®) Trainer, Exams Proctor, Supervisor and Invigilator. He is also EXIN accredited trainer for ITIL – 41 credits (All Modules leading unto expert), ISO 20000, ISO 27002, Lean IT and Cloud Computing.

Recommended articles for you

Project Management Life Cycles - Evolution over the years


A Trainer's Perspective: In Conversation with Melanie Todd


Project Life Cycle vs. Product Life Cycle: CAPM Certificatio...