Your name goes here
Project Document
Risk Register
Version: ##
Sample Template
Project
Date
Executive Summary:
<Provide an assessment of current project [the computing environment] and areas
of concern. Document the most serious risks. Describe the areas of most concern
based on the information above and the probable events that might occur. Do a risk
audit and discuss the potential problems. You should add a summary assessment on
the current state of the project vs. the ideal state and make recommendations.>
SE 477 Winter 2017
Risk Register
Page 1 of 10
Your name goes here
Risk Number:
##
Risk Rating:
<High –
low>
Risk Owner:
<Name>
Description:
<Risk description>
Project
Objective(s)
Impacted:
<Identify project objective—cost, time, scope, quality—impacted by this risk>
Risk
Probability:
Potential
Triggers or
Precursors:
Potential
Mitigation
Potential
Responses:
Root Causes (if
identified):
<0.0-1.0>
Risk Impact:

<List potential triggers or precursors that might indicate the risk event is
about to occur>

<List any ways that the likelihood of the risk can be reduced or its impact
on the project reduced>

<List potential responses should the risk event occur. These do not need to
be detailed risk response plans but should provide sufficient detail to
clearly describe how the risk event will be handled>

<List root causes of the risk, if possible>
SE 477 Winter 2017
Risk Register
Page 2 of 10
Your name goes here
Risk Number:
##
Risk Rating:
<High –
low>
Risk Owner:
<Name>
Description:
<Risk description>
Project
Objective(s)
Impacted:
<Identify project objective—cost, time, scope, quality—impacted by this risk>
Risk
Probability:
Potential
Triggers or
Precursors:
Potential
Mitigation
Potential
Responses:
Root Causes (if
identified):
<0.0-1.0>
Risk Impact:

<List potential triggers or precursors that might indicate the risk event is
about to occur>

<List any ways that the likelihood of the risk can be reduced or its impact
on the project reduced>

<List potential responses should the risk event occur. These do not need to
be detailed risk response plans but should provide sufficient detail to
clearly describe how the risk event will be handled>

<List root causes of the risk, if possible>
SE 477 Winter 2017
Risk Register
Page 3 of 10
Your name goes here
Risk Number:
##
Risk Rating:
<High –
low>
Risk Owner:
<Name>
Description:
<Risk description>
Project
Objective(s)
Impacted:
<Identify project objective—cost, time, scope, quality—impacted by this risk>
Risk
Probability:
Potential
Triggers or
Precursors:
Potential
Mitigation
Potential
Responses:
Root Causes (if
identified):
<0.0-1.0>
Risk Impact:

<List potential triggers or precursors that might indicate the risk event is
about to occur>

<List any ways that the likelihood of the risk can be reduced or its impact
on the project reduced>

<List potential responses should the risk event occur. These do not need to
be detailed risk response plans but should provide sufficient detail to
clearly describe how the risk event will be handled>

<List root causes of the risk, if possible>
SE 477 Winter 2017
Risk Register
Page 4 of 10
Your name goes here
Risk Number:
##
Risk Rating:
<High –
low>
Risk Owner:
<Name>
Description:
<Risk description>
Project
Objective(s)
Impacted:
<Identify project objective—cost, time, scope, quality—impacted by this risk>
Risk
Probability:
Potential
Triggers or
Precursors:
Potential
Mitigation
Potential
Responses:
Root Causes (if
identified):
<0.0-1.0>
Risk Impact:

<List potential triggers or precursors that might indicate the risk event is
about to occur>

<List any ways that the likelihood of the risk can be reduced or its impact
on the project reduced>

<List potential responses should the risk event occur. These do not need to
be detailed risk response plans but should provide sufficient detail to
clearly describe how the risk event will be handled>

<List root causes of the risk, if possible>
SE 477 Winter 2017
Risk Register
Page 5 of 10
Your name goes here
Risk Number:
##
Risk Rating:
<High –
low>
Risk Owner:
<Name>
Description:
<Risk description>
Project
Objective(s)
Impacted:
<Identify project objective—cost, time, scope, quality—impacted by this risk>
Risk
Probability:
Potential
Triggers or
Precursors:
Potential
Mitigation
Potential
Responses:
Root Causes (if
identified):
<0.0-1.0>
Risk Impact:

<List potential triggers or precursors that might indicate the risk event is
about to occur>

<List any ways that the likelihood of the risk can be reduced or its impact
on the project reduced>

<List potential responses should the risk event occur. These do not need to
be detailed risk response plans but should provide sufficient detail to
clearly describe how the risk event will be handled>

<List root causes of the risk, if possible>
SE 477 Winter 2017
Risk Register
Page 6 of 10
Your name goes here
Risk Number:
##
Risk Rating:
<High –
low>
Risk Owner:
<Name>
Description:
<Risk description>
Project
Objective(s)
Impacted:
<Identify project objective—cost, time, scope, quality—impacted by this risk>
Risk
Probability:
Potential
Triggers or
Precursors:
Potential
Mitigation
Potential
Responses:
Root Causes (if
identified):
<0.0-1.0>
Risk Impact:

<List potential triggers or precursors that might indicate the risk event is
about to occur>

<List any ways that the likelihood of the risk can be reduced or its impact
on the project reduced>

<List potential responses should the risk event occur. These do not need to
be detailed risk response plans but should provide sufficient detail to
clearly describe how the risk event will be handled>

<List root causes of the risk, if possible>
SE 477 Winter 2017
Risk Register
Page 7 of 10
Your name goes here
Risk Number:
##
Risk Rating:
<High –
low>
Risk Owner:
<Name>
Description:
<Risk description>
Project
Objective(s)
Impacted:
<Identify project objective—cost, time, scope, quality—impacted by this risk>
Risk
Probability:
Potential
Triggers or
Precursors:
Potential
Mitigation
Potential
Responses:
Root Causes (if
identified):
<0.0-1.0>
Risk Impact:

<List potential triggers or precursors that might indicate the risk event is
about to occur>

<List any ways that the likelihood of the risk can be reduced or its impact
on the project reduced>

<List potential responses should the risk event occur. These do not need to
be detailed risk response plans but should provide sufficient detail to
clearly describe how the risk event will be handled>

<List root causes of the risk, if possible>
SE 477 Winter 2017
Risk Register
Page 8 of 10
Your name goes here
Risk Number:
##
Risk Rating:
<High –
low>
Risk Owner:
<Name>
Description:
<Risk description>
Project
Objective(s)
Impacted:
<Identify project objective—cost, time, scope, quality—impacted by this risk>
Risk
Probability:
Potential
Triggers or
Precursors:
Potential
Mitigation
Potential
Responses:
Root Causes (if
identified):
<0.0-1.0>
Risk Impact:

<List potential triggers or precursors that might indicate the risk event is
about to occur>

<List any ways that the likelihood of the risk can be reduced or its impact
on the project reduced>

<List potential responses should the risk event occur. These do not need to
be detailed risk response plans but should provide sufficient detail to
clearly describe how the risk event will be handled>

<List root causes of the risk, if possible>
SE 477 Winter 2017
Risk Register
Page 9 of 10
Your name goes here
Cause-and-Effect Diagram
SE 477 Spring 2015
Risk Register
Page 10 of 10