1. Tools and Techniques
1.1. [Refer to any risk management systems or tools to be used, and note any preference for techniques which may be used for each step in the risk management procedure]
2. Introduction
2.1. [State the purpose, objectives and scope, and identify who is responsible for the strategy]
3. Risk Management Procedure
3.1. The procedure should cover activities such as:
3.2. Identify
3.3. Assess
3.4. Plan
3.5. Implement
3.6. Communicate
4. Records
4.1. [Define the composition and format of the Risk Register and any other risk records to be used by the project]
5. Reporting
5.1. [Describe any risk management reports that are to be produced, including their purpose, timing and recipients]
6. Timing of Risk Management Activities
6.1. [State when formal risk management activities are to be undertaken - for example, at end stage assessments]
7. Roles and Responsibilities
7.1. [Define the roles and responsibilities for risk management activities]
8. Scales
8.1. [Define the scales for estimating probability and impact for the project to ensure that the scales for cost and time (for instance) are relevant to the cost and timeframe of the project. These may be shown in the form of probability impact grids giving the criteria for each level within the scale, e.g. for ‘very high’, ‘high’, ‘medium’, ‘low’ and ‘very low’]
8.2. [Define the risk response categories to be used, which themselves depend on whether a risk is a perceived threat or an opportunity]
9. Proximity
9.1. [Provide guidance on how proximity for risk events is to be assessed. Typical proximity categories will be: imminent, within the stage, within the project, beyond the project]
10. Risk Categories
10.1. [Define the risk categories to be used (if at all). These may be derived from a risk breakdown structure or prompt list.]
11. Risk Response Categories
12. Early-warning Indicators
12.1. [Define indicators to be used to track critical aspects of the project so that if certain predefined levels are reached, corrective action will be triggered.]
13. Risk Tolerance
13.1. [Define the threshold levels of risk exposure, which, when exceeded, require the risk to be escalated to the next level of management. (For example, a project-level risk tolerance could be set as any risk that, should it occur, would result in loss of trading. Such risks would need to be escalated to corporate or programme management).]
14. Risk Budget
14.1. [Describe whether a risk budget is to be established and, if so, how it will be used]
15. How to use this template
15.1. How to share this template with your team
15.1.1. Send an email
15.1.1.1. 1. Click Share this map
15.1.1.2. 2. Select Invite People
15.1.1.3. 3. Write a message
15.1.1.4. 4. Click Invite
15.1.2. Send a link
15.1.2.1. 1. Click Share this map
15.1.2.2. 2. Tick Link to share
15.1.2.3. 3. Copy the link to share it
15.1.3. Export
15.1.3.1. 1. Click down arrow, bottom right
15.1.3.2. 2. Select the export option you want
15.2. How to complete this template
15.2.1. Complete the sections in square brackets
15.2.1.1. [....]
15.2.2. Read these sections for help on the template
15.2.2.1. Purpose
15.2.2.2. Advice
15.2.3. Navigate using the links in Contents
15.2.3.1. Contents
15.3. Attribution
15.3.1. Copyright © AXELOS Limited 2009. All rights reserved. Material is reproduced with the permission of AXELOS
15.4. Get this template here
16. Overview
16.1. Purpose
16.1.1. A Risk Management Strategy describes the specific risk management techniques and standards to be applied and the responsibilities for achieving an effective risk management procedure.
16.2. Contents
16.2.1. The Risk Management Strategy should cover the following topics.
16.2.2. Introduction
16.2.3. Risk Management Procedure
16.2.4. Tools and Techniques
16.2.5. Records
16.2.6. Reporting
16.2.7. Timing of Risk Management Activities
16.2.8. Roles and Responsibilities
16.2.9. Scales
16.2.10. Proximity
16.2.11. Risk Categories
16.2.12. Risk Response Categories
16.2.13. Early-warning Indicators
16.2.14. Risk Tolerance
16.2.15. Risk Budget
16.3. Advice
16.3.1. The Risk Management Strategy is derived from the: Project Brief; Business Case; The corporate or programme management’s risk management guide, strategy or policy.
16.3.2. A Risk Management Strategy can take a number of formats, including: Stand-alone document or a section in the Project Initiation Document; Entry in a project management tool.
16.3.3. The following quality criteria should be observed:
16.3.3.1. Responsibilities are clear and understood by both customer and supplier
16.3.3.2. The risk management procedure is clearly documented and can be understood by all parties
16.3.3.3. Scales, expected value and proximity definitions are clear and unambiguous
16.3.3.4. The chosen scales are appropriate for the level of control required
16.3.3.5. Risk reporting requirements are fully defined.
17. Document information
17.1. Project Name
17.1.1. [name]
17.2. Date
17.2.1. [date]
17.3. Release
17.3.1. Draft/Final
17.4. Author
17.4.1. [author]
17.5. Owner
17.5.1. [owner]
17.6. Client
17.6.1. [client]
17.7. Document Number
17.7.1. [number]
17.8. Revision, Approvals & Distribution
17.8.1. Revision History
17.8.1.1. Revision # [....]
17.8.1.1.1. Revision Date
17.8.1.1.2. Previous Revision Date
17.8.1.1.3. Summary of Changes
17.8.1.1.4. Changes Marked
17.8.1.2. Revision # [....]
17.8.1.2.1. Revision Date
17.8.1.2.2. Previous Revision Date
17.8.1.2.3. Summary of Changes
17.8.1.2.4. Changes Marked
17.8.1.3. Revision # [....]
17.8.1.3.1. Revision Date
17.8.1.3.2. Previous Revision Date
17.8.1.3.3. Summary of Changes
17.8.1.3.4. Changes Marked
17.8.1.4. Date of next revision:
17.8.1.4.1. [....]
17.8.2. Approvals
17.8.2.1. Approval # [....]
17.8.2.1.1. Name
17.8.2.1.2. Signature
17.8.2.1.3. Title
17.8.2.1.4. Date of Issue
17.8.2.1.5. Version
17.8.2.2. Approval # [....]
17.8.2.2.1. Name
17.8.2.2.2. Signature
17.8.2.2.3. Title
17.8.2.2.4. Date of Issue
17.8.2.2.5. Version
17.8.2.3. Approval # [....]
17.8.2.3.1. Name
17.8.2.3.2. Signature
17.8.2.3.3. Title
17.8.2.3.4. Date of Issue
17.8.2.3.5. Version
17.8.3. Distribution
17.8.3.1. Distribution # [....]
17.8.3.1.1. Name
17.8.3.1.2. Title
17.8.3.1.3. Date of issue
17.8.3.1.4. Version
17.8.3.2. Distribution # [....]
17.8.3.2.1. Name
17.8.3.2.2. Title
17.8.3.2.3. Date of issue
17.8.3.2.4. Version