Risk Register

Risk Register For Project: Great Things 0

Project Manager: A. Allen 0
Version Date: YYYY-MM-DD 0
0
Risk P T $K PxT P x $K
Approval delays 30% 15 $75 4.5 $23
Team turnover 20% 40 $200 8 $40

Resource availability 30% 30 $150 9 $45

Vendor issues 40% 20 $100 8 $40
Procurement delays 50% 20 $100 10 $50
Requirements changes 40% 50 $250 20 $100
“Problems at end” 70% 30 $150 21 $105
Development problems 60% 40 $200 24 $120
Risk budget: 104.5 $523

Use

CODING: White cells are for entry, blue for results.

RISKS (MORE): If you insert rows for more risks, make sure you copy the formulas from an existing row
RISKS (LESS): You can delete rows if not needed.
BEFORE & AFTER: For larger projects you sometimes include both the P, T, $, PxT, Px$ columns from bef
there are separate tabs duplicating the spreadsheet for before and after, which keeps the final one after re

Refer to the Deeply Practical Project Management book or online course for more information on use of this documen

Page 1
 Risk Register

Page 2
 Risk Register

0
Owner Trigger Response Plan
B. Baker Org change. Avoid: resolve in planning!
Mitigate: empower, trust ...

Mitigate: Func Mgr commitments

Mitigate: Weekly status
Avoid: resolve in planning!
Mitigate: user review tool ...
Mitigate: pilot, phase ...
Mitigate: Resources, track ...

ormulas from an existing row into the PxT and PX$ columns.

$, PxT, Px$ columns from before response planning and after response planning in this spreadsheet. This makes the spre
ich keeps the final one after response planning simpler.

Page 3
 Risk Register

0
Secondary Risks Residual Risks Resolution Date

ning in this spreadsheet. This makes the spreadsheet more complex however, so sometimes instead

Page 4