risk-register

Document Sample
risk-register Powered By Docstoc
					Risk Register Template
IT & Project Management

1. BASIC RISK INFORMATION
Risk Number       Risk Description / Risk           Responsible        Date Reported
                  Event Statement                                      day-month-year


Provide a unique      A risk event statement        Name or title of   Enter the date
identifier for risk   states (i) what might         team member        the risk was first
                      happen in the future and      responsible for    reported
                      (ii) its possible impact on   risk
                      the project. "Weather" is
                      not a risk event
                      statement. "Bad weather
                      may delay the project" is
                      a risk event statement.



Example               Concrete prices may           Materials                  12/1/2005
R1                    increase, causing the         Acquisitions
                      project to go over budget     Manager
Example R 2   Key supplier may lose a    Project Manager   12/15/2006
              pending lawsuit and go
              out of business, creating
              the need to find a new
              supplier, which will cause
              schedule delays
                    2. RISK ASSESSMENT INFORMATION
Last Update         Impact       Impact      Probability           Timeline       Status of
day-month-year      H/M/L        Description H/M/L                 N/M/F          Response
                                                                                  N / P / PE /
                                                                                  EE
Enter the date      Enter here H   List the         Enter here H   Enter here N   Enter here N
the risk (not the   (High); M      specific         (High)         (Near-term);   (No Plan); P
entire log) was     (Medium); or   impact the       M (Medium)     M (Medium-     (Plan but not
updated             L (Low)        risk could       or L (Low)     term); or F    enacted); PE
                    according to   have on the      according to   (Far-term)     (Plan enacted
                    impact         project          probability    according to   but
                    definitions    schedule,        definitions    timeline       effectiveness
                                   budget,                         definitions    not yet
                                   scope, and                                     known); EE
                                   quality. Other                                 (Plan enacted
                                   impacts can                                    and effective)
                                   also be listed
        1/12/2006 M                The cost of      H              M              PE
                                   the concrete
                                   could be as
                                   much as 50%
                                   more
                                   expensive
                                   than budgeted
                                   for, resulting
                                   in an overall
                                   cost overrun
                                   of 15% on the
                                   project
1/12/2006 H   Finding a new N/A   N/A   N/A
              supplier,
              negotiating
              contract, and
              getting re-
              started is
              estimated to
              cause a 6-
              month delay
3. RISK RESPONSE INFORMATION
Completed Actions Planned Future              Risk Status
                  Actions                     Open / Closed /
                                              Moved to Issue

List, by date, all     List, by date, what    State if the risk is
actions taken to       will be done in the    open (still might
respond to the risk.   future to respond to   happen and still has
This does not          the risk               to be managed);
include assessing                             closed (has passed
the risk                                      or has been
                                              successfully
                                              mitigated); moved
                                              to issue (risk has
                                              happened)


10-Jan-2006: Asked     12-Jan-2006:          Open
concrete supplier to   Investigating cost of
guarantee a price;     purchasing
request denied         materials now and
                       storing them until
                       needed
12-Jan-2006: Met    N/A   Moved to issue
with supplier to
discuss options
15-Jan-2006:
Spoke with other
suppliers regarding
availability
20-Jan-2006:
Prepared
contingency plan
and RFP in case
supplier goes
bankrupt
25-March-2006:
Moved risk to issue
process -- supplier
lost lawsuit and
declared bankruptcy

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:2
posted:10/23/2011
language:English
pages:6