Id Description of Risk Impact on Change Date of Mitigation Actions Responsibility Cost Timeline Work (including any Project Review (Preventative or for mitigation for Breakdown identified (Identify Contingency) action(s) mitigation Structure ‘triggers’) of of consequences ) action(s) and (combined Grade Assessment Likelihood Assessment Seriousness Seriousness) Likelihood <n> <A <Describe the <Change <Date of <Specify planned <Specify who <Specify This is to “newspaper headline” style nature of the in Grade last mitigation is responsible timeframe indicate that statement. Also risk and the since last review> strategies: for undertaking for the identify relevant impact on the review> Preventative each mitigation identified triggers that may project if the risk (implement mitigation action(s) mitigation cause the risk to be is not mitigated immediately) action(s)> to be action has realised.> or managed> Contingency complete been (implement by> included in if/when risk the WBS occurs).> (workplan). 1 Steering Committee Lack of H H A NEW 15/02/06 Preventative: Project NA 15/03/06 Y unavailable. availability will Highlight Manager Identified triggers: stall progress strategic Steering (ie. delayed connection - link Committee decisions will Project meetings defer output Objective to repeatedly finalisation, relevant Agency rescheduled extend project strategic due to lack of timelines and objectives availability; staff resources Confirm 2006 Members do will be required meeting not attend for longer than schedule in despite prior anticipated) January confirmation of Confirm SC attendance. membership Widen representation (include other Agencies)
Id Description of Risk (including any identified ‘triggers’) Impact on Project (Identify consequences ) Assessment of Likelihood Assessment of Seriousness Grade (combined Likelihood and Seriousness) Change Date of Review Mitigation Actions (Preventative or Contingency) Responsibility for mitigation action(s) Cost Timeline for mitigation action(s) Work Breakdown Structure <n> <A “newspaper headline” style statement. Also identify relevant triggers that may cause the risk to be realised.> <Describe the nature of the risk and the impact on the project if the risk is not mitigated or managed> <Change in Grade since last review> <Date of last review> <Specify planned mitigation strategies: Preventative (implement immediately) Contingency (implement if/when risk occurs).> <Specify who is responsible for undertaking each mitigation action(s)> <Specify timeframe for mitigation action(s) to be by> This is to indicate that the identified mitigation action has been included in the WBS (workplan). 1 Steering Committee unavailable. Identified triggers: Steering Committee meetings repeatedly rescheduled due to lack of availability; Members do not attend despite prior confirmation of attendance. Lack of availability will stall progress (ie. delayed decisions will defer output finalisation, extend project timelines and staff resources will be required for longer than anticipated) H H A NEW 15/02/06 Preventative: Highlight strategic connection - link Project Objective to relevant Agency strategic objectives Confirm 2006 meeting schedule in January Confirm SC membership Widen representation (include other Agencies) Project Manager NA 15/03/06 Y complete
Risk-Register-Template-Tas.docx